ZBTOS by ETEGY
Ten questions · 5 minutesTransformation Lens Check →

One enterprise. Many teams. One way to define the transformation.

The Foundation Course: two days, private to your enterprise. Up to twelve people from the transformation office, PMOs and in-flight workstreams learn ZBTOS™ on one shared case and leave with one method and one language.

Request program information →Get the one-page sponsor memo ›
Day one of a ZBTOS Foundation Course
Two days.
Private to your enterprise.
Up to twelve people.
From the transformation office, PMOs and in-flight workstreams.
One shared case.
Meridian, worked end to end. Certificate of Completion.
The two days

Day 1: read the transformation. Day 2: build and prove the response.

Everyone works the same shared case, so each team learns the method the same way. Application moments connect each tool to the transformation work participants already know. About 40 percent of the time is exercises and breakouts, a third is teaching, and the rest is debrief and faculty challenge.

Day 1 · Read the transformation
Day 1 · AMZero-Based Transformation™ doctrineMandate, intended value and the actual operating system, not the initiative list as given.
Day 1 · AMGSDPI™ Lifecycle Map: map the workPopulate the five functions against the case: how work is actually produced and the evidence it emits, phase by phase, boundary by boundary.
Day 1 · PMReading the work six waysVertical, Horizontal, Seams, Node, Swimlane and Macro expose different operating conditions. Groups reconcile competing reads into one view.
Day 1 · PMVoice of the System™ and the Seam & Handoff LabActual work, exceptions and workarounds as signals; how work crosses hands, state and meaning.
Day 2 · Build and prove the response
Day 2 · AMTransformation Architecture Map and governed conditionsMandate, conditions, requirements, enablement and work. Then owners, decision rights, evidence and gates.
Day 2 · PMTransformation Traceability Map and Value Proof MapFollow the response into work, authority, evidence and control, then hold each claim to the strongest position its evidence allows.
Day 2 · CloseThe Integrated Case LabTeams run the whole system from mandate to value proof, and defend the reasoning against faculty challenge.

Optional close: a facilitated mapping exercise that applies the frame to your own situation, without the course becoming about it.

What participants learn to see

One unit of work, followed across the seams.

On day one the cohort maps a quote-to-cash flow on the GSDPI™ Lifecycle Map: five functions across, the teams that touch the work down. Then they follow one request through it. The exhibit below is the kind of read they produce. Every team did its step correctly. The defect entered at intake, crossed four handoffs unflagged, and surfaced as a customer dispute that PROVE could catch but not fix.

EXHIBIT · PROFESSIONAL SERVICES, QUOTE-TO-CASH
GET
SORT
DO
PROVE
IMPROVE
Governance
Intake standard
Deal desk review
Status & risk
Portfolio review
Margin review
Sales
1Inbound request
Qualify opportunity
2Scope & estimate
Quote approved
Change request
Pricing rules
Delivery
Resource request
3Staff assignment
Project setup
Deliverable review
4Time & expense
Utilization & margin
Estimate calibration
Finance
Rate card & terms
Revenue plan
5Bill run
Revenue recognition
6Invoice
Forecast reliability
Customer
Statement of need
Acceptance
7Dispute
Renewal signal
1 Started here: the request arrived without the terms that priced it.7 Showed up here: the customer dispute.Numbered boxes trace one unit of work across the seams.
Where it started
The request came in without the terms that priced it: scope boundary, rate tier, change rule. Intake accepted it anyway. Nothing failed yet, so nothing was flagged.
How it compounded
Each handoff inherited the gap and added to it. The estimate was built on the assumed scope, the staffing on the estimate, the time booked against the staffing, the bill run against the time. By the invoice, four functions had each done their step correctly.
Why PROVE caught it, and couldn’t fix it
The dispute is where the evidence finally had to stand up. Billing owned the invoice, Delivery owned the hours, Finance owned recognition. Nobody owned the proof that the work matched what was sold. The dispute was settled; the intake rule was never changed.

Day two turns the read into operating requirements: what intake must make true, who owns proof across lanes, and how IMPROVE closes the loop. Participants leave able to produce this read on their own transformation.

What they leave with

A common language, and the toolkit to use it.

The five foundational tools
GSDPI™ Lifecycle Map
You get: How the work actually moves across the five functions, and the priorities to read next.
Voice of the System™
You get: The condition that deserves deeper inquiry.
Transformation Architecture Map
You get: The chain from strategy to work that most needs its connections tested.
Transformation Traceability Map
You get: The value question that most affects what you can claim.
Value Proof Map
You get: Every value claim placed no stronger than its evidence allows.
Plus seven practice aids: Method Map · Mandate & Transformation Frame · Read Guide · Seam & Handoff Inquiry · Owner / Decision Right / Evidence / Gate Sheet · Case Synthesis Canvas · First-Read Plan.
Also in their hands
Guides and completed case work
The Participant Guide carries the method; the Applied Workbook carries their own working. Every exercise completed on the case goes home with them.
One evidence discipline
Every observation carries its evidence basis: Seen, Recorded or Reported.
Certificate of Completion
Recognizes completed participation and exercise work. The Practitioner Intensive’s Certificate of Applied Completion is the applied standard.
For the sponsoring executive

You are not buying a training day. You are installing a common operating language.

Most enterprises now run several transformations at once, each with its own owner, vocabulary and definition of done. Foundation puts them on one model: every area keeps its own transformation and reads it on the same architecture, so overlaps, gaps and work that should be owned once surface across them.

KPMG, Transforming the Enterprise 2026: an average of 3.5 concurrent transformations; 14% rate themselves top performers (n = 1,750).

Nominate the people who carry your transformations, from as many teams as need to read it the same way. Before Day 1, a 30-minute sponsor orientation covers what ZBTOS is, what the two days teach, and what your team will and will not leave able to claim.

Afterward, ask them one question: what do you now see that you couldn’t see before?

Bring your teams into one room for two days.

Most cohorts go on to the Practitioner Intensive with their own live transformation.

Request program information →See the Practitioner Intensive ›
ZBTOS by ETEGY

Training, assessment and support for transformation capability.

Carrying an external mandate? ETEGY →
Zero-Based Transformation™, ZBTOS™, GSDPI™, Voice of the System™ and Traceability Ratio™ are trademarks of ETEGY. Get. Sort. Do. Prove. Improve.® is a registered trademark of ETEGY. Privacy · © 2026 ETEGY