PROCESS

Here is How to Build

Design

System

One box, one owner

The map now has its boxes, their kinds, the value they add and the links between them. What it does not yet have is anyone who answers for them. This discipline names them. Every box on the map has one owner: one person who answers for that process as a whole, for its outcome, its design and the links it makes with other boxes. Not a team, not a committee, not a department. A single person, so that when something goes wrong in the process, there is no question whose it is to put right.

The owner is not the person who does all the work. Most processes are worked by many people, often in several departments, and the owner may do little of it directly. Nor is the owner automatically the head of whichever department does most of the work, because boxes cross departments, and a department head answers for people, not for a flow. The owner answers for the flow: whether it delivers what it is for, and whether its design still fits.

Two owners are no owner. A box shared between two people has the same flaw as work shared across a link: each assumes the other has it. The Sub volume names owners too, but at a different height. A sub-process owner answers for a part, and for the result the larger process depends on. A box owner answers for a whole process, to the company.

The highest possible standard is to name one owner for every box on the map (a person who answers for the process as a whole), to choose that person for the flow rather than for the department, and never to let a box be owned by two.

Key Takeaway: Every box has one owner: one person who answers for the process as a whole, for its outcome, its design and its links. The owner is not the person who does all the work, nor automatically the head of the department that does most of it, because boxes cross departments. Two owners are no owner, for the same reason that shared work sits on neither side. Sub's owners answer for a part to the larger process; box owners answer for a whole process to the company.

One box, one owner. Two owners are no owner, because each assumes the other has it.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 7: Owners · Section: One box, one owner

MarvinPro | October 2026

marvinpro.com

Owners keep the links

Links requires every crossing to be agreed by both sides. Owners gives those sides their people. A link is kept by the owners of the two boxes it joins: they agree what passes, when it passes and what received means, and they keep that agreement true as both boxes change. A link does not get an owner of its own. A third owner standing between two boxes would only add another crossing.

Keeping a link means the rule from Links is held by someone. Any change on either side that touches the link goes to the other side's owner before it goes live, and the agreed cases are run across it. The owner of the side making the change answers for raising it; the owner of the other side answers for checking that it lands. A small update no longer depends on someone happening to think of the link.

Sometimes the two owners cannot agree. A change suits one box and costs the other. A disagreement on a link along the value stream goes to the end-to-end process owner: the one person who answers for the customer's outcome across the whole stream, who decides against that outcome. A disagreement on any other link goes to the management process. In neither case does it go to whoever pushes hardest, because the link would then belong to the louder side.

The highest possible standard is to have every link kept by the owners of the two boxes it joins, never by a third owner, to make the owner of the changing side raise every change and the owner of the other side check it lands, and to send disagreements to the end-to-end process owner or the management process, never to whoever pushes hardest.

Key Takeaway: A link is kept by the owners of the two boxes it joins, who agree it and keep it true as both boxes change; it never gets a third owner of its own. The owner of the changing side raises every change that touches the link, and the owner of the other side checks it lands, before it goes live. Disagreements on the value stream go to the end-to-end process owner, and others go to the management process. Neither goes to whoever pushes hardest.

A link is kept by the owners on its two sides. When they cannot agree, it goes up, never to whoever pushes hardest.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 7: Owners · Section: Owners keep the links

MarvinPro | October 2026

marvinpro.com

The end-to-end process owner

Box owners answer for their boxes, and between them they keep the links. But the customer experiences neither boxes nor links. They experience the value stream: the thread that runs through four or five boxes from first contact to renewal. Someone has to answer for that thread as one. That is the end-to-end process owner: the owner of the value stream, who answers for the customer's outcome across every box the stream touches.

The end-to-end process owner does not own the boxes, and does not do their work. Each box keeps its own owner. The end-to-end process owner's work is different: to make sure every box and every link on the stream has an owner who actually holds it, and that those owners are working towards the same outcome. A box owner can deliver everything their box promises while the customer still falls between two boxes. The end-to-end process owner is the one who sees that fall, and answers for it.

When a gap opens between boxes, it is the end-to-end process owner's to close. Not by taking the work over, which would only put a new owner in the middle of someone else's box, but by getting the right box owners to take it. Ownership of the stream sits with one person. Ownership of each box sits with its box owner. The two hold each other up: the end-to-end process owner keeps the stream whole, and the box owners keep each part of it working.

