Retrospective Facilitator

Run a structured team retrospective to identify what went well, what did not, and improvement actions

🧪 Tested by a human Beginner 👤 Manager 👤 Developer 👤 It Admin
Create a retrospective document for [PROJECT/SPRINT/QUARTER]. Structure it using the Start-Stop-Continue framework: (1) START — things we should begin doing (new practices, tools, habits), (2) STOP — things we should stop doing (wasteful activities, bad habits), (3) CONTINUE — things that are working well and should keep going. For each section, provide 5 thought-provoking questions the facilitator should ask. Then include: (4) Top 3 Action Items — specific improvements with owners and deadlines, (5) Celebration — highlight one team achievement to recognise.

Works on

⭐ M365 Copilot (Best) 🟢 ChatGPT 🟠 Claude

Copy & Open in

🟢 ChatGPT 🟠 Claude

Prompt is copied to your clipboard when you click

Tips for Best Results

  • Replace [PROJECT/SPRINT/QUARTER] with your context
  • In Loop, create this as a collaborative document — team adds their points live
  • Great for sprint retros, project post-mortems, or quarterly team reviews
  • Follow up with “Summarise the action items into a Planner task list”

📎 More Prompts

Lessons Learned Document

●●
Create a lessons learned document for [PROJECT]. Structure: (1) Project overview (scope, timeline, outcome), (2) What went well (5-7 items with impact), (3) What could improve (5-7 items with root cause), (4) What we would do differently, (5) Recommendations for future projects, (6) Key metrics vs plan. Get input from: [TEAM MEMBERS]. Tone: constructive and forward-looking.
⭐ M365 🟢 GPT 🟠 Claude

Project Notebook Template

●
Create a project notebook template for [PROJECT NAME] with these sections: (1) Project Charter — objective, scope, stakeholders, success criteria, (2) Meeting Notes — template for recurring meeting minutes, (3) Decision Log — table with Date, Decision, Rationale, Owner, (4) Action Item Tracker — Task, Owner, Due Date, Status, (5) Risk & Issue Log — structured risk register, (6) Key Contacts — stakeholder directory with roles and contact details, (7) Reference Documents — links to important files and resources, (8) Lessons Learned — ongoing capture of what went well and what to improve, (9) Status Dashboard — weekly RAG indicators template. Each section should have a brief description of what goes there.
⭐ M365 🟢 GPT 🟠 Claude

Project Plan from Brief

●●
Create a detailed project plan from this brief. Include: (1) Project Overview — objective, scope, success criteria, (2) Phases — break the project into 3-5 logical phases, (3) Tasks — list tasks within each phase with estimated duration, (4) Milestones — key checkpoints with dates, (5) Dependencies — which tasks depend on others, (6) Resource Requirements — roles needed for each phase, (7) Risk Register — top 5 risks with likelihood, impact, and mitigation, (8) Communication Plan — who gets updated, how often, through what channel. Present as a structured document with tables.
⭐ M365 🟢 GPT 🟠 Claude
💬