Principal Technical Writer—AI Knowledge Architect
Delivering technical knowledge at scale—for humans and agents.
Hi, I'm Richard. I bring 20+ years of experience creating product and engineering documentation for SaaS and enterprise software.
Dual Identity
What I do.
Technical Communication
With a master's degree in technical communication, I'm an expert in researching and organizing complex technical information, designing attractive documents, and creating content that people actually read.
AI Knowledge Architecture
I build AI knowledge assets and governance frameworks that enable teams (and agents!) to deliver quality knowledge to their audiences as the docs grow. This site is proof: a docs-as-code pipeline that lints prose, validates links, and deploys vetted content via CI/CD.
Selected Work
A sampling of things I've shipped.

Why Aesthetics Matter in Technical Docs, with Richard Rabil
A conversation on how visual design and usability shape how documentation gets read.
Read the piece
Order Out of Chaos: Patterns of Organization for Writing on the Job
Reusable organizational patterns for professional writing in the workplace.
Read the piece
Content Strategy in Action: Enabling Sales with Product Documentation
How documentation quality and structure became a sales enablement asset.
Read the piece
Opower Digital Self-Service - Energy Management
The complete guide to the Digital Self Service - Energy Management product experience, from bill comparisons to data trends to solar power usage.
Read the documentation
Opower Analytics Visualization
How subject areas, measures, and attributes come together to build visualizations and inform business decisions.
Read the documentation
Data Transfer Specifications
Documentation on transferring energy use data securely from utilities to Oracle in the right structure and format.
Read the documentationWhat Is This Site?
Not a metaphor.
Every push runs all five before anything ships. If a check fails, the site doesn't deploy. Every page also publishes a Markdown twin and an llms.txt entry, so an agent can read the source instead of scraping the page.
Want to Get in Touch?