Agile Flexing: Naming It Without Naming Anyone

What Agile flexing looks like

Someone uses their Agile knowledge to appear relevant rather than to make the work better. The framework becomes a credential to wave instead of a tool to use. It rarely looks like hostility — more often it looks like correction. The right term, supplied. The article, cited. The reminder that this is not really Scrum.

The tell is not what the person says. It is what happens to the room afterward.

• People stop offering half-formed ideas. They wait until a thought is bulletproof, which means most thoughts never get said.
• Questions dry up. Nobody wants to ask the thing that gets them corrected in front of their peers.
• The conversation narrows to the two most confident voices while everyone else waits for it to end.
• The retro gets polite. Nothing is wrong. Nothing is ever wrong.

The cost, in order

It ends at ownership, which is the whole point of the work. A team that cannot say the uncomfortable thing in a retro cannot own its delivery either — because owning delivery means saying we will not make that date while there is still time to do something about it. Flexing trains a team out of exactly the muscle you need most.

Why it is hard to raise

Every instinct you have is a trap. Name the person and you have made the retro a trial, and you have proven the room is unsafe in the act of complaining that it is unsafe. Say nothing and you have ratified it — the team now knows the person facilitating will not intervene, which is worse than saying nothing at all.

There is a third option, and it is the only one that works: name the effect, never the person.

Why I air it in the retrospective

This is one of the main reasons I am such a strong advocate for retrospectives. Not because the ceremony is sacred — because it is the only room built for this.

• It is the one ceremony about how we work, not what we shipped. Every other event on the calendar is about the product. This is the only one whose subject is the people doing the building.
• It is already on the cadence. I never have to call a special meeting — and calling one would announce a crisis and make the whole thing about a person before anyone said a word.
• It is the team’s room, not mine. Raising something there is not an ambush. It is the venue they already own, on the schedule they already expect.
• The alternative is the hallway. Anything I would say in a corridor I would rather say in a retro, because the hallway version turns into gossip and the retro version turns into an agreement.

The retrospective is where the team gets permission to say what needs to be said — regardless of where the behaviour comes from. That is the whole reason I protect the ceremony as hard as I do.

How I raise it in a retro

1. Prepare the ground before you need it.The easiest time to have this conversation is before there is anyone to have it about. If the team agreement already says how we disagree and how we treat each other, you are pointing at a commitment the team made to itself — not at a person. Build that early, and this conversation is half-solved before it starts.
2. Open on the effect, not the cause.I ask a version of: “When in the last two weeks did you decide not to say something you were thinking?” Nobody is accused. Everybody has an answer. And the pattern surfaces itself, in the team’s own words, without me having to allege anything.
3. Let the silence do its work.The first answer takes a while. Wait for it. If I fill the gap, I have taken the conversation back and the team learns that I will always fill it. The longest pause in the retro is usually the most useful thing in it.
4. Narrow to the behaviour, not the biography.“What happened right before you decided not to say it?” That question moves the room from feelings to a specific, observable moment — and a moment can be changed. A personality cannot.
5. Close on a commitment the team writes.Open the space, narrow the options, close on a decision. The output is not an apology, it is a line in the working agreement in the team’s own language. They wrote it, so they enforce it — and I am no longer the one policing it.
6. Handle the defensiveness privately, and without shame.Someone usually recognises themselves. If they get defensive in the room, I do not press — winning that exchange costs more than it gains. I take it one-to-one afterward: never in shame, always how can I help? Most people flexing are not cruel. They are insecure about their standing and reaching for the only lever they trust.
7. Come back to it once.Two retros later I ask the same opening question again. If the answers have changed, the team hears its own progress. If they have not, the agreement was decoration and we work on it in the open.

Inside the team, or outside it

The flex does not always come from a teammate. Just as often it arrives from outside the room — a stakeholder in the review, a manager who drops into standup, a coach from another train, an executive who has just finished a book. I air both in the retro. I handle them completely differently.

When it comes from outside, I take it out of the room and have the conversation myself, one-to-one, with the person or with their leader. Never in shame. Most of the time they have no idea what their presence costs — they think they are being helpful, or engaged, or rigorous. Told plainly and privately, most people adjust.

• I tell the team it is handled. Not the details — the fact. If the team raises something and never hears what came of it, they stop raising things, and I have taught them the retro is theatre.
• If I cannot fix it, I say so. Honestly, and then we change what we do control — who attends which session, how a review is structured, what gets pre-socialised so nobody is corrected in front of their peers.
• I never trade the team’s name for my own standing. The escalation carries my name on it, not theirs.

Flexing versus leadership

The distinction is not how much you know. It is what the knowing is for.

Same expertise. Opposite direction. One spends knowledge on standing, the other invests it in people — and only one of those compounds.

How I handle it — five moves

Protect the team. Surface the truth. Coach the behaviour. Everything above reduces to these five, in this order.

1. Notice.Recognise the moment knowledge stops being useful and starts being performance or intimidation. The signal is never the sentence — it is the room going quiet after it.
2. Surface.Bring the behaviour into the retrospective when it affects the team — whether it came from inside the team or from outside it. Name the effect, never the person.
3. Coach.Challenge the behaviour without diminishing the person. Most people flexing are not cruel; they are insecure about their standing and reaching for the only lever they trust. Take it privately, never in shame.
4. Protect.Create and defend a space where people can speak, question, learn, and disagree safely. When the behaviour comes from outside the team, the escalation is mine and it carries my name, not theirs.
5. Cultivate.Turn individual expertise into team capability, curiosity, and ownership. The point was never to make the expert smaller. It is to make everyone else larger.

The honest part

I am not writing this from a position of never having been in the room where it happened. I am writing it as the person who was responsible for the room and had to decide whether to say something. Both choices cost you. Saying nothing costs the team more.

A team that watches its Scrum Master notice something and stay quiet learns exactly what that silence is worth. So I raise it — in the retro, on the cadence, naming the effect and never the person — whether it came from inside the team or landed on them from outside. That is the job.

Knowledge is a tool. Ego is noise. Leadership builds others. Agile is not a performance — it is a practice, and the point of knowing more than the people around you is to lift them, not to stand above them. The goal was never to be the one who was right. It was to do right by the team.