Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

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

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

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

  1. Ask for any missing inputs, then confirm the playbook scope in one sentence.
  2. List the triggers that tell a reader this playbook applies.
  3. Convert what worked into numbered practices, each with an owner and a timing cue.
  4. Convert what struggled into watch-for entries with a mitigation and an early warning sign.
  5. Build a phase checklist covering impact assessment, communication, training, and adoption support.
  6. Add a communication map: group, message, channel, cadence.
  7. 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".