1.3. Communicate as Much as Possible
- Tell your users what you are going to do
- Tell your users what you are doing
- Tell your users what you have done
1.3.1. Tell Your Users What You Are Going to Do
- The nature of the change
- When it will take place
- Why it is happening
- Approximately how long it should take
- The impact (if any) that the users can expect due to the change
- Contact information should they have any questions or concerns
System Downtime Scheduled for Friday NightStarting this Friday at 6pm (midnight for our associates in Berlin), all financial applications will be unavailable for a period of approximately four hours.During this time, changes to both the hardware and software on the Finance database server will be performed. These changes should greatly reduce the time required to run the Accounts Payable and Accounts Receivable applications, and the weekly Balance Sheet report.Other than the change in runtime, most people should notice no other change. However, those of you that have written your own SQL queries should be aware that the layout of some indices will change. This is documented on the company intranet website, on the Finance page.Should you have any questions, comments, or concerns, please contact System Administration at extension 4321.
- Effectively communicate the start and duration of any downtime that might be involved in the change.
- Make sure you give the time of the change in such a way that it is useful to all users, no matter where they may be located.
- Use terms that your users understand. The people impacted by this work do not care that the new CPU module is a 2GHz unit with twice as much L2 cache, or that the database is being placed on a RAID 5 logical volume.