The Darnok Principle

A knowledge and project application for protecting world-class outcomes from cumulative stakeholder compromise, scope drift and design-by-committee degradation using the DARNOK method.

The Darnok Principle: In collaborative design and decision-making, individually reasonable stakeholder changes can collectively degrade the final outcome unless every change is continuously assessed against the original intent and the whole system is kept on track.

Define • Assess • Revalidate • Navigate • Optimise • Keep on Track

New Darnok project

0 stakeholder proposals / 0 actions

Why this matters: Committees can contain excellent people making individually reasonable decisions and still create a collectively inferior outcome. The DARNOK Principle focuses attention on the cumulative effect of those decisions, not merely whether each change is defensible in isolation.

D — Define

Define the North Star outcome, what world-class means, the true constraints and the explicit non-goals before debate begins.

A — Assess

Assess every stakeholder contribution and classify it as Requirement, Constraint, Evidence, Preference or Assumption.

R — Revalidate

Revalidate each proposed change against the original intent and the agreed Critical-to-Outcome criteria.

N — Navigate

Navigate genuine trade-offs transparently. Do not allow compromise to occur invisibly merely to achieve consensus.

O — Optimise

Optimise the whole system, not individual departments, local objectives or the collection of compromises.

K — Keep on Track

Keep the evolving solution aligned through drift monitoring, the Racehorse Check and deliberate re-baselining where justified.

What the Darnok Principle Protects Against

Design by committee

A strong initial concept can become diluted as additional preferences, constraints and compromises accumulate. Consensus is not automatically evidence of excellence.

The Burgoyne Effect

The progressive degradation of an intended outcome caused by the cumulative effect of individually acceptable stakeholder compromises.

Outcome baseline

Define the intended world-class outcome before debating changes. Without a baseline, drift is difficult to recognise or challenge.

Critical to Outcome (CTO)

CTOs are the weighted success factors that determine whether the intended outcome remains excellent, viable and sustainable.

Requirements ≠ preferences

Classify inputs as Requirement, Constraint, Evidence, Preference or Assumption. Seniority does not convert preference into requirement.

Cumulative assessment

Each change must be considered both individually and as part of the total evolving solution. Local optimisation can degrade the whole.

Original Diagram — How a Racehorse Becomes a Donkey

🏇 Intended Outcome

World-class concept with clear purpose, success criteria and value proposition.

→

Stakeholder Accumulation

“Could we also…?”
“My department needs…”
“To get agreement, add…”
“It would be safer if…”

→

🫏 Burgoyne Effect

Every decision appears rational in isolation, but the whole is no longer the best answer to the original need.

The Five Input Classes

R — Requirement

Mandatory need arising from customer, contract, law, safety, regulation or technical necessity. The source should be identifiable.

C — Constraint

A genuine boundary within which the solution must operate, such as time, budget, interface or physical limitation.

E — Evidence

Verified information that informs the decision, such as test data, customer evidence, capability data or prior learning.

P — Preference

A desired feature or approach that may be useful but is not mandatory. Preferences should not silently become requirements.

A — Assumption

Something believed to be true but not yet evidenced. Assumptions should be validated before being allowed to reshape the solution.

Key challenge

Whenever a stakeholder asks for a change, ask: R, C, E, P or A? Then ask what evidence demonstrates benefit to the whole.

“Optimise the whole, not the compromises.”

Learning point: The Darnok Principle does not suppress stakeholder contribution. It improves it by requiring every contribution to remain connected to the intended outcome.

The Darnok Method

D — Define

Define the intended world-class outcome and freeze the initial outcome baseline.

→

A — Assess

Assess each stakeholder input, its evidence, classification, benefit and risk.

→

R — Revalidate

Revalidate the evolving proposal against the original intent and CTO criteria.

N — Navigate

Navigate genuine trade-offs deliberately and visibly rather than through accidental compromise.

→

O — Optimise

Optimise the whole system and protect the highest-value total outcome.

→

K — Keep on Track

Keep the solution aligned through drift checks, Racehorse reviews and controlled re-baselining.

DARNOK Governance Cycle

1. Define Intent

State the North Star outcome, success criteria, non-goals and genuine constraints.

→

2. Challenge Change

Classify each proposal and demand evidence of contribution, impact and trade-off.

→

3. Revalidate Whole

Compare the evolving solution with the original baseline using unchanged success criteria.

Darnok Controls for World-Class Committee Output

1. Outcome Charter

