The headlines are consistent. Capital One eliminated Scrum Master positions at scale. Meta cut them. Others followed. The rationale is the same across all of it: teams can self-organize, the role is redundant, agility doesn’t require a dedicated facilitator.
That rationale isn’t wrong about self-organization. It’s wrong about what the role was actually doing.
There are two versions of this role. One runs ceremonies. It schedules standups, facilitates retrospectives, updates the board, and reports status upward. That version is cuttable. It was always cuttable. If that’s what an organization hired for, eliminating it is a reasonable decision — and most organizations hired exactly that. The job descriptions they wrote, the interviews they ran, the scope they defined all produced a ceremony coordinator. They got what they asked for. Then they cut it for being exactly that.
The other version is something different. It operates at the intersection of team reality and organizational decision-making — close enough to the team to see what’s actually happening, credible enough with the people making decisions to translate in both directions. When a policy is about to land badly on a team, that version catches it before it hits. When a team is losing ground, that version names it before it shows up in a velocity chart three sprints later. It is, in function, an early warning system. And organizations are cutting it without knowing it exists.
Here’s what that looks like in practice.
Engineering identifies foundational technical work — infrastructure, tooling, the kind of investment that doesn’t ship a feature but makes everything downstream faster and more stable. Product sees off-roadmap activity and moves to block it. The ask doesn’t fit the frame product uses to evaluate priority, so the default answer is no.
What happens next depends entirely on whether anyone in that system can translate. The Scrum Master who understands the technical context well enough to grasp what engineering is actually building, and understands the product priorities well enough to see the connection product missed, can reframe the conversation. The foundation work isn’t a detour from the roadmap. It’s the prerequisite for the item already on it. Block the technical investment and the roadmap item gets slower, more fragile, or fails quietly in ways that won’t be diagnosable until later.
That outcome looks like alignment. Two functions moving in the same direction. Leadership sees a coordinated team and calls it a healthy process. What leadership doesn’t see is the conversation that produced it — or what happens to that dynamic when nobody is doing that work anymore.
This is the function organizations consistently misread. The role produces no artifact. No code, no design, no deliverable in a status report. What it produces is conditions — translated decisions, absorbed friction, stability when the organization is generating noise. Those things are invisible until they’re gone. And they’re gone before anyone can point to the moment they disappeared.
The same logic that causes retrospectives to fail in roadmap-adherence cultures causes this misread at the leadership level. The system measures what it can see. Ceremonies are visible. The lateral conversation that kept two functions from spending three weeks misaligned — that doesn’t appear anywhere. Leadership looks at the role and sees coordination overhead. They aren’t wrong about what they see. They’re wrong about what they’re not seeing.
Self-organizing teams are real. The best teams require less active facilitation as they mature. But self-organization describes how a team operates internally. It says nothing about what happens when the organization makes decisions that land on the team without context — when a policy changes, a priority shifts, or a resource gets pulled based on logic that made sense at the leadership level and creates damage at the team level. That gap doesn’t close itself. Someone has to stand in it, translate in both directions, and make sure the team knows someone is moving on it — so they don’t have to carry the weight of every organizational decision while also trying to build something.
When that role is gone, the team still feels every impact. They just feel all of it, without the buffer, without the translation, without anyone close enough to catch what’s fracturing before it compounds.
The organizations cutting these roles didn’t cut a ceremony coordinator. They cut the version that was doing all of that — because it looked the same from the outside.
They’ll find out the difference. Not immediately. In the quarter after that, when something that should have been caught early wasn’t — and nobody can explain exactly when it started going sideways.
Want the Experiment-Driven Agile Retrospective Toolkit?
If you’d like the Toolkit, reach out and I’ll send details (what’s included, pricing, and how teams use it). Or subscribe for new posts and updates.