Bounded facilitated application
Make the decision rule visible before a system hardens it.
Decision Modelling & Operational Logic
Align the people who own, inform, operate, and review one recurring decision around a rule they can explain—and the exceptions it must not hide.
The work improves the basis for choice. It does not make the decision for its owner or promise that every exception can be resolved.
Fit and reason to act
Is this the decision?
Use focused work when a consequential operational choice recurs, its interpretation is scattered, and another commitment could scale the wrong rule.
- RecurrencePeople meet the same situation repeatedly, but the expected choice is not stable.
- InterpretationAuthority, evidence, and operating knowledge live with different people or systems.
- ExceptionA rare but material case could make the apparent rule unsafe or misleading.
Decision trigger Use it before automating, replacing a workflow, or funding reporting built on unclear operational logic.
Five-voice decision rehearsal
Let each person finish only the line they carry.
These are simultaneous perspectives, not process steps. Ask the relevant people to complete their line aloud without first negotiating a shared answer.
- Owner
- “We are deciding whether to name the consequential choice.”
- Evidence holder
- “The choice changes when this evidence crosses a meaningful condition.”
- Operator
- “I can carry it out if the rule, authority, and next action are usable here.”
- Exception holder
- “The rule breaks when this material case falls outside its safe boundary.”
- Reviewer
- “We reopen it when new evidence or a named event changes the trade-off.”
If two people complete the same decision differently, that disagreement is the first bounded scope. The rehearsal does not produce a recommendation; it reveals what focused work must reconcile.
What focused work changes
Turn competing completions into defensible operating logic.
The engagement stays with one decision long enough to expose what is binding, what is uncertain, and what should remain a human-owned exception.
- Language
Reconcile different descriptions of the decision without erasing legitimate disagreement.
- Authority
Name who can choose, who informs the choice, and who carries it into operation.
- Evidence
Select the smallest useful review of recent decisions that could change the next action.
- Exception
Test which cases materially alter the rule and which are routine variation.
- Review
State the evidence or event that should reopen the choice after commitment.
Possible outcomes remain genuinely different: clarify the current rule and ownership; reduce the decision scope; investigate one material uncertainty; or defer system change until the logic can be defended.
Output, investment, and boundary
Bound one decision, not the whole system.
Scope, fee, inputs, schedule, and definition of done are agreed before work begins. The engagement cannot manufacture authority or evidence access that is not available.
One recurring decision + accessible recent examples + a named owner → bounded operational logic
You receive
A decision model people can inspect.
A bounded decision model, option comparison, logic and evidence register, named owner, accepted trade-offs, next action, and review trigger.
Boundary and stop condition
Clarity without manufactured certainty.
One agreed decision domain and accessible evidence. The work stops at the agreed model and next commitment; it does not include a production system or guarantee that every exception can be resolved.
Continue independently
Compare a worked decision first.
The playbook keeps four credible choices open and shows what bounded evidence can—and cannot—establish.
Use the worked playbookOptional fit conversation
When interpretations need reconciling
Describe the recurring decision and what makes it difficult. An email starts a conversation; it does not reserve capacity or purchase work.
Ask about a bounded application