PROCESS

Here is How to Build

Design

Core

The spine of the design

A process is not a heap of rules and steps of equal weight. It has a shape, and at the centre of that shape is one main flow that carries the work the process exists to do, from where it begins to where it ends. That main flow is the core process. It is the spine: the thing the rules are written to govern, the thing the exceptions edge, the thing the sub-processes connect to. Everything else in the design hangs on it, which is why it is the first thing a designer must find and shape. Get the core right, and the rest has something sound to hang on. Get it wrong, and there is nothing under the design that holds.

To find the core process, you do not start with the process at all. You start with the business. Every frame, a company, a department, a team, exists to do some main thing, and that main thing is its core business. A transport company's core business is transport. A bar's is the drinks it sells. Name that core business first, plainly, and the core process follows: it is the process that delivers it, the main flow that turns the core business from an intention into a thing the customer receives. You cannot point at the core process until you have named the core business it serves, because the core process is defined by what it delivers, not by how busy it is or how many people it touches.

This is why naming comes before everything. A designer who begins by drawing flows, before naming the core business those flows are meant to serve, is building without knowing what the building is for. Name the core business, find the process that delivers it, and you have the spine. Only then is there something worth directing, deepening, and connecting, the work of the chapters that follow. The core process is not the busiest process, nor the most complex, nor the one with the most rules. It is simply the one that does the core business, and finding it is the act of naming that business and following it to the process that serves it.

The highest possible standard is to find the core process by naming the frame's core business first, plainly, and following it to the main flow that delivers it, so the spine of the design is identified by what it is for, not by how large or busy it appears.

Key Takeaway: A process has a shape, and at its centre is one main flow that carries the work the process exists to do: the core process, the spine the rules govern, the exceptions edge, and the sub-processes connect to. Everything hangs on it, so it is the first thing to find. To find it, start not with the process but with the business: name the frame's core business, plainly (transport for a transporter, drinks for a bar), and the core process follows, the flow that delivers it. The core is defined by what it delivers, not by how busy it is; name the core business first, and the spine follows.

The core process is the main flow that delivers the frame's core business, the spine the whole design hangs on.

MarvinPro · PROCESS · Here is How to Build · Design · Core · Discipline 1: A Core Process · Section: The spine of the design

MarvinPro | September 2026

marvinpro.com

What the world calls core, and what it is

The word core is already in the world's mouth, and it is used loosely. Some call these the primary processes, some the operational processes, some the main processes; and a common scheme sorts every process a company has into three buckets, core, support, and management, the core ones being those that deliver value to the customer, the support ones enabling them, the management ones guiding them. There is truth in all of this, and this book does not quarrel with it. But the terms are used so variously, from framework to framework and company to company, that they have lost their edge. So it is worth saying plainly what this book means by a core process, and holding to it.

A core process, here, is the main process that delivers a frame's core business, the value-delivering work the business or department exists to do. That is the whole of the definition, and its two words carry the weight. Core, because it does the core business, the thing the frame is for, not the things that merely support or guide it. Process, because it is a flow with a beginning and an end, not a department or a function or a team. A finance department is not a core process; the flow by which money is collected might be a core process of that department, but the department is not. So when this book says core process, it means one thing: the flow that delivers the core business. Not the important-sounding, not the customer-facing by accident, but the one that does the work the frame exists to do.

This precision matters because the loose use of core leads designers astray. A designer who calls a process core because it feels important, or because an executive wanted it made visible, has not named a core process; they have applied a label. The test is not feeling or visibility. It is delivery: does this process deliver the frame's core business? If yes, it is core. If it only supports or enables the delivery, it is not, however vital it is. Purchasing keeps the factory running, and the factory would stop without it, but purchasing does not deliver the core business of making and selling the product; it supports the process that does. The distinction is not about importance. It is about what delivers the core business and what merely serves it.

The highest possible standard is to mean by core process only the flow that delivers the frame's core business, holding to that plain test, delivery, not importance or visibility, and setting aside the looser uses of the word so the core is named by what it does and nothing else.

Key Takeaway: The world uses core loosely, primary, operational, main, and sorts processes into core, support, and management. There is truth in this, but the terms have lost their edge, so this book fixes its meaning: a core process is the main process that delivers a frame's core business, the value-delivering work it exists to do. Core because it does the core business; process because it is a flow, not a department. The test is delivery, not importance or visibility: purchasing is vital but supports the core rather than delivering it. Name the core by what it does, and nothing else.

A core process is the flow that delivers the frame's core business; the test is delivery, not importance or visibility.

MarvinPro · PROCESS · Here is How to Build · Design · Core · Discipline 1: A Core Process · Section: What the world calls core, and what it is

MarvinPro | September 2026

marvinpro.com

Core is not a level

There is one confusion to clear before the volume goes on, because it runs through all the chapters that follow. Core and level are not the same thing, and they must never be mixed. Core is about which process it is, and what it delivers. Level is about how much detail you are looking at. They are two separate axes, and a process has a position on each, independently.

