PROCESS

Here is How to Build

Design

Sub

A part of a process

When a process is small, it is one flow: a handful of steps, done in order, and the work is complete. But a process does not stay small. As the work it carries grows, the flow grows with it, more steps, more turns, more that must happen between the start and the end, until the single flow is too large to hold in one piece. At that point the process is no longer best seen as one flow of steps. It is better seen as a flow of parts, larger chunks, each holding several steps, each doing a coherent piece of the whole. Those parts are its sub-processes.

A sub-process is a part of a process. It is a chunk of the process's own flow, drawn out and treated as a unit: large enough to be worth naming, small enough to be one coherent piece. It is not the whole process, and it is not a single step; it sits between, a middle thing, a piece of the flow big enough to have an inside of its own. Inside it are steps, or smaller sub-processes again, arranged into the coherent piece of work it performs. Seen from outside, it is one thing, a named part the process is built from. Seen from inside, it is a small flow in its own right, with a beginning, an end, and a job it does.

This is why a sub-process matters as a thing in itself, and not merely as a region of the backbone. When a process is divided into sub-processes, each part becomes something that can be named, understood, designed, and reasoned about on its own, without holding the whole process in mind at once. A large process seen as one undivided flow is hard to grasp, hard to build, and hard to change, because there is too much of it to hold together. The same process seen as a handful of named parts, each a coherent piece, becomes tractable: you can work on one part at a time, know what it does and where it sits, and trust the others to do theirs. Dividing a process into sub-processes is how a process too large to hold becomes a process you can work with.

The highest possible standard is to see a large process as a flow of parts rather than a flow of steps, recognising its sub-processes as the coherent chunks it is built from, each a named piece with an inside of its own, so the process becomes something that can be designed and understood part by part rather than all at once.

Key Takeaway: A small process is one flow of steps; but as the work grows, the flow grows too large to hold in one piece, and is better seen as a flow of parts, larger chunks, each a coherent piece. Those parts are its sub-processes. A sub-process is a part of a process: a chunk of its own flow, large enough to name, small enough to be coherent, sitting between the whole and the single step, with an inside of its own (steps, or smaller subs). Dividing a process into sub-processes is how one too large to hold becomes one you can work with, part by part.

A sub-process is a part of a process: a coherent chunk of its flow, large enough to name, with an inside of its own.

MarvinPro · PROCESS · Here is How to Build · Design · Sub · Discipline 1: A Sub-Process · Section: A part of a process

MarvinPro | October 2026

marvinpro.com

What the world calls a sub-process

The word sub-process is already in use, and like most such words it is used loosely. It is applied to almost anything smaller than a whole process: a chunk of flow, a single activity, a step, sometimes a task. And it is used relatively: what one person calls a process, another calls a sub-process of something larger, and both are right, because the same thing is a process from one height and a sub-process from another. Accounts receivable is a process to the team that runs it and a sub-process of finance to the company above; and within accounts receivable, matching a payment is itself a sub-process, with its own steps below. Sub-process names a position in a hierarchy, not a fixed size, and the position depends on where you stand.

This book keeps the relative sense, because it is true, but fixes the meaning tightly. Here, a sub-process is a coherent part of a process: a chunk of the process's own flow, large enough to have an inside of steps, small enough to be one coherent piece of work. The two words both do work. Sub, because it is part of a larger process, below the whole, a piece of it and not the whole itself. Process, because it is itself a flow, with a beginning, an end, and steps between, and not a single indivisible act. A sub-process is a process that is part of a process, which is exactly the relative sense the world uses, held to one clear size: bigger than a step, smaller than the whole.

And the relativity is not a flaw to be removed but a truth to be used. A sub-process, looked at on its own, is a process, and can be designed exactly as the Core volume taught any process to be designed: named, directed, deepened. A process, looked at from above, is a sub-process of the larger one it belongs to. This is the same relativity met in the Core volume, where a department's core turned out to be, from the company's frame, a sub of the company's own core. Whether a thing is a process or a sub-process depends on the frame you take: in its own frame it is a process; in the frame of the larger whole it is a part. The word shifts with the frame, and that is as it should be.

