Led an Office-wide effort to make developer content clearer, more useful, easier to find, and more responsive to customer intent.
Context
Office developer content was technically accurate, but it was often formal, dense, and difficult to scan. Customer feedback repeatedly asked for plain English, shorter explanations, clearer examples, and faster answers. Teams were also publishing across multiple platforms with limited insight into customer intent, search behavior, and whether people could find what they needed.
The challenge was not simply to adjust word choice. Microsoft needed a modern approach to technical content that combined customer intent, usability, findability, concise writing, empathy, SEO, and ongoing measurement.
Role
I led the Voice for Developers workstream as part of a broader Office-wide Discovery and Voice initiative. I represented the developer-documentation organization on the cross-functional leadership team and translated the broader voice strategy for highly technical audiences. I led the pilot, created examples and training materials, recruited early adopters, coached writers and editors, and helped turn an experiment into a broader organizational practice.
- Leading the developer-content pilot and representing developer documentation on the cross-functional leadership team
- Creating before-and-after examples, training materials, workshops, and reusable review checklists
- Recruiting and coaching early adopters across writing and editorial teams
- Connecting content decisions to customer intent, search behavior, usability, and measurement
- Presenting the approach to other Microsoft developer-content organizations
- Supporting continuing education, peer review, and alignment with broader Microsoft voice guidance
Approach
We treated voice as part of the entire content-development process, not as a final editorial pass. Writers began by identifying customer intent, understanding the task, and reviewing available feedback and search data. They then reshaped content so the main answer was easier to find, scan, understand, and act on.
The core principles emphasized active voice, concise explanations, everyday language where appropriate, precise technical terminology where necessary, stronger titles and headings, and empathy without becoming overly casual.
The rollout combined pilot content, before-and-after examples, one-on-one coaching, workshops, peer discussion, training waves, and reusable checklists. An early pilot involved 12 writers and editors who produced 31 examples for wider adoption.
A study with 1,600 participants compared formal, empathetic, and intentionally overdone versions of the same content. The empathetic version performed better in ease of understanding, usefulness, friendliness, credibility, clarity, and perceived depth—including among developers and IT professionals.
Outcomes
The initiative established shared modern-voice principles for Office developer content and a practical model for applying them.
Writers and editors gained clearer guidance, concrete examples, training, and a repeatable way to review technical content through the customer’s eyes.
The program expanded beyond the initial pilot, influenced training across the Office content organization, and was shared with other Microsoft developer-documentation teams.
Voice became less about sounding friendlier and more about making technical guidance useful, findable, concise, and easier to act on.
Lessons Learned
Content standards do not create change on their own. People need evidence, examples, opportunities to practice, peer feedback, and a clear connection between new behaviors and customer outcomes.
Technical accuracy and approachable writing are not opposing goals. Clearer content can remain precise while reducing friction for new and experienced developers.
Meaningful content transformation requires both craft and change leadership. The larger impact came from creating a system that helped an organization plan, write, review, and measure content differently.