From analysis to action — the eclipse of paralysis.
Proprietary instruments, developed for DDD — deliberate, decisive decisions.
Metamodels, models, frameworks, diagnostic instruments, tools and operating systems — some to diagnose, others to decide and act. A selection is shown here. Each answers a single question before anything is designed or decided, and prevents a different kind of error before acting.
Diagnose
Decide & act
Framework
MDIF · Multi-Dimensional Integrity Framework
The question: is this diagnosis seeing the whole situation, or only one line of sight?
Important decisions are often taken on diagnoses that are true but incomplete. MDIF keeps a many-sided human or organizational situation — and the real capacity of the people involved to act on it — from collapsing into a single angle, by testing the reading for the different ways an apparently valid diagnosis can still mislead.
The principle: it diagnoses; it does not decide. What it gives the decision-maker is the possibility of not deciding blindly.
Where it is used
- Before a major decision — on a complex human or organizational situation
- When capacity to act is itself in question — before assuming the people involved can carry the decision
- Second opinion — stress-testing a reading that already feels convincing
Diagnostic instrument
CM 360 · The Clarity Matrix
The question: where does clarity — over authority, accountability and purpose — actually break down?
Unclear goals are rarely the problem. Undefined boundaries of decision, accountability and purpose are.
CM 360 is a universal clarity architecture: wherever there is relationship, decision and connection — any structured action or decision, not only roles — it turns clarity into a verifiable condition and shows exactly where it is missing. Where tools like RACI or Bain’s RAPID assign roles and decision rights, CM 360 works one level up, on the clarity those tools take for granted.
McKinsey estimates that ineffective decision making costs a typical Fortune 500 company around $250 million a year in wasted management time.
Where it is used
- Any structured decision — before commitment, checking that authority, accountability and purpose are clear
- Governance audit — finding where clarity is undefined or in conflict
- Delegation — transferring decisions with autonomy, accountability and purpose specified
- Conflict resolution — tracing structural conflict back to where clarity broke down
Diagnostic instrument
The Tetramid
The question: before intervening, where in the person does the blockage actually sit?
Two people can fail at the same task for opposite reasons — and the same intervention will help one and harm the other. The Tetramid is the map that locates where a blockage actually sits, so the response matches the real cause instead of the visible symptom — the whole map, not a single axis of it.
Where it is used
- Diagnosis before coaching or training — locating the real point of blockage
- Matching intervention to cause — not to the loudest symptom
- Designing development — sequencing what to build, and in what order
Diagnostic instrument
The Categorial Cascade
The question: does every part of this plan actually derive from its purpose?
A plan can look complete on paper while teams quietly disagree on what it is for. The Categorial Cascade traces a course of action down its constitutive layers — each of which must follow from the one above — and exposes the exact level where coherence breaks.
Where it is used
- Plan review — before execution, checking that structure follows purpose
- Alignment — surfacing where teams diverge on intent
- Diagnosis of drift — finding the layer where a plan detached from its goal
Tool
TRD · Transdisciplinary Reality Diagnosis
The question: at what moment, and on which part of the system, does this actually need to be acted on?
Continuous effort on a problem that will not move usually means the intervention is aimed at the wrong moment or the wrong level. TRD reads a situation across time and across the system before an intervention is timed or targeted, so effort lands where it changes the outcome rather than on the loudest symptom.
Where it is used
- Intervention design — timing and targeting before resources are committed
- Stalled problems — locating why sustained effort produces no movement
- After an episode — deciding what to restore, and where
Metamodel
AACM · Axiological Action Coherence Model
The question: does this action deserve to be taken — not only, can it be taken?
Most decision and productivity models — from Boyd’s OODA loop to PDCA — stop once a course of action is viable. AACM adds the step they leave out by design: before execution, it checks the action against the values and the purpose it is meant to serve. It does not compete with the tools an organization already uses; it orders them and inserts the coherence check between design and execution.
Where it is used
- Before execution — at the hinge between a plan that works and a plan that should be launched
- Ordering existing toolkits — turning a menu of models into one sequence
- Across fields — first refined in critical-thinking programs; applicable to leadership, change and innovation
Model
The Triad of Action · The Three Existential Prepositions
The question: for this action, what does it free, what does it make me answer for, and what is it ultimately for?
Every decision has a reach and a set of consequences. The Triad of Action makes them explicit before the action is taken — what it frees you from, what it commits you to answer for, and the result it serves — so freedom and responsibility for the consequences stay matched. Freedom without responsibility is arbitrariness; responsibility without freedom is exploitation.
Where it is used
- High-consequence decisions — weighing reach and accountability before acting
- Delegation — handing over a decision with its consequences owned, not just its task
- After the fact — tracing an unintended consequence back to the frontier that was left open
Framework
Foundational Construction Criterion · The Law of Directionality
The question: which way is this being built — down from a purpose, or up from action — and does it still hold to a purpose either way?
A system can be built top-down, from purpose toward action, or bottom-up, from action back toward purpose — both legitimate directions. What matters is not the direction but that, either way, it stays anchored to a purpose rather than drifting into activity that serves none. This criterion makes the direction of construction visible and tests that the anchor holds — reading three things in turn: the direction a system runs (from its purpose, or toward one it never quite reaches), where the break sits, and, if it has drifted, how to re-anchor it.
Where it is used
- Strategy review — testing that initiatives, however they arose, still hold to a purpose
- Restructuring — finding where structure lost its link to intent
- Portfolio triage — separating anchored work from drift
Operating system
TDOS · Transversal Dialogic Operating System
The question: is this conversation built to produce real impact — or only to be held?
Meetings inform; they rarely leave a mark. TDOS structures dialogue so that it produces impact — a real shift in understanding, decision or commitment — rather than leaving that outcome to chance, and it does so at every level where dialogue exists, from one person’s internal deliberation to the conversation of a whole organization.
Where it is used
- Facilitation — designing conversations that move something, not minutes
- Culture and learning — building dialogue into how a group develops
- High-stakes forums — where the quality of the conversation determines the outcome
Tool
SMARTIES / SMARTIEST
The question: is this objective actually sound — not just clear, but ethically and strategically defensible?
An open extension of the SMART goal test (George T. Doran, 1981). Most goal-setting stops at clarity and measurability; SMARTIES extends it into fuller operational soundness, and SMARTIEST adds the ethical, intentional and sustainability scrutiny that strategic objectives demand — before the objective is committed to.
Where it is used
- Goal validation — before a target is locked in
- Strategic decisions — adding ethical and long-horizon scrutiny to major objectives
- OKR / target reviews — upgrading “clear” goals into defensible ones
“Purpose precedes Structure. Structure sustains action. Action provides Results.”
Each framework is described here by the question it answers. The full methodology is shared in conversation, under NDA.