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.
I agree with your technique for dealing with vagueness. I've always assumed
that's part of my job.
On Fri, Jul 10, 2009 at 3:46 PM, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> "Technical" or "non-technical," if you're not "aggressively" insisting
> that your ignorance of subject matter is some kind of advantage, I don't
> think Richard was talking about you.
> My SMEs know they can be this vague with their comments if they need
> something added and aren't sure exactly what the "appropriate" bit of
> information is at the moment they're reviewing a document because they
> know that if I don't have it already I will get it, even if I have come
> back and hound them until I get it from them.
> Gene Kim-Eng
> ----- Original Message -----
> From: "Kathleen MacDowell" <kathleen -at- writefortheuser -dot- com>
> > In my experience, vagueness is more likely to originate with engineers
> > or
> > software developers who are busy doing their primary job, which is not
> > typically writing instructions or user assistance.
> > As a non-technical technical writer who does an excellent job
> > documenting
> > software and hardware, I also take exception to the whole tenor of
> > your
> > comment. A so-called technical writer who would insert an ambiguous
> > phrase
> > is simply not in tune with the requirements of the job. It doesn't
> > matter if
> > they're "technical" or "non-technical".
> Free Software Documentation Project Web Cast: Covers developing Table of
> Contents, Context IDs, and Index, as well as Doc-To-Help
> 2009 tips, tricks, and best practices.
> Help & Manual 5: The complete help authoring tool for individual
> authors and teams. Professional power, intuitive interface. Write
> once, publish to 8 formats. Multi-user authoring and version control!
> You are currently subscribed to TECHWR-L as kathleen -at- writefortheuser -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
> Please move off-topic discussions to the Chat list, at:
kathleen -at- writefortheuser -dot- com
kathleen -dot- eamd -at- gmail -dot- com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-