The highest possible standard is to mean by sub-process a coherent part of a process, bigger than a step and smaller than the whole, holding to that fixed size while keeping the relative sense the world rightly uses, so that the same thing is understood as a process in its own frame and a sub-process in the frame above it.

Key Takeaway: The world uses sub-process loosely (for almost anything smaller than a whole process) and relatively (what one calls a process, another calls a sub-process of something larger, both right). This book keeps the relative sense but fixes the size: a sub-process is a coherent part of a process, a chunk of flow with an inside of steps, bigger than a step and smaller than the whole, a process that is part of a process. The relativity is a truth to use: a sub-process on its own is a process, designed as Core taught; a process from above is a sub-process. The word shifts with the frame, as it should.

A sub-process is a coherent part of a process, bigger than a step and smaller than the whole; the same thing is a process in its own frame, a sub-process in the frame above.

MarvinPro · PROCESS · Here is How to Build · Design · Sub · Discipline 1: A Sub-Process · Section: What the world calls a sub-process

MarvinPro | October 2026

marvinpro.com

A sub, not a step, not a separate process

A sub-process must be told apart from two things it is easily confused with, because it sits between them, and mistaking it for either loses what it is. Below it is the step. A step is a single act, done and passed on, with no inside to speak of, no flow of its own. A sub-process is larger: it has an inside, a small flow of steps arranged into a coherent piece. The test between them is whether the thing has an inside worth drawing. If it is a single act, it is a step; if it is a flow of several acts doing one coherent piece of work, it is a sub-process. To call a step a sub-process is to name an inside that is not there; to call a sub-process a step is to flatten a flow into an act, and lose the structure within it.

Above and beside it is the separate process, the one the process connects out to rather than contains. In the Core volume, the core handed off to other processes, the finance process that charges, the mobility process a breakdown calls, and these were reached across a handoff, each a process in its own right, running its own course, owned elsewhere. A sub-process is not that. It is not reached across a handoff and it is not a separate process; it is a part of this process, inside it, a chunk of its own flow. The difference is containment: a sub-process is within the process, one of the parts it is made of; a connected process is outside it, something it reaches to. To mistake a connected process for a sub-process is to try to design, as a part of this process, something that is really a whole process of its own, belonging to someone else.

So a sub-process is the middle thing, and holding it in its place keeps the design honest. It is more than a step, because it has an inside; it is less than a separate process, because it is a part and not a whole reached across a seam. When a designer divides a process, the question at each cut is which of the three a piece is: a step, if it is a single act; a sub-process, if it is a coherent flow within this process; a connected process, if it is a separate whole this process reaches out to. Name each piece as what it is, and the process divides cleanly into the parts it is truly made of, with its steps as steps, its sub-processes as parts, and its connections to other processes left as the handoffs they are.

The highest possible standard is to tell a sub-process from a step, which has no inside, and from a separate process, which is reached across a handoff and owned elsewhere, holding the sub-process in its middle place as a coherent part within the process, so each piece of the flow is named as the step, sub-process, or connection it truly is.

Key Takeaway: A sub-process sits between two things it is confused with. Below is the step: a single act with no inside; a sub-process is larger, with an inside of steps forming a coherent flow; the test is whether it has an inside worth drawing. Above and beside is the separate process: the thing the process connects out to across a handoff, a whole in its own right, owned elsewhere; a sub-process is contained within this process, a part of it, not reached across a seam. So at each cut, name the piece: a step (single act), a sub-process (coherent flow within), or a connection (a separate process reached out to).

A sub-process is the middle thing: more than a step (it has an inside), less than a separate process (it is a part within, not a whole reached across a seam).

MarvinPro · PROCESS · Here is How to Build · Design · Sub · Discipline 1: A Sub-Process · Section: A sub, not a step, not a separate process

MarvinPro | October 2026

marvinpro.com

A real example