Agree the intended outcome, what excellence means, constraints and non-goals before solution discussion begins.

2. CTO Weighting

Weight success criteria before evaluating options so the criteria cannot later be manipulated to favour a preferred idea.

3. Outcome Guardian

Nominate one person with explicit authority to challenge drift, preference masquerading as requirement and cumulative compromise.

4. Burden of Proof

A proposed change must demonstrate why it should be accepted; the baseline should not have to continually defend itself.

5. No Consensus Trap

Consensus is useful but is not the decision criterion. Evidence and whole-system performance take priority.

6. Racehorse Check

At key gates ask whether the result is still what the team would deliberately select if presented afresh today.

7. Controlled Re-baseline

If evidence shows that the original intent should genuinely change, redefine it deliberately and transparently rather than drifting accidentally.

The Darnok Comparison

Present the original baseline and the current proposed solution side-by-side and score both against the same CTO criteria. If the current solution would not be selected over the original when viewed afresh, cumulative degradation has occurred.

Baseline A

Original concept before stakeholder accumulation.

⇄

Same CTO Criteria

No retrospective re-weighting without formal justification.

⇄

Current B

Evolved concept after committee changes.

Outcome Charter

Define the racehorse before the committee starts redesigning it.

Organisation / Team

Project / Concept

Project Reference

Assessment Date

Decision Owner

Outcome Guardian

Current Baseline Version

Decision Gate

North Star Outcome

Success Definition

Genuine Constraints

Explicit Non-Goals

Critical to Outcome (CTO) Criteria

Weight the factors that define excellence. Total weighting should equal 100%.

#	CTO Criterion	Description	Weight %	Baseline Score /10	Current Score /10	Evidence / Notes

Project Dashboard

0%CTO weighting

0Baseline weighted score

0Current weighted score

100%Outcome Integrity

0Accepted proposals

HealthyDarnok status

Stakeholder Proposal Register

Capture each proposed change before it becomes part of the solution.

ID	Stakeholder / Function	Proposal	Class	Source / Evidence	Benefit to Outcome	Complexity	Risk to Whole	Decision

High contribution to intended outcome with low complexity or downside.

Evaluate

High contribution but high complexity, cost, risk or irreversible consequence.

Question

Low contribution and low complexity. Avoid clutter that adds little value.

Reject

Low contribution with high complexity or whole-system degradation.

Escalate uncertainty

Where evidence is weak, convert the debate into an investigation rather than a compromise.

Re-baseline deliberately

If the environment has genuinely changed, formally redefine the intended outcome rather than allowing silent drift.

Outcome Integrity Test (OIT)

For each significant proposal, answer the six questions below before acceptance. A change should not proceed merely because nobody objects.

1. What problem does this change solve?

2. Which CTO does it improve?

3. What evidence supports it?

4. What does it negatively affect?

5. What complexity or unintended consequence does it add?

6. Is the whole now closer to or further from the North Star?

Outcome Drift Visualisation

100% represents the original baseline. The current marker moves left as weighted outcome performance falls.

100%Current integrity

0%Cumulative loss

0Accepted preferences

0Accepted assumptions

0Rejected proposals

LowDrift risk

The Racehorse Check

“If the original proposal and the current proposal were presented side-by-side for the first time today, which would we deliberately choose?”

The current solution is still recognisably aligned to the original North Star. Current changes demonstrably improve or preserve weighted CTO performance. No preference has been silently treated as a mandatory requirement. Assumptions affecting the design have been identified and validated or bounded. Complexity added by stakeholders is proportionate to the value created. The current solution would still be selected if reviewed afresh against the original criteria. Implementation remains technically, operationally, financially and organisationally sustainable. Any intentional departure from the original concept has been formally re-baselined.

Baseline Solution — What did we originally intend?

Current Solution — What are we now proposing?

Would we choose the current solution if presented afresh?

Racehorse Decision

Decision Rationale

Interpretation: Complete the CTO scoring and Racehorse Check to assess whether committee changes remain aligned to the intended world-class outcome.

Governance Action Plan

Turn drift, uncertainty and design compromise into controlled actions.

ID	Action	Type	Owner	Target	Purpose / Expected Benefit	Status

Darnok Principle Project Report

Create a concise evidence-based record of the outcome charter, CTO baseline, stakeholder changes, integrity score, Racehorse Check and governance actions.

Key Findings

Primary Drift Risk

Committee Behaviour to Control

Recommended Decision