Re: Document the detritus?

[jenny_berger -at- fairfieldresidential -dot- com]

I'd keep it in. Management probably knows the junk's in the system, but 
they've forgotten about it.  Seeing it all in the doc, like you mentioned, 
might remind them of the stuff and prompt them to at least make a decision 
about what to do with it. At any rate, it's sometimes easier to take 
content out later than add it at crunch time.

Jenny Berger
Technical Writer
Information Systems
Fairfield Residential





John Posada <JPosada -at- book -dot- com>
Sent by: bounce-techwr-l-115343 -at- lists -dot- raycomm -dot- com
05/15/2003 09:42 AM
Please respond to John Posada

 
        To:     "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
        cc: 
        Subject:        Document the detritus?
So, I guess the question is should I clean up the documentation to 
represent
the way the system should be, or should I take the position that the
document is what the system IS?

On the plus side of keeping the scraps in, it may prompt management to
initiate a system-wide cleanup program. 


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

Robohelp X3, from eHelp, lets you quickly and easily create 
professional Help systems for all your Windows and Web-based 
applications, including Net. 

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module. 
 
Order RoboHelp today: http://www.ehelp.com/techwr-l

---
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.