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.
Its a basic overview, for people totally unfamiliar to tech writing, and is fine for what it is...
Except this concept of a documentation plan is odd to me. When I started my first job as a tech writer, I was told to start with a documentation plan; but after a bit of head-scratching I abandoned it, because it was a chicken-an-egg situation: there was no way I could plan out an entire document up front, without knowing anything about the app I was going to write about.
So in effect, my doc plan would have included the target audience, a scope of "describe every feature in the product", and a timeline of "have it done in time for the release of the software, which at this point, is only vaguely projected to be 'sometime in December/maybe january'". So... not useful in any way.
The structure of the information was built/evolved as I worked through researching and documenting each feature. Developing a detailed "plan" to do that would have been a waste of time.
-----Original Message-----
From: techwr-l-bounces+lynne -dot- wright=kronos -dot- com -at- lists -dot- techwr-l -dot- com <techwr-l-bounces+lynne -dot- wright=kronos -dot- com -at- lists -dot- techwr-l -dot- com> On Behalf Of Cardimon, Craig
Sent: Tuesday, May 8, 2018 9:17 AM
To: 'TechWhirl (techwr-l -at- lists -dot- techwr-l -dot- com)' <techwr-l -at- lists -dot- techwr-l -dot- com>
Subject: "How to Write a User Manual"
Information contained in this e-mail transmission is privileged and confidential. If you are not the intended recipient of this email, do not read, distribute or reproduce this transmission (including any attachments). If you have received this e-mail in error, please immediately notify the sender by telephone or email reply.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