The highest possible standard is to name one end-to-end process owner for the value stream, answering for the customer's outcome across every box it touches, to keep box ownership with the box owners, and to close every gap between boxes by getting the right owners to take it, never by taking the work over.

Key Takeaway: The customer experiences the value stream, not boxes or links, so the stream needs one end-to-end process owner who answers for the customer's outcome across it. The end-to-end process owner does not own the boxes or do their work; they make sure every box and link on the stream has an owner who holds it. A gap between boxes is theirs to close, by getting the right box owners to take it, not by taking the work over. Ownership of the stream sits with one person; ownership of each box stays with its box owner.

The end-to-end process owner does not do the work of the boxes. They make sure every box owns its part, so nothing falls between them.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 7: Owners · Section: The end-to-end process owner

MarvinPro | October 2026

marvinpro.com

Who owns the map

The map itself needs an owner, and its natural owner is the owner of the governance process. On this map, that is govern the company, the management process whose work is to set direction and check that the company's processes keep their promises. The owner of the map decides when a box is added, split or removed, confirms the kind of each, and keeps the map true when the organisation changes, so that the picture at L0 still matches the company it describes.

Ownership belongs to a role, not to a person. Next to every box, link and stream, the map records the role that owns it, and a person fills the role. When someone leaves, the role stays on the map and is filled again. A company that records its owners by name finds its boxes unowned the week someone moves on, and nobody notices until something fails.

With the map owned, every level of ownership has its place: box owners for each process, the owners on each side of each link, the end-to-end process owner for the value stream, and the owner of the map above them all. Each answers for their own, and none answers for someone else's. That is what makes the map governed rather than merely drawn.

The highest possible standard is to have the map owned by the owner of the governance process, deciding when boxes are added, split or removed and keeping the map true as the organisation changes, and to record every ownership on the map as a role, so that it is filled again when a person moves on.

Key Takeaway: The map is owned by the owner of the governance process, who decides when boxes are added, split or removed, confirms their kinds and keeps the map true as the organisation changes. Every ownership belongs to a role recorded on the map, not to a name, so nothing is left unowned when someone leaves. With the map owned, every level has its place: box owners, link owners, the end-to-end process owner and the owner of the map, each answering for their own.

Ownership belongs to a role on the map, not to a name, so no box is left unowned when someone moves on.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 7: Owners · Section: Who owns the map

MarvinPro | October 2026

marvinpro.com

A real example

Alongside the redesign in Links, the end-to-end process owner for subscriptions asked a plain question: who should have known that the update would break the link? There was no answer. Finance ran collections and called collect payments its box. The update had been installed for collect payments, but the software itself was run by IT, which saw the update as routine work of its own. Each had assumed the other would tell provide subscriptions.

The end-to-end process owner did not take the problem over, and did not fix the link personally. They made each side own its part. Collect payments got one owner, in finance, who answers for the process as a whole, including its link to provide subscriptions. The payments software stayed with IT, owned inside run IT, with one addition: every change to it goes to the owner of collect payments before it is released.

The link between collect payments and provide subscriptions was then given its keepers by name: the owners of the two boxes, each recorded on the map as a role. So when the next routine update came, IT sent the change to the owner of collect payments, who reopened the link with the owner of provide subscriptions, and the three agreed cases ran. That is how the renamed field was caught two days before release.

The end-to-end process owner did not fix the link; they made finance and IT each own their part, which is how the next update was caught before release.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 7: Owners · A real example

MarvinPro | October 2026

marvinpro.com

Owners

Every box on the map has one owner: one person who answers for the process as a whole, for its outcome, its design and its links. The owner is chosen for the flow, not for the department, and two owners are no owner. Links are kept by the owners on their two sides, who raise and check every change before it goes live, and disagreements go up, never to whoever pushes hardest.

The value stream has one end-to-end process owner, who answers for the customer's outcome across every box it touches. The end-to-end process owner does not own the boxes or do their work, but makes sure every box and link on the stream is owned, and closes the gaps between boxes by getting the right owners to take them.

The map itself is owned by the owner of the governance process, who decides when boxes are added, split or removed and keeps the map true. Every ownership belongs to a role recorded on the map, so nothing is left unowned when people move on. Owned this way, every part of the system has someone who answers for it, and no part has two.

Give every box one owner, the value stream one end-to-end process owner and the map one owner at the top, and record each as a role so it outlasts the person.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 7: Owners · Chapter Outcome

MarvinPro | October 2026

marvinpro.com

Think Simple.