New liaison model #6065
New liaison model #6065
Conversation
austin-schaefer
added
content
|
Hi @austin-schaefer 👋 Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes). |
Gatsby Cloud Build Reportdocs-website-develop 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 17m |
x8a
moved this from Hero to triage
to In progress/being reviewed (by Hero or any TW)
in Docs PRs and Issues
| @@ -76,7 +76,7 @@ To update the alias, type the following into the chat box: `!hero set @YOUR_SLAC | |||
| Common questions and requests include: | |||
|
|
|||
| - **Questions about docs content**. Answer the question if you know it, or reach out to other writers if it's an area you're not familiar with. Encourage the requestor to edit the docs or submit an issue wherever possible. | |||
| - **Triage requests for docs support**. If it's a project that already has a [liaison](/docs/agile-handbook/sprint-mechanics/liaisonships/) attached, connect the requestor to the appropriate writer. If it's a project without exisitng writing support, connect them to a tech docs team manager to have a scoping conversation. | |||
| - **Triage requests for docs support**. If it's a project that already has a [liaison](/docs/agile-handbook/sprint-mechanics/liaisonships/) attached, connect the requestor to the appropriate writer. If it's a project an active liaison or point person, connect them to a tech docs team manager to have a scoping conversation. | |||
There was a problem hiding this comment.
Do you mean a project without* an active liaison/point person, i.e., if no such liaison exists, connecting with the tech docs team manager is the next step?
| * Project requires significant information architecture work. | ||
| * Project will produce enough docs that consistency across those docs will be hard to achieve without a centralized editor. | ||
| * Project SMEs would benefit from a consistent "face" of the tech writing team. | ||
| No matter what support level we assign to an area, the liaison is never the only person to edit! We all share ownership of the site, and you should expect that other writers will edit and contribute to your areas of expertise. |
There was a problem hiding this comment.
This was a great change. I remember reading this during the early weeks and found this classification system a little daunting/another thing to remember/follow. (Which isn't to say that was the intent, but I find being more rule-based can create a work culture of prescriptivism rather than experimentation + creativity.)
Making these designations more generalized as "roles" actually shifts the perspective: rather than remembering and following different rules for categorizing a project, we have a focused area to start at, learn, and improve. Feels more rooted.
src/content/docs/agile-handbook/sprint-mechanics/liaisonships.mdx
Outdated
Show resolved
Hide resolved
urbiz-nr
removed this from In progress/being reviewed (by Hero or any TW)
in Docs PRs and Issues
Update agile handbook to reflect new liaison model.
Requesting @Broseberg as reviewer for her perspective as manager, and @akristen for her "beginner's mind" perspective as someone newer to the team.