A retrospective tool for teams that want to get better
Capture thoughts throughout the sprint. Reflect together. Turn insights into action.
The problem
Two weeks of work, one hour, a grid of faces on a call. You’ve probably been in this one.
Asked what went well, everyone remembers the last three days. The thing that actually hurt, in week one, never comes up.
With Muni Write it down the moment it happens — a line is enough, on your phone.
The others have something to say. There’s never a good moment to unmute and say it.
With Muni Everyone answers a check-in in one tap, or adds a thought without taking the floor.
When everyone can see who said it, the candid version turns into something safe — or nothing at all.
With Muni Thoughts stay sealed until collection closes, then show up together, without names.
Action items are vague, have no owner, and nobody looks at them again — so the same problem comes back every sprint.
With Muni One to three experiments, each with an owner who said yes — and they open the next retro.
So Muni starts the retro before the meeting, lets everyone in, and remembers what you agreed. Here’s how
A retro with Muni
The facilitator runs the shared stage. Everyone else holds the private half on their phone. Here’s the same retro from both sides — and which problem each step answers.
FacilitatorOpens the stage. Faces light up as people join, and last time’s experiments come back first. A cue in the corner, on their screen only, says what to say and do next.
EveryoneOpens Muni on their phone — that’s joining — and sees last time’s changes; the facilitator records whether each one actually helped.
Answers“Agreed three times. Revisited never.”FacilitatorSees how many have voted — never who, or for what — and moves on when most have. The shared screen has no vote buttons; their own votes go on their phone too.
EveryoneVotes on their own phone, with at most half as many votes as topics — so choosing means leaving something out. The quiet ones decide the agenda too.
Answers“Two people talk. Seven are muted tiles.”FacilitatorReads the topic’s thoughts with the room first. Their cue suggests when to ask how it showed up, when to share the answers — counts and lines, never names — and what to note.
EveryoneAnswers in one tap, or adds an example or a question without taking the floor.
Answers“The hard thing gets softened.”FacilitatorTurns the room’s idea into one to three experiments, each with a sign it helped and an owner.
EveryoneThe owner says yes on their phone. The experiment opens the next retro — to see if it worked.
Answers“Action items are vague and have no owner.”FacilitatorPublishes the recap — filled in from what the retro recorded, then in their own words.
EveryoneOne page to come back to: who came, what the team will try and who owns it, and what each topic left behind.
Answers“Monday’s lesson is gone by Friday.”Or watch the whole sprint in 75 seconds, from the first thought to the last yes
01 During the sprint
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 a room of your own if you pick one of eight characters. If the signal drops, it waits and sends when you’re back, and tells you plainly when a thought has reached the sprint.
02 Sealed
Not the facilitator, not your manager. Until collection closes, the only thoughts you can see are your own — and you can still change them.
03 Collection closes
When the facilitator closes collection, everyone’s thoughts appear at once on the sprint’s page, shuffled — so the team can read them before the retro. Nothing on screen says who wrote a thought, or ties one person’s thoughts together.
04 Before the retro
If it helps, the facilitator ticks the thoughts that belong together and names them — a theme, with a question to open it. Every thought stays exactly as written, and whatever isn’t in a theme becomes one more topic: Everything else.
05 The retro
The shared screen puts what people wrote first, not a summary of it. What the room says about it comes after — answers to a check-in, lines added from phones — without names.
Now talking about · topic 1 of 3 · 5 votes
PR review turnaround
What would make a first review arrive within a day, without making reviews shallower?
On everyone’s phone How did this show up for you?
PRs sat waiting for review for two or three days.
The daily review window helped: my two PRs were reviewed the same day.
I liked that reviews were slower — the comments were more thoughtful than the usual rubber stamp.
A ‘review buddy’ for the sprint, so every PR has a named first reviewer.
What the room said without names
How it showed up
4 felt this · 1 not in their work · 1 needs context
Did last time’s experiments help? What matters most? Then the talk, topic by topic, and what to try. The steps open and close the vote themselves.
Only on the facilitator’s screen, never when presenting: a line to say and the one thing to do next. A first retro can be run from it alone.
At most half as many votes as topics — six topics, three votes each — cast on everyone’s own phone. The stage has no vote buttons; the facilitator sees how many have voted, never who.
Opposing views sit side by side in their own words. Nothing is averaged into a paragraph, and nobody is called on.
06 Quiet ways in
When it helps, the facilitator asks how a topic showed up for people. One tap is a whole answer; a line is optional. Nothing is shown until the facilitator shares it — and never with a name.
07 Agree
One to three concrete changes, each with an owner who says yes, a sign that it helped, and a date to revisit.
We’ll rememberReviews wait because nobody owns the first look.
Experiment
For the next sprint, reserve a 15-minute daily review window right after standup.
08 Next sprint
Reserve a 15-minute daily review window right after standup.
“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.
“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.
Privacy
Muni uses your account information and contributions to provide and protect the service. We don’t sell your personal data, use your contributions for advertising, or use them to train AI models.
Until the facilitator closes collection, nobody on your team can read what you wrote — the facilitator included. Then the sprint sees every thought at once, in random order, without names.
Sprints are encrypted in the browser by default, before anything reaches Muni’s servers, and the servers don’t hold the keys to read them. A facilitator can set a sprint up without encryption, and it says so. Muni still knows who wrote each thought and when, and your wording can still give you away.
You sign in with a passkey — your fingerprint, face or screen lock. It’s the only way in: there’s no password to steal, and no email that can sign you in. If a facilitator loses theirs mid-sprint, a workspace owner can take over running it.
The app has no analytics, ad trackers or session recording, and no thought is sent to an AI service.
Open source
Muni’s source code is public under the Apache 2.0 license. Read how a thought is sealed on your device, check what the server keeps, or run your own copy on Cloudflare.
The whole encryption design is written down, so anyone can check it. If you spot a problem, tell us privately.
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.
Your first evening
A new account opens with five short lines on how a sprint in Muni goes. Then a firefly settles on the one real control to use next — from naming your team to starting the first retro — with a line on what it’s for.
Join from your team’s QR code, a link or an emailed invitation, and sign in with a passkey — no password. Use it in the browser, or install it on your phone.