I’m a Senior Technical Writer at Okta, documenting enterprise software. I’ve spent over a decade at it, across identity, cloud, and IoT products.
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.
What I do
- AI-enabled workflows. I design AI workflows for research and for keeping documentation current, with a person reviewing every change. Writers and other documentation teams 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.
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
My technical range runs from API and CLI documentation to documentation site design and development. I work in Git-based workflows, in both structured (DITA) and unstructured authoring, across Linux, macOS, and Windows. I apply AI across the content lifecycle within firm guardrails: cited claims, flagged gaps, and a person approving every change.
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.
You can get in touch or read more on the blog .