I've stepped back from full-time work. I still consult with documentation teams and take on projects with a clear scope and an end date. Remote, up to 25 hours a week.
Start a conversation → See the workAn hour or a few weeks of advice. I review your docs, your toolchain, or your plan, and tell you what I'd change. Good for teams with writers who want a second opinion.
How consulting works →Scoped work I do myself: a docs-as-code setup, an audit, a style guide, an editing pass, an API reference. Each project has a fixed scope and an end date.
What I take on →A free series on the craft and career of technical writing: 35 articles across 8 phases, each with an exercise. Read them in any order.
The hourly rate isn't the raise it looks like.
What to show when everything you've written belongs to someone else.
Docs you should delete without breaking anything.
Describe what's broken. I'll tell you how I'd approach it and whether it's a consulting question or a project.
Get in touch →