PROCESS

Here is How to Build

Design

Rules

The five agree

The earlier disciplines took the five dimensions one at a time, the deed, the manner, the moment, the reason, the one it falls to, each designed with its own care. But a rule is not five things; it is one. The five are decided separately so they can be seen clearly, yet they live together in a single rule, and a rule is sound only when they agree. This discipline steps back from the parts to the whole, and asks not whether each dimension is good on its own, but whether the five, together, make one rule that holds.

Agreement means the five serve each other. The manner suits the reason, a fixed template serves the end of one clear word to every customer. The moment suits the who, the message falls where the team that owns it can send it. The deed suits its manner, the reason justifies the moment, each dimension fits the others, all pulling the same way. When the five agree, the rule is whole: it does one thing, in one way, at one place, for one reason, by one team, and every part of it points at the same purpose. Such a rule is more than the sum of five good choices; it is a single coherent decision, and it will hold in use because nothing in it works against anything else.

This is why the five are designed together, not in turn and bolted up at the end. A designer who fixes the deed, then the manner, then the moment, each in isolation, may end with five decisions that are each defensible alone and yet do not fit, a manner too rigid for the moment it lands in, a doer who cannot reach the place the moment requires. The five must be chosen with each other in view, so that the reason chosen shapes the manner chosen, and the moment chosen shapes the who. Agreement is not luck; it is the result of designing the five as one. The test of a sound rule is to lay the five side by side and ask whether they agree, whether each could be explained as serving the same end as the rest.

The highest possible standard is to design the five dimensions so they serve each other, laying them side by side to confirm the deed, manner, moment, reason, and doer all point at one purpose, so the rule is a single coherent decision and not five separate choices that happen to coexist.

Key Takeaway: A rule is not five things but one, and it is sound only when the five agree, when they serve each other, the manner suiting the reason, the moment suiting the who, each pulling the same way. A rule whose five agree is whole: one thing, one way, one place, one reason, one team, all pointing at the same purpose, and it holds in use because nothing works against anything else. Agreement is not luck but the result of designing the five together, with each other in view, rather than fixing each alone and bolting them up at the end.

A rule is sound when its five agree: the deed, manner, moment, reason, and doer all serving one purpose.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 7: A Sound Rule · Section: The five agree

MarvinPro | June 2026

marvinpro.com

A rule at war with itself

When the five do not agree, the rule is at war with itself, and it will show in use even when each dimension looked right on its own. The disagreement is rarely visible on paper, where each decision can be read alone and found sound. It surfaces only when the rule is run, when the dimensions that pull against each other meet in the doing, and the rule strains, slows, or breaks at the seam where they disagree.

The shapes of disagreement are worth knowing, because they are how a rule fails quietly. A manner that fights its reason: a template so rigid it cannot carry the human judgement the reason was meant to protect, so the rule, followed to the letter, betrays its own purpose. A moment that fights its who: the rule fires at a point where the team it falls to is not yet in the work, or has already left it, so the right team cannot act at the time the rule demands. A deed that fights its moment: the act is placed where the thing it depends on has not yet happened, so it runs on nothing. In each, two dimensions were each chosen well, and chosen without the other in view, and the rule carries a contradiction it will pay for later. The cost is hidden until the rule runs, and then it is paid in workarounds, in delay, in a rule that is followed and still fails.

So testing a rule for soundness is testing the five for agreement, before they are paid for in use. Lay them side by side and look for the pair that pulls apart: does any dimension ask for something another denies? Does the manner serve the reason, or strain against it? Does the moment suit the doer, or strand them? A rule that passes this test, whose five agree, is sound at its core; a rule that fails it carries a war inside that no quality in the single dimensions can settle. The fix is never to harden one dimension further; it is to bring the disagreeing ones back into agreement, to redesign the pair as one. A rule is mended by making its five agree, not by making any one of them stronger.

The highest possible standard is to test a rule by laying its five dimensions side by side and looking for the pair that pulls apart, mending any disagreement by bringing those dimensions back into agreement rather than by hardening one of them, so the rule carries no contradiction into use.

Key Takeaway: When the five do not agree, the rule is at war with itself, and it shows only in use, not on paper, where each decision reads as sound alone. Disagreement has knowable shapes: a manner that fights its reason (too rigid to carry the judgement the reason protects), a moment that fights its who (firing when the team is not in the work), a deed that fights its moment (placed before what it depends on). The cost is hidden until the rule runs, then paid in workarounds and delay. Test for it by laying the five side by side, and mend by bringing the disagreeing pair back into agreement, not by hardening one.

A rule at war with itself reads sound on paper and fails in use; mend it by making its five agree, not by hardening one.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 7: A Sound Rule · Section: A rule at war with itself

MarvinPro | June 2026

marvinpro.com

What a rule is

Having designed every dimension and seen what makes them one, you can now say plainly what a rule is. Begin before the rule, with the requirement. A requirement is something that must be, a need the work has to meet for it to be right, safe, lawful, or whole. The customer, client, patient, student, or citizen must be informed. The record must never be wrong. Each is a statement of what must or must not be, and it exists before anyone has designed how to meet it. The requirement says what must be true; it does not yet say how, or when, or by whom. That is left to the rule.

