![]() |
![]() |
|
|
|
When people ask me what I do for a living, I tell them I write all of those manuals that no one ever reads. That's right. I'm a technical writer. In the course of my career, I've written lots of manuals, proposals, training courses, reference guides, and scripts for audiocassette and video presentations. I've also produced numerous marketing brochures, promotional flyers, business reports, and newsletters. I didn't set out to be a technical writer. I was an English teacher. After teaching for several years, I wanted to try something else, so I took a job as a newspaper reporter. Working as a reporter, I discovered that I especially liked writing stories that required research and figuring out how things work. I liked talking to engineers, geologists, and other technical people. I was fascinated with the science behind the technology and wanted to explain it to my readers in a way that they would understand. I didn't know it at the time, but I was thinking like a technical writer. Eventually, I went to work as an editor and writer for a trade publishing company. While on that job, I decided to write a procedures guide for my job so someone else would be able to take over in an emergency. Although I didn't think of it as such, that procedures guide was my first technical document. My procedures guide came in handy a few months later when I had to be off work for two weeks following surgery. My boss was delighted that others were able to do my job by following the guide I had written, and asked me to write similar guides for other people's jobs as well. In the early 1990s, I began freelancing. One day, I heard about a great freelance opportunity. A large government agency needed a technical writer to write an lengthy document for a savings and loan company. I wasn't sure I was qualified for the job, but I decided to try anyway. When asked for samples of my work, I showed the interviewer the procedures guides I'd written. Those guides got me the contract. I was officially a technical writer. After that project ended, I found more work as a technical writer, and the rest is, as they say, history. I've written technical documentation and training courses for telecommunications, financial, software development, computer, medical and public utilities companies. I also have written training programs for government agencies such as NASA, the Department of the Army, and the Department of the Navy.My experiences have created a foundation of knowledge that enables me and my associates to bring energy, enthusiasm, and creativity to our projects. By having “been there, done that,” I can show you approaches that will save you time and money. I’ve successfully helped companies get projects back on track, as well as helped plan and direct projects from beginning to completion. Most of all, I listen to you and learn what your needs are, then come up with suggestions that are tailored to your unique circumstances. I hope to hear from you!
|
|
|||||||||||||||||||||||||||||
|
|