Re: This too is technical communication

[Ned Bedinger <doc -at- edwordsmith -dot- com>]

Emily Berk wrote:
> The question is when does the writer cry uncle and admit that she understands just about nothing of all the source materials she's looked at and can't even imagine where to start

I've heard it called _spin cycle_, by analogy to a car spinning its 
wheels without traction. Or maybe something to do with a washing machine.

I'm sure a lot of tech writers end up in a similar-sounding situation, 
but for the other reason--unqualified for the project work they've taken 
on.

In either case, the way out is to come clean and let the team decide if 
you're to be folded with the laundry or torn up for rags :-) Yours is a 
good example of doing the right thing. Thanks for sharing.

Ned Bedinger
doc -at- edwordsmith -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


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.