The retrospective ends. Three people dominated the conversation. Everyone else nodded along. The same issues were raised as last time. Nothing will change.
Sound familiar? I've sat through more retros like this than I can count — and I've facilitated enough of them to know exactly where the format breaks down.
This pattern persists because standard retro formats favor certain work styles and silence others.
Why Your Retro Keeps Hearing the Same Voices
Verbal processors think out loud and fill the space. They're not being pushy — they're processing in real-time, and the format rewards it.
Internal processors need time to formulate thoughts — time that fast-moving discussions don't provide. By the time they're ready to speak, the conversation has moved on.
Relating types may avoid surfacing concerns that could create conflict. They read the room and self-censor when tension is high.
Doing types may disengage entirely if the discussion feels unproductive. I've watched action-oriented team members literally check their phones three minutes into a retro that was going in circles.
The result: partial input, repeated issues, and a ritual that feels performative. But how many teams actually redesign the format instead of just blaming "low engagement"?
A Retro Structure That Works for Everyone
Silent Writing First (10 min)
Before any discussion, give everyone time to write:
- What went well?
- What didn't go well?
- What should we change?
This levels the playing field. Reasoning types get processing time. Creating types can explore without interruption. Everyone's input is captured before vocal dynamics take over.
I was working with an engineering team at a fintech company in Penang — twelve people, a mix of Malaysian and international team members. Their retros had become a weekly exercise in frustration. We introduced silent writing at the start, and the shift was immediate. The team lead told me afterward, "We got more honest input in that first ten minutes than we'd gotten in the last three retros combined."
Share All Perspectives
Have everyone post their notes — physical sticky notes or digital equivalent. Read through them together before discussing.
Now the quiet person's insight sits alongside the vocal person's. Ideas are evaluated on merit, not volume. This is where the real magic happens.
Structured Discussion
Instead of open forum:
- Group similar themes
- Discuss one theme at a time
- Go around the table for input on each
This ensures participation isn't optional for the quieter styles. Structure isn't bureaucracy here — it's equity.
The Questions That Unlock Each Style
Engage Reasoning Types
Ask: "What patterns do you see in the data?" "What root causes might explain these issues?"
They excel at systematic analysis. Direct questions activate their contribution. Don't just ask what happened — ask them to explain why it happened.
Engage Creating Types
Ask: "What if we approached this completely differently?" "What possibilities haven't we considered?"
They bring innovation to process improvement. Give them permission to think beyond incremental fixes. Some of the best process breakthroughs I've seen in client teams came from a Creating type who was finally asked the right question.
Engage Relating Types
Ask: "How did this sprint affect team dynamics?" "What's the unspoken concern we're not addressing?"
They sense what others miss. Their observations often identify root causes that the rest of the team can't see because they're too focused on the technical side.
Engage Doing Types
Ask: "What specifically should we do differently?" "What's the single most impactful change we could make?"
They orient toward action. Help them convert discussion into concrete improvements. When a Doing type says "this retro was actually useful," you know you're onto something.
Closing for Commitment
End with explicit commitments:
- What will we change?
- Who owns each change?
- How will we know it worked?
This satisfies Doing types' need for action and ensures the conversation produces results. It also signals to every style that their input matters — because it's being acted on, not just heard.
The Retro Checklist
Before:
- [ ] Prepared silent writing prompts
- [ ] Set up anonymous submission option if needed
- [ ] Planned structured rounds for discussion
During:
- [ ] Started with silent writing
- [ ] Shared all input before discussing
- [ ] Used structured rounds to ensure participation
- [ ] Asked style-specific questions
After:
- [ ] Clear, owned action items
- [ ] Follow-up scheduled to assess changes
- [ ] Thanked participants for specific contributions
When Every Voice Actually Gets Heard
Retrospectives that hear everyone produce better insights and more commitment to change. The quiet person's observation might be the breakthrough. The action-oriented person's impatience might drive real improvement.
Here's what I've learned from years of facilitating these: the value of a retro isn't in the talking. It's in what surfaces that wouldn't have surfaced otherwise. And that only happens when your format is designed for every style in the room — not just the loudest ones.
Every voice adds value. But only if your format lets them speak.
