One of the ways that I communicate desktop changes to the end user is via a Memo. This memo is printed on colored paper (light blue) which has been reserved for IS memos. This sets apart IS information from all others. A memo normally goes out about a week before a change. I have found that sometimes giving too much time before a change the user will forget about it and then be surprised.
After the change(s) have been made, a memo is left at their desktop outlining the changes that have been made or maintenance that has been performed on their machine. This memo (also on blue paper), is taped to the monitor (that way they have to see it).
All communications leave an "open door" for questions and comments.
Major upgrades(primarily accounting versions), get voice mail and email two weeks prior; a follow up (voice mail and email) one week prior; a final follow up by both methods two days prior to the event. These events are *always* scheduled for weekends or holidays.
While I consider email to be the easiest way to send detailed information to end users, the info is sometimes read after the fact. My solution is simple....in the users NT logon script, I have added a few DOS commands, a CLS, an ECHO with the message and a PAUSE. Even if they don't read their email, listen to voice mail of look at a posted memo or notice, they have a chance at getting informed as soon as they sign on the the network.
I make use of network broadcast messages. I can send a notice to one user, a group or the entire network. It's great!
for formal information I choose transfering information via email. but some time we have to send the information a.s.a.p, then I use popup instant message to inform all the user in my network. it's real time transfer. they can respond as soon as they read the message.
- Keyboard Shortcuts: