How It Works
After you contact me, we'll set up a time to talk about your project. We can talk via Slack, Hangout, or Skype; on the phone; or in person. You can tell me about your documentation problem, question, or project, and I'll tell you how I can help. We'll establish what you expect and how we'll work together.
Next, I'll review any source materials and existing docs. I'll talk to your folks as needed to gather information and get started on a draft.
You'll review the draft and give me feedback and corrections. I'll incorporate your feedback and corrections into an updated draft. This is usually the final draft, but sometimes there's one more round of review and feeback.
You'll sign off on the final review with an email.
And that's all! The details vary, but this is the high-level view of how the process works for most projects.
Who You're Working With
My name is Hillary, and I'm a technical writer and editor. Ever since I wrote an employee manual in my first job, I've been fascinated with how documentation can solve problems and make things easier for people.
I believe documentation is a company asset. Your tech docs are just like any other asset: employees, platforms, code, offices, and trade formulas. They are vital to your business! If you aren't treating your documentation like an asset, I can show you how to do that.