System
A company does not run on one process. It runs on many at once: one that does its core business, others that support it, others that steer it, each handing work to the next. Together they are the system, and it is the first thing a designer must see, because every process in it (and every rule, exception, part and step within those processes) is designed as a piece of that whole. This volume is about that system: how to map it, sort it, link it and govern it, so that the design of any single process starts from the whole it belongs to.
The work starts at the top. Before any one process is directed or deepened, the system is drawn as a map: every process the company runs, at one level, on one page. This is the level practitioners often call L0 (the process map), and it sits above the direction of any single process (L1), which Core takes up next. Get the map right, and every process can be placed, linked and owned; leave it undrawn, and each process is designed alone, pushing its problems onto the others. So this volume teaches the system from the top: map every process, sort each by kind, link what flows between them, and govern the whole, until the ground the rest of the design stands on is clear.
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 again. There it showed you the rules, and in the Exceptions the edges of those rules. Here it shows you the whole company, from above, for the first time.
In the Rules and 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. From above, that work turns out to be one process among many. It is real and it matters, but it is a support process, and it sits on the map next to the others that keep the company running.
What else is on that map? At its centre sits the work the company exists to do: it sells software by subscription, and keeps each customer subscribed, licensed and running. That is its core, and the next volume designs it. Around the core sit the processes it cannot run without. Finance charges each subscription, sends the invoice and collects what is due. IT keeps the systems that the subscription depends on running. A people process hires and trains the teams who do the work. Communication tells customers what is happening when something goes wrong. And above them all sit the processes that steer the company: planning, which decides which plans to sell and in which markets, and governance, which checks that every process does what it promises.
None of these processes works alone. A charge passes from the core to finance when a subscription is taken. A failed payment in finance changes what the core does next. A fault the core cannot fix becomes work for communication. Every line between two processes on the map is a place where work passes, and a place where it can be lost. Seen one process at a time, each can look sound. Seen as a system, you can tell where they meet well, where they meet badly, and who answers for each.
That is the case, seen through the system lens: one software company, many processes, one map. Read it, as before, as a story first. The chapters that follow take this one company and turn it, so that each part of seeing its system (what a system is, its levels, the map, the kinds of process, the value they add, the links between them and the owners who answer for them) can be seen at work in something real.
System is built on the Rules and the Exceptions. Where those volumes worked at the scale of the single rule and its edges, inside one process, this one steps back to the widest view of all: every process the company runs, seen together as one system. It shows how to map that system, sort each process by kind, link what flows between them and govern the whole, so that every process this book designs from here on, beginning with the core, is designed as a part of the system it serves. Each discipline builds on the one before, from what a system is to the system seen whole.
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.
