Re: Feedback [LONG]

Subject: Re: Feedback [LONG]
From: Steven Brown <stevenabrown -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 15 Jul 2003 09:15:54 -0700 (PDT)

Thus far everyone has suggested publishing substantial
content that's mostly right, so let me take a
(tentative) contrarian approach.

Perhaps we should publish substantially less content
that is known to be 100 percent right. Why? Because if
our readers use documentation and find an error (or
multiple errors, as John's scenario implies), our
credibility suffers. Subsequently, readers' confidence
in the remaining documentation is reduced and they may
choose not to continue referring to it.

Now in fairness, you could take the other side of
arguement: If our readers refer to a document and
cannot find what they're looking for, they'll be less
likely to refer to it in the future. True enough.

Maybe it's a personal worldview, but I almost assume
that any document or book that I read is going to be
incomplete, if only because most systems and areas of
knowledge are so expansive that no one could be
expected to completely document everything.

But hey, I'm really not sure, that's why I offer this
tentatively. It's a great question.

Steven Brown
Technical Writer

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!


sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required!

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot-

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.


Feedback [LONG]: From: John Posada

Previous by Author: Latest WOW
Next by Author: Re: Getting Answers: Representing Priority and Urgency to the Tech Writer
Previous by Thread: RE: Feedback [LONG]
Next by Thread: RE: Feedback [LONG]

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

Sponsored Ads