Rollout plan elements and go-live user enablement
Key Takeaway
A rollout plan prepares people as much as technology. Time go-live to a company event, plan backward from that date, and train super users first so they can help train everyone else.
A rollout plan is the preparation you do before you turn new Salesforce functionality on for users, instead of switching it on for everyone at once. A planned rollout drives higher adoption and more business value, because a new tool often means a new way of working that users must be ready for. Go-live user enablement covers communication, training, go-live day support, and the adoption and feedback work that continues after go-live.
What a rollout strategy includes
A rollout is as much about preparing users as it is about the technical steps. For many companies, a new tool is a cultural shift, so the rollout needs champions at all levels of the organization.
A rollout strategy is a full plan, not a single switch. For a Salesforce mobile app rollout, the plan includes these elements:
- Understanding user needs and business needs
- Defining requirements and use cases
- Identifying success metrics
- Customizing the app to fit the use cases
- Building and testing a prototype
- Assembling a launch team
- Creating communication and training plans
- Developing device and security policies
- Encouraging adoption
- Collecting feedback to measure business impact
Some users may already use the Salesforce mobile app on their own before the official rollout. Letting people discover the app for themselves gives lower adoption and less value than a planned rollout.