Routine

90-Day Retrospective Routine for learning at scale

A repeatable, facilitator-friendly routine that captures outcome-focused learning, turns insights into prioritized experiments with owners and success criteria, and tracks adoption with a 30-day check-in cadence. Includes built-in experiment entries, owner commitments, and a quick remote facilitation checklist.

Interactive Tool

90-Day Retrospective Routine — Facilitator Guide & Output Capture

Purpose

This routine helps teams turn quarterly reflection into measurable experiments and reliable follow-through. Use the form below during or immediately after the session to capture data review notes, designed experiments, owners, and short-term follow-ups. The structured outputs make the retrospective repeatable, discoverable, and trackable.

Before the session

Ask participants to submit outcome metrics and short anecdotes. Paste them into the pre-work fields. Collecting objective metrics before the session focuses discussion on outcomes.

During the session

Follow the suggested timing: data review (about 20 min), facilitation prompts and sensemaking (about 40 min), experiment design (about 25 min), owner commitments (about 5 min). Use the remote facilitation checklist below if needed.

List the primary metrics (KPIs) that define success for this 90-day period. Include numbers, time ranges, and owners where possible.
Short, specific anecdotes that help explain metric changes. One anecdote per line is fine.
Write a 2–5 sentence outcome-focused summary. Note surprising trends, major wins, and risks.
Record the prompts you used and the most useful team responses. Example prompts: 'What surprised you?', 'What did we control vs not control?', 'What assumptions were wrong?'
Use during remote sessions to keep engagement high.
Select the prioritization approach used in the session.
Short descriptive title.
State the hypothesis you will test.
Describe the action, scope, and first steps.
Who will own execution and status updates?
Set a realistic due date for first measurable outcome.
How will you know the experiment worked? Be specific and measurable.
Team's confidence that this experiment will produce the desired effect.
1.0 10.0
Short descriptive title.
State the hypothesis you will test.
Describe the action, scope, and first steps.
Who will own execution and status updates?
Set a realistic due date for first measurable outcome.
How will you know the experiment worked? Be specific and measurable.
Team's confidence that this experiment will produce the desired effect.
1.0 10.0
Short descriptive title.
State the hypothesis you will test.
Describe the action, scope, and first steps.
Who will own execution and status updates?
Set a realistic due date for first measurable outcome.
How will you know the experiment worked? Be specific and measurable.
Team's confidence that this experiment will produce the desired effect.
1.0 10.0
Ask each owner to write a one-line commitment (what they'll do and by when). One commitment per line.
Choose the cadence for short check-ins to review experiment progress.
Enter the date for the first follow-up check-in.
Person who will coordinate reminders and collect status updates.
Call out dependencies, resource needs, or blockers that will affect experiments.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.