Library · read it before you commit to it

You should be able to inspect the method
before you build a capability on it.

The doctrine, instruments and working logic behind ZBTOS are published in full. Test them against your own operating model and judge the method on its own terms.

The technical paper

Counted, Not Proven

Why leaders may be defending a number their operating model cannot trace.

Defines traceability as a proof principle, specifies the Traceability Ratio™ as the metric produced by applying it to detected work, and sets out the origin–flow state read. Written for executives, boards and value-creation leaders accountable for converting transformation investment into governed execution and measurable enterprise value.

Read the paper → See the instrument →
The argument in six moves
The readingThe proof principleThe ratioThe deceptive caseThe forward readThe standard
2026 Edition · Darrin Devereaux
Published in full.
Start from where you sit

The same system reads differently
depending on what you are accountable for.

Two seats now carry transformation value, and one team runs it.

Chief Strategy Officer
Does the strategy convert?

Strategy stopped being a planning function. The plan is approved and the question that follows is whether the operating model can execute it at all — a different question from whether the plan is good. Required conditions, not initiatives, decide it.

Zero-Based Transformation™ — the doctrine →Voice of the System™ →Mandate framing checklist →
Chief Financial Officer
Can you defend the number?

Transformation value has landed on your desk whether or not it was ever in the mandate. The opex case, the automation case and the performance-improvement forecast are all priced against a work population most operating models have never reconciled. Find out how much of it can be followed before it is banked.

Counted, Not Proven — the paper →Traceability Ratio™ →Baseline defensibility checklist →
Transformation Office
You run it day to day.

You carry the mandate operationally: admitting demand, holding gates, producing evidence, reconciling what was promised against what happened. Project method delivers work once the work is known. What is missing is a way to read whether it should have entered at all.

GSDPI™ — the Core →Transformation office, day one →Steering committee readiness →
The instruments

How the operating model is read.

Read Guides

Sixty questions per function.
And the answer that should worry you.

Not a task list — there is nothing to tick off as done. A Read Guide is the inquiry that establishes actual state: twelve questions for each of the five GSDPI™ functions, marked as it stands today, producing a function profile and an assignable work plan. The complete instrument is issued inside Foundation and the Practitioner Intensive. One function is published free so you can judge the depth.

Free sample · published in full Finance · Prove Twelve questions on how finance evidences value — whether a claimed saving reaches the P&L, who verifies it, and what would falsify it. Marks build a work plan you can assign and print. Open the sample →
Course material The complete instrument All sixty questions across Get, Sort, Do, Prove and Improve, with the five-function profile. Issued and taught inside Foundation and the Practitioner Intensive. Foundation → Practitioner Intensive →
Checklists

Eight ways to find out
before it costs you.

Conditions drawn straight from the doctrine. Tick through one, see where you stand, print it for the room.

Read it, then run it.