How to Run a Team Retro When Everything Lives on WhatsApp
For a lot of small teams, WhatsApp is the office. Client requests, quick questions, voice notes, "did you see this?" — it all happens there, and honestly it works. The problem is what a retro looks like in that world: a call nobody can schedule, a conversation that scrolls away, and no record of what the team decided to change.
A retrospective is just a short, regular look back. It doesn't need a meeting room, a facilitator or sticky notes. Here's a version built for teams that already live in chat.
Use three prompts, nothing more
The simplest retro format asks the same three things every time:
- What went well? — what we'd happily repeat.
- What got in the way? — where we lost time, or someone was stuck.
- What will we change? — one concrete action, with an owner.
Keeping it to three stops the retro turning into a general complaints session, and it makes replies quick to write.
Run it in a 24-hour window
Pick a day — the last working day of your cycle works well — and post the three prompts in the team chat in the morning. Give everyone until the next morning to answer, whenever suits them. That matters for teams spread over more than one time zone, because nobody has to be online at the same moment.
- Short text answers are fine. Voice notes work too, as long as someone writes up the gist afterwards.
- Ask people to answer before reading others' replies, so the first response doesn't anchor everyone.
- Keep it blameless: talk about what happened, not who did it.
Turn the chat into one page
This is the step most teams skip, and it's the one that makes a retro worth doing. Someone — rotate the job — reads the replies and boils them down to a few lines under each prompt, plus the single action the team agreed on. Two rules keep it honest:
- Group repeated points instead of listing them separately. Three people mentioning the same delay is a signal.
- Limit yourselves to one or two actions. A retro with eight action items produces none.
A retro that stays in the chat is a conversation. A retro that ends up in a place you can find again is a habit.
Keep the result where the work lives
WhatsApp is a poor archive. In three months nobody will scroll back to find what you decided. Record the outcome next to the work itself. In Alignr, a retrospective has three lists — achievements, problems and action items — which map directly onto the three prompts above, plus a notes field. You can attach a retro to a specific sprint or run a standalone one, list who took part, and export it as PDF, Word or JSON if you need to share it with a client or a partner.
Retrospectives are part of the Team plan ($2 per user per month, billed in USD). If you're on the free plan, the same three-prompt routine works fine in a shared document until you decide the upgrade is worth it.
Check last time's action first
Before you send this cycle's prompts, look at the action from the previous retro and ask a single question: did we do it? If yes, good. If not, either do it now or drop it honestly. Checking your last commitment is what stops retros from becoming a ritual with no effect.
A quick template you can paste
"Sprint check-in 🙌 Reply by tomorrow morning: 1) What went well? 2) What got in the way? 3) One thing we should change next cycle. Keep it short — voice note is fine."
New to sprints altogether? Start with planning your first sprint in one afternoon, and see how async standups across Africa's time zones keep the days in between just as light. Ready to try it? Start free.