Technical Writer?

I've been interested in technical writing since I first read a really bad product user manual about 20 years ago. I thought that there must be an opportunity there. I knew I could create a manual that would be better than that, so I went back to school, got a degree in English and Communications, and started a small business.

I've worked as a documentation specialist, business analyst, and documentation consultant for some of the highest profile companies in Minnesota. I especailly enjoy troubleshooting, Microsoft Word problems, creating user manuals and process documentation. I enjoy my work and the entire consulting process, because client projects can be very interesting. They often require a writer that can provide many different deliverable types. I have had many roles, including project manager, writer, business analyst, interviewer, note taker, administrator, and have even made copies for meetings.

Deliverables

  • Software life-cycle documentation
  • Requirements gathering
  • Compliance documentation
  • Business process, policy, and procedure documentation
  • Network infrastructure documentation
  • User manuals
  • Quick reference guides
  • Usability studies
  • Name rebranding
  • Standard Operating Procedures (SOPs)
  • Statements of Work (SOWs)
  • Proposals

    • Hire a Technical Writer

    I have experience with all aspects of communication and documentation. Experience in state-of-the-art legacy applications and systems. Work well independently or in a team environment. Expert at making clients and subject matter experts feel that their involvement and participation in writing/documentation projects is crucial but painless.

    If you need a technical writer for any documentation project, you should hire someone with a lot of experience that can complete your project better, faster, and cheaper. You usually only get to pick two.

    Clients depend on me to finish projects by deadline and under budget.