The announcement said they were removing unnecessary management layers to move faster.
Six months later, a product decision had been stalled for three weeks. Not because the team was struggling. Not because the call was complicated. Because the layer that used to hold accountability for exactly that kind of call had been reorganized out of existence. The question of who could actually make it floated above the org chart with no owner.
Nobody replaced what had been removed. They announced it, then moved on.
This is the part that doesn’t show up in flattening announcements: removing the layer doesn’t remove the accountability. It removes the address. And an accountability without an address is just a problem that belongs to everyone in general and no one in particular. I started to dig into this issue in What Middle Management Was Actually Doing.
The Design Question
When I built Nimbus, a multi-agent AI system with an explicit foreman/worker coordination architecture, I had to answer a question that most human organizations never ask out loud.
When two agents reach different conclusions about the same task, who wins?
In a human organization, that question has an implicit answer. Someone in the hierarchy has authority. The chain of command resolves the conflict. You don’t have to write it down because everyone carries it. We’re taught that early on. The org chart is a routing table for decisions, and it’s always running in the background.
In an AI system, there’s no implicit anything. I had to make it explicit. Deference hierarchies: which agent defers to which, under which conditions, and why. Escalation criteria: what counts as a genuine conflict versus a difference that the system should resolve on its own. Pre-execution audit logging: who’s accountable for what the system did before it did it, not after.
It took weeks to write down what any competent middle manager would have just known.
That’s the thing about implicit systems: they work until you try to replace them, and then you discover how much they were doing. The org chart wasn’t just a reporting structure. It was a decision routing table. It answered the “who wins?” question before anyone had to ask it. When you flatten the org, that routing table gets thinner. The question doesn’t go away. It just stops having a default answer.
What Happens to the Call
In a flat org, ambiguous calls don’t resolve more cleanly. They resolve more slowly, or they resolve through whoever is most persistent.
That second outcome is worth sitting with. When the hierarchy no longer answers “who wins?”, something else fills the gap. Usually: whoever sends the most messages, or whoever escalates to a shared stakeholder first, or whoever simply doesn’t yield. None of those are decision systems. They’re just noise with an outcome attached.
The leader who inherited broader scope after the flattening often absorbs this without naming it. They start showing up in threads they shouldn’t need to be in. They find themselves making calls that used to resolve two levels below them. They’re not doing it wrong. They’re doing it because the routing table has a gap, and the call has to go somewhere.
This is the work that migrates up when the layer comes out. Not the visible coordination work; AI can handle most of that. The work that migrates is the judgment about who should hold which call, under what conditions, with what authority. That judgment lived in the middle. When the middle is gone, it lives wherever it lands.
Usually: on the people the announcement quietly promoted into broader scope, without briefing them on what they just inherited.
Before the Announcement Goes Out
There’s one question that has to be answered before any flattening announcement goes out. Most organizations skip it.
When two people now at the same level of your new flat org reach different conclusions about an important call, who makes the decision?
In a hierarchy, the answer is structural. In a flat org, it has to be explicit. It has to be written down before the first ambiguous call arrives. If it isn’t, you haven’t designed a flatter organization. You’ve removed the mechanism that was making calls without anyone noticing, and left the calls with nowhere to go.
This isn’t an org chart exercise. It’s a decision routing exercise. For every major decision class: who owns it, who provides input, who has veto authority, and what the escalation path looks like when the owners can’t align. That document doesn’t exist in most organizations because the hierarchy made it unnecessary. Flattening makes it mandatory.
IMD’s 2026 research on organizational design put the frame plainly: “The winners in 2026 will not be those deploying the most models, but those reinventing how decisions, teams, and execution work.” The reinvention is the part most orgs skip. They announce the structure. They don’t redesign the routing.
Ask the room which calls are now unaddressed. The silence will tell you how much work is left.
The hierarchy went away. The accountability didn’t. It just lost its address.
ZenOne also produces trance music. The mixing arc behind his productions is at zenonemusic.substack.com.