Chapter 9. The branch: cells, not jobs

A working draft, November 2026. This book is being written while The Grove is being built; expect it to change. Checked against the build as it stood on 1 November 2026.

In this chapter

• What bundling a person, a pile of work and a place in a hierarchy into a job costs
• What a branch holds, a purpose, accountabilities, domains and practices, and why no person is named
• How seats and crews bring people in, so several hats can be worn in the open
• The one rule that stops a single person deciding alone in a forum
• How new branches grow from the work, and how branches split, join and fade

Every few years a new way of organising arrives with its own vocabulary, and the sceptic has seen enough of them to know the pattern.

Departments become tribes. Managers become leads. Job descriptions become roles. A consultant draws circles instead of boxes, and for a while everyone talks differently. Then, quietly, the same people do the same work, answer to the same person and guard the same territory. The words changed. The organisation didn't.

So when we say that an organisation on The Grove is made of branches rather than jobs, a fair reply is: isn't a branch just a job title in a nicer coat?

It's a good question, and this chapter tries to answer it honestly. The short answer is that a job is shaped around a person, and a branch is shaped around a piece of work. That sounds like a small distinction. In practice it changes almost everything about who decides, who carries what, and how the organisation grows.

What the job costs

A job bundles three things together that don't belong together: a person, a pile of work and a place in a hierarchy.

Because they're bundled, they move as one. When the person leaves, the work leaves with them, and someone spends weeks discovering what they actually did. When the work changes, the job description doesn't, because rewriting it means renegotiating someone's position, pay and pride. When the hierarchy changes, people lose work they were good at and gain work they never asked for, because the chart moved and the work was stapled to it.

The bundle also forces a lie. Most people in most organisations do several kinds of work. The finance person also runs the office move. The developer also answers the hardest customer emails because they're the only one who understands the problem. None of that appears anywhere. The job title says one thing; the week says another. So the real shape of the organisation lives in people's heads, invisible to anyone trying to understand it, and lost when they go.

And jobs make empires possible. A job comes with a territory, and territory can be expanded. Hire two people under you, and your job grows. Hire ten, and you have a department. Nobody designed this as a way to accumulate power. It's simply what happens when the unit of organisation is a person with a patch.

The cost to the business is slowness and fragility: work that can't move without moving people, knowledge that walks out of the door. The cost to people is quieter. They're asked to be one thing on paper and several things in practice, and to defend a patch they may not even want.

A body with no one in charge

When we began designing The Grove's structure in early September 2026, the branch was the first thing we drew. Before forums, before proposals, before Wise-Eye, there was the question of what an organisation is made of.

The picture that unlocked it came from the sea. The Portuguese man o' war looks like a single jellyfish, but it isn't one. It's a siphonophore: a colony of many small, specialised units living as one body. Some keep it afloat. Some catch food. Some digest it. Some defend. Some reproduce. Each is shaped entirely by what it does, and none of them is in charge.¹ The body works because every part knows its function and the parts fit together, not because something at the top is directing traffic.

That gave us the starting point. The unit of an organisation isn't a person or a department. It's a function: something that needs doing, with the shape that doing it requires.

What a branch is

A branch, in an organisation on The Grove, is a part of the organisation shaped around a piece of work. It holds four things.

A purpose: the potential it exists to serve. When someone senses that something isn't right, or could be better, it's the purpose they're sensing it against.

Its accountabilities: the ongoing activities others in the organisation can expect of it. Not tasks to be ticked off, but the work it answers for, week after week.

Its domains: the things it controls. The website, a mailbox, a bank account, a supplier relationship. Think of them as keys. If a branch holds the key to the website, changes to the website go through that branch.

And its practices: how the work is done. These are agreed in the branch's own forum, and they bind everyone doing that work, including the AI. They're written in the plural, "we publish on Thursdays", so that a second person could step in and fit.

Notice what's missing. There's no person in that list. A branch says what needs doing and how, not who does it.

A branch is also a container. It can hold smaller branches inside it, each with its own purpose, accountabilities, domains and practices. Holacracy, the most worked-out boss-free system before ours, uses two separate units for this: circles, which contain things, and roles, which do things.² We merged them. A branch is both its function and a home for the smaller functions inside it. As Chapter 5 put it, each part is also a whole. That one choice makes the structure fractal: the same shape at every scale, from the root of the organisation down to a single small piece of work.

Because branches nest, every accountability has a path, like an address: root, then branch, then smaller branch, then the accountability itself. Two branches can share a name. Two can both be called "Outreach", say, in different corners of the organisation. They can never share a path. Nothing gets confused for something else.

Seats and people

If the branch doesn't name a person, where do people come in?

Each branch has a seat, held by a steward, as Chapter 7 described. Nobody takes a seat by their own proposal, unless they'd be deciding alone anyway. Someone else proposes them, and the forum around the branch's parent decides. We haven't yet built a step where the person named says yes. A seat can be shared, by two people co-stewarding or by a crew of the people doing the branch's work. When a shared seat takes part in a decision it carries one seat's voice, and each holder takes part as a person. Anyone can resign a seat, with a notice period they set themselves. If a seat empties, the branch above holds it meanwhile, so the work isn't orphaned.

Work is assigned to branches, never to people. And inside a branch, nothing hands out the pieces. Anyone in the crew can take a piece in hand, and the system shows who has it so it isn't dropped. Who takes what is the crew's business.

