PROCESS

Here is How to Build

Design

Exceptions

A measure, not a slogan

This volume opened with a claim: a good design has as few exceptions as possible. Held up at the start, that was a direction to aim at. Held up now, at the end, it is something more useful, a measure. You can look at any design and read its health from the exceptions it carries: how many cases still need handling, how many bridges still stand, how much still escalates to a person because no rule yet fits. A design thick with live exceptions is not a well-run one with busy handlers; it is an immature one, its work still spilling past its rules. A design where almost every case is met by a rule that fits, and little is handled and less escalates, is a mature one. The exception load is not a footnote to quality. It is quality, made visible and countable.

This is why the phrase is worth more at the end than at the start. At the start it asked for an intention. At the end it offers a gauge, a way to look at a real design, your own or another's, and say how far along it is, not by opinion but by counting what still falls outside the rules. Two designers may both believe in simple process; the one whose work throws fewer exceptions has more of it. The measure does not flatter and cannot be argued with. It simply shows how much of the work the design has managed to make ordinary, and how much still needs a way forward built by hand.

So the designer learns to read a design the way this measure asks. Not "is it finished?", no design is, but "how much still falls outside it?" A rising count of live exceptions is a design losing ground, its edges outrunning its rules. A falling count is a design maturing, its rules catching up to its work. The number, watched over time, tells the truth about the design more plainly than any description of it could.

The highest possible standard is to treat the exception load as the visible measure of a design's quality, reading a design's maturity not from opinion but from how few cases still fall outside its rules, and watching that count over time as the plainest truth about whether the design is maturing or losing ground.

Key Takeaway: The volume's opening claim, a good design has as few exceptions as possible, is at the start a direction to aim at and at the end a measure. You can read a design's health from the exceptions it carries: many live exceptions, many standing bridges, much escalation means an immature design, its work still spilling past its rules; almost every case met by a rule that fits means a mature one. The exception load is not a footnote to quality, it is quality made visible and countable, and watched over time it tells the truth about the design more plainly than any description.

The exception load is the visible measure of a design's quality: read its maturity from how few cases still fall outside its rules.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 8: As Few As Possible · Section: A measure, not a slogan

MarvinPro | June 2026

marvinpro.com

A settled process needs none

Here is how far the measure reaches, and it is further than "few." A mature process, running steadily and undisturbed, needs no exceptions at all. Every case it meets is met by a rule that fits, because every case that recurred has been folded into the rules and every bridge has been crossed and taken down. What remains outside the rules is only the thinnest residue, the genuinely rare case kept lightly handled on purpose, because a rule for what almost never happens would bloat the design more than it would help. Set that thin residue aside, and a settled process carries no live exceptions. It simply runs.

This tells the truth about what exceptions are. They are the signature of change, not of steady running. A process throws exceptions when something has shifted, when it is new, or has just changed, or has met conditions it was not yet built for, and the cases begin arriving that its rules do not fit. Then the disciplines of this volume run: the exceptions are surfaced early, handled so no Performer is stranded, and folded back into the rules as their permanent answers land. And as they fold back, the count falls, the bridges come down, and the process settles again toward none. So a high exception load does not mean a bad process. It means a process in the middle of absorbing a change. And a process that never settles, that carries a standing crowd of exceptions year after year, is not busy; it is one whose changes were never finished being folded back.

This is where the volume rejoins the two ideas that shaped it. It rejoins the Rules, because a process with no exceptions is one whose rules now suffice, meeting the whole of its work, which is the sound whole the Rules aimed at, reached from the other side. And it rejoins Think Simple, because the settled process is simple on both counts at once: as few exceptions as possible, which in the settled state is none, and as few rules as necessary, no rule added that no case will use. Neither leaking nor bloated. Complete and clean. That doubled simplicity, everything covered, nothing spare, is what a mature process looks like between one change and the next.

