Five operating functions across the top. The people who touch the work down the side. Every question a transformation actually turns on has an address here. Six reads — and the one you choose decides which questions you are able to ask.
GSDPI™ is not a process map or a fixed sequence. It is a common coordinate system for examining transformation at any level of the enterprise — one unit of work, an operating function, a team, a business unit, a region, or a whole portfolio. The model stays fixed; your point of view changes. Read it vertically, horizontally, across the seams, at a single node, by swimlane, or at the macro level — each read answers a different question while preserving the same operating logic. That is what lets a leader move from execution detail to the 50,000-foot view without changing frameworks.
Project method reads one row. Process work reads one column. Neither is wrong — but a transformation is lost at the seams between them, and no single read finds those on its own.
There is no meeting where an enterprise resolves to leave its transformation ungoverned. The structure simply never gets stood up, and the consequence arrives in the same order every time.
…but nobody converts it into operating requirements. Teams are handed outcomes and left to infer what has to become true.
…and the work that falls between them belongs to no one. Seams are where transformation is lost, and no scope owns a seam.
…without a governed origin. Capacity is consumed by work the model never sanctioned and the forecast never priced.
…and value is reported rather than proven. Execution succeeded, therefore the benefit is assumed.
Every one of those is a governance absence, not an execution failure. That is why running the projects harder never closes it.
ZBTOS does not add a layer of oversight on top of delivery. It changes what is true at five points where transformation normally leaks.
Transformation is not an event that concludes. The next mandate arrives before the last one is proven, which means the read has to be repeatable by people who stay. An external read produces a finding; a capability produces a standard — and the standard is what holds when the engagement ends.
That is the whole design intent of ZBTOS. The doctrine is published, the instruments are documented, and the method is taught rather than retained. Your practitioners run it. ETEGY carries it only where you want it carried.
Actual state, on demand, without waiting for a statement of work.
What qualifies as a governed origin here, and what evidence is required.
Authority to decline work that cannot be traced — the one thing no external party can exercise.
A dated history of what was claimed and what was proven, that survives leadership change.
The value is not another model.
It is one operating logic the enterprise can keep using.
Each layer answers the one above it. Nothing in ZBTOS exists without a layer it reports to.
Establishes what must change, from actual state rather than current state, ideal state or launch-first planning.
The five standing operating functions every unit of business work moves through. It reads vertically as functions, horizontally as work in phases, and at the macro level as the integrated execution path.
Two instruments apply the lifecycle to a live enterprise: one reads where conversion stops, the other measures whether the work can be followed to a governed origin at all.
Three free reads establish the condition. Four deeper assessments put a defensible number and narrative behind it.
Foundation teaches the method on a standard worked case. The Practitioner Intensive moves a cohort from guided application to governed practice on one live transformation.
The operating rhythm that keeps required state, work, evidence and value reconciled after the capability is in place.
An assessment tells you what is true; it does not carry the change. When the finding needs someone to carry enterprise intervention against a live mandate, that is ETEGY — where the system was built and is still applied.
The operating condition does not wait for the portfolio to be ready. Reading it early costs a diagnostic; reading it late costs the program.