I’m a Senior Technical Writer at Okta, documenting enterprise software.
I write documentation for complex products and design the systems around it: how a documentation set is structured, how work flows from engineering to publication, and how AI can help without taking judgment away from the people accountable for accuracy.
I came to technical writing from marketing and communications, which is why I treat documentation like a product: I start with who it’s for, what they need, and what gets in their way.
What I do
- AI-enabled workflows. I design AI workflows for research and for keeping documentation current, with a person reviewing every change. Writers across the team have adopted them.
- Documentation architecture. I design information architecture and navigation that help readers find what they need, from a single product to an entire documentation site.
- Launch documentation. I lead documentation for new product introductions, aligning writers and partner teams from planning through release.
- Documentation operations. I improve how documentation is planned, produced, and released, working closely with Engineering, Product, and UX.
- Documentation experience. I apply UX research methods to documentation itself, finding where readers get lost and shipping fixes for the problems they raise most.
You can see the details in the case studies.
How I lead
I lead through influence. I scope ambiguous problems, build partnerships across Product, Engineering, UX, and Marketing, and bring teams to decisions they can commit to. I create standards and tools that other writers and teams adopt, and I mentor writers as they join and grow within the team.
A colleague once put it this way:
“Thanks for the stellar work exploring and managing the documentation strategy, being on top of things, communicating, and bringing us together as a team to think about the best long term approach for our product and customers."
How I work technically
- Content: CLI and API documentation, UI content and microcopy, release notes, and conceptual and procedural topics.
- Systems: information architecture, structured (DITA) and unstructured authoring, Git-based workflows, and documentation site design and development, across Linux, macOS, and Windows.
- AI-enabled workflows: agent and prompt design, human review, and documentation governance. I’ve written about what makes the guardrails work.
- Working with teams: launch leadership, cross-team alignment, mentoring, and UX research methods.
I do my best work on problems that sit between content, systems, and teams: situations where the challenge isn’t simply writing the documentation, but deciding how the information should be structured, how the work should happen, and how different teams can align on a better approach.
What I look for in a team
- Early access to the people building the product. Documentation is better when writers are in the conversation before a feature is final.
- A shared definition of “ready." Stable terminology, final UI text, and an accepted spec before documentation work begins.
- Room to improve the process, not just the pages. The best fixes often sit upstream of the content.
You can read the case studies, see my career, or get in touch.