RE: "They don't need no stinkin' documentation..."

Subject: RE: "They don't need no stinkin' documentation..."
From: Annamarie Pluhar <apluhar -at- mindspring -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 30 Oct 2001 10:06:12 -0500

David Locke says:

These days the biggest issue in the PC industry is how do we get phobic to use PCs and PC software. These people will not endure man pages. They will not tolerate what they feel is poor documentation. They are not motivated to learn or to wait. They don't want controls. They want to do their work. They don't want to do something, because the software insists on it. They insist on design.

Their insistence on design extends beyond manuals and help. They want the software tasks to be allocated to the software. They want to focus entirely on tasks from the automated domain, not the automation. They want defaults and power without all the feature bloating controls. They want embedded. They want a picture or a table that cuts a thousand words. They want a view, not a black box.

Sure the market for technical enthusiast technology will always be there, and a lot of us serve that market. But, the markets and audiences after that one still need good content, but the content changes and eventually, in phobic markets, better disappear almost completely.

Hello all,

I'm amused by this thread and generally agree that content is first and that design should aid the ability of the reader to obtain the information that they need.

But David's comment above puzzles me, and indicates that there are many different audiences for technical documentation. PC phobic? Unlikely to even pick up the technical documentation. In that case the user needs training, not documentation. That's my job as an instructional designer. It all depends on the audience. I can think of some businesses where "pretty" would be welcomed as "user-friendly" - (Hallmark Cards?) and others where it would be seen as frivolous. (KMPG)

Everything that David talks about in the first two paragraphs I would consider to be issues that should be addressed by training, carefully designed to suit the audience. After training users should have some well designed, useful Job Aids to have at their desk.

I've always assumed that technical documentation served the non-phobic users who understand that they'll get more out of the software if they read about it.

I guess I've stopped lurking.

Annamarie Pluhar

IDD Tech Solutions
Instructional design and development for technology.

(301) 588 - 4001
(301) 646 - 5002 (Mobile)
apluhar -at- idd-solutions -dot- com
Silver Spring, MD

Announcing new options for IPCC 01, October 24-27 in Santa Fe,
New Mexico: attend the entire event or select a single day. For details and online registration, visit

Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

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 for more resources and info.

RE: "They don't need no stinkin' documentation...": From: david . locke

Previous by Author: Re: What if the marketing head...
Next by Author: FWD: Bonus instead of raise -- why?
Previous by Thread: RE: "They don't need no stinkin' documentation..."
Next by Thread: Re: "They don't need no stinkin' documentation..."

What this post helpful? Share it with friends and colleagues:

Sponsored Ads