A rule is a requirement given form. It takes the thing that must be and makes it a deed that can be done, in a fixed manner, at a fixed place in the structure, for a written reason, by the team whose work it is, the five decisions, designed as one. The requirement is the source; the five are the form. And because a rule is born from a requirement, it binds: it carries the must or must not of its requirement into the work. This is what a common definition sees from the outside, a rule as a statement of what is allowed, required, prohibited, or expected under certain conditions. That is true, and it is the rule as the one who follows it meets it: a constraint that says what may, must, or must not be done, and when. But this book is for the one who builds it, and to the builder a rule is more than a constraint to obey. It is a requirement given form, five decisions held as one, each of which could have been chosen differently, and was chosen for a reason.

So you can now give both definitions, and say why the second is the deeper. To whoever follows it, a rule defines what is required or prohibited under conditions. To whoever designs it, a rule is a requirement given form: a single statement that is five decisions designed as one, a deed, in a fixed manner, at a fixed place in the structure, for a written reason, by the team whose work it is, binding because it is born from a requirement, and sound when its five agree. The follower meets the rule as a wall; the designer meets it as a decision, and knows every part of why the wall stands where it does. That knowledge, the whole of it, is what this book has been building, and it is what lets a designer make rules that are not only complete, but sound.

The highest possible standard is to hold the whole of a rule in view, the requirement it is born from, the five decisions that give it form, the force it carries because it is a requirement, and the agreement of its five that makes it sound, so you can explain what a rule is to anyone, from either side.

Key Takeaway: A rule begins before itself, in a requirement, something that must be (the customer, client, patient, student, or citizen must be informed), which says what must be true but not how, when, or by whom. A rule is that requirement given form: five decisions designed as one, and binding because it is born from a requirement. A common definition names the rule from outside, what is allowed, required, prohibited, or expected under conditions, the follower's view; the designer's view is deeper: a requirement given form, five decisions held as one, sound when they agree.

A rule is a requirement given form: five decisions designed as one, binding because it is a requirement, and sound when its five agree.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 7: A Sound Rule · Section: What a rule is

MarvinPro | June 2026

marvinpro.com

A real example

Take the rule one last time, whole. The requirement came first: every customer must receive the same clear word at each step of their case. That was what had to be true, the need, before any rule existed. The rule gave it form, the deed of informing, in the fixed manner of a template, at three fixed moments in the case, for the written reason that every customer hear the same, by the teams whose work each message was. Five decisions, and behind them a requirement that made the whole thing binding: the messages were not a courtesy but an obligation, because the requirement said they must be.

And the five agreed. The manner served the reason, a fixed template gives one clear word. The moment suited the who, each message fell where the team that owned it was already in the work. The deed suited its moment, the resolution message placed after the work it reports, never before. Lay the five side by side and none pulled against another; each could be explained as serving the same end. Had they disagreed, had the template been too rigid for a moment that needed a human hand, or a message timed for a team not yet in the case, the rule would have read well and failed in use. Instead it held, because it was one coherent decision, not five separate ones. The same holds outside a company: a hospital's requirement that a patient be told of a change becomes a sound rule only when the deed, manner, moment, reason, and the ward that carries it all agree, and it binds because the requirement said the patient must be told.

So the rule, seen whole, is what this book set out to build: a requirement given form, five decisions designed as one, binding because it is a requirement, and sound because its five agree. To the patient or the customer it is simply what must happen and when. To the designer it is every one of those decisions, made on purpose, fitting together, and explainable to anyone who asks, from either side.

A rule is a requirement made into five decisions that agree, binding because it is required, and whole because it is designed as one.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 7: A Sound Rule · A real example

MarvinPro | June 2026

marvinpro.com

A Sound Rule

A rule is not five things but one, and it is sound when its five dimensions agree. The deed, the manner, the moment, the reason, and the one it falls to are decided separately so they can be seen clearly, but they live in a single rule, and a sound rule is one where they serve each other, the manner suiting the reason, the moment suiting the who, every part pointing at one purpose. Such a rule is a single coherent decision, and it holds in use because nothing in it works against anything else. This is why the five are designed together, with each other in view, not fixed one at a time and bolted up at the end.

When the five do not agree, the rule is at war with itself. The disagreement hides on paper, where each decision reads as sound alone, and surfaces only in use, where the dimensions that pull against each other meet, a manner too rigid for the moment it lands in, a deed placed before the thing it depends on, a rule followed to the letter and failing anyway. So a rule is tested by laying its five side by side and looking for the pair that pulls apart, and it is mended by bringing those dimensions back into agreement, never by hardening one of them further.

And now the whole of a rule can be said. A rule is born from a requirement, something that must be, the customer, client, patient, student, or citizen must be informed, a statement of what must be true but not yet of how, when, or by whom. A rule is that requirement given form: a single statement that is five decisions designed as one, a deed, in a fixed manner, at a fixed place in the structure, for a written reason, by the team whose work it is. It binds because it is born from a requirement. A common definition names it from the outside, what is allowed, required, prohibited, or expected under conditions, and that is the rule as the one who follows it meets it. The designer's definition is deeper: a requirement given form, five decisions held as one, sound when they agree.

You now hold the whole of a rule. You can name what it is born from, the requirement; what it is made of, the five decisions; what gives it force, that it is itself a requirement; and what makes it sound, that its five agree. You can explain it from either side, as a constraint to whoever follows it, and as a designed decision to whoever builds it. This is what the disciplines have been for: not to make rules that are merely complete, with every dimension filled in, but rules that are sound, whole, coherent, binding for a reason, and explainable to anyone who asks. The last discipline turns from the single rule to what rules make together, for a process is a structure of rules.

A rule is a requirement given form, five decisions designed as one, binding because it is a requirement, and sound when its five agree.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 7: A Sound Rule · Chapter Outcome

MarvinPro | June 2026

marvinpro.com

Think Simple.