PROCESS

Here is How to Build

Design

System

Seven disciplines, one system

This volume began by asking what a system is: the company's processes seen together, at a height where no single process fills the picture. Seven disciplines later, the picture is complete. The levels placed it at L0, the top of the ladder. The map drew every process as a box. The kinds sorted each box by who it is for. Value drew the stream the customer lives through. Links designed every crossing between boxes. Owners gave every box, every link, the stream and the map itself someone who answers for it. Together, those layers are the system.

The layers are not a list. Each rests on the one before it. The kinds cannot be sorted until the boxes are drawn. Value cannot be tested until the kinds say what each box is for. Links cannot be designed until the value stream shows where the crossings are. Owners cannot be named until there are boxes, links and a stream to own. Take one layer away and the ones above it stop holding: an owner with no link to keep, a link with nothing to carry, a box with no kind and no line to the customer.

That dependence is what separates a system from a diagram. A diagram shows boxes. A system shows boxes that know what they are for, what they add, how work crosses between them and who answers for each. The same eight boxes can be either. What makes them a system is everything done to them after they were drawn.

The highest possible standard is to build the system as one picture at L0, layer by layer (the map, the kinds, the value stream, the links and the owners), with each layer resting on the one before it, and never to call a map a system while any layer is missing.

Key Takeaway: The seven disciplines of this volume build one picture at L0, layer by layer: the map, the kinds, the value stream, the links and the owners. Each layer rests on the one before it, so taking one away leaves the layers above it with nothing to hold. That dependence is what separates a system from a diagram: a diagram shows boxes, while a system shows what each box is for, what it adds, how work crosses between boxes and who answers for each.

A diagram shows boxes. A system shows what each box is for, what it adds, how work crosses between them and who answers for it.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 8: The System · Section: Seven disciplines, one system

MarvinPro | October 2026

marvinpro.com

Kept, never finished

A system is drawn once and kept for as long as the company runs. Companies change: a product is added, a team is reorganised, a channel opens, a supplier is replaced. Each change touches some part of the system, and if the system does not change with it, the picture and the company begin to diverge. Each divergence is small, and the next decision is made on a picture that is no longer true.

Keeping the system is the work of the owner of the map, through the cycle Three Kinds set for management: a plan each year, a review each quarter, a check whenever something changes. The yearly plan asks whether the map still matches the business the company intends to run. The quarterly review checks the value stream, the links and the owners against what actually happened. And between them, any change to a box, a link or an owner reopens that part of the system before the change goes live: the rule Links set for a single crossing, now held for the whole map.

A system that nobody keeps fades back into a diagram. The boxes stay on the wall, but their kinds go out of date, the links grow by habit again and the owners move on without being replaced. The work of building it is not lost in one failure. It is lost over a year of small changes that nobody brought to the map.

The highest possible standard is to keep the system true for as long as the company runs, through a yearly plan, a quarterly review and a check whenever something changes, and to reopen the part of the system that any change to a box, a link or an owner touches before that change goes live.

Key Takeaway: A system is drawn once and kept for as long as the company runs. The owner of the map keeps it true through the management cycle: a yearly plan that tests the map against the business, a quarterly review that tests the stream, the links and the owners against what happened, and a check whenever something changes. Any change to a box, a link or an owner reopens that part of the system before it goes live. A system nobody keeps fades back into a diagram, not through one failure but through a year of small changes nobody brought to the map.

A system is never finished. It is kept, or it fades back into a diagram.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 8: The System · Section: Kept, never finished

MarvinPro | October 2026

marvinpro.com

Where System ends

System works at one height: L0, the top of the ladder, where the company's processes are seen together. It does not design the inside of any process. That is the work of the volumes below, each on its own rung. Core takes the box the business rests on, sets its direction at L1 and deepens it to the backbone, from L1 to L3. Below the backbone, Sub cuts the process into its parts, Procedure lays out the steps inside each part, and Guides reach the single step.

The system is the frame they all design within. Whatever is built below has to fit inside one box, honour the links that box has agreed and answer to that box's owner. A design that needs a new crossing goes back to the map, where the link is written with both sides. A design that blurs two boxes goes back to the owner of the map. The volumes below add depth; they never redraw the map from underneath.

That is why System comes first. Designing a process without the system is like designing one room without the plan of the house: it may be a good room, but its doors can open onto nothing. With the system in place, Core can start where it should: with the one box the whole business rests on.

The highest possible standard is to keep System at L0, designing no process inside, and to treat the system as the frame every volume below designs within: each design fitting one box, honouring that box's links and answering to its owner, with any new crossing or blurred boundary taken back to the map.

Key Takeaway: System works at L0 and designs the inside of no process. The volumes below each take a rung: Core sets the direction of the box the business rests on and deepens it to the backbone, from L1 to L3, and Sub, Procedure and Guides go further down. The system is the frame they all design within: every design fits one box, honours its links and answers to its owner, and a new crossing or a blurred boundary goes back to the map. The volumes below add depth; they never redraw the map from underneath.

System designs the inside of no process. It is the frame every process below is designed within.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 8: The System · Section: Where System ends

MarvinPro | October 2026

marvinpro.com

A real example

A year after its map was first drawn, the software company opened a new channel: partners who would resell its subscriptions to their own customers. In the past, a change like this would have started with a project team and a blank page. This time it started with the map.

The owner of the map asked the system's questions in order. Was partner sales a new box? No: it served the same purpose as selling directly, winning the customer and handing them on to the core, so it sat inside sell subscriptions. Its kind stayed support, and the tally stayed the same: one core, five support and two management. On the value stream, it added a second point of first contact. And it touched one link: the crossing from sell subscriptions to provide subscriptions would now carry partner orders as well, so the link was reopened, written again with its three parts and its way back, and the agreed cases were run across it, now including an order from a partner.

The owners closed the rest. The owner of sell subscriptions took the partner channel into the box, with partner management as a new role inside it. The end-to-end process owner checked the new entry point against the customer's outcome: a partner's customer should receive the same thing, in the same way, as anyone else. The change went live in two weeks. Nothing fell between the boxes, because every question it raised already had a place on the map and someone who answered for it.

A new channel took two weeks, not months: every question it raised already had a place on the map, and an owner.

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

MarvinPro | October 2026

marvinpro.com

The System

A system is the company's processes seen together at L0, built in layers: the map, the kinds, the value stream, the links and the owners. Each layer rests on the one before it, and a map with any layer missing is a diagram, not a system.

A system is never finished. Its owner keeps it true through the management cycle (a plan each year, a review each quarter and a check whenever something changes), and any change to a box, a link or an owner reopens that part before it goes live. A system nobody keeps fades back into a diagram.

And a system designs the inside of no process. It is the frame every volume below works within: Core sets the direction of the box the business rests on and deepens it to the backbone, and Sub, Procedure and Guides go further down, each design fitting its box, honouring its links and answering to its owner. Built and kept this way, the system is where every design in the company begins.

Build the system at L0 in layers, keep it true as the company changes, and design every process below it within its frame.

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

MarvinPro | October 2026

marvinpro.com

Think Simple.