∅
ApproachTHE METHODWorkCASE LIBRARYFor WhomFOR WHOMPlatformTHE INSTRUMENTBeginREQUEST A DIAGNOSTIC →
Shun-Ya / The approach

From confusion to a designed system.

Nine steps. Ninety days. The practitioner exits. The system runs.

0Idealized design first
1Governing signal
7Exit criteria
Feedback & leverage
The paradox

When every part reports success,
the whole bleeds.

An organisation has purposes. Its parts have purposes. The larger system it belongs to has purposes. All three must be served simultaneously.

— after Russell Ackoff
LEVEL 01
The Parts

Each reports success. KPIs in green. Reviews passed. The whole bleeds.

LEVEL 02
The Whole

Runs below capacity despite everyone working. No one can name the one signal.

LEVEL 03
The Containing System

Externalities uncounted. Second and third-order effects invisible to the dashboard.

The people inside are working. Hard. In good faith. They simply cannot see the one thing that, if it moved, would move everything else. Shun-Ya gives them the mirror.

One governing constraint

Find the one thing limiting the signal.
Everything subordinates.

Noise — many metrics, none governing
Signal — the one metric that proves movement
Constraint — the one thing limiting it now
The method

Nine steps. Ninety days.

The practitioner exits. The system runs.

9steps
90days
0dependency at exit
→ Drag to move through the method
0
Entry
Anonymous Diagnostic

Fifteen questions. No account required. The system identifies whether the pain is signal, noise, constraint, or rhythm.

Before account · 15 min
1
Understand
System Map

The organisation defined from the outside in. Boundary, purpose, parts, flows, current reality, desired natural state. Not a department chart.

Day 1–3
2
Design
Zero Session

If this organisation didn't exist, what would you build? The founding cell answers. The Design Record becomes the standard — the people's own design.

Day 1–14
3
Name
One Signal

The one metric that proves movement toward purpose. Named by the people inside. If three answers emerge, the first noise is found.

Day 14–16
4
See
Noise Catalogue

Every meeting, report, KPI, approval, review that does not move the signal. Named, typed, owned. Naming it is the first act of removal.

Day 29–45
5
Focus
Constraint

The one thing that, if relieved, would move the signal for the whole. Named. Owned. Everything else subordinates.

Day 29–75
6
Run
Weekly Rhythm

Thirty minutes. Same five questions every week. Did the signal move? What blocked it? One decision — a name and a date. The practitioner is not in the room.

Weekly · Day 15–90
7
Document
Operating Charter

The stable operating logic: signal, constraint rule, decision rights, rhythm. Compiled from engagement data. Printed. On the wall.

Day 76–90
8
Exit
Dependency Removed

Seven criteria. All must pass. If the system collapses after exit, Shun-Ya failed. Exit is not a ceremony. It is proof of ownership.

Day 90
The seven questions

Asked against the design.

The design is the standard — the people's own stated design, measured against itself. Not the practitioner's prior judgment.

Q.0
What did the people inside say it should be?
The anchorThe design. The standard everything else is measured against.
Q.1
What is the one output this organisation exists to produce?
SignalIn the language of the people, not the practitioner.
Q.2
What metric proves it is moving toward that output?
MeasurementThree answers = first noise found. The signal cannot be plural.
Q.3
Which decisions repeat without being made?
GovernanceDecision rights absent or unclear.
Q.4
Which meetings produce no decision and no changed behaviour?
NoiseInstitutionalised noise in its most expensive form.
Q.5
Where does a handoff fail or slow between functions?
InterfaceWhere the system breaks between its own parts.
Q.6
What does the incentive system actually reward vs. claim to?
Most criticalThe real signal governs behaviour. The most important question.
Q.7
What in the current organisation does not appear in the design?
Noise filterEverything present that was not in the design is a candidate for removal.
Natural state

When harmony is found.

One Signal

Everyone names the same metric: what is the one thing this organisation exists to move?

No Internal Conflict

Each part's success contributes to the signal of the whole. Local efficiency is not rewarded at the cost of throughput.

Constraint Known

The one thing limiting the signal is named, owned, and being actively relieved.

Decisions Flow

The decision is made by the person who can make it, with the information needed, when it is needed.

Rhythm Holds

Thirty minutes every week. Same questions. The system runs the rhythm without the practitioner.

Practitioner Unnecessary

The organisation owns its signal, constraint logic, and rhythm. The practitioner is not in the room.

The exit discipline

If the system collapses after exit,
Shun-Ya failed.

Exit is not a closure ceremony. Exit proves ownership. If the review stops when the practitioner leaves, the engagement failed. Not paused. Failed.

Exit criteria — all seven must pass

Signal defined and tracked

Three weekly entries captured without practitioner prompting.

Constraint known and owned

Constraint logic held by the local team, not the practitioner.

Rhythm runs without practitioner

Two complete weekly reviews led by the local owner.

Operating Charter printed

Wall sheet owned and legible without the practitioner.

Local owner explains the design

Signal, constraint, rhythm — in the owner's own language.

Noise Catalogue in local hands

The organisation identifies new noise without the practitioner.

Practitioner write access removed

System access terminated. The engagement is complete.

Begin here

See where your system stands.

Begin with the fifteen-minute diagnostic — it names whether your pain is signal, noise, constraint, or rhythm before anything else.

Start the diagnostic →