Writing
The themes I care about: clarity under pressure, documentation that behaves like a product, and leadership that leaves teams healthier.
Principles
Documentation is a product
Docs aren’t an afterthought. They have users, journeys, and failure modes. When treated like a product, documentation becomes a stabilizer for complexity, not a memorial to it.
- Optimize for tasks, not page counts
- Make the “right answer” easy to find
- Measure confusion and reduce it
Clarity is a force multiplier
Clear definitions, clean taxonomies, and explicit decision-making remove friction across engineering, product, and support.
- Define terms once, reuse everywhere
- Prefer stable patterns over clever exceptions
- Publish with release intent (what changed, what matters)
Guardrails beat heroics
Systems should prevent avoidable errors. That’s true in APEX apps, doc pipelines, and team process.
- Validation close to the data
- Workflow states with clear transitions
- Automation for repeatable steps
Respect the reader
The reader is busy. Give them clean structure, plain language, and the shortest route to “done.”
- Front-load decisions and prerequisites
- Use examples that match reality
- Write for scanning, not just reading