ROTI Retrospective (Return on Time Invested)
The only format here that retros the retro — evaluate the ritual itself instead of the sprint.
Free · No credit card · Guests join by link
The board
01
WORTH IT
What made this retro worth the time?
02
NOT WORTH IT
What wasted time in this retro?
03
CHANGE NEXT TIME
What should we do differently next retro?
ROTI — Return on Time Invested — was originally a one-question, end-of-meeting rating: on a scale of 1 to 5, was this worth your time? Retromik's version keeps the spirit but trades the numeric scale for cards, because a number tells you the retro underperformed without telling you why.
This is the one template in the catalog that isn't about the sprint at all — it's about the retro practice itself. Every other format asks the team to reflect on their work; ROTI asks them to reflect on whether the reflecting is working. It's meant to be run occasionally, not every sprint, as a maintenance check on a ritual that's easy to let go stale.
When to use a ROTI Retrospective
- Quarterly, as a maintenance check on the retro ritual itself rather than the sprint
- After changing facilitators, format, or cadence, to see if the change actually landed
- When attendance or participation in regular retros has been quietly dropping
- When leadership questions whether retros are worth the time — run this to get evidence instead of opinions
How to run a ROTI Retrospective
- 1
Review the retro, not the sprint
Say it at the start: this board is about how the team runs its retrospectives. Sprint problems belong in the next regular retro.
- 2
Look at format, timing and facilitation
Prompt people to think about all three: the template, how long things took, and how the discussion was led.
- 3
Give everyone an equal voice
Cards are anonymous, so people can say the retro is a waste of time without it being awkward. That honesty is the point of the format.
- 4
Change one thing about the next retro
Pick the top Change Next Time card and try it at the very next retro. Then check whether it helped.
Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.
Example cards
What good cards look like for a software team. Specific, about the work, never about a person.
WORTH IT
- Voting meant we only discussed what mattered.
- The 5 Whys on the outage found the real cause.
NOT WORTH IT
- Twenty minutes reading every card out loud.
- Discussing the same topic as last time without a new angle.
CHANGE NEXT TIME
- Try a different template.
- Timebox each discussion to eight minutes.
A 20-minute agenda
- 0–2 minSay what you're reviewing: the retro itself
- 2–8 minWrite cards silently
- 8–10 minVote
- 10–17 minDiscuss the top cards
- 17–20 minPick one change for the next retro
Common mistakes
- Turning it into another sprint retro. Keep it about the meeting.
- Only the facilitator's view counting. Every card weighs the same.
- Agreeing a change and not trying it next time.
- Running it every sprint. Every few sprints is enough.
Frequently asked questions
What does ROTI stand for?
Return on Time Invested. It originated as a simple 1-5 rating asked at the end of any meeting. Retromik's version turns it into a full retro — cards instead of a single number — so the team can explain the rating, not just give one.
How is ROTI different from a normal retrospective?
A normal retrospective reflects on the sprint's work. ROTI reflects on the retrospective practice itself — whether the meeting format, length, and facilitation are actually delivering value, or have become a ritual nobody questions.
How often should you run a ROTI retro?
Occasionally, not every sprint — quarterly is common. Running it too often turns 'evaluate the ritual' into its own stale ritual, which defeats the purpose.
Do participants need to stay anonymous for honest ROTI feedback?
It helps considerably. 'This retro wastes time' is much easier to write as an anonymous card than to say out loud to the facilitator directly. Retromik keeps cards concealed until a deliberate reveal, which is what makes candid feedback about the meeting itself realistic.
Who should facilitate a ROTI retro?
Ideally someone other than the usual retro facilitator, so the person whose meeting is being reviewed isn't also leading the review. Rotating facilitation also gives the team a fresh view of its retros.
Related templates
Lean Coffee Retrospective
Open Agenda
The only single-column format here — no categories, just an open, priority-ordered agenda the group builds together.
ViewStrengths, Risks, Learnings Retrospective
Strengths · Risks · Learnings
A balanced sprint review that looks backward and forward at once — Retromik's signature format.
ViewKaizen Retrospective
Muda · Mura · Muri
Toyota's lean lens for sprint retros — hunt waste, unevenness, and overload instead of vague complaints.
ViewRun a ROTI Retrospective with your team
Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.
Start free