One methodology, three working parts.
ZBT is the principle. GSDPI is the model that carries it. Two supporting instruments make the read actual and the outcome provable — together, the system behind every ETEGY engagement.
Zero-Based Transformation
Start from zero. Read how the enterprise actually works today — not what it was designed to do — and rebuild from evidence.
Explore →GSDPI lifecycle
Get · Sort · Do · Prove · Improve — the five stages every unit of work travels from demand to provable value.
Explore →Voice of the System & the Traceability Ratio
One reads the model in its actual state; the other measures whether the result can be traced to a governed origin — the input and the proof.
Explore →A challenger's note on the category's proof gap: Claims vs. evidence →
Get · Sort · Do · Prove · Improve
Every unit of work — a request, a deal, a deliverable, a decision — travels the same five stages. Read the model across all five, and you see exactly where strategy stops converting.
An operating model, read across the Core.
An anonymized contract-management value chain — 106 pain points across 32 work nodes, weighted by severity and frequency.
Actors, systems, pain, seams, and requirement signals across the Core.
Read horizontally for handoffs, vertically for lifecycle-stage failure patterns.
Mistaking a process map or status report for what the model can actually do.
No vertical is clean. The pain is systemic, not local — heaviest at Do and Prove, where work is executed and where it must be proven.
Surfacing this stopped the CLO from digitizing a broken model. Correcting the gaps — not the tool — let the rebuild target 60% faster contract review, 95% risk-flag accuracy, and 30% less manual effort, protecting the platform spend before a dollar was committed.
Begin with actual-state. It exposes the enablement requirements hidden by current-state, ideal-state, and launch-first planning.
We read the model as it actually runs — then prove it moved.
Every operating model has two versions: the one on the slide, and the one that runs on Monday. Voice of the System surfaces the second — the real pains, gains, and requirements at each stage. The Traceability Ratio then measures how much of the result reconciles to a governed origin — the difference between a number you report and one you can defend. A number you can trace beats a change multiple you can't.
Pains
Where work stalls, reverts, or routes around the governed path.
Gains
What already works and must be protected as the model changes.
Requirements
What the model must do to carry strategy to a provable outcome.
The Diagnostic
A structured readout and a board-ready deck: every pain point across the model, weighted and prioritized — yours to act on however you choose. Where you want to go further, the optional Enablement Roadmap partners a joint team to match and outline solutions to each prioritized pain. Yours to act on
Two words the field uses loosely. We hold them precisely.
Method lives in language. Where the vocabulary is fuzzy, the work drifts — so two terms carry a sharper definition inside GSDPI than the market gives them.
Mining and analytics render the current state from system logs — the paths the software can see. We read the actual state: how the work truly runs, including the pains, gains, and workarounds no log records. The current state is the map; the actual state is the territory.
In the field, enablement is often reduced to tools and training for the front line. We hold it higher and earlier: enablement is the set of executive decisions, integrations, prioritization, and funding the redesigned flow depends on. Change the model, and these are the moves leadership must own for it to run — not a training rollout after the fact.
How an engagement runs.
Three phases carry the engagement to the Diagnostic — the weighted, prioritized read of the operating model, the core deliverable. From there, optional continuations go as far as it's yours to own: the Enablement Roadmap, and guided delivery.
Prepare the approach
Frame the value stream, align sponsors, and ready the read — so the Discovery starts on the right work, with the right people in the room.
Conduct the Discovery
Structured working sessions read the actual state across GSDPI and rank the pains and gains — the evidence base, on a page.
Present the Diagnostic
The read becomes the deliverable: every pain point across the model, weighted and prioritized, in a structured readout and a board-ready deck — yours to act on as you choose. The core output of the engagement.
Build the Enablement Roadmap
Where you want to go further: over 2–4 weeks a joint team matches and outlines the solutions that resolve each prioritized pain — validating in-flight work and aligning with your SMEs.
Guide & resource the build-out
Where the change is yours to own, we stay to guide and resource delivery alongside your teams — and prove the outcome held.
GSDPI has a discipline, a language, and a growing body of work.
The full model — its stages, gates, and practice — is detailed across the ETEGY methodology.