Core
A process has a spine: one main flow that carries its core work from beginning to end. That spine is the core process, and it is the first thing a designer must find and shape, because everything else, its rules, its exceptions, the sub-processes it reaches out to, hangs on it. This volume is about that core: how to name it, direct it, and deepen it into the backbone the rest of the design rests upon.
The work moves from the top down. The core is set first as a direction, cheap to change while it is only a direction, and only then deepened into the end-to-end backbone that shows every step, team, and system the core work passes through. Get the direction right and agreed first, and the detail beneath it is built once; get it wrong, and everything below is built again. So this volume teaches the core from the top down: name the core business, find the process that serves it, direct it, and deepen it, until the spine of the whole design stands.
Think Simple.
Roles
Owner
Owns the end to end of their area. The decision rights and the full responsibility are theirs, at any level, in any place.
Leader
Leads, and can design a part, but does not own the end to end. (If they did, we would call them the Owner.)
Designer
Designs the part in focus, an Owner across their area, or a Leader within their part. Designing is what owning and leading ask of you.
Stakeholder
Holds a stake in the process.
Challenger
Challenges, and brings something to work with. The point may be right. Engage it.
Performer
Performs the steps.
Refuser
Refuses, and brings nothing to work with, at any level. Look first for a root. If there is none, the way past is above them.
The Example
This volume returns to the same company you met in the Rules. The case is the same; only the lens has turned. There it showed you the rules. Here it shows you the core those rules serve.
In the Rules, and again in the Exceptions, the work you studied was the communication around a fix: how trouble is sorted, worked, and told, inside the company and out to the customer. That work is real and it matters, but it was never the company's core business. It was the support around it. The company's core business is the one named in the very first line of that example: it sells software by subscription. Selling and delivering working, licensed software is the thing this company exists to do, the thing a customer pays for, the thing that, if it failed, would end the company no matter how well it communicated. That is the core, and the process that delivers it is the core process this volume designs.
What does that core process actually do? It carries a customer from wanting the software to using it, licensed and working, and it keeps them there. It begins when a subscription is taken and must be brought to an active state, the payment settled, the account opened, the entitlement recorded. Then the software must reach the customer: most often a download, an install, and a login, the path by which what was bought becomes what is running on their machine. And it does not end there, because a subscription is not a sale but a standing promise. So the core runs on, quietly, for as long as the customer stays: a system checks, again and again, whether the subscription is still active, and where it is not, it holds the software back, because the company sells the use of the software only for as long as it is paid for. Subscribe, activate, deliver, and verify, over and over, for every customer, for the life of every subscription. That is the spine.
Everything else in the design hangs on that spine. The communication you already know, the messages, the templates, the escalation paths, is a support process around it: it exists because the core sometimes falters, and a customer whose software has stopped must be told well. The money that moves through the core, the charge when a subscription is taken, the invoice, the collection when a payment is due, is not the core's own work either; it reaches out to financial sub-processes, the charging, the matching, the accounts, that are their own processes with their own rules, and that this book meets in the volume after this one. The core does not do their work. It connects to them, at the points where money must move, and carries on.
And this core, like most, is rarely drawn on a blank page. The company had a way of activating and delivering software before any designer sat down to shape it; what a designer usually does is inherit that core and redesign it, when the plans change, when a new delivery method arrives, when the entitlement rules must tighten. So the example holds both: the core as it must be designed from its direction down, and the core as it is more often met, already running, and changed.
That is the case, seen through the core lens. A software company delivering what it sells: bringing a subscription to life, putting the software in the customer's hands, and holding it there only while it is paid for, the spine on which its rules are written, its exceptions handled, and its sub-processes hung. Read it, as before, as a story first. The chapters that follow take this one core and turn it, so that each part of designing it, naming it, directing it, deepening it, connecting it, agreeing it, and redesigning it for change, can be seen at work in something real.
Core is built on the Rules and the Exceptions. Where those volumes worked at the scale of the single rule and its edges, this one steps back to the whole process they serve: the spine that carries the core work from end to end. It shows how to name that core, give it a direction the business agrees on, deepen that direction into the detailed backbone, connect it out to the sub-processes it reaches, and, where a core already exists, redesign it for the change that comes. Each discipline builds on the one before, from naming the core business to the sound core process the whole design rests upon.
IMPORTANT NOTE
Readers are strongly encouraged to access and share the original content through marvinpro.com. MarvinPro is a continuously evolving body of work, with content regularly updated to reflect new insights, improved frameworks and enhanced learning materials. Material copied or reproduced elsewhere may no longer represent the latest version, whereas the live site will always provide the most current and complete learning experience.
© COPYRIGHT 1990-2026 MarvinPro
All rights reserved. Content is free to read and share via link. You are welcome to share quotes from this work provided the complete attribution is reproduced exactly as it appears in the text, including the quote, author name, year and marvinpro.com. Copying or reproducing other parts, complete sections or chapters without prior permission is not permitted.
Think Simple.
