Goal
Everyone affected leaves knowing why the change is happening, what it means for their own work, when it starts and where to get help.
Inputs
- The change: [e.g. moving from spreadsheets to a CRM, new expense approval process]
- Why it is happening: [the problem it solves, in plain words]
- Teams and roles affected: [list]
- What changes for each role: [old way and new way]
- Timeline: [training dates, go-live date, date the old way stops]
- Support: [training, guides, contact person by role, office hours]
- Known concerns from staff: [list or none]
Steps
- Lead with the problem the change solves, before the solution.
- Show the change from each role's point of view.
- Give dates for training, go-live and the old way ending.
- Answer known concerns directly.
- End with one clear action for each person.
Output format
- | Slide | Title | Content (max 4 bullets) | Speaker notes |
- Eight slides: why we are changing, what is changing, what it means for you (by role), what stays the same, timeline, training and support, your questions answered, what to do this week.
- | Role | What stops | What starts | What stays the same | First action |
- FAQ: eight questions with short answers.
Check before answering
- No promise the inputs do not support, such as "this will save two hours a day".
- Concerns are answered honestly, including ones where the answer is "we do not know yet, and we will tell you by a date".
- The old process end date is stated clearly.
- The deck takes under 20 minutes to present.






