Re: Re: Two TOCs (Was: Transitioning user expectations...)

[technical -at- theverbalist -dot- com]

  :: Task based documents are written that way. Their approach is
  :: different, their structure is different, and they are written
  :: differently than a function or feature based document.

Oh, I hear ya. My specific problem is that while I have client developers
out in the field who want task-based information about using the product,
I also have internal users, like managers and VPs who use the
documentation but think about the product in terms of the features. When
they can't find information in the ToC about a specific feature, that's
where they stop looking and email my manager to ask where the information
about the feature is. Tra la...

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

Technical Communication Certificate online - Malaspina-University College, Canada. Online training in technical writing, software (FrameMaker, RoboHelp, Dreamweaver, Acrobat), document & web design, writing manuals, job search. www.pr.mala.bc.ca/tech_comm.htm for details.

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.