Have you ever prepared for a presentation and heard this advice:
Tell ’em what you’re gonna tell ’em. Tell ’em. Then, tell ’em what you told ’em.
In case that slang isn’t very clear to read, that says to tell your audience what you’re going to tell them as the first step. Then actually tell the audience exactly that. When you’re done with that, recap what you just said. Basically it says to communicate!
This can be likened to what’s needed when an organization is adopting new software. You really need to inform your members, constituents and users what’s going on. Before you push the green button, here are 3 steps to help that.
1. Tell ‘Em What You’re Gonna Tell ‘Em
Send out an email, TPS report or general announcement that you’re going to be adopting a new tool. Inform your members well in advance that you’re going to be adopting new software and what they can expect. Tell them when they can expect to begin interacting with the new software and provide them with an outline. Depending on how complex the software is, the outline should detail not only the actions that the members need to take, but also provide a time-line of events and milestones.
2. Tell ‘Em
Launch you new software initiative. Push the green button! You have an outline too, right? An outline of all the settings and features that you need to turn on, tweak, adjust, etc. You should.
3. Tell ‘Em What You Told ‘Em
Now that you’ve pushed the green button and your folks are using the new software, make sure they understand the purpose and benefits of using the software. Provide best practices, help, and support. Recap why you’re using the software and how your organization will enhance its efforts towards world peace with this new software. Or just tell them how you going to save money, save time, and generally make the organization better.
What have been your experiences with adopting new software? Do you have any horror stories you’d be willing to share? Or any really successful launches? What contributed the success or demise of the new process?