PROCESS

Here is How to Build

Design

Exceptions

The banked decision

The world already has a thing it calls a pre-approved exception, and it is not quite this. There, a pre-approved exception is a single deviation cleared in advance but still treated as an exception: temporary, its risk formally accepted, set to expire and be reviewed again. It remains an exception the whole time; it has only been authorised early, and the authorisation lapses, so the case comes back around. That is a governance instrument, and its home is the Govern domain, where who may accept a deviation, and for how long, and at what risk, is the proper question. It is not what this book means.

Here, pre-approved means a standing answer. The designer foresaw the case, decided how it should be handled, wrote that handling into a guide, and had it signed off once. From then on, the guide stands. Any Performer who meets the case looks it up, follows it, and proceeds, within full sanction, because the decision was already made and the approval already banked. The approval is not granted-and-expiring; it is made once and standing. The Performer is not bending a rule or spending a risk allowance; they are following a settled answer that the design put in place before they ever arrived. What was, for the world, a deviation to be re-authorised each cycle is, here, a written answer the Performer simply uses.

And there is a difference in where the burden falls, which matters more than it first seems. In the world's version, the expiry lands on the doer: the grant lapses, and the case must be brought back for approval again, a touch-point returned to whoever meets it. Here it is the opposite. To the Performer, the pre-approved guide never expires. It stands, and they follow it indefinitely, never asking again. The only expiry is the designer's, and it is a responsibility, not a lapse: the designer holds the standing duty to fix the exception when possible, folding it into the rules so the case ceases to be an exception at all. The Performer feels none of that. They follow a stable guide until, one day, without friction, the case is simply the normal way and the guide is quietly no longer needed. The provisionality is the designer's to carry; the Performer is given only stability.

The highest possible standard is to mean by pre-approved not a temporary, risk-accepted, expiring grant that keeps a case an exception and lands its lapse on the doer, but a standing answer, designed, written into a guide, and signed off once, that the Performer follows within full sanction and never has to seek again, while the designer alone carries the duty to resolve it upward in time.

Key Takeaway: The world's pre-approved exception is a single deviation cleared in advance but still an exception, temporary, risk-accepted, expiring, re-reviewed, a governance instrument that belongs to the Govern domain. Here, pre-approved means a standing answer: designed, written into a guide, signed off once, and followed by every Performer within full sanction, the approval banked, not granted-and-expiring. And the burden falls differently: the world's expiry lands on the doer, who must seek approval again; here the guide never expires on the Performer, and the only expiry is the designer's own duty to fold it into the rules in time.

Pre-approved is a standing answer, written and signed off once, that the Performer follows within full sanction and never has to seek again.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 5: Pre-Approved · Section: The banked decision

MarvinPro | June 2026

marvinpro.com

What can be pre-approved

Not every exception can be pre-approved, and knowing which can is the judgment this discipline turns on. A case can be pre-approved when its answer is knowable in advance and safe to write down: the condition that marks the case can be defined clearly, the response is fixed and correct every time it occurs, and no live judgment is needed to apply it. The opted-out customer is such a case. The condition is plain, the customer asked not to be contacted, and the response is fixed, suppress the message and proceed. There is nothing to weigh in the moment, so the answer can be written once and followed by anyone. A case whose answer is that stable belongs at pre-approved.

A case cannot be pre-approved when its answer is not yet knowable, or when applying it genuinely needs a decision made in the moment. The unknown issue cannot be pre-approved, because no one yet understands it well enough to write its answer; you cannot write a guide for a case you have not understood. A case that turns on a judgment, how much to concede, whether the circumstances truly fit, what the right exception is among several, cannot be safely reduced to a written step either, because the writing would have to pretend a certainty the case does not hold. For these, the way forward is escalation, treated next, not a guide.

And here is the guard that keeps this honest: do not pre-approve a case that needs a live decision. A guide written for a case that genuinely requires judgment is a false guide, and a false guide is worse than none. It tells the Performer to proceed by a fixed answer where no fixed answer is right, and so it produces confident, uniform, wrong handling, harder to catch than an obvious gap, because it looks like the design working. The designer's precision here is to pre-approve exactly what is safe to pre-approve, and to route the rest to escalation without pretending it can be written down. Coverage that is false is not coverage; it is a hidden fault wearing the shape of an answer. Better an honest escalation than a written lie.

