Open the Box retrospective template

Treat how your team works like a box of tools — then decide what stays, goes, and gets added.

Open the Box asks the team to imagine everything about how they work — meetings, tools, rituals, rules, documents — packed into a single box. You open it, take each item out, and decide its fate: keep it, throw it away, add something that is missing, or recycle it into a more useful shape. Turning process into objects makes it much easier to say "this can go" without it landing as criticism of whoever introduced it.

It is a close cousin of Start, Stop, Continue with one extra move: recycling. Most teams have rituals that are not worthless but are not working in their current form — a standup that has become a status report, a template nobody fills in, a channel that only gets bot noise. Recycle gives those a third option besides keep and kill, which is usually where the best conversations happen.

Timebox

45–60 minutes

Team size

3–12 people

Cadence

Every few sprints, at quarter end, or when a team inherits someone else’s process

The Open the Box board

Keep in the box

What earns its place? What would you fight to protect if it were cut?

  • The Friday demo — it is the only time stakeholders see real work
  • Blind voting in retros; it changed what gets discussed
  • The 15-minute standup cap
  • Pairing on anything touching payments
  • The incident channel template — nobody has to think during an outage
  • Written decision records for architecture calls

Take out of the box

What is dead weight — costing time, attention, or morale for very little back?

  • The Monday status meeting that duplicates the board
  • Story-point estimation on tickets under half a day
  • The three-approver rule on config-only changes
  • The dashboard nobody has opened since it was built
  • Manually copying release notes into two places
  • The "urgent" label — everything has it, so it means nothing

Add to the box

What is missing that would make the next month noticeably easier?

  • A rota for handling inbound support escalations
  • A written definition of done we all actually agree on
  • Automated flaky-test detection instead of manual reruns
  • A short onboarding runbook for the next hire
  • A named owner for each service, published somewhere findable
  • A monthly hour for paying down the worst tech debt

Recycle

What has value but the wrong shape? Keep the intent, change the form.

  • Standup is a status report — turn it into a blocker-only round
  • Sprint planning drags — split refinement out into its own 30 minutes
  • The design review is too late — move it to before the ticket is estimated
  • The weekly all-hands becomes a written update plus a Q&A slot
  • The postmortem doc template is 12 pages — cut it to one page
  • On-call handover email becomes a five-minute live handover

How to run an Open the Box retrospective

  1. 1

    Set up the box (5 min)

    Explain the metaphor and, importantly, define what is in the box: this team’s ways of working over the last quarter — meetings, tools, rituals, documents, rules. Without that boundary, half the cards will be about the company.

  2. 2

    Empty the box (8 min)

    Silent writing across all four prompts, cards hidden. Ask people to name specific things — "the Tuesday planning meeting", not "meetings" — because the whole point of the format is deciding item by item.

  3. 3

    Reveal and group (7 min)

    Reveal everything and cluster. Watch for the same item appearing in two different columns: one person wants to keep the standup, another wants it gone. That contradiction is usually the most productive discussion in the session.

  4. 4

    Vote (3 min)

    Give everyone 4–5 votes across the whole board, not per column. Which column wins tells you something in itself — a board full of votes on "take out" means the team is buried in process.

  5. 5

    Decide item by item (15–20 min)

    Work through the top clusters and give each a verdict: kept as is, removed from this week, added with an owner, or recycled into a specific new shape. Vague verdicts do not survive contact with a busy sprint.

  6. 6

    Close the box (5 min)

    Read back the final contents: what is now in the box, what left it, what changed shape. Assign an owner and a date to each change, and check them at the next retrospective.

Open the Box examples for engineering teams

Keep

  • Trunk-based development with feature flags
  • The one-day PR review SLA
  • Runbooks required before a service takes traffic

Take out

  • Estimating bugs — we fix them regardless of the number
  • The staging sign-off form nobody reads
  • Release trains; we deploy on merge now

Add

  • Alert ownership tags so pages route to the right team
  • A monthly dependency-upgrade slot
  • A written rollback checklist per service

Open the Box examples for remote and hybrid teams

Distributed teams accumulate coordination rituals faster than anyone else, because every gap gets patched with another meeting. The recycle column is where most of those belong.

Keep

  • Written-first decisions so time zones do not gate progress
  • Core overlap hours nobody books over
  • Recorded demos for people who cannot attend live

Take out

  • The 8am call that only works for one time zone
  • "Quick sync" invites with no agenda
  • Status updates in three channels at once

Recycle

  • Live standup becomes an async thread plus a weekly live round
  • The all-hands becomes a written update with a Q&A slot
  • Onboarding calls become a runbook plus one live session

