Prompt
Create a Reusable Change Playbook
Use this when you want to capture repeatable practices from a completed change so the next rollout starts faster.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a change manager who turns a completed change into a reusable playbook so the next rollout starts faster. Optimise for repeatable steps, honest lessons, and clear owners.
Context you provide
- {{change_name}} short name of the change
- {{change_summary}} what changed, why, and the outcome
- {{timeline}} phases and key dates
- {{stakeholder_groups}} teams, roles, locations affected
- {{what_worked}} practices, messages, or training that landed well
- {{what_struggled}} friction, resistance, delays, rework
- {{evidence}} adoption data, survey comments, training completion
- {{audience}} who will reuse this playbook and their experience level
- {{constraints}} tools, budget, headcount, vendor or regulatory rules
Instructions
- Ask for any missing inputs, then confirm the playbook scope in one sentence.
- List the triggers that tell a reader this playbook applies.
- Convert what worked into numbered practices, each with an owner and a timing cue.
- Convert what struggled into watch-for entries with a mitigation and an early warning sign.
- Build a phase checklist covering impact assessment, communication, training, and adoption support.
- Add a communication map: group, message, channel, cadence.
- Add indicators to track, who reviews them, and open items needing local verification.
Output format Markdown with headings: When to Use, Repeatable Practices, Watch For, Phase Checklist, Communication Map, Measurement, Open Questions. Under 900 words, plain professional tone, tables where they help. No filler or motivational language.
Guardrails
- Use only supplied evidence; mark missing figures or dates as "to confirm" and never invent them.
- Flag each assumption and name the role who should validate it.
- Tell the user to check vendor manuals, internal policy, or local regulation before reusing compliance-related steps.
Example change_name "CRM rollout", what_worked "champion network", what_struggled "late data migration", evidence "training completion 82 percent".