This is where the honest answer to the sceptic begins. Because a person can hold several seats, the finance person who also runs the office move can say so: they hold the finance branch and the premises branch. The structure finally shows what the week already knew. People wear more than one hat, and now they can do it in the open.

One rule instead of many

Forums are made of people, not branches. A branch is governed in one forum: the stewards of its parent and of its sibling branches, with the branch's own steward taking part as a person, and never the people of the branches below it. That's where its remit is decided. The root has no parent, so it's governed by its own stewards and the stewards of the branches grown directly from it, and that's where its remit and purpose are decided. Someone holding several seats can sit in many forums, and a crew carries one seat's weight. Autonomy over the means, accountability for the ends.

That raises an obvious problem. What if one person holds a branch and all the branches inside it? Their "forum" would be a room with one person in it, approving their own decisions.

For a while we had a cluster of separate rules to deal with this and related problems. One to stop empire-building. One to let a solo founder get started. One about when a small piece of work could become a container. One saying no branch is ever governed by a single person. On 22 September they collapsed into a single rule.

A forum with fewer than two distinct people doesn't decide. Its decisions route up to the nearest forum that does have two or more, and if none does, they end at the root. One person holding several branches is still one person in the room.

A great deal follows from that one sentence.

A solo founder builds freely, because there's nobody else yet, and everything routes to the root where they sit. The moment a second person takes a seat, decisions start being caught by a real plurality. Nobody can build an empire alone, because however many branches they hold, they can never be the only person in the room where those branches are decided. And a leaf held by one person, a branch with nothing inside it, becomes a container only with consent from the forum around its parent, because the forum around it, with nothing inside it yet, has only one person in it. A leaf whose seat is shared by two or more people can decide that for itself.

That last point matters. Only structural change routes up. The day-to-day work stays local, with the people doing it.

How structure grows

The root of the organisation is just another branch. It holds the purpose, and anything that hasn't found a home yet. At the start, that's everything. As branches form, accountabilities move out of the root to the branches that carry them.

New branches don't come from a design session. They grow from the work. Work that no branch holds rises to the branch above, and at the root it becomes a question for the forum: is a job missing here?

Wise-Eye watches for the pattern. When a kind of work arrives four or more times in four weeks, spread over at least two, with no accountability covering it, whether it comes from outside or from the organisation's own committed work, Wise-Eye offers the branch an accountability for it. A person raises that as a proposal, and the forum decides. And when a branch answers for two or more things and one of them is clearly defined, repeating work, it can be offered as a branch of its own.

The organisation's reading, the continuous view of its traces described in Chapter 5, shows where a branch wants to grow, wither, split or merge. From there one of a branch's jobs can grow into a branch of its own, or a job that reads as two can be split. A branch's jobs can join another branch where that work already lives, and a branch can be folded back into its parent. And a branch that fades is composted. We're building towards twinning, a sibling that tests a different approach with a hypothesis, a measure and a review date, and towards spinning a branch off into an organisation of its own. What it holds moves on to other branches; its name stays in the record.

One thing the reading never does is suggest merging two branches because the same people hold both. People wear the hat of the branch they're working in. Two hats on one head are still two hats.

We should be plain that most of this hasn't yet met real organisations in daily use. The rules have been walked through in test runs and simulated organisations. How the four-in-four-weeks threshold feels in a busy month, or how often jobs grow into branches, is something only real use will show.

How we decided

The name took a while. We considered "zooid", the biologist's word for each unit of a siphonophore, which was accurate and impossible to say in a meeting. "Cell" was close but sounded like a spreadsheet or a prison. "Bough" was lovely and slightly too poetic. We chose "branch" because it nests, a branch grows smaller branches, and because it fits the picture of a tree with a root.

Merging circle and role into one unit was the biggest structural choice. It cost us the familiarity of Holacracy's terms, and some people who know that system will miss the distinction. We judged that a single unit, the same at every level, was simpler to understand and harder to game.

Collapsing several rules into the routing rule was the most satisfying. Each separate rule had edge cases that the others had to patch. One rule, based on counting distinct people in the room, covered all of them.

We rejected two things that kept coming back. One was an "expandable" flag on roles, a setting that said whether a piece of work was allowed to grow smaller pieces inside it. The routing rule already gates that, through consent from the forum around the leaf's parent, so the flag was redundant. The other was a "Project" object with an owner and a plan. It looked harmless. It was the project manager smuggled back in: a person with a patch and authority over others' time. Work that needs doing belongs to a branch.

And we decided never to infer a merge from shared people. It would be easy to read overlap as duplication. It usually isn't.

What's still uncertain: whether people used to jobs will find it natural to say "I hold three branches" rather than "my job is". Whether shared seats will feel like real shared stewardship or slide into one person doing it and the others watching. Whether the routing rule, so clean on paper, will feel right when a two-person forum has to decide something one of them cares about far more. We think it will. We don't know yet.

What you might take from this

A job title shapes the work around a person. A branch shapes it around what needs doing, and lets people step in, share and step out without the work falling apart.

The sceptic is right that renaming jobs changes nothing. What changes things is organising the work first, so people can wear more than one hat honestly.

Notes and further reading

On the holon, a part that is also a whole: Koestler, A. (1967), The Ghost in the Machine, Hutchinson. On nested circles governed by consent, which Holacracy built on: Endenburg, G. (1998), Sociocracy: The Organization of Decision-Making, Eburon. On the different ways organisations group their work, by function, by market and more: Mintzberg, H. (1979), The Structuring of Organizations, Prentice-Hall.