Origins
Rants & Raves came out of a specific situation. A team had burned through multiple Scrum Masters and an RTE before I was assigned to them. They wanted nothing to do with another coach. They had decided agile was something being done to them, not with them, and every new face was just the next person who would try to make them change.
Walking in with a process improvement plan would have been the same move that had failed four times before. So no plan came in the door. Instead, an open meeting got scheduled and called Rants & Raves. The invitation was simple: come vent about anything bothering you. No agenda. No follow-ups you don't ask for. No notes shared with management.
The first session was uncomfortable. Some people said nothing. A couple unloaded everything. No one defended, redirected, or tried to solve. The coach asked questions — how long has that been going on?, what would good look like?, who else does this affect? — and then shut up and let the next person talk.
Over weeks the format did something unexpected. It wasn't producing a list of issues to fix. It was producing trust.
What It Actually Is
Rants & Raves is not a retro. A retro is part of a delivery cadence and assumes the team is willing to participate in process improvement. This format makes no such assumption. It is a standalone forum — running parallel to whatever else is happening — whose job is to give people permission to be honest without consequence.
Three things make the format distinct:
- It is not tied to delivery. Nothing on the rant board has to become a backlog item. Nothing has to feed a retrospective. The team is not being mined for improvement opportunities.
- It is explicitly emotional. The invitation is to vent, complain, and grieve. Not to be constructive. Not to be solution-oriented. Just to say what is hard.
- The coach is not problem-solving. The coach is listening, asking, mapping. Any action the coach takes is on their own time, behind the scenes.
Why It Works
The deepest insight from running this format with hostile teams: anti-agile sentiment is almost never actually about agile. By the time a team has decided to resist coaching, they are usually carrying frustrations that long predate the current coach — failed promises, broken trust with management, layoffs dressed up as transformation, agile transformations used as cover for cost cuts, or years of being told what to do without ever being asked what they think.
None of that surfaces in a normal retro. A team that has decided coaches are the problem will not honestly answer what could we try differently? They will answer what's pissing you off this week? — especially if the asker has earned the right to ask.
The format earns that right through three disciplines:
- No defensiveness. When someone rants about agile, the coach does not defend agile. When someone rants about a past Scrum Master, the coach does not explain. The complaint is the data; the coach is the recorder.
- Confidentiality is real. What is said in the room stays in the room. If it doesn't, the format dies in one session.
- Slow follow-through. The coach picks one or two of the smallest, most concrete blockers and clears them — quietly, without fanfare. The team notices. Over weeks, that pattern is what builds trust.
The Progression
Run with a hostile team, the format moves through phases. None of them are planned; they emerge as the room becomes safer.
Phase 1: Venting
The early sessions are just complaints. About process, about leadership, about the last coach, about the tools, about the meeting tomorrow. The coach listens, asks clarifying questions, and doesn't try to fix anything yet. The team is testing whether this is safe.
Phase 2: Small Wins
The coach starts clearing small obstacles — the ones the team has been carrying for months because no one ever asked. A pointless recurring meeting gets killed. A stale Jira workflow gets simplified. An access request that has been blocked for three weeks gets unblocked. None of it has to be agile. All of it is the coach proving that asking what's wrong leads to things actually getting fixed.
Phase 3: Common Ground
Now the team will engage. Not on big philosophical questions about Scrum, but on small concrete ones — what if the standup moved to a different time, what if WIP was limited to two for a couple of weeks. The coach can introduce agile concepts framed in the team's own vocabulary, anchored to problems the team has already complained about.
Phase 4: The Real Conversation
Eventually — and this is the phase that matters most — the team starts revealing what the resistance was actually about. In this case it turned out to be a deep distrust of management. Two failed reorgs in three years. A leader who promised autonomy and then took it back. Several talented people leaving in frustration. Agile, to them, had been a wrapper around all of that. Once that got named openly, real healing could start.
Phase 5: Healing
The team that loved agile by the end was the same team that had been hostile at the beginning. Nothing changed about them. What changed was the relationship — with the coach, with leadership (worked behind the scenes in parallel), and with the practices themselves. Agile became something they did because it worked for them, not something done to them.
When to Use It
This format is the right tool when:
- The team has cycled through multiple coaches without success.
- People show up to retros and don't talk, or talk only sarcastically.
- There is clearly a story underneath the resistance that no one is telling.
- Leadership is pressing for process change and the team is digging in.
- The trust deficit is so deep that asking the team to improve feels like an insult.
When It's the Wrong Tool
Equally important to know:
- Functional teams don't need it. A team that is already willing to engage with retros doesn't need a standalone vent forum.
- It can't be used to mine for performance reviews. The moment leadership asks what people said in there, the format is over.
- It is not a substitute for actual coaching. Once trust is built, the work of process improvement still has to happen. Rants & Raves is the bridge, not the destination.
- Don't run it forever. The format exists to rebuild trust. Once trust is there, it can fold back into normal retros, 1:1s, and team rituals.
The Coach's Job
Running this format well requires a specific kind of discipline. The coach is not there to defend agile, to defend leadership, to defend themselves, or to fix things on the spot. The coach is there to:
- Listen, without judgment. Including when the complaints are unfair, irrational, or directed at the coach personally.
- Ask, not advocate. Open questions, not leading ones. The team's words, not the coach's framework.
- Take notes privately. The coach is building a map of the team's actual pain. That map informs what the coach quietly clears between sessions.
- Protect the room. Confidentiality is the entire foundation. If a rant becomes a manager email, the format is dead.
- Be patient. The progression takes weeks to months, not sessions. Coaches who want fast wins should not run this format.
What It's Really About
Underneath the simple two-word name, Rants & Raves is a deliberate technique for one of the hardest situations in coaching: a team that has decided the coach is the problem. The format works because it rejects the premise. The implicit message: I am not here to change you. I am here to listen, and to see if I can earn your trust by being useful before being right.
That stance — psychological safety first, alignment second, technique a distant third — is the actual content of the practice. The two columns of rants and raves are just the wrapper.
Coaching Tips
Don't Bring an Agenda
The whole point is the team sets the topic. Showing up with talking points signals you're still trying to "fix" them. Walk in empty.
Protect Confidentiality Absolutely
If a single comment makes its way back to management without consent, the format is over. Tell the team the rules and then live them.
Clear Something Small Every Week
Pick the smallest, most concrete obstacle the team mentioned. Clear it quietly. Trust is built by useful action, not by promises.
Don't Defend Agile
When someone rants about Scrum, don't explain Scrum. Ask what about it specifically hurts. The defense reflex is the trap.
Listen for What's Underneath
The surface rant is rarely the real issue. Layoffs, broken promises, distrust of leadership — those are usually the actual content. Map them quietly.
Work Both Sides
What you hear in the room often tells you what needs to change above the team. Coach leadership in parallel — that's where the systemic fixes happen.
Summary
Rants & Raves is the coaching tool for teams that have decided coaches are the enemy. It rejects the assumption baked into most agile practices — that the team is willing to participate in their own improvement — and instead does the slow, unglamorous work of earning permission to coach them at all. Used with patience and real confidentiality, it can rebuild trust in teams that no one else has been able to reach. It takes longer than every other technique in the toolkit, and the work is mostly invisible while it's happening. But the team on the other side is genuinely willing — not compliant, not defeated, willing — and that's the difference between agile that lasts and agile that doesn't.