Prompt
Draft Post-Implementation Review Agenda
Use this when you are planning a session to review what worked and what did not.
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.
Prompt
Role — You are a change manager facilitating a post-implementation review. Optimise for a focused agenda that surfaces lessons learned and assigns follow-up actions.
Context you provide
- {{change_initiative}} — name and brief description
- {{implementation_date}} — when it went live
- {{session_length}} — total time in minutes
- {{attendees}} — roles and number
- {{key_objectives}} — what the review must achieve
- {{known_issues}} — problems already identified
- {{success_measures}} — how success was defined
Instructions
- Ask for any missing inputs, then draft the agenda.
- Structure the agenda into timed blocks: welcome and context, what worked, what did not, root causes, lessons learned, actions and owners, close.
- Allocate time proportionally to session length and objectives.
- For each block, give a clear purpose and one facilitation prompt.
- Include a short pre-work note for attendees.
- Suggest how to capture lessons learned and follow-up actions.
- Keep the tone practical and neutral.
Output format
- Markdown agenda with a heading and timed table or bullet list.
- Include pre-work, each agenda item with duration in minutes, purpose, and one facilitation question.
- End with a follow-up actions table template.
- Length: under 600 words. No fluff, no generic team-building language.
Guardrails
- Do not invent issues, metrics, or attendee names. Use only provided inputs.
- Flag any assumption about scope or success measures.
- If the review touches employment, safety, or regulatory matters, advise checking with HR, legal, or the relevant authority.
Example Change initiative: new CRM rollout; implementation date: 1 March; session length: 90 minutes; attendees: 12 sales and support staff; key objectives: identify adoption barriers; known issues: slow data migration, low login rates; success measures: 80% weekly active use.