You'll find the workbook to help you complete this activity in the sidebar under "Resources."
Teams are often so focused on building the system, that the distribution of the system is overlooked, or left as an afterthought. This is the real beginning of your design system journey, opening it up for use. Having a clear rollout plan is key to successful adoption of the system
Build material that will help you roll out, train and get adoption from your team.
- Other relevant stakeholders
Think through how you will approach each of the following questions as part of your rollout plan.
- Which groups will you be rolling this out to? The earlier we can let them know the better!
What will be the order of the rollout? Will you rollout to everyone at once? Or one at a time?
How will you communicate this to users and stakeholders?
If doing a phased rollout, what will the cadence be?
When will the second, third or fourth round of rollouts occur?
Does certain success criteria need to be met to rollout to another group?
What occurs as part of a rollout?
Will there be a lunch and learn? Formal training sessions? A retro or feedback session?
Don't go in blind: Have a plan in place for how this will be distributed and adjust as needed.
Collect feedback: Include avenues for team members to share feedback on what’s working, what’s not and areas for improvement.
Planning ahead will help you succeed. Here are some things to track as part of your rollout planning:
- Scope the rollout deliverable(s)
- Identify people & roles
- Set timelines & milestones
- Develop "definition of done"
- Map user pains & requirements
- Align rollout to a need or purpose
- Establish a definition of a successful rollout