The highest possible standard is to pre-approve exactly those cases whose answer is knowable in advance and safe to fix in writing, with a clear condition and a fixed correct response, and to route every case that needs live judgment to escalation instead, never writing a guide that pretends a certainty the case does not hold.

Key Takeaway: A case can be pre-approved when its answer is knowable in advance and safe to write: clear condition, fixed correct response, no live judgment needed, like the opted-out customer. It cannot be pre-approved when its answer is not yet known, like the unknown issue, or when applying it genuinely needs a decision in the moment. The guard: never pre-approve a case that needs live judgment, a false guide is worse than none, because it produces confident, uniform, wrong handling that looks like the design working. Pre-approve what is safe; route the rest to escalation honestly.

Pre-approve only what is knowable and safe to write; a guide that pretends a certainty the case lacks is worse than no guide at all.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 5: Pre-Approved · Section: What can be pre-approved

MarvinPro | June 2026

marvinpro.com

The fewest touch-points

Ask why the designer reaches for pre-approved first and hardest, and the answer is the Performer. Every way forward costs the Performer something: an ask, a wait, an escalation, a hand-off, a decision sought from someone else. These are touch-points, and each one is a place the work stops. The whole of this design exists to let the Performer work as fast as possible, with as few actions and as few touch-points as the case allows. Pre-approved is where that cost falls to nearly nothing. The Performer meets the case, follows the standing guide, and proceeds, in the flow of the work, stopping for no one. A pre-approved exception is one the Performer barely feels, because the design already did the asking, the deciding, and the approving, in advance, so they do not have to.

This is why pre-approving is the highest-leverage handling there is. Each pre-approval takes a case that would have cost a touch-point, an escalation to a Leader, a wait for a decision, and removes that cost for every Performer who will ever meet the case. The designer does the thinking once; the saving repeats forever. So the designer reaches for pre-approved before the higher tiers, not out of tidiness but because it is where the most friction is removed from the most people. And pre-approving pairs with parking as the two ways a design goes live without waiting for perfection: park what can safely wait, and pre-approve what has a knowable answer, so the work can launch now, the Performer covered from the first day, rather than held back until every case is a rule. A pre-approved guide is often exactly this, the answer written down so the design can go live, sometimes the settled answer for the case, and sometimes a temporary work-around the designer means to replace as soon as the proper fix is ready. To the Performer the two are the same, a stable guide to follow; the difference lives only in the designer's intent.

And the touch-points fall further still, below pre-approved, when the case is folded into the rules. A pre-approved guide costs the Performer one small action, look it up, follow it. A rule costs even that no longer, because the case is no longer an exception; it is simply the normal work, handled by the rule that now fits it. So the descent the last discipline described, escalation to guide to rule, is, seen from the Performer's side, a steady stripping-away of touch-points: from asking someone, to reading a guide, to nothing at all. The designer drives every case as far down that path as it will go, because the aim, under all of it, is a Performer who meets fewer and fewer cases that cost them anything, and moves through the work as if the exceptions were never there. The guides this produces are the concern of the volume that treats guides in full; here, the point is only that each one exists to spare the Performer a touch-point.

The highest possible standard is to pre-approve wherever a case's answer can be safely written, because it removes a touch-point for every Performer who will ever meet the case, and to drive each case further down still, toward the rule that costs no touch-point at all, so the Performer works as fast as possible with as little to do as the design can arrange.

Key Takeaway: The designer reaches for pre-approved first because of the Performer: every way forward costs a touch-point, an ask, a wait, an escalation, and pre-approved costs almost none, the Performer follows the standing guide in the flow of work, stopping for no one. It is the highest-leverage handling: the designer thinks once, and the saving repeats for every Performer forever. It pairs with parking to let a design go live without waiting for perfection, and a pre-approved guide may be a settled answer or a temporary work-around, the same to the Performer. Below it, folding into a rule strips the touch-point away entirely.

Pre-approve to spare the Performer a touch-point, and fold into a rule to spare them even that, so they move as if the exception were never there.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 5: Pre-Approved · Section: The fewest touch-points

MarvinPro | June 2026

marvinpro.com

A real example

Return to the software company and the opted-out customer, the clearest pre-approved case in the design. Its answer was knowable in advance and safe to write: when a customer has asked not to be contacted, suppress the message and proceed. There was nothing to judge in the moment, so the handling was written into a guide, signed off once by those who held the authority over it, and set standing. From that day, any Performer who met an opted-out customer looked up the guide, followed it, and moved on, no one asked, no one interrupted, the case handled in the flow of the work. To the Performer it cost a single small action and no waiting. The approval had been banked; the touch-point was nearly gone.