The highest possible standard is to drive a process, between changes, all the way to no live exceptions, every recurring case folded into a rule that fits and only the genuinely rare left lightly handled, so that the design is simple on both counts, as few exceptions as possible and as few rules as necessary, and settles clean until the next change reopens its edges.

Key Takeaway: The measure reaches further than "few": a mature process, running steadily, needs no exceptions at all, every case met by a rule that fits, only the thinnest residue of genuinely rare cases kept lightly handled on purpose. Exceptions are the signature of change, not of steady running: a process throws them when it is new or has just changed, then the disciplines run, they fold back, and it settles toward none. A high load means a process absorbing a change, not a bad one. This rejoins the Rules (a process with no exceptions is one whose rules now suffice, the sound whole) and Think Simple (as few exceptions as possible, and as few rules as necessary, complete and clean).

A settled process, between changes, needs no exceptions: everything met by a rule that fits, only the genuinely rare left lightly handled.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 8: As Few As Possible · Section: A settled process needs none

MarvinPro | June 2026

marvinpro.com

The craft of it

A process with no exceptions is a piece of craftsmanship. It is the visible proof that the work was understood so fully that nothing it meets falls outside the design, the way a good beer is clean because whoever made it understood every step and got each one right. Exceptions are the seams that show; their absence is the smoothness of a thing made well. So the aim of this whole volume is not merely fewer interruptions or a lighter handling load. It is craft, a process made so well that it simply holds, and holds without apology, until the work itself changes.

And craft is earned, not read. The disciplines in this book are knowledge, and knowledge can be given, surfaced early, triaged honestly, a way forward at every turn, the recurring folded back. But the craft of actually reaching a clean, exception-free process does not come from reading them. It comes from years of doing the work: from meeting real exceptions in real processes and folding them back, again and again, until the judgment is yours, when a case has recurred enough to earn a rule and when it is rare enough to leave handled, where the real edges lie, which bridge to finish first, what a rule should say once the trouble is finally understood. That judgment is not in these pages. It is built at the bench, over time, by the practitioner who does this until doing it well becomes second nature. The book can give the way of thinking. The craft you earn.

So this is the honest close of the volume. It does not promise that reading it makes a designer whose processes never spill. It promises something truer and harder: here is the craft's way of thinking, the disciplines by which exceptions are found, carried, and folded away, and if you practise them, for years, on real work, you will come to make processes that meet almost everything with a rule that fits and need almost nothing handled by hand. That is the mark of the craft, and, like every craft, it is reached not by finishing a book but by a long time spent making the thing well.

The highest possible standard is to treat a process with no exceptions as craftsmanship, the proof of work understood and made well, and to know that the craft of reaching it is earned over years of doing the work and folding real exceptions back, not read from any set of disciplines, however sound.

Key Takeaway: A process with no exceptions is craftsmanship, the visible proof that the work was understood so fully nothing falls outside the design, the way a good beer is clean because every step was got right. And craft is earned, not read: the disciplines are knowledge, which can be given, but the judgment to reach a clean, exception-free process, what to fold and what to leave, where the edges lie, what a rule should say, comes only from years of doing the work and folding real exceptions back. The book can give the way of thinking; the craft you earn at the bench.

A process with no exceptions is craftsmanship, and the craft of reaching it is earned over years of the work, not read from any book.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 8: As Few As Possible · Section: The craft of it

MarvinPro | June 2026

marvinpro.com

A real example

Return, one last time, to the software company, and watch the measure over its life. In the early days, just after the communication process went live, it threw exceptions constantly. The unknown issue arrived and had no template. The opted-out customer arrived and had no guide. The administrator wanted their own channel; a promise needed varying; trouble came that no one had met. The design was thick with live exceptions and standing bridges, escalations running, work-arounds holding, the designer close in hypercare. Read by the measure, the process was immature, not because it was badly made, but because it was new, and new is when exceptions come.

