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.
RE: Hi-Tech Company Hasn't Used Tech Writers in Years
Subject:RE: Hi-Tech Company Hasn't Used Tech Writers in Years From:"Mark Baker" <mbaker -at- ca -dot- stilo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 27 Oct 2003 14:05:10 -0500
> This used to be a typical practice (it may still be, but I've
> been out of the
> industry for a long time now). Military personnel in the field take the
> 500 page manuals that design engineers and technical writers produce,
> tear out the 50 or so pages that contain the information they *really*
> need, then redline it to reflect the way things are *really*
> done.
Some variation on this is typical practice everywhere and for everything. It
comes back to the basic issue of the social life of information. People's
first point of reference is their own experience. Second, they ask the
people around them. Only third, if at all, do they read documentation.
The ordinary user does not read the docs. The person who reads the docs is
the maven -- the person everybody else asks when they have a problem. Even
when the question is answered by reference to the docs it is usually the
maven who looks it up to answer the question posed by the ordinary user. I
see this repeatedly on our own user's group. Most of the questions asked are
answered in the docs. And, as in all user groups, we have a handful of
mavens who answer most of the questions. And they often answer the question
by referring to the appropriate page in the docs. All this makes perfect
sense, by the way, and is not merely a reflection on the laziness of the
average user -- the mavens are sometimes mavens on the docs as much as they
are mavens on the products -- they know where the answers are.
In many cases however, the mavens don't need much from the docs beyond the
hard core reference material. The rest they know by heart and by experience.
Thus the 50 redlined pages.
I believe there is a fundamental flaw in the user needs analysis that most
of us do. We assume that we are writing for the average user. In most cases,
I am convinced, this is not the case. We are really writing for the maven.
It is the maven who will read what we write, not Joe user. Not every maven,
however, will want or need the documentation -- most have a depth of
experience to draw on. Our real business, therefore, is the training of new
mavens. New mavens may be a very small part of the user base, but they are
vital to the life of a product: no mavens = no market.
I suspect that we would actually do better making our case to management in
these terms as well. Management knows as well as we do that nobody reads the
manuals -- so why put in the effort. The answer is, to inform that one
customer in a hundred who is an up-and-coming maven -- a person who will
support your user community (for free) for years to come. Your company needs
those mavens and every penny spent cultivating and informing them is money
well spent.
Required Reading:
(on mavens) Malcolm Gladwell, The Tipping Point
(on the social life of information) John Seely Brown, Paul Duguid, The
Social Life of Information
---
Mark Baker
Stilo Corporation
1900 City Park Drive, Suite 504 , Ottawa, Ontario, Canada, K1J 1A3
Phone: 613-745-4242, Fax: 613-745-5560
Email mbaker -at- ca -dot- stilo -dot- com
Web: http://www.stilo.com
This message, including any attachments, is for the sole use of the
intended recipient and may contain confidential and privileged
information. Any unauthorized review, use, disclosure, copying, or
distribution is strictly prohibited. If you are not the intended
recipient please contact the sender by reply email and destroy
all copies of the original message and any attachments.
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.