PROCESS

Here is How to Build

Design

System

What the customer pays for

With every process on the map and every box sorted, the next move is to ask what each one adds. Value is decided from the customer's side, not the company's. Work adds value when the customer would pay for it: the software running, set up the way they asked, there when they need it. A company can be proud of a step, measure it and staff it heavily, and still find that the customer would not pay anything for it.

Most work on the map does not add value directly, and it does not have to. Collecting payments, running IT and developing people add nothing the customer would pay for on its own, but they make possible the work that does. That is the second way work earns its place: it enables value. The test is a line. From any piece of work, it should be possible to draw a line, through the processes it serves, to something the customer pays for.

Work with no line is waste. Not because the people doing it are idle, but because nothing they produce reaches the customer, directly or through another process. Waste hides well. It is often busy, often careful and often old, done because it was once needed and nobody has asked whether it still is. The value test asks that question on purpose.

The highest possible standard is to judge value from the customer's side, to accept work as valuable only when the customer would pay for it or when it enables work they would pay for, and to treat any work with no line to the customer as waste, however busy it looks.

Key Takeaway: Value is decided by the customer: work adds value when the customer would pay for it. Most work on the map adds value indirectly, by enabling the processes that do, and that is just as legitimate. The test is a line from the work, through the processes it serves, to something the customer pays for. Work with no line is waste, even when it is busy and careful, and most waste survives because it was once needed and nobody asked again.

Value is what the customer would pay for. Everything else on the map either makes that possible or is waste.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 5: Value · Section: What the customer pays for

MarvinPro | October 2026

marvinpro.com

Value crosses boxes

The customer never sees the boxes. They see one experience: being sold to, being set up, using the software, being billed, getting help, renewing. That thread runs through four or five boxes on the map, and to the customer it is one thing. This thread is the value stream: the path of everything the company does for one customer, from first contact to renewal, across whichever boxes it touches.

The map and the value stream are two views of the same company. The boxes show how the work is organised. The value stream shows how the customer receives it. Neither replaces the other, and a map without the value stream drawn on it shows the company only from the inside. The value stream is also not the core process. Core designs one process, from its direction down to its backbone. The value stream runs across processes at the height of the map, through the core and the support processes that touch the customer.

Value is rarely lost inside a box. Each team knows its own work and looks after it. Value is lost where the stream crosses from one box to the next: an order waiting for someone to pick it up, a customer asked again for details they already gave, a change one team made that the next never heard about. Drawing the value stream shows where those crossings are. How each crossing is designed is the work of Links, the next discipline.

The highest possible standard is to draw the value stream across the map, from first contact to renewal, so the company sees itself the way the customer does, to keep it distinct from the core process, and to mark every point where it crosses from one box to the next.

Key Takeaway: The customer experiences one thread, not boxes: the value stream, from first contact to renewal, across every box it touches. The map shows how the work is organised and the value stream shows how the customer receives it; the company needs both. The value stream is not the core process: Core designs one process, while the value stream runs across processes at the height of the map. Value is mostly lost where the stream crosses between boxes, so drawing it marks the crossings that Links will design.

The customer never sees the boxes. They see one thread running through them, and every crossing is a place where it can break.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 5: Value · Section: Value crosses boxes

MarvinPro | October 2026

marvinpro.com

Every box earns its place

With the value stream drawn, every box on the map can be tested. For each box, and for the main work inside it, the question is the same: does it create value, enable a process that does, or neither? The test applies to every kind. A management process earns its place by keeping the company pointed at what the customer pays for, and a support process by keeping the processes that serve the customer running. Kind is a role, not a rank, and no kind is exempt.

When the test finds a problem, there are two outcomes. Work that creates no value and enables nothing is cut. Work that is done twice, in two boxes, for the same purpose, is consolidated: it stays in one place and stops in the other. Duplication rarely looks like waste from inside either team, because each copy is used. It shows only on the map, where the two copies sit side by side.

Consolidating raises a design question: where does the work stay? Two things decide it. Capability decides the destination: the work moves to the team that does it best, usually the one closest to its source, with the fewest crossings. Capacity decides the timing. If that team cannot carry the extra work yet, the answer is to give it the resources and move the work when it can absorb it, not to leave the work with whichever team happens to have time. Moving work to whoever has room is how most duplicates start.

The highest possible standard is to test every box, of every kind, for whether it creates value, enables it or neither, to cut work that does neither, to consolidate work done twice into the team that does it best, and to move it when that team has the capacity to carry it.

Key Takeaway: Every box is tested, whatever its kind: does it create value, enable it, or neither? Work that does neither is cut. Work done twice is consolidated into one place, and a duplicate is usually visible only on the map. Capability decides where consolidated work stays, usually with the team closest to its source; capacity decides when it moves. If the better team cannot carry the work yet, it is resourced first, because moving work to whoever has room is how duplicates begin.

Cut what adds nothing. Keep what is done twice in the team that does it best, and move it when that team can carry it.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 5: Value · Section: Every box earns its place

MarvinPro | October 2026

marvinpro.com

A real example

With its eight boxes sorted, the software company drew its value stream for the first time, following one customer from the first sales call to the first renewal. The line ran through four boxes: sell subscriptions, provide subscriptions, collect payments and support customers. Two findings came out of it.

The first sat where sell subscriptions handed the customer on to provide subscriptions. Sales still required a signed order form, typed into the system by hand, before the software could be activated. The rule dated from the years when contracts were signed on paper. By now the customer had already accepted the terms online. The form added nothing the customer would pay for and enabled nothing, and it held back activation by two days, at the very point where the customer first received anything they had paid for. It was cut, and activation now follows acceptance directly.

The second finding was off the value stream. Plan the business and govern the company each built a monthly figures pack from the same data, one for planning and one for the leadership review. Each team used its own, so neither pack looked like waste. The pack stayed with the finance team that builds it inside plan the business, because the figures start there and its pack was already reconciled. But month-end is finance's heaviest week, so the team was given extra hands for it, and a quarter later, once it could carry the work, the leadership review switched to finance's pack and the second one stopped. The map still had eight boxes. It now also had one line drawn across them, and less work inside them.

The value stream showed a form that delayed what the customer pays for and a report made twice; one was cut, and the other was kept where it was made best.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 5: Value · A real example

MarvinPro | October 2026

marvinpro.com

Value

Value is decided by the customer. Work adds value when the customer would pay for it, and most work on the map adds value indirectly, by enabling the processes that do. From any piece of work there should be a line, through the processes it serves, to something the customer pays for. Work with no line is waste, however busy it is.

The customer experiences the company as one thread, the value stream, from first contact to renewal, across every box it touches. It is not the core process, which Core designs as one process; it runs across processes at the height of the map. Drawing it shows the company the way the customer sees it, and marks the crossings where value is most often lost.

With the value stream drawn, every box of every kind is tested: does it create value, enable it, or neither? Work that does neither is cut. Work done twice is consolidated, in the team that does it best, once that team has the capacity to carry it. Tested this way, every box on the map has a line to the customer, and every crossing on that line is ready to be designed.

Draw the value stream across the map, give every box its line to the customer, and cut or consolidate the work that has none.

MarvinPro · PROCESS · Here is How to Build · Design · System · Discipline 5: Value · Chapter Outcome

MarvinPro | October 2026

marvinpro.com

Think Simple.