Then the disciplines did their work, month by month. The what-ifs were gathered and triaged. Each scoped-in case got its way forward, a guide where an answer could be written, an escalation where it could not. And as the permanent steps landed, the recurring cases folded back: the unknown issue became known and passed into troubleshooting and rules, the opt-out became a rule needing no guide, the partner case was negotiated and folded once the agreement held. The count fell. The bridges came down. What had escalated last quarter was pre-approved this quarter and a plain rule the next. And the ruleset stayed clean, because the one genuinely rare request was left handled, not written into a rule no one would use.

Until, one steady season, the process simply ran. A Performer could work a full week and meet nothing the rules did not cover, no bridge to cross, no one to ask, every case ordinary. The exception load had reached, but for that thin rare residue, none. That was the craft made visible: a communication process so well understood that trouble arrived already answered. It held that way, clean, until the company entered a new market with new rules and new promises, a big change, and the edges opened again. The exceptions returned, and the disciplines began once more, surface, carry, fold back, driving the count down toward none a second time. The mark of the mature design was never that exceptions never came. It was that, between changes, they were gone, and the Performer was both never stranded and rarely troubled, because almost everything, by then, simply fit.

Between changes the process ran with no exceptions, everything already answered; and when the next big change opened its edges, the disciplines drove the count back down to none.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 8: As Few As Possible · A real example

MarvinPro | June 2026

marvinpro.com

As Few As Possible

This volume opened by asking for as few exceptions as possible, and closes by showing what that means. It is a measure before it is anything else: a design's health read from how few cases still fall outside its rules, its maturity counted, not described. A design thick with live exceptions is immature, its work spilling past its rules; a design that meets almost everything with a rule that fits is mature. And the measure reaches all the way to none. A settled process, running undisturbed, needs no exceptions, every recurring case folded into a rule, only the thinnest residue of the genuinely rare left lightly handled, because a rule for what almost never happens would bloat the design more than help it. Exceptions are the signature of change, not of steady running: they come when the work is new or has just shifted, and the disciplines of this volume drive them back down to none.

This is where the two halves of the book meet. Part 1 was that no Performer is ever stranded: for every case the rule does not fit, a sanctioned way forward, pre-approved where it can be written, escalated where it needs a decision. Part 2 was that the exceptions do not last: the recurring ones are folded back into the rules until they are exceptions no more. These are not two aims but one care held at two moments, to leave no one without a way through today, and to need fewer ways through tomorrow. The eight disciplines are that one care in motion: surface the exceptions early, triage them honestly, carry the Performer through, and fold the recurring away, over and over, until the process meets its work with rules that fit and the Performer is both never stranded and rarely troubled.

And a process that reaches this is a piece of craftsmanship. No exceptions is the visible proof that the work was understood so fully nothing falls outside it, the way a good beer is clean because every step was got right, everything present that should be, nothing that should not. It rejoins the Rules from the far side: a process with no exceptions is one whose rules now suffice, the sound whole reached by closing every gap the exceptions revealed. And it rejoins Think Simple: complete and clean, as few exceptions as possible and as few rules as necessary, neither leaking nor bloated.

But the craft is earned, not read. This book gives the way of thinking; it cannot give the years. The judgment that makes a clean process, what to fold and what to leave, where the edges lie, what a rule should say once the trouble is understood, is built only by doing the work and folding real exceptions back, again and again, until it becomes second nature. So the discipline never truly ends. Edges always remain, the unforeseen still comes, and each new change reopens the work, calling the maker back to the bench. What this volume leaves you is not a finished process but a way to keep making one well: to answer every case a Performer meets, and, over time and with craft, to need almost none of the answers built by hand.

A design with as few exceptions as possible is craftsmanship, earned over years: no Performer stranded today, and, between changes, almost nothing left that the rules do not already fit.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 8: As Few As Possible · Chapter Outcome

MarvinPro | June 2026

marvinpro.com

Think Simple.