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: Training Documentation From:Smokey Lynne L Bare <slbare -at- JUNO -dot- COM> Date:Fri, 8 Jan 1999 20:37:34 -0500
Tanya,
I have found that storyboarding was a good starting point. There are
many wonderful books and articles available, as well as professional
training association material to complement your job task. Taking the
ideas that your client expresses interest in and storyboarding them will
assist you in providing a comprehensive, big picture methodology.
Accountability will also become apparent, and especially, especially who
'OWNS' it. How many times have wonderful programs been delivered, and a
client/end user has commented along the lines...this is not quiet what we
were looking for.... you have your storyboard, they tasked you to develop
XYZ, and they were a part of the storyboard process. Here is where the
client can change things prior to training development.
I put huge 3' wide newsprint (from the local university press room) rolls
of paper around the wall. Using 3x5 colored post-its, I assign a color
to represent either a process/ person/source. Later this can be
transposed to documentation or graphics. Just one idea of the many you
will receive .....