Open the Box examples for product and design teams

Keep

  • Weekly design crit with rotating presenters
  • Research clips shared in the team channel
  • One-pagers before anything over two weeks of work

Take out

  • The roadmap slide that changes before every readout
  • Duplicating specs in the tracker and the doc
  • Feature-count reporting with no usage data attached

Add

  • A standing slot for support-ticket themes in refinement
  • Post-launch usage review two weeks after every release
  • A shared glossary — three teams use "account" differently

Best for

  • Teams drowning in accumulated process nobody has audited
  • Quarter-end or project-end reviews of ways of working
  • Teams that have merged, split, or inherited another team’s rituals
  • Groups where Start Stop Continue has gone stale and needs a fresh frame

Facilitation tips

Force specificity, one item at a time

The format only works if cards name actual things. "Too many meetings" cannot be kept, removed, or recycled; "the Tuesday planning meeting" can. Ask "which one, exactly?" until every card names something you could point at.

Recycle is where the value is

Teams find keep and remove easy and skip recycle. Push the other way: most struggling rituals have a real purpose and a broken form, and recycling them keeps the intent without the cost of relearning why it existed.

Ask who introduced it — then let it go anyway

Some items were somebody’s idea and removing them can feel personal. Naming that out loud, once, defuses it: the box belongs to the team now, and process that outlived its reason is not a failing of whoever wrote it.

Cap the changes at three

A box that empties and refills completely in one session just means a chaotic month. Take out one or two things, add one, recycle one — then check at the next retro whether the team noticed.

Variations

Three columns: add, keep, remove

Drop recycle for a faster 30-minute version. Closest to Start Stop Continue, and a reasonable choice when the team is already short on process rather than buried in it.

Repair instead of recycle

Some facilitators use "repair" for things that are broken but worth fixing, and reserve "recycle" for things whose parts can be reused elsewhere. Pick one word and define it before writing starts.

Unpack someone else’s box

After a merge or reorg, run it on the process the team inherited. It gives newcomers permission to question rituals they were handed without a reason, and gives veterans a place to defend the ones that matter.

Async box

Collect cards on a board over two days, cluster them beforehand, then meet for 25 minutes to vote and decide. Works well for distributed teams and keeps the writing away from the loudest voice.

Frequently asked questions

What is the Open the Box retrospective?+

Open the Box is a retrospective format that treats the team’s ways of working as a box of items. The team writes down specific meetings, tools, rituals, and rules, then decides for each one whether to keep it in the box, take it out, add something missing, or recycle it into a better shape.

What are the four Open the Box prompts?+

Keep in the box (what earns its place), take out of the box (what is dead weight), add to the box (what is missing), and recycle (what has value but the wrong form). Some facilitators run a three-column version without recycle, or use "repair" in its place.

How is Open the Box different from Start Stop Continue?+

Start Stop Continue asks about behaviours in three directions; Open the Box asks about concrete things the team owns, and adds a fourth option — recycling — for rituals that are worth keeping but not in their current shape. It suits teams auditing accumulated process, where Start Stop Continue suits teams deciding what to do differently next sprint.

How long does an Open the Box retrospective take?+

Plan 45–60 minutes for a team of up to 10, since four columns generate more cards than three: about 8 minutes writing, 7 minutes grouping, 3 minutes voting, and 20 minutes deciding item by item.

Run Open the Box online in FocusRetro

Start a blank board, name the columns Keep in the box / Take out of the box / Add to the box / Recycle, and invite the team with a link — then run the phases with timers, hidden cards, and blind voting. Free plan available at focusretro.com.

Start a board free

No credit card required

Related guides

Start, Stop, Continue retrospective template

The fastest way to turn team feedback into concrete behavior changes.

Keep, Problem, Try retrospective template

Three columns that chain together: what to keep, what hurts, and the experiment you run next.

Lean Coffee template

An agendaless meeting that builds its own agenda in ten minutes — then actually sticks to it.

How to run a sprint retrospective (step-by-step guide)

A step-by-step sprint retrospective guide: the 5-phase agenda, exact timings for a 60-minute session, facilitation tactics, remote tips, and common failure modes.

What is a retrospective? The complete guide for teams

A retrospective is a recurring team meeting for inspecting how you work and deciding what to change. Learn the formats, agenda, timings, and mistakes to avoid.

Retrospective timebox calculator

How long Open the Box should run for your sprint length and team size, split across the five phases.

Icebreaker and check-in questions

Openers for the first two minutes of a Open the Box session, sorted by situation.