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: This too is technical communication From:"Lauren" <lt34 -at- csus -dot- edu> To:"'Mike Starr'" <mike -at- writestarr -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 5 Jun 2007 14:57:46 -0700
Mike,
You made sense the first time. I don't understand why people keep confusing
the process with the product. The process makes sense. Play dumb and get
as much information as necessary. The product, a document, obviously, will
not have all of that information, but it can be much more clear compared to
a product that has limited information because the writer will have enough
information to complete a cogent document.
I am really confused as to why people keep saying that the documentation
written from information gathered by somebody taking the stance of a
clueless idiot will only apply to clueless idiots. The product is not the
process. Of course, documentation will not be written for clueless idiots,
but the stance of the writer in the information gathering process can be
that of a clueless idiot. How did people get so lost and confuse the
product with the process?
Lauren
> -----Original Message-----
> From: techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com] On
> Behalf Of Mike Starr
> Sent: Tuesday, June 05, 2007 1:57 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: This too is technical communication
>
> I'm not trying to write documentation for clueless idiots but
> I may adopt
> the persona of one when interviewing a subject matter expert
> or testing a
> software product.
<...>
>
> Mike
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-