PROCESS

Here is How to Build

Design

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 what happens when a rule does not fit, and what a designer does about it.

A company sells software by subscription, and its work is not the fixing of software but the communication around it: how trouble is sorted, worked, and told, inside the company and out to the customer. You already know how it sorts trouble. One customer's problem is an issue, worked as a single case. The same trouble across many customers is an emerging issue, something larger. And an issue is known or unknown. A known issue is one the company has seen before, with instructions ready and a template to explain it. The Performer meets a known issue and proceeds: the rule fits, the template is there, the way forward is written. Most cases are like this, and that is the design working.

The exception is the unknown issue. It is the trouble nobody has met yet, the case with no template, because you cannot template what you do not yet understand. Here the rule does not fit. The Performer faces a customer in trouble and has no written words to send, no instruction to follow. They cannot proceed by the rule, because for this case there is no rule. This is the moment the whole volume is about: the Performer, blocked, needing a way forward that the design must already have given them.

And the design has given them one. Long before this case arrived, the designer asked the Performers what they feared: what if trouble comes that we have no template for? That what-if, raised before the work went live, is the first exception, surfaced not in a crisis but in a quiet room, early enough to design for and early enough for the Performers to learn the answer before they ever needed it. The answer designed for it is the escalation path. When the Performer meets an unknown issue, they do not invent a reply and they do not go silent. They carry the case up the path the design built for exactly this: to the Owner, who brings in the Technical Team that can work it. Meanwhile the customer is not left in silence either; the Performer sends the shaped updates the design provides for an unfolding case, a little more certain with each one, each ending with the next step, even when the next step is only to wait. The Performer is never stranded. The rule did not fit, but the design still told them what to do.

Not every what-if could be answered at once. The Performers raised more than the designer could scope in before the live date: the rare customer who asks not to be contacted at all, the client whose administrator insists on a channel of their own, the case that touches a promise only the Offer Owner may vary. Some of these the designer scoped in straight away, as a small written guide the Performer follows without asking anyone, proceed this way, it is already approved. Some needed a living decision and were routed to where the authority sat: a deviation the Performer's own Leader could permit, and a larger one only the area's Owner could sanction. And some, honestly, were parked: noted as known exceptions to be designed later, because the designer had only so much time, and it is better to record an open exception than to pretend it is closed. A way forward at every turn, written where it could be, escalated where it must be, and never simply absent.

But the heart of this volume is what happens after the unknown issue is worked. It does not stay an exception. As the Technical Team finds the steps that resolve it, the Owner turns those steps into troubleshooting the Performer can follow and into templates the customer will receive. At that moment the unknown becomes known. The case that had no rule now has one. The next Performer who meets it will not escalate; they will reach for the template and proceed, because the exception has become a known issue, folded back into the rules, and is an exception no longer. This is the quiet engine you already saw in the Rules, read now from the other side: the process does not merely handle its exceptions, it manufactures their replacements. Every emerging issue solved leaves behind a permanent piece of process, and the universe of untemplated trouble shrinks by one.

That is the case, through the exception lens. A Performer meets a case the rule does not fit, and is not stranded, because the design built the way forward in advance: a guide to follow, or a path to escalate. And the exception does not last, because the design folds the solved case back into the rules, until what was once an exception is simply the normal way. The chapters that follow take this and turn it, so that each part of designing an exception, surfacing it, giving the Performer the way forward, and designing it away, can be seen at work in something real.

Exceptions is built on the Rules. Where that volume showed how a rule is made, this one shows what to do when a rule does not fit: how the case is surfaced, how the Performer is given a way forward, and how the exception is folded back into the rules until it is one no longer. Each Discipline builds on the one before, from the single blocked case to a design that leaves almost nothing outside its rules.

This is not a theoretical guide. It comes from real work across global operations, system migrations and process design. The ideas here were observed, applied and refined in complex environments involving many countries, many systems and many people.

All examples are anonymised and abstracted. They are based on real situations, but names, organisations and identifying details have been removed on purpose. The point is not to show where the experience was gained, but to show how the thinking can be applied in any large, international environment.

This is not a book about what should work. It is a book about what works, consistently, when processes are designed to scale, systems are aligned to support them, and organisations are ready to change.

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.