PROCESS

Here is How to Build

Design

System

Processes, not departments

Ask a company to draw its process map, and the first draft is very often its organisation chart in disguise. The boxes read Sales, Finance, IT, Support, People: the departments, laid side by side. It looks like a map, and it is quick to draw, because everyone already knows the departments. But it answers the wrong question. An organisation chart shows who reports to whom. A process map shows what the company does.

The difference matters because the work does not follow the departments. Providing a subscription to a customer passes through sales, finance, IT and support before it is done; drawn as departments, it disappears into four boxes and belongs to none of them. Departments are also reorganised far more often than the work changes. A map built on the organisation chart has to be redrawn every time the chart moves, while the work it should show goes on exactly as before.

So name every box for what it delivers, not for the team that does it. A verb and an object work best: provide subscriptions, collect payments, support customers, plan the business. A name like that says what goes in, what comes out, and what the company would lose if the box stopped. It also survives a reorganisation, because the work it names is still there when the teams around it have moved.

The highest possible standard is to draw the map as the company's processes, not its departments, naming every box for what it delivers with a verb and an object, so that the map shows what the company does, follows the work across teams, and stays true when the organisation changes.

Key Takeaway: The first process map is often the organisation chart in disguise: Sales, Finance, IT, Support. But an organisation chart shows who reports to whom, while a process map shows what the company does. The work crosses departments, and departments are reorganised more often than the work changes, so a map built on departments hides the work and has to be redrawn with every reorganisation. Name every box for what it delivers, with a verb and an object, so the map follows the work and survives the next reorganisation.

A process map shows what the company does, not who reports to whom; name every box for what it delivers, not for the team that does it.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 3: The Map · Section: Processes, not departments

MarvinPro | October 2026

marvinpro.com

Every piece of work, once

A good map covers everything the company does, and covers it once. Every piece of work belongs to exactly one box. Nothing falls outside the map, and nothing sits in two boxes at the same time. That is easy to say and hard to do, and it is the test that turns a drawing into a map you can rely on.

The test is simple. Pick any piece of work the company does: a refund, a new hire, a price change, a security patch. Then try to place it. If it fits in no box, the map has a gap, and somewhere that work is being done by whoever happens to notice it, with no one designing it. If it fits in two boxes, the map has an overlap, and an overlap is usually where work is lost or done twice: each side assumes the other has it, or both do it their own way.

Placing work once does not mean a process works alone. Plenty of work starts in one box and finishes in another; a customer asks for something in one process, and another process carries it out. That is fine, as long as each piece of the work sits in one box and passes across a clear line to the next. What the map must never show is the same piece of work owned by two boxes at once. Where it crosses, it is handed on; it is never shared.

The highest possible standard is to test the map with real pieces of work until every one of them can be placed in exactly one box, closing every gap and removing every overlap, so that work which crosses from one process to another is handed on across a clear line rather than shared between two boxes.

Key Takeaway: A good map covers all the company's work, and covers it once: every piece of work belongs to exactly one box. Test it by picking real pieces of work (a refund, a new hire, a price change) and placing them. Work that fits nowhere is a gap, done by whoever notices; work that fits in two boxes is an overlap, where it is lost or done twice. Work may start in one process and finish in another, but each piece sits in one box and is handed on across a clear line, never shared.

Every piece of work belongs to exactly one box; where work crosses from one process to another, it is handed on, never shared.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 3: The Map · Section: Every piece of work, once

MarvinPro | October 2026

marvinpro.com

One page, read in a minute

The map has to fit on one page and be read in about a minute. That is not a rule of taste. It is what makes the map useful. A leader deciding where to invest, a designer about to change a process, a new manager trying to understand the company: each of them needs to see the whole at once, and a map that takes an afternoon to read will not be read at all.

Fitting on one page keeps the map honest. All its boxes sit at the same level, L0, as the previous discipline asked. If the page is crowded, the map has usually slipped down a level, and stages or parts of processes have crept in among the processes themselves. If a box needs a paragraph to explain it, its name is wrong, or it is really two processes sharing one name. Either way, the crowding is a sign to look again, not to find a bigger page.

So keep the map to as few boxes as the work allows, and no fewer. Too many, and the whole cannot be seen. Too few, and boxes become vague containers that hold several kinds of work, which brings the overlaps back. The right number is the one where every box names one clear piece of the company's work, every piece of work has a box, and the whole still fits on a single page that anyone in the company can read.

The highest possible standard is to keep the map on a single page that anyone can read in about a minute, with every box at L0, every name clear without explanation, and as few boxes as the work allows, treating a crowded page as a sign that the map has slipped down a level or that a name is hiding more than one process.

Key Takeaway: The map must fit on one page and be read in about a minute, because those who use it need to see the whole at once. One page also keeps it honest: a crowded page usually means the map has slipped below L0, and a box that needs explaining has the wrong name or hides two processes. Keep as few boxes as the work allows, and no fewer: too many hide the whole, too few become vague containers that bring the overlaps back.

The map fits on one page and is read in a minute: as few boxes as the work allows, every one at L0, every name clear on its own.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 3: The Map · Section: One page, read in a minute

MarvinPro | October 2026

marvinpro.com

A real example

When the software company first drew its map, it drew its departments: Sales, Finance, IT, Customer Support, People, Management. It fitted on a page and everyone recognised it. But when the team tried to follow a single subscription through it, from the first payment to the software running on a customer's machine, the subscription vanished. It passed through four of the six boxes and belonged to none of them.

So the map was redrawn as processes, each named for what it delivers. Plan the business. Sell subscriptions, which wins the customer and hands them on to the core. Provide subscriptions, which is the core: subscribe, activate, deliver and verify. Collect payments. Support customers, which holds the communication around a fix that the Rules and the Exceptions studied. Run IT. Develop people. Govern the company. Eight boxes, one page, and the subscription could now be followed from start to finish.

Then the team tested it with real work, and the refund failed the test. It fitted in two boxes: the support process promised refunds, and the payments process paid them. Each side assumed the other owned the refund, and some refunds were promised and never paid. The fix was to place the refund once. Paying it back belongs in the payments process; the support process takes the request and hands it across a clear line. The overlap closed, and the missing refunds stopped. How each of these boxes is sorted, linked and owned is the work of the disciplines that follow.

The company's first map was its departments; redrawn as eight processes named for what they deliver and tested with real work, it showed a refund owned twice and paid by no one.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 3: The Map · A real example

MarvinPro | October 2026

marvinpro.com

The Map

The map shows the company's processes, not its departments. The first draft is often the organisation chart in disguise, but an organisation chart shows who reports to whom, while a map shows what the company does. The work crosses departments, and departments change more often than the work. So name every box for what it delivers, with a verb and an object, and the map follows the work and survives the next reorganisation.

A good map covers every piece of work once. Test it with real work: a refund, a new hire, a price change. Work that fits nowhere is a gap, done by whoever notices; work that fits in two boxes is an overlap, where it is lost or done twice. Work may start in one process and finish in another, but each piece sits in one box and is handed on across a clear line, never shared.

And the map fits on one page, read in about a minute, with every box at L0 and every name clear on its own. A crowded page means the map has slipped down a level; a box that needs explaining has the wrong name or hides two processes. Keep as few boxes as the work allows, and no fewer, and the map becomes the one picture of the company that anyone can read, and the ground on which each process is sorted, linked and owned.

The map is the company's processes on one page: each named for what it delivers, every piece of work placed once, as few boxes as the work allows.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 3: The Map · Chapter Outcome

MarvinPro | October 2026

marvinpro.com

Think Simple.