Migration
One path for two merging products
- Situation
- As Microsoft Sentinel moved into the Microsoft Defender portal, the guidance customers needed was all gated, scattered, and confusing.
- What I did
- I consolidated information from many stakeholder teams into one article that customers could follow and took it public with the product preview.
- Outcome
- The customer experience team lead cited it as the most requested content from their customers during the initial migration period.
Incident response
Customer guidance after a major supply-chain attack
- Situation
- After a widely publicized nation-state attack, customers needed clear steps to understand their exposure and mitigate it.
- What I did
- I was asked to write the article and owned it through months of review by legal, product, and threat-intelligence teams. It had to pull guidance from across Microsoft Security services into one piece that covered both prevention and recovery. I worked with security researchers and legal reviewers who rarely deal with documentation. The topic was sensitive, and every statement had to hold up.
- Outcome
- Published guidance that customers around the world used to respond.
Acquisition
Documentation through an acquisition
- Situation
- A newly acquired Operational Technology security product had to fit into its new parent company’s platform and documentation standards, with a unique set of customer audiences and needs.
- What I did
- As the sole documentation owner, I restructured the enterprise product docs, created an online catalog for supported hardware devices, rebuilt API and CLI references, and created self-service deployment procedures for user personas who were accustomed to more handholding. In this role, I also served as a design partner on the Microsoft Learn PDF refresh effort, arguing for the offline PDFs our users relied on.
- Outcome
- A fully integrated set of content that both met unique customer needs and clicked into the enterprise standards and processes.
Documentation revamp
AlgoSec: from PDFs to an online help system
- Situation
- AlgoSec’s documentation was managed in a legacy system and delivered to customers as PDFs. The company was growing, and it was still working out what dedicated technical writing could contribute and whether its docs should be public.
- What I did
- As the sole full-time writer, I owned the docs end-to-end and managed subcontractors for the migration and lower-priority work. I moved the content into MadCap Flare and published an online help system with product and version selectors, and made the case for publishing the docs publicly. I kept the internal knowledge base current, tied the docs’ branding and language to the marketing materials so customers recognized what they had bought, and set up Jira-based content tracking and Google Analytics reporting.
- Outcome
- Support efforts were smoother, and by the time I left, technical content had a recognized place in the company, with a brand and direction of its own for my successors. The online help’s main structure, selectors included, is still recognizable years later.