Transformation or Improvement?
New mandate. How much must actually change?

Calling it wrong is expensive either way: a transformation run as improvement leaves the flows unchanged, and an improvement run as a transformation buys a portfolio one function could have delivered.Just 12% of organizations are agile enough to launch a strategic initiative in under three months.KPMG, Deliver real value from enterprise transformation (2026), from Transforming the Enterprise, n = 1,750
Two kinds of mandate
A new strategy, a new CEO or a new financial target arrives, and it is usually called a transformation. Some of these mandates can be met by improving performance inside the operating model the enterprise already runs. Others cannot be met until the operating model itself changes.
Improvement makes the current flows faster, cheaper or more reliable. Transformation changes how the flows work: where work enters, how it is routed, what counts as done and how value is proven. Both are legitimate. They are different kinds of work.
Four questions that tell them apart.
What your team can do after training.
Foundation teaches the method on the Meridian case, with each area applying it to its own work. Practitioner Intensive applies it to one live transformation.
Run the Foundation Course with the incoming leadership team and the people who will carry the work. They learn to perform the mandate assessment themselves, and each area leaves knowing what to examine in its own program.
Outcome: Tell improvement from transformation before money is committed. Learned through the Meridian case in Foundation; applied to one live transformation in the Practitioner Intensive.
Little-t work improves a part. Big-T work changes how the parts connect.
Can one mandate be both?
Often. A transformation of one flow may be surrounded by improvements in others. The point is to know which parts are which, so each gets the method and governance it needs.
Why does the label matter?
Because methods built to deliver defined work are good at improvement and not built to define a transformation. The label decides which method gets used.
Where does ZBTOS teach this?
The Foundation Course opens with it: reading a mandate against the operating model of a shared case to decide how much must change.

