PromptShop
Business Strategy· OperationsIntermediate

Retrospective and Continuous Improvement Framework

Conduct regular retrospectives on projects and processes to drive continuous improvement for teams and individuals.

Customize

Your prompt

You are a continuous improvement facilitator with expertise in agile retrospectives and organizational learning.

Design a retrospective framework for {{retrospective-scope}} with {{frequency}} cadence.

RETROSPECTIVE STRUCTURE:
- Set the stage (5 minutes) with purpose reminder and psychological safety check
- Gather data (15 minutes) reviewing what happened using objective evidence (metrics, events, decisions)
- Generate insights (20 minutes) identifying patterns, root causes, and systemic issues
- Decide what to do (15 minutes) selecting specific improvements to implement
- Close (5 minutes) with appreciation and commitment to action items

FACILITATION APPROACH:
Use different formats to prevent retrospective fatigue (Start-Stop-Continue, Sailboat, 4Ls, Mad-Sad-Glad, Timeline). Ask powerful questions that drive deeper thinking (What surprised us? What would we do differently? What assumptions were wrong?). Encourage equal participation and prevent domination by loud voices. Focus on systems and processes, not individual blame. Create safe environment for honest feedback and difficult conversations.

DATA COLLECTION:
Review quantitative metrics (project timeline, budget, quality indicators, customer satisfaction). Gather qualitative feedback (team sentiment, stakeholder input, customer comments). Document significant events, decisions, and turning points during the period. Compare results to initial goals and expectations.

INSIGHT GENERATION:
Look for patterns across multiple data points. Identify root causes using 5 Whys or fishbone analysis. Distinguish between one-time issues versus systemic problems. Celebrate what went well and identify practices to continue or amplify.

IMPROVEMENT IMPLEMENTATION:
Select 1-3 specific improvements to implement (focus over comprehensiveness). Assign clear owners and deadlines for each improvement action. Make improvements visible and trackable. Follow up on previous retrospective action items before adding new ones. Measure impact of improvements in next retrospective.

Format as facilitation guide with format variations library, question banks, tracking templates, and improvement monitoring system.

— via PromptShop: https://promptshop.munirabbasi.me/prompts/retrospective-and-continuous-improvement-framework

How to use it

For project retrospectives, conduct within one week of completion while details are fresh. For sprint retrospectives, hold at end of every 2-week sprint for regular course correction. For quarterly retrospectives, review bigger patterns and strategic direction. For annual retrospectives, evaluate year-long themes and set direction for next year.

Small teams can use simple formats and quick sessions, large teams need structured facilitation and more time for input gathering.

Tags

Related prompts