TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: formal training for new writer From:Kris Olberg <kjolberg -at- IX -dot- NETCOM -dot- COM> Date:Wed, 19 Aug 1998 18:51:05 -0500
-----Original Message-----
From: Julie Deutz <jdeutz -at- GPS -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Wednesday, August 19, 1998 3:22 PM
Subject: formal training for new writer
>[snip]
>Does anyone know of an intensive (meaning one to two-week) course that goes
>through the "nuts and bolts" for an experienced professional who is new to
>the world of technical writing? Location isn't an issue.
Much as I'd like to oblige with info about a book called "Learn Technical
Writing in 21 Days," I can't. Here's what I can offer:
- Position your expectations appropriately. Don't expect her to churn out
work immediately.
- Get her enrolled in a technical writing course at an accredited
institution.
- Suggest she subscribe to TECHWR-L.
- Have her read Strunk and White's "Elements of Style" and the Chicago
Manual of Style (or other style manual if your company follows a different
standard). "Elements of Style" is short and can be read in a couple of
hours.
- Put her in touch with another technical communicator (preferably not
yourself) who is willing to mentor her at her request.
- Give her short assignments at first. Make sure that peer reviews are
thorough and all problem areas are discussed in detail.
- Have her read examples of good and bad technical writing. Thoroughly
discuss the differences.
- Make sure she understands your process (e.g., write outline, collect
source, write and revise, edit, technical review, etc.)
Advice for you:
- Keep in mind that the probability of success is less than optimal.
- Use concrete measurements for assessing her progress. Examples are pages
per hour, technical notes per month, etc. Share the measurements with her so
she knows what your expectations are.
- Don't let her languish if writing isn't her cup of tea.
Best of luck!
Regards...Kris
-----------------------------
kolberg -at- actamed -dot- com
kris -at- olberg -dot- com
