RE: Time to perfom a procedure

["Carey Jennifer (Cry)" <jennifer -dot- carey -at- cdi -dot- cerberus -dot- ch>]

John,

To answer your question, I haven't ever included the time a process should
take, but I think it's a *fantastic* idea and would consider doing it
wherever appropriate (relevant, useful) in my own documentation.  I also
think explaining that this is a one time procedure and will take 20-30
minutes is a good thing to include in the text right before the procedure.

I document a process for the folks who install our systems at client sites.
One phase of the process certainly involves 50+ steps. They aren't
executives like your audience and expect to spend the time on the process
but the information would help them to plan their own schedules...Thanks!

Jennifer

--------------------------
John wrote:

What I would like to know is if anyone has ever included in the
document the amount of time that an average user from the targeted
audience should be able to perform the process. Even though we've got
maybe 50 steps, I don't think the process start to end should take no
more than 20/30 minutes and once they do, they never have to do it
again.

How have you addressed this concept? 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com

Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr

---
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
http://www.raycomm.com/techwhirl/ for more resources and info.