GSDPI™ gives every team the same five plain words for the work: Get, Sort, Do, Prove, Improve. A finance lead, an IT owner and a sponsor can describe the same flow the same way, at every level and in every business unit. Here are those words, and the few others the method uses.

A Traceability Ratio™ state: work the flow should have produced did not appear at all.
A Traceability Ratio™ state: work was performed or billed with no governed origin behind it.
A Traceability Ratio™ state: work entered under governance but never reached its result or its billing.
A Traceability Ratio™ state: work entered under governance and reached its result. The state a flow is expected to hold.
Being answerable for an outcome, including where the outcome crosses teams. Distinct from doing the work in a lane.
Work performed and reported: milestones met, workstreams green, status on track. A transformation can be fully active and still leave the operating model unchanged.
The operating model as it runs today, observed in the work rather than as documented or intended.
A family of delivery methods that build and release in short iterations. Agile executes defined work; it does not define what the operating model must make true.
The third step of BRACE™ for Transformation: defining the operating requirements the change must satisfy.
Establishing which change produced a result, and how much of it. A financial task in its own right, separate from tracing work to its governed origin.
The documented starting position against which later change is read. Without one, movement cannot be shown.
The person accountable for producing a benefit in the operation and for the evidence that it occurred.
The discipline of turning delivered work into value the business can verify, traced from a governed origin through a change in how the work runs.
A fix inside one team’s work is improvement, little t. A change that crosses a seam between teams, or needs an enterprise function owner, is transformation, Big T.
The first step of BRACE™ for Transformation: setting what the transformation covers, its object and its limits.
The transformation application process: Bound · Read · Architect · Connect · Establish Proof. Its steps do not map one-to-one to the GSDPI™ functions.
The argument for an investment: expected value, cost and risk. A business case can be arithmetically correct and still depend on operating conditions no one has established.
What an enterprise’s own people can do repeatably, on their own work, after any program or advisor has left.
Awarded on completing the Practitioner Intensive. An internal completion recognition, not an external certification, accreditation or license.
Awarded on completing the Foundation Course.
The discipline of helping people adopt a change. It works alongside transformation; it does not define what the operating model must make true.
The executive accountable for how the enterprise turns strategy into operating change: which initiatives are funded, stopped or re-sequenced, and whether each GSDPI™ function has a named enterprise function owner.
A statement that value was, or will be, produced. Every claim sits in an evidence state, and should carry no more authority than its evidence permits.
The group taking a course together: up to twelve people drawn from many teams within one enterprise.
The first lens of the Operating Requirements Model: what must change?
The fourth step of BRACE™ for Transformation: connecting the work, owners and enablement to the operating requirements.
A Governing Criteria rating: the criterion has been stated, but it is disputed or read differently by the people who must hold it.
One of the four narrow seam columns between the five GSDPI™ functions, where something must survive the transition from one function to the next.
The distance between what a strategy requires and what the operating model can produce: where approved intent fails to become changed work.
The value-producing business work of the enterprise: order-to-cash, hire-to-retire, procure-to-pay and the like. The subject of Zero-Based Transformation™.
The ETEGY evidence and traceability paper. It develops the Traceability Ratio™ and argues that reported value is insufficient without governed origin, flow, measurement and proof.
Who decides what, and at which point. One of the three parts of transformation governance, with cadence and an evidence standard.
Building and running defined work, in any method: projects, products, agile teams. Delivery executes what has been defined.
Higher-order GET: how demand is generated and taken in across the enterprise, a cross-functional orchestration no single person owns.
A business unit, department, region, site or product. Inside a flow, a domain is a swimlane; read on its own, it is its own lifecycle.
The fourth lens of the Operating Requirements Model: what does it take?
The Enablement Requirements a change depended on that were never built: records, rules, handoff checks and ownership. Invisible until it costs money, it collects wherever a function has no enterprise owner.
What must be owned, funded, sequenced, governed, installed or corrected so that a change becomes executable.
The one person accountable for a GSDPI™ function across the whole enterprise: whether GET, SORT, DO, PROVE or IMPROVE is built for the fastest path to value, on its own and with the other four. An accountability, not a department.
Coordinating flows and functions across the enterprise so that results are not lost between owners.
The fifth step of BRACE™ for Transformation: establishing the evidence that the required change occurred.
The firm that developed ZBTOS™ and authors its papers. ETEGY carries external transformation mandates; ZBTOS builds internal capability.
The fifth lens of the Operating Requirements Model: how will we know?
The position a value claim holds: Proposed, Forecast, Evidenced or Validated. A claim moves between states only as its evidence changes.
An evidence state: operating records show what has actually changed in the work.
One stream of value-producing business work, such as order-to-cash or hire-to-retire.
An evidence state: an expected result with an operating and financial basis, not yet observed in the work.
A two-day private course for up to twelve people from many teams within one enterprise. Teams learn the method on the Meridian case, applied to their own work where they choose. Certificate of Completion.
The first GSDPI™ function: work enters. The GET record is the governed origin of the work.
Authority, decisions, accountability and control over a transformation. Distinct from the Governing Criteria, which set what the transformation must satisfy.
The GET record: the point where work entered the flow under governance. The anchor every Traceability Ratio™ state is read against.
What a transformation must satisfy, evaluated qualitatively as Stated, Contested or Missing. Never scored. One of the four components of Zero-Based Transformation™.
Get. Sort. Do. Prove. Improve.® Five standing functions present in every flow, whether or not anyone is managing them. Six ways to read them. One coordinate system.
A course exhibit that lays one flow across the five GSDPI™ functions. Taught in the Foundation Course.
A point where work passes from one team, system or lane to another, and where something must survive the transition.
One of the six named GSDPI™ reads: following one flow through the five functions.
Raising performance inside the operating model you already run. Contrast transformation, which changes the operating model itself.
A funded unit of work within a transformation portfolio.
A change introduced into the operation, such as AI, a platform or a reorganization. It may change any or all of the five functions; it is never the organizing logic of GSDPI™.
One of the five questions every operating requirement must answer in the Operating Requirements Model. Lenses are questions, not types of requirement.
The whole: every flow together, or a comparison across complete wholes. A view, not an axis. One of the six named reads.
The authorized charge to change something, with its scope, its sponsor and its expected result.
The controlled shared case worked in the Foundation Course. Teams apply it to their own work, or work it end to end where they prefer not to expose their own.
A Governing Criteria rating: the criterion has not been stated.
The layer between strategy and delivery where the operating requirements go undefined.
Every GSDPI™ function runs at two levels: inside each lane, and higher-order across the enterprise. One lane’s output is another lane’s GET.
A point in the architecture: one function in one lane. A seam is between; a node is at. One of the six named reads.
The value-producing business work a read declares it is reading. Every read declares its object.
An operating model is a collection of integrated end-to-end value streams and lifecycles/workflows engineered and orchestrated to produce scalable value.
An examination of how a flow actually runs, set against the requirements, decisions, resources and evidence that govern how it produces value.
What the operating model must make true for a strategy to hold. They come in two kinds: Transformation Requirements and Enablement Requirements.
A supporting model that asks one question, “What must the operating system make true?”, and tests every requirement against five lenses: Condition, Reach, Authority, Enablement and Evidence.
Coordinating work that no single owner holds, so that it arrives where it is needed.
A result in the operation: work running differently, value produced. Distinct from an output.
Something delivered: a system, a process, a document. An output may or may not produce an outcome.
Who does the work in a lane. Every workstream has an owner; ownership alone does not say who decides at the seams.
A project or portfolio management office. It governs delivery: scope, schedule, budget and risk.
The set of initiatives funded under a transformation, reviewed for what they change and what that is worth.
One cohort works one explicit live transformation of its own and produces real artifacts and defendable outputs. Certificate of Applied Completion.
The steps and decisions within a defined scope, drawn so a step can be improved. A process map may cross several teams.
Evidence that a claimed change occurred in the work and produced the value attributed to it.
An evidence state: the opportunity and its assumptions have been identified.
The fourth GSDPI™ function: completion and value are evidenced.
The second lens of the Operating Requirements Model: where must it hold?
An examination of the operating model through GSDPI™. GSDPI™ has six named reads: Vertical, Horizontal, Seams, Node, Swimlane and Macro.
The second step of BRACE™ for Transformation: reading the actual operating model in scope through GSDPI™.
Value that has actually occurred and been recognized. A defensible or forecast value is not yet realized value.
An operating handshake where something must survive a transition: between functions, between swimlanes, or between levels.
One of the six named GSDPI™ reads: examining the handshakes where work must survive a transition.
The three marks a Voice of the System™ point carries.
The second GSDPI™ function: work is routed. Higher-order SORT routes each unit of work to its lowest capable, most cost-effective path.
The executive who funds a transformation and is accountable for its result.
A Governing Criteria rating: the criterion has been stated and is held the same way by the people who must satisfy it.
Where the business is going and how it intends to compete. A strategy holds only when the operating model can make it true.
ZBTOS™ Success Support: bounded, fixed-scope principal support while a trained team applies the method. The client team owns every deliverable.
A row in a flow: one team, function or domain across the five GSDPI™ functions. Some lanes enter the flow later.
One of the six named GSDPI™ reads: following one lane across the five functions.
An intended future state, usually described as structure, roles and capabilities. The distance between it and the actual state is where many redesigns stall.
Whether a piece of work, or the value claimed from it, connects back to its governed origin.
A way to read whether work connects from its governed origin, the GET record, to its result. Four states: 1:1 got and billed, 1:0 got, no-bill, 0:1 side door, 0:0 expected activity absent.
Changing the operating model itself: how work enters, is routed, done, proven and improved across a flow. Contrast improvement.
An enterprise’s ability to see its operating model, define what must change, carry the change and prove the result, with its own people.
The decision rights, cadence and evidence standard that determine whether a transformation is changing the operating model.
A free orientation: ten questions, five minutes, showing the operating model behind your transformation. Not a skills score or certification.
The function that governs operating change across a portfolio: what each initiative must change and whether the evidence shows it changed.
What must change in the Core for a strategy to hold.
A free, structured self-assessment of the system behind your transformation.
An evidence state: the claimed result has passed the applicable review and validation requirements.
One end-to-end flow of value-producing work, from a request entering to its value being proven, across every team and system it passes.
One of the six named GSDPI™ reads: inspecting one function across the enterprise.
The read of the Zero-Based Transformation™ sessions: pain and gain points heard in aggregate. Each point is marked Seen, Recorded or Reported.
The sequence a piece of work follows through tasks and systems.
A delivery unit within a transformation program, usually with its own owner, plan and status.
The integrated operating system that brings the doctrine, architecture, instruments and governance of Zero-Based Transformation™ together.
The methodology. It establishes what must change, and comprises the Governing Criteria, GSDPI™, BRACE™ for Transformation and the ZBTOS™ operating system.
Not ready for a course? Get the ZBTOS Briefing › New terms, reads and tools as the method develops.

