Microsoft · Content governance + documentation
Turning guidance intoa self-service content system.
How recurring questions, stakeholder input, and research shaped a practical hub for style, accessibility, legal, process, and onboarding guidance.
The problem
Having guidance did not make it easy to use
Microsoft’s official style guidance was comprehensive, but people still needed quick answers in the middle of daily work: Which term should I use? How should this be capitalized? What does accessibility require? Where is the approved legal language? What is the team’s process?
The answer often existed, but it could be difficult to locate or apply quickly. The content-design team became a frequent point of contact for questions from new team members and cross-functional partners.
We needed a practical working layer that connected everyday questions to authoritative guidance without trying to replace Microsoft’s official sources.
Evidence boundary: This case documents the system created and the decisions behind it. It does not claim a measured reduction in support requests or onboarding time.
My ownership
Discovery through maintenance
I led development of the Content Hub. I gathered recurring questions from the content-design team, opened a stakeholder feedback channel, partnered with researchers to validate common needs, prioritized topics, designed the information structure, and curated practical guidance, examples, checklists, and source links.
I also designed a repeatable content pattern so future owners could add and update guidance without rebuilding the resource.
Decision 01
Start with repeated work
I began with the content-design team’s day-to-day experience: the questions that arrived most often, the official guidance that felt too dense for a quick decision, and the “quick hits” that could prevent repeated explanation.
Then I opened discovery to product, marketing, engineering, and design partners. Their questions exposed needs the content team could easily underestimate. Capitalization, acronyms, and jargon, for example, were routine decisions for writers but recurring friction points for non-writers.
Discovery flow
Decision 02
Balance demand with risk
I partnered with user researchers to review permitted support-thread language and frequency patterns. That work helped distinguish an isolated request from a recurring need.
Frequency was not the only criterion. Accessibility requirements and legal-language warnings deserved visibility because the consequences of an incorrect decision could be high, even when the question appeared less often.
Decision 03
Curate the answer—do not duplicate the source
The hub did not reproduce Microsoft’s official style guides. I extracted the guidance people needed most often, translated it into a practical first answer, and linked readers back to the authoritative source for deeper detail.
Complete policy, background, exceptions, and related guidance.
Direct answer, short explanation, examples, risk warning, checklist, and source link.
Representative rendering
Write accessible link text
Use a link label that describes the destination or action. Avoid generic labels such as “Click here” or “Learn more” when a more specific phrase is available.
- Name the page, file, or action.
- Make the label understandable out of context.
- Keep neighboring links distinct from one another.
Artifact note: The rendering above was created for this portfolio. It demonstrates the documented content pattern; it is not a screenshot of Microsoft’s internal interface.
Information architecture
Organize guidance around decisions people make
I grouped material into clear, durable categories so people could recognize where a question belonged and future owners could extend the system without redesigning it.
A consistent page pattern and clear ownership model supported maintenance. Internal documentation loses value quickly when source links, update expectations, and responsibility are unclear.
Delivered output
Documentation designed as infrastructure
- Stakeholder feedback channel and topic inventory
- Research-informed prioritization of recurring needs
- Information architecture for style, terminology, accessibility, legal, process, and onboarding guidance
- Curated answers, examples, checklists, and authoritative source links
- Reusable content pattern for new guidance
- Structure designed for continued maintenance
Having guidance is not the same as making it usable.
With additional measurement, I would track what people searched for, where they failed to find an answer, which source links they followed, and which recurring questions still reached the content-design team.