Return to the software core, deepened in the Core volume to its backbone: subscribe, activate, deliver, verify. Look at one beat, activate, and ask what it is. It is not a single step. To bring a subscription to an active state, a payment must be settled, and then an account opened, and then an entitlement recorded, three acts, in order, each depending on the one before, together doing one coherent thing. That inner flow is exactly what makes activate a sub-process and not a step: it has an inside, a small flow of its own, arranged into the coherent piece of work called activation. The core is built of such parts; activate is one of them.

Now look inside activate, and the three distinctions appear at once. Recording the entitlement may be a single act, a value written, a flag set, done and passed on, with no flow of its own. That is a step, and to treat it as a sub-process would be to invent an inside it does not have. Settling the payment, on the other hand, may itself be a sub-process: taking the payment details, handling a failure, confirming success, a flow of several acts doing one coherent piece. And within that settle sub-process, the charge itself, where it is performed by a separate finance process the core reaches out to, is neither a step nor a sub-process but a connection: reached across a seam, owned elsewhere, and designed in its own right. Three pieces in and around one beat, each a different kind: a step, a sub-process, and a connection reached from inside it.

And activate shows the relativity too. Seen from inside the subscription core, it is a sub-process, one part of a larger flow. Seen on its own, by whoever owns and designs activation, it is a process in its own right, a small core with its own direction (bring a subscription to an active state), its own backbone (settle, open, record), its own edges. The word shifts with the frame: a sub-process to the core above, a process to itself. So the software core, looked at through this lens, is not one undivided flow but a nest of parts: sub-processes where a piece has an inside, steps where a piece is a single act, connections where a piece is a separate process reached out to, each named as what it is, and the whole made tractable by being seen as the parts it is built from.

Activate is a sub-process of the core, built of steps and smaller subs, beside a connection to a separate process, and is itself a process when seen on its own.

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

MarvinPro | October 2026

marvinpro.com

A Sub-Process

A small process is one flow of steps, but as the work it carries grows, the flow grows too large to hold in one piece, and is better seen as a flow of parts, larger chunks, each a coherent piece of the whole. Those parts are its sub-processes. A sub-process is a part of a process: a chunk of its own flow, large enough to be worth naming, small enough to be one coherent piece, sitting between the whole and the single step, with an inside of its own: steps, or smaller sub-processes again. Dividing a process into sub-processes is how one too large to hold becomes one you can work with, part by part.

The world uses sub-process loosely and relatively, for almost anything smaller than a whole process, and relative to where you stand, so the same thing is a process from one height and a sub-process from another. This book keeps the relative sense, because it is true, but fixes the size: a sub-process is a coherent part of a process, bigger than a step, smaller than the whole, a process that is part of a process. And the relativity is a truth to use: a sub-process on its own is a process, designed as the Core volume taught; a process from above is a sub-process of the larger whole. The word shifts with the frame, as it should.

So a sub-process must be told from two things it sits between. From the step below it, which is a single act with no inside; a sub-process is larger, with an inside of steps forming a coherent flow, and the test is whether there is an inside worth drawing. And from the separate process beside it, the one this process connects out to across a handoff, a whole in its own right, owned elsewhere; a sub-process is contained within this process, a part of it, not reached across a seam. At each cut, a piece is one of the three: a step, a sub-process, or a connection, and naming it rightly keeps the design honest.

So the discipline is this: when a process grows too large to be one flow, see it as a flow of parts, and recognise its sub-processes as the coherent chunks it is built from, each a part with an inside of its own. Hold the sub-process in its middle place, more than a step, less than a separate process, and tell it from both. Keep the relative sense the world rightly uses: a sub-process in its frame above, a process in its own. Do this, and a process too large to hold becomes a thing you can design and understand part by part, which is where the work of dividing it well, the work of the chapters that follow, begins.

A sub-process is a coherent part of a process, more than a step and less than a separate process; see a large process as the parts it is built from, and it becomes one you can work with.

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

MarvinPro | October 2026

marvinpro.com

Think Simple.