Roles, Not Jobs

You removed the job titles. You said everyone is equal. Six months later, three people are doing everything, nobody knows who decides what, and the person who used to be the manager is still, somehow, the person who decides.

Removing hierarchy does not distribute authority. It just hides where the authority went. Roles are what actually distribute it.

A job is a bundle, and the bundle is the problem

A job title is an unexamined package of about fifteen different responsibilities, held together by one person's name and one salary.

"Operations Manager" might mean: supplier contracts, the office lease, onboarding new people, the tooling budget, health and safety, and being the person everyone asks when something is unclear. Six distinct things, with six different skill requirements, six different decision rights, and no reason at all why one human should hold all of them.

The bundle causes specific, predictable damage:

It hides authority. Nobody knows whether the Operations Manager can sign a lease or has to ask. Including, often, the Operations Manager.

It makes exit catastrophic. When they leave, fifteen unlisted responsibilities leave with them. You discover what they were doing by finding out what stopped happening.

It concentrates load. Someone competent accumulates responsibilities because they are the safe pair of hands, and there is no natural point at which the bundle is examined.

It blocks contribution. Someone who would gladly run supplier contracts cannot, because that is part of a job somebody else holds.

What a role is instead

A role is one named responsibility, with a purpose, some accountabilities, and explicit authority.

One person can hold several. Several people can hold pieces of what used to be one job. Roles get created, changed and dissolved by the group as the work changes, without anyone being hired or fired.

Write one like this:

Role: Supplier Contracts

Purpose: Our supplier relationships are on terms we can afford and can exit.

Accountabilities:

- Negotiating and signing supplier agreements under 10k a year

- Keeping a current list of what we are committed to and when each ends

- Flagging any renewal 60 days before it auto-renews

Authority: Signs agreements under 10k without approval. Above 10k, seeks advice from Finance and the affected team, then signs.

Held by: Ana, since March 2026.

Four short pieces and a name. That is the whole artifact.

The part everyone skips

Authority is the point. A role description that lists responsibilities but not decision rights has changed nothing. It has only written down who does the work while leaving unclear who gets to decide about the work, which is exactly the ambiguity you were trying to remove.

Every role needs a sentence that starts with a verb like signs, approves, decides, spends, hires, ends, and a boundary where that authority stops.

If you cannot write that sentence, the role is not real yet. You have described a task, and the decision still lives somewhere unnamed, which in practice means it lives with whoever is most senior.

Purpose over tasks

Write the purpose as a state of the world, not a list of activities.

Not: "Runs the onboarding process."

But: "Someone who joins us is useful and comfortable within two weeks."

The difference shows up the moment reality changes. A role defined by tasks keeps doing the tasks after they stop working. A role defined by a purpose lets the holder notice the purpose is not being met and change the tasks without asking permission.

How roles change hands

This is the mechanic that makes the whole thing worth doing, and it is much lighter than hiring.

Creating one: someone names a tension ("nobody flags renewals, we auto-renewed twice"), the group proposes a role, runs it through consent, and someone takes it.

Filling one: ask who wants it. Not who is qualified on paper. Someone who wants a responsibility and has to learn half of it will usually outperform someone who has the skills and resents the work.

Leaving one: you may hand a role back. Out loud, at a governance meeting, without it being a failure. A group where handing back a role is shameful is a group that will discover its overload through burnout instead.

Ending one: roles are allowed to die. Review them. If a role has had no work in six months, dissolve it rather than leaving it on a chart as decoration.

Where it goes wrong

Writing the org chart you already had. If your roles map one-to-one onto your old job titles, you have renamed things. Split them until each is genuinely one responsibility.

Roles with no authority. Covered above, and it is the most common failure by a distance.

Too many, too fast. Forty roles for eleven people is a filing system, not an organization. Start with the responsibilities that are currently ambiguous or currently overloading someone. Add roles when a tension calls for one.

Never reviewing. Role definitions go stale faster than anyone expects. If nobody has changed a role definition in a year, either your work is not changing or your governance is not working.

Assuming the role holder does all the work. A role holder is accountable for the purpose being met. They can and should get help. Accountability and labor are different things.

What good looks like

Someone new asks "who decides whether we can buy this?" and gets an answer in ten seconds, from a document, without asking a founder.

Someone leaves, and the group can see the four roles they held, and can redistribute them in one meeting instead of discovering the gaps over three months.

Someone is overloaded, and it is visible as six roles next to one name rather than as a person who seems tired.

Try this week

Take the most overloaded person in your organization. Sit with them and list every distinct responsibility they actually hold, not what their title says. Expect between eight and twenty.

Then, for each one, ask the only question that matters: what can the holder of this decide without asking anyone?

The ones where nobody can answer are where your hierarchy is still hiding.