Notice what the design did not do. It did not write a guide for the unknown issue, because the unknown issue had no knowable answer yet, and a guide pretending one would have told the Performer to proceed with confidence into a case no one understood. That case was left to escalation, honestly, until its answer was found. And notice too that not every pre-approved guide in the design was a final answer. When a work-around was found for a parked case, a way the Back Office could hold a client's channel preference by hand until the proper handling was built, that work-around was written up and pre-approved as well, so the Performer could follow it directly instead of escalating each time. It stood exactly like the opted-out guide, and the Performer followed it exactly the same way. The difference was invisible to them and lived only in the designer's intent: the opt-out guide was the settled answer, and the work-around guide was a bridge, to be replaced as soon as the real fix was ready.

So the design went live with a set of pre-approved guides doing quiet, heavy work, some settled, some temporary, each one sparing the Performer an ask or a wait. The opted-out customer never again reached a Leader; the client-channel work-around held the Performer steady until its rule was built; and the unknown issue, once solved, would have its own answer written into a guide in turn, dropping from escalation to pre-approved and sparing the next Performer the escalation the first had to make. Every guide was a touch-point removed, banked in advance by the designer so the Performer, meeting the case, could simply proceed. That is the pre-approved tier doing what it is for: making the exception, to the one who meets it, feel almost like no exception at all.

Every pre-approved guide, settled or temporary, was a touch-point the designer removed in advance, so the Performer could meet the case and simply proceed.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 5: Pre-Approved · A real example

MarvinPro | June 2026

marvinpro.com

Pre-Approved

The world calls a pre-approved exception a single deviation cleared in advance but still an exception, temporary, its risk accepted, set to expire and be reviewed again, a governance instrument whose home is the Govern domain. This book means something else. Here, pre-approved is a standing answer: the designer foresaw the case, decided its handling, wrote that into a guide, and had it signed off once, and from then the guide stands. The Performer follows it within full sanction and never seeks approval again, because the approval was banked, made once and standing, not granted-and-expiring. And the burden falls differently: the world's expiry lands on the doer, who must bring the case back for approval; here the guide never expires on the Performer, and the only expiry is the designer's own duty to fold the case into the rules in time. The provisionality is the designer's to carry; the Performer is given stability.

Not every case can be pre-approved. A case can be, when its answer is knowable in advance and safe to write, a clear condition, a fixed correct response, no live judgment needed, like the opted-out customer. It cannot be, when its answer is not yet known, like the unknown issue, or when applying it genuinely needs a decision in the moment. And the guard that keeps this honest: never pre-approve a case that needs live judgment, because a guide written for such a case is a false guide, and a false guide is worse than none, producing confident, uniform, wrong handling that looks like the design working. Pre-approve exactly what is safe to write; route the rest to escalation, without pretending it can be written down.

The reason the designer reaches for pre-approved first is the Performer. Every way forward costs a touch-point, an ask, a wait, an escalation, and pre-approved costs almost none: the Performer meets the case, follows the standing guide, and proceeds in the flow of the work, stopping for no one. It is the highest-leverage handling, because the designer thinks once and the saving repeats for every Performer who ever meets the case. It pairs with parking to let a design go live without waiting for perfection, park what can wait, pre-approve what has a knowable answer, launch now. And a pre-approved guide may be a settled answer or a temporary work-around; to the Performer they are the same stable guide, and the difference lives only in the designer's intent to replace the one and keep the other.

So the discipline is this: pre-approve every exception whose answer is knowable and safe to write, and no more. Write the standing answer into a guide, have it signed off once, and let the Performer follow it without asking anyone, sparing them a touch-point every time. Do not write a guide where the case needs live judgment; send that to escalation honestly. And carry, as the designer's own responsibility, the duty to drive each pre-approved case further down still, folding the recurring ones into the rules, until the case costs the Performer not even a guide, because the rule now fits it. Under all of it is one aim: a Performer who works as fast as possible, with as few actions and as few touch-points as the design can arrange, meeting each exception as though it were barely an exception at all.

Pre-approve what can be safely written, so the Performer follows a standing guide and stops for no one; then fold it into the rules, so in time the exception costs them nothing at all.

MarvinPro · PROCESS · Here is How to Build · Design · Exceptions · Discipline 5: Pre-Approved · Chapter Outcome

MarvinPro | June 2026

marvinpro.com

Think Simple.