What Replaces the Manager

Flat organizations do not usually fail because self-management does not work. They fail because someone deleted the manager and assumed the functions the manager performed would distribute themselves.

They do not. They fall on whoever notices first, which is usually the most conscientious person, who then burns out and leaves, and the group concludes that self-management was a nice idea.

What a manager was actually doing

Before you remove the role, list what it held. In most organizations it is about nine distinct things:

1. Deciding what gets done and in what order
2. Allocating who does what
3. Unblocking when something is stuck between people
4. Noticing when someone is drowning
5. Feedback, both directions
6. Pay decisions
7. Hiring and letting go
8. Holding context: connecting today's task to why it matters
9. Absorbing anxiety: being the person who is responsible when it goes wrong

Nine functions in one person. Removing the person does not remove the functions. Each one needs a home, and the homes are different.

Where each one goes

Deciding what gets done goes to roles plus the advice process. The person holding the role decides within their authority. Bigger calls run the advice process. See Roles, Not Jobs.

Allocating work mostly becomes self-selection: people take what they can do. This works better than expected and fails in one specific way, which is that the unglamorous work does not get taken. Name the unglamorous work as roles explicitly, rotate them, and make holding one visible and valued. If nobody will take it, that is information about whether it needs doing.

Unblocking goes to a named facilitator role, not to "everyone". A blockage between two people is precisely the thing that no one feels entitled to touch. Give someone that entitlement by name.

Noticing overload is the one that gets skipped, and it is the one that kills people. It does not distribute naturally, because the whole point of overload is that the overloaded person is the least able to raise it. So make it structural: a regular explicit round where everyone says their load out loud, or a named role whose purpose is that nobody is quietly drowning. See the check-in article.

Feedback needs a structure or it will not happen. Peer feedback is not spontaneous in most cultures; without a rhythm, people simply do not do it, and problems that would have been a conversation become resignations.

Pay needs its own process, and it is the hardest one. See Compensation Without a Boss.

Hiring and letting go becomes a group process with a defined path. This must be designed before you need it. Designing an exit process while you need to use it is how organizations end up with a person nobody can address for two years.

Holding context is the most underrated. A manager constantly translated between "why we exist" and "what you are doing today". Without that, work becomes a list of tasks with no visible connection to purpose, and motivation quietly drains. This belongs in your governance rhythm, out loud, repeatedly.

Absorbing anxiety is the one that cannot be assigned, and pretending otherwise is dishonest. In a hierarchy, when things went wrong there was a person whose problem it was. In self-management, it is genuinely everyone's, which means it lands hardest on whoever feels most responsible. Usually the founder, who has now removed their own authority but kept all of the anxiety. That is the worst of both arrangements, and it is extremely common.

The only real answer is collective practices that make the anxiety shared and visible: open numbers, an honest look at runway together, saying the hard thing in the room rather than protecting people from it.

The two failure modes

Structurelessness. No roles, no process, no explicit authority, "we all just figure it out". This does not remove hierarchy. It hides it, and an informal hierarchy is worse than a formal one because you cannot see it, cannot challenge it, and cannot leave it. It is held by whoever is most confident, has been there longest, or talks the most. Newcomers cannot find it and cannot get in.

If your group has no written roles, you still have a hierarchy. Ask a newcomer to draw it; they will be able to.

Bureaucracy. The overcorrection. Forty roles, a policy for everything, a process to change a process. Now the work is running the system. This happens when groups adopt a full framework at once instead of adding structure in response to actual tensions.

The rule: add structure only when a tension calls for it. Every role and every policy should be traceable to a specific thing that went wrong. If you cannot say what went wrong, you are adding structure because it feels organized, and you will pay for it in overhead.

Where it goes wrong

Deleting the manager on a Monday. Do it function by function over months. Take one of the nine, find it a home, watch it for a month, take the next.

The former manager stays and says they are not the manager. Everyone still treats them as one, because thirty years of conditioning does not lift because of an announcement. They have to actively refuse the role in visible moments: declining to arbitrate, sending people to the role holder, publicly backing a decision they disagreed with.

Assuming feedback and overload will surface on their own. They will not. They are the two functions that most need explicit structure, and they are the two most often left to "culture".

What good looks like

Someone is overloaded, and it is spotted by the structure in week two rather than by their resignation in month five.

Two people are stuck, and a named person has the standing to walk in and help, without it being a power move.

And the founder is no longer the only one who lies awake about the runway, because everyone can see the runway.

Try this week

Take the nine functions and write, next to each, the name of the person or role that holds it today. Be honest: if the answer is "nobody", write nobody. If the answer is "the founder, informally", write that.

The rows that say nobody are your next three months of work. The rows that say "the founder, informally" are your actual org chart.