A core process can be seen at any level of detail. At the top, it is a direction, a single line of intent: bring the subscription to life and deliver the software. Deepened, it becomes the end-to-end backbone, every step, team, and system the core work passes through. Deepened further, it becomes the detailed how of each step. It is the same core process throughout, seen closer and closer. The level does not make it more or less core; it only shows more or less of it. So a core process at its simplest, top level is still the core; a core process in full detail is still the core. Level is the zoom, not the identity.

This matters because the chapters ahead move down the levels, from the core's direction at the top to its detailed backbone below, and it would be easy, wrongly, to hear that descent as a change of what the process is. It is not. The direction is the core; the backbone is the core; they are the same spine at different depths. And the same holds for the sub-processes the core connects to: a sub-process is not a lower level of the core, it is a separate process, with its own levels, that the core reaches out to. Keep core and level apart, and the volume stays clear: core names the process by what it delivers, and level names only how closely you are looking at it.

The highest possible standard is to keep core and level as two separate axes, letting a core process be seen at any depth without ceasing to be the core, and never confusing the descent into detail with a change in what the process is or mistaking a sub-process for a lower level of the core.

Key Takeaway: Core and level are two separate axes and must never be mixed. Core is which process it is and what it delivers; level is how much detail you are looking at. A core process can be seen at any level, a direction at the top, the backbone deepened, the detailed how below, and it is the same core throughout; the level is the zoom, not the identity. This matters because the volume descends the levels, and that descent must not be heard as a change in what the process is: the direction is the core, the backbone is the core, the same spine at different depths.

Core is what a process delivers; level is how closely you look at it; a core process is the core at every level.

MarvinPro · PROCESS · Here is How to Build · Design · Core · Discipline 1: A Core Process · Section: Core is not a level

MarvinPro | September 2026

marvinpro.com

A real example

Return to the company you met in the Rules, the one that sells software by subscription. There, the work you studied was the communication around a fix, and it was rich enough to teach a rule whole. But ask the plain question this discipline asks, what is this company's core business?, and the answer is not communication. It is the software subscription itself. The company exists to sell and deliver working, licensed software; that is what the customer pays for, and that is the thing that, if it failed, would end the company. So the communication, for all its importance, is support. The core business is the subscription, and the core process is the one that delivers it.

Name that core business, and the core process follows at once. It is the flow that brings a subscription to an active state, delivers the software to the customer by download, install, and login, and then keeps checking that the subscription is still active, holding the software back when it is not. That is the spine: subscribe, activate, deliver, verify, for every customer, for the life of every subscription. It was there all along, beneath the communication the earlier volumes studied; it simply was not named, because those volumes were teaching rules and exceptions, and a support process served that teaching well. Here, naming the core business brings the real spine into view.

And notice what naming it settles. The communication is not the core, however much work it is, because it does not deliver the core business; it supports it, speaking for the company when the core falters. The charging and invoicing are not the core either; they are sub-processes the core connects to when money must move. What is left, once the supports and the connect-outs are set aside, is the one flow that delivers what the company sells: the subscription brought to life and the software delivered and held. That is the core process this volume will direct, deepen, and connect. It was found not by looking for the busiest or most visible flow, but by naming the core business and following it to the process that serves it.

The core business is the software subscription, and the core process is the spine that delivers it: subscribe, activate, deliver, and verify.

MarvinPro · PROCESS · Here is How to Build · Design · Core · Discipline 1: A Core Process · A real example

MarvinPro | September 2026

marvinpro.com

A Core Process

A process has a shape, and at its centre is one main flow that carries the work the process exists to do: the core process, the spine the rules govern, the exceptions edge, and the sub-processes connect to. Everything hangs on it, so it is the first thing a designer must find. And it is found not by starting with the process but with the business: every frame exists to do some main thing, its core business, and the core process is the flow that delivers it. Name the core business plainly, transport for a transporter, drinks for a bar, the subscription for the software company, and the core process follows, defined by what it delivers, not by how busy or visible it is.

The world uses core loosely, primary, operational, main, and sorts processes into core, support, and management. This book holds to one plain meaning: a core process is the main process that delivers a frame's core business. Core, because it does the core business; process, because it is a flow, not a department. The test is delivery, not importance: purchasing is vital, but it supports the core rather than delivering it, so it is not core. Name the core by what it does, and set the looser uses aside.

And keep core apart from level, for they are different axes. Core is which process it is and what it delivers; level is how much detail you are looking at. A core process can be seen at any depth, a direction at the top, a detailed backbone below, and it is the same core throughout; the level is only the zoom. The chapters ahead descend the levels, from the core's direction to its backbone, and that descent must never be mistaken for a change in what the process is. The direction is the core; the backbone is the core; the same spine, seen closer.

So the discipline is this: to find the core process, name the frame's core business first, plainly, and follow it to the main flow that delivers it. Hold to the test of delivery, not importance or visibility, so the core is named by what it does. And keep core and level separate, so the spine can be seen at any depth without losing its identity. Do this, and you have the thing the whole design rests on, the spine ready to be given a direction, deepened into a backbone, and connected to the processes around it, which is the work of all that follows.

The core process is the flow that delivers the frame's core business: name the business, follow it to the spine, and the whole design has something sound to hang on.

MarvinPro · PROCESS · Here is How to Build · Design · Core · Discipline 1: A Core Process · Chapter Outcome

MarvinPro | September 2026

marvinpro.com

Think Simple.