Re: What do you call this doc?

[David Neeley <dbneeley -at- gmail -dot- com>]

Since this report goes to the clients who experienced the service
interruption and contains both what actions were taken to rectify it
and what actions are in place to avoid the problem in the future, I
would seriously consider couching it in a more positive
light...something like "after action report" might be one approach.

It is up to you to define the situation, and doing so in a positive
light without minimizing the problem might be well received by all.

Instead of "we had this unfortunate problem, and scrambled around to
fix it" you would be saying "Here is what we discovered and what we
have done to restore service and to further assure uptime in future."

Actions, after all, speak louder than words--and words about actions
speak louder than words about problems.

David

On 8/2/05, Barry Campbell <barry -dot- campbell -at- gmail -dot- com> wrote:
> 
> If you're just documenting the Incident, then it's an "Incident Report."
> 
> If you're actually explaining why it happened in addition to what
> happened, then it's a "Root Cause Analysis Report."
> 
> - bc

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

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l


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