Training, assessment and support for transformation capability.
Carrying an external mandate? ETEGY →GSDPI™ gives every team the same five plain words for the work: Get, Sort, Do, Prove, Improve. A finance lead, an IT owner and a sponsor can describe the same flow the same way, at every level and in every business unit. Here are those words, and the few others the method uses.
A Traceability Ratio™ state: work the flow should have produced did not appear at all.
A Traceability Ratio™ state: work was performed or billed with no governed origin behind it.
A Traceability Ratio™ state: work entered under governance but never reached its result or its billing.
A Traceability Ratio™ state: work entered under governance and reached its result. The state a flow is expected to hold.
Being answerable for an outcome, including where the outcome crosses teams. Distinct from doing the work in a lane.
Work performed and reported: milestones met, workstreams green, status on track. A transformation can be fully active and still leave the operating model unchanged.
The operating model as it runs today, observed in the work rather than as documented or intended.
A family of delivery methods that build and release in short iterations. Agile executes defined work; it does not define what the operating model must make true.
The third step of BRACE™ for Transformation: defining the operating requirements the change must satisfy.
Establishing which change produced a result, and how much of it. A financial task in its own right, separate from tracing work to its governed origin.
The documented starting position against which later change is read. Without one, movement cannot be shown.
The person accountable for producing a benefit in the operation and for the evidence that it occurred.
The discipline of turning delivered work into value the business can verify, traced from a governed origin through a change in how the work runs.
A fix inside one team’s work is improvement, little t. A change that crosses a seam between teams, or needs an enterprise function owner, is transformation, Big T.
The first step of BRACE™ for Transformation: setting what the transformation covers, its object and its limits.
The transformation application process: Bound · Read · Architect · Connect · Establish Proof. Its steps do not map one-to-one to the GSDPI™ functions.
The argument for an investment: expected value, cost and risk. A business case can be arithmetically correct and still depend on operating conditions no one has established.
What an enterprise’s own people can do repeatably, on their own work, after any program or advisor has left.
Awarded on completing the Practitioner Intensive. An internal completion recognition, not an external certification, accreditation or license.
Awarded on completing the Foundation Course.
The discipline of helping people adopt a change. It works alongside transformation; it does not define what the operating model must make true.
The executive accountable for how the enterprise turns strategy into operating change: which initiatives are funded, stopped or re-sequenced, and whether each GSDPI™ function has a named enterprise function owner.
A statement that value was, or will be, produced. Every claim sits in an evidence state, and should carry no more authority than its evidence permits.
The group taking a course together: up to twelve people drawn from many teams within one enterprise.
The first lens of the Operating Requirements Model: what must change?
The fourth step of BRACE™ for Transformation: connecting the work, owners and enablement to the operating requirements.
A Governing Criteria rating: the criterion has been stated, but it is disputed or read differently by the people who must hold it.
One of the four narrow seam columns between the five GSDPI™ functions, where something must survive the transition from one function to the next.
The distance between what a strategy requires and what the operating model can produce: where approved intent fails to become changed work.
The value-producing business work of the enterprise: order-to-cash, hire-to-retire, procure-to-pay and the like. The subject of Zero-Based Transformation™.
The ETEGY evidence and traceability paper. It develops the Traceability Ratio™ and argues that reported value is insufficient without governed origin, flow, measurement and proof.
Who decides what, and at which point. One of the three parts of transformation governance, with cadence and an evidence standard.
Building and running defined work, in any method: projects, products, agile teams. Delivery executes what has been defined.
Higher-order GET: how demand is generated and taken in across the enterprise, a cross-functional orchestration no single person owns.
A business unit, department, region, site or product. Inside a flow, a domain is a swimlane; read on its own, it is its own lifecycle.
The fourth lens of the Operating Requirements Model: what does it take?
The Enablement Requirements a change depended on that were never built: records, rules, handoff checks and ownership. Invisible until it costs money, it collects wherever a function has no enterprise owner.
What must be owned, funded, sequenced, governed, installed or corrected so that a change becomes executable.
The one person accountable for a GSDPI™ function across the whole enterprise: whether GET, SORT, DO, PROVE or IMPROVE is built for the fastest path to value, on its own and with the other four. An accountability, not a department.
Coordinating flows and functions across the enterprise so that results are not lost between owners.
The fifth step of BRACE™ for Transformation: establishing the evidence that the required change occurred.
The firm that developed ZBTOS™ and authors its papers. ETEGY carries external transformation mandates; ZBTOS builds internal capability.
The fifth lens of the Operating Requirements Model: how will we know?
The position a value claim holds: Proposed, Forecast, Evidenced or Validated. A claim moves between states only as its evidence changes.
An evidence state: operating records show what has actually changed in the work.
One stream of value-producing business work, such as order-to-cash or hire-to-retire.
An evidence state: an expected result with an operating and financial basis, not yet observed in the work.
A two-day private course for up to twelve people from many teams within one enterprise. Teams learn the method on the Meridian case, applied to their own work where they choose. Certificate of Completion.
The first GSDPI™ function: work enters. The GET record is the governed origin of the work.
Authority, decisions, accountability and control over a transformation. Distinct from the Governing Criteria, which set what the transformation must satisfy.
The GET record: the point where work entered the flow under governance. The anchor every Traceability Ratio™ state is read against.
What a transformation must satisfy, evaluated qualitatively as Stated, Contested or Missing. Never scored. One of the four components of Zero-Based Transformation™.
Get. Sort. Do. Prove. Improve.® Five standing functions present in every flow, whether or not anyone is managing them. Six ways to read them. One coordinate system.
A course exhibit that lays one flow across the five GSDPI™ functions. Taught in the Foundation Course.
A point where work passes from one team, system or lane to another, and where something must survive the transition.
One of the six named GSDPI™ reads: following one flow through the five functions.
Raising performance inside the operating model you already run. Contrast transformation, which changes the operating model itself.
A funded unit of work within a transformation portfolio.
A change introduced into the operation, such as AI, a platform or a reorganization. It may change any or all of the five functions; it is never the organizing logic of GSDPI™.
One of the five questions every operating requirement must answer in the Operating Requirements Model. Lenses are questions, not types of requirement.
The whole: every flow together, or a comparison across complete wholes. A view, not an axis. One of the six named reads.
The authorized charge to change something, with its scope, its sponsor and its expected result.
The controlled shared case worked in the Foundation Course. Teams apply it to their own work, or work it end to end where they prefer not to expose their own.
A Governing Criteria rating: the criterion has not been stated.
The layer between strategy and delivery where the operating requirements go undefined.
Every GSDPI™ function runs at two levels: inside each lane, and higher-order across the enterprise. One lane’s output is another lane’s GET.
A point in the architecture: one function in one lane. A seam is between; a node is at. One of the six named reads.
The value-producing business work a read declares it is reading. Every read declares its object.
An operating model is a collection of integrated end-to-end value streams and lifecycles/workflows engineered and orchestrated to produce scalable value.
An examination of how a flow actually runs, set against the requirements, decisions, resources and evidence that govern how it produces value.
What the operating model must make true for a strategy to hold. They come in two kinds: Transformation Requirements and Enablement Requirements.
A supporting model that asks one question, “What must the operating system make true?”, and tests every requirement against five lenses: Condition, Reach, Authority, Enablement and Evidence.
Coordinating work that no single owner holds, so that it arrives where it is needed.
A result in the operation: work running differently, value produced. Distinct from an output.
Something delivered: a system, a process, a document. An output may or may not produce an outcome.
Who does the work in a lane. Every workstream has an owner; ownership alone does not say who decides at the seams.
A project or portfolio management office. It governs delivery: scope, schedule, budget and risk.
The set of initiatives funded under a transformation, reviewed for what they change and what that is worth.
One cohort works one explicit live transformation of its own and produces real artifacts and defendable outputs. Certificate of Applied Completion.
The steps and decisions within a defined scope, drawn so a step can be improved. A process map may cross several teams.
Evidence that a claimed change occurred in the work and produced the value attributed to it.
An evidence state: the opportunity and its assumptions have been identified.
The fourth GSDPI™ function: completion and value are evidenced.
The second lens of the Operating Requirements Model: where must it hold?
An examination of the operating model through GSDPI™. GSDPI™ has six named reads: Vertical, Horizontal, Seams, Node, Swimlane and Macro.
The second step of BRACE™ for Transformation: reading the actual operating model in scope through GSDPI™.
Value that has actually occurred and been recognized. A defensible or forecast value is not yet realized value.
An operating handshake where something must survive a transition: between functions, between swimlanes, or between levels.
One of the six named GSDPI™ reads: examining the handshakes where work must survive a transition.
The three marks a Voice of the System™ point carries.
The second GSDPI™ function: work is routed. Higher-order SORT routes each unit of work to its lowest capable, most cost-effective path.
The executive who funds a transformation and is accountable for its result.
A Governing Criteria rating: the criterion has been stated and is held the same way by the people who must satisfy it.
Where the business is going and how it intends to compete. A strategy holds only when the operating model can make it true.
ZBTOS™ Success Support: bounded, fixed-scope principal support while a trained team applies the method. The client team owns every deliverable.
A row in a flow: one team, function or domain across the five GSDPI™ functions. Some lanes enter the flow later.
One of the six named GSDPI™ reads: following one lane across the five functions.
An intended future state, usually described as structure, roles and capabilities. The distance between it and the actual state is where many redesigns stall.
Whether a piece of work, or the value claimed from it, connects back to its governed origin.
A way to read whether work connects from its governed origin, the GET record, to its result. Four states: 1:1 got and billed, 1:0 got, no-bill, 0:1 side door, 0:0 expected activity absent.
Changing the operating model itself: how work enters, is routed, done, proven and improved across a flow. Contrast improvement.
An enterprise’s ability to see its operating model, define what must change, carry the change and prove the result, with its own people.
The decision rights, cadence and evidence standard that determine whether a transformation is changing the operating model.
A free orientation: ten questions, five minutes, showing the operating model behind your transformation. Not a skills score or certification.
The function that governs operating change across a portfolio: what each initiative must change and whether the evidence shows it changed.
What must change in the Core for a strategy to hold.
A free, structured self-assessment of the system behind your transformation.
An evidence state: the claimed result has passed the applicable review and validation requirements.
One end-to-end flow of value-producing work, from a request entering to its value being proven, across every team and system it passes.
One of the six named GSDPI™ reads: inspecting one function across the enterprise.
The read of the Zero-Based Transformation™ sessions: pain and gain points heard in aggregate. Each point is marked Seen, Recorded or Reported.
The sequence a piece of work follows through tasks and systems.
A delivery unit within a transformation program, usually with its own owner, plan and status.
The integrated operating system that brings the doctrine, architecture, instruments and governance of Zero-Based Transformation™ together.
The methodology. It establishes what must change, and comprises the Governing Criteria, GSDPI™, BRACE™ for Transformation and the ZBTOS™ operating system.
{{ leaveBlurb }}
ZBTOS teaches you to read, define and govern the work yourselves. ETEGY does it for you.
Not ready for a course? Get the ZBTOS Briefing › New terms, reads and tools as the method develops.

Training, assessment and support for transformation capability.
Carrying an external mandate? ETEGY →