A retrospective tool for teams that want to get better

Good retros start before the meeting.

Capture thoughts throughout the sprint. Reflect together. Turn insights into action.

How Muni works

  1. 01 During the sprint

    Set it down while it’s fresh.

    A thought takes ten seconds to write on Tuesday and is gone by Friday. Muni keeps a quiet place open all sprint — on your phone, between tasks, in your own words.

  2. 02 Sealed

    Nobody reads them yet.

    Not the facilitator, not your manager. Until collection closes, the only thoughts you can see are your own — and you can still change them.

  3. 03 Opening the sprint

    One batch. Random order. No names.

    Everything is revealed at once, shuffled. Shared screens never show who wrote a thought, when it was written, or anything that ties one person’s thoughts together.

  4. 04 Discover

    Thoughts become themes.

    Grouped by meaning, not keywords — with an optional AI draft the facilitator edits. The original words are never replaced. Votes are private until the round closes.

05 The retro

One topic. The actual words.

The shared screen puts what people wrote at the centre — not a summary of it. Voices are invited one at a time, and the room moves at the pace of the conversation.

Sprint 42 — Billing export
  1. Arrive
  2. Remember
  3. Discover
  4. Discuss
  5. Decide
  6. Leave
12:40

Topic 1 of 3

PR review turnaround

What would make a first review arrive within a day without making reviews shallower?

Improve

PRs sat waiting for review for two or three days. I stopped opening small PRs because it wasn’t worth the wait.

Might help: a daily 15-minute review window?

Improve

Reviews: I actually liked that reviews were slower this sprint — the comments were more thoughtful than the usual rubber stamp.

Keep

The retro experiment (daily review window) helped: my two PRs were reviewed the same day.

Improve

The daily review window didn’t change much for me — reviews still waited until someone had slack.

Try

Try a ‘review buddy’ pairing for the sprint so every PR has a named first reviewer.

Jonas, anything you’d add? Next voice NOpen the floor O
A discussion screen: the topic “PR review turnaround”, five original observations including two that disagree, and an invitation for Jonas to speak.
  • Voices, one at a time

    Invitations follow who is present and ready — never who wrote what. Passing is one tap, and it’s immediate.

  • A companion on every phone

    Follow the stage, vote privately, add context to a topic, or step out of the rotation.

  • Disagreement stays visible

    Opposing views sit side by side in their own words. Nothing is averaged into a paragraph.

06 Decide

Leave with something to try.

One to three concrete changes. Each has an owner who says yes, a signal that it helped, and a date to look back.

TakeawayReviews wait because nobody owns the first look.

Experiment

For the next sprint, reserve a 15-minute daily review window right after standup.

We’ll know it helped if
PRs wait less than one working day for a first review.
Owner
M Maya Reyes accepted
Look back on
Next retro

07 Next sprint

And it begins again, with “Last time, we said…”

Reserve a 15-minute daily review window right after standup.

Helped owner Maya Reyes

“Most PRs got a same-day first pass. Bigger PRs still waited.”

Write the sprint goal as one sentence at the end of planning and pin it.

Didn’t help owner Jonas Weber

“We wrote it, but planning overran and nobody looked at it again.”

Honest outcomes, including the ones that didn’t work. That’s the difference between a team that meets and a team that learns.

The privacy promise, exactly

Privacy

Your identity is verified to access each sprint. Your entries and votes are shown without your identity to teammates and facilitators. The service operator may technically be able to associate activity with accounts. Your wording can still reveal who you are.

We’d rather be precise than reassuring.

Hidden, everywhere shared

Stage, preparation view and exports never show who wrote an entry, who voted for what, or when something was submitted.

The facilitator

Sees nothing during collection except their own entries. Afterwards: everyone’s entries, anonymously, and who is present.

The operator

Muni stores who saved each entry so only you can edit it. There’s no button to join those records. This is application-level anonymity, not cryptography.

AI, only if chosen

Decided before collection starts. Entry text goes to the provider to draft themes — never names, emails, attendance or authorship.

muni

mu·ni /ˈmu.ni/ Filipino

From muni-muni: to reflect; to turn something over in your mind until you understand it a little better.

A moment to reflect. A chance to improve.

Bring it to your next sprint.