
The body of work
TransformationOS™, mapped.
Tap or hover any term: what it means, where it sits, and why it is there.
Large companies fund transformation to move faster and to grow. The hard part is rarely the strategy.
Thousands of people have to willingly change how they think and work while the business keeps running. TransformationOS™ is the system we built for that problem. The map below shows every working part and how they connect.
People do not resist change. They resist being changed.
The reading order
- 1The problem, reframed
- 2The outcome
- 3The asset: adaptive capacity
- 4The machinery: real work to mechanisms
- 5Ways of engaging
The same order the argument runs in: problem first, method last.
The map
One connected system.
TransformationOS™ sits at the top. Below it, the whole system in reading order: the problem it reframes, what it produces, and the machinery that makes it work.
TransformationOS™ sits at the center. To the right: what it produces, the asset it builds, and where capability develops. To the left: the problem reframed and the machinery that makes it work.
The breakdown
The map, in words.
The same definitions as the map, written out for reading top to bottom — and for smaller screens.
The operating system
TransformationOS™
How we help big companies change faster and grow: your own people solve real business problems, coached by operators who have done it before, and along the way the company gets better at change itself.
Everything on this map is a part of that system. Start anywhere.
Why change programs stall
The Problem, Reframed
Most programs assume the hard part is finding the right answer. It rarely is. The hard part is getting thousands of people to change how they work, willingly, while the business keeps running.
The key difference
Adaptive vs. technical challenges
A technical problem has a known fix: install the system, done. An adaptive challenge asks people to change how they work, and you find the answer as you go.
Trouble starts when leaders treat the second kind like the first.
Root cause
Why people resist
People do not resist change. They resist being changed. What looks like stubbornness is someone protecting something real: their status, their skill, their sense of who they are.
Heavy resistance usually means the change came at people the wrong way.
What it looks like
Passive resistance
Everyone nods in the meeting. Then they go back to doing what they did before. Nobody argues, and nothing changes.
Why training is not enough
Knowing is not doing
Your people already know what to do. Then the quarter gets hard and old habits win. More training is the wrong tool for that.
The difference that matters
Adoption ≠ adaptation
Adoption is using an answer someone else picked. Adaptation is getting better at handling whatever comes next.
You can push adoption. Adaptation you have to build.
Our design rule
Designing Out Resistance™
The program itself creates most of the resistance it meets: the answer came from somewhere else, and the people who have to live with it got no say.
Design the change with those people, and most of that resistance has no reason to form.
Why the executive cares
The Outcome
Two results, produced together: the transformation moves faster, and the company grows more than the old plan was going to deliver.
The result
Accelerated Transformation
The strategy moves at the speed you promised the board. Less resistance, less rework, fewer projects that stall after the announcement.
The result
Breakthrough Growth
Growth the old plan was not going to deliver: new markets, new ways of selling, money the old model left on the table. It comes from people being able to do new things.
What the company builds
The Asset
Under the results sits the thing that produces them: how good your organization is at change. We build that on purpose and measure it, because it decides how fast everything else moves.
The asset
Adaptive Capacity
How well your people handle change: they respond when plans break, solve problems with no playbook, and build whatever skill the strategy needs next.
Plans go stale fast. This is what keeps the company ready anyway.
What the strategy needs now
Specific Capabilities
The concrete skills: enter the new market, price on value, run big accounts differently, build real pipeline.
Courses rarely build them. Doing the work does.
Where people build skills
Consequential Real Work
People rarely learn this in a classroom. They learn it by solving problems the business needs solved, with real deadlines and real money on the line.
The idea
The work is the curriculum
A real project, a real deadline, a real number. People try harder and learn faster when the problem is real.
The payoff
Two results at once
Each project delivers a business result and better people. You stop choosing between running the business and developing your team.
The order that works
Mindset → Skillset → Toolset
Belief comes first. Skills come next, built in the work. Tools come last, when a team asks for them. Hand out tools first and they end up on the shelf.
How we run it
AIRAS
Align → Inspire → Reflect → Apply → Scale. The rhythm we run inside a company, one cohort at a time.
Agree on the goal
Align
Leadership gets clear on the real challenge and on the room teams have to move. Freedom works when the edges are clear.
Show what is possible
Inspire
Operators who have done it share what worked at companies like yours. People start to believe there is a way.
Find the real problem
Reflect
Teams turn the lens on their own business: what is really in the way, and what they will own. The answers people find themselves are the ones they act on.
Do the work
Apply
Teams run Growth Projects™ on live problems with a coach beside them. This is where the learning gets real.
Pass it on
Scale
What worked spreads. The people who did it coach the next group, so the skill stays in the company.
What makes it work
The Mechanisms
The working parts. Each one creates a condition that lasting change needs.
Where ownership starts
Co-diagnosis
Ask the people closest to the work what the real problem is, before anyone brings an answer.
Hand people a diagnosis and they poke holes in it. Let them make it and they defend it.
Mechanism
Structured Autonomy
Clear boundaries, real freedom inside them. Leaders own the what; teams own the how. That trade turns participation into ownership.
Mechanism
Guided Discovery
Coaches ask instead of tell. What people figure out themselves, they defend.
The measure
AQ® / GRIT™
Two measures of how people handle hard things: AQ® for how they respond to setbacks, GRIT™ for how long they keep going. Measure before, build through the work, measure again.
The unit of work
Growth Projects™
A small team, a real problem, about 90 days, ending in front of the leadership team. One project produces a result, skills, owners, and proof.
Mechanism
Operator-Coaching
Coaches who have done the job themselves. They ask more than they tell, and the room listens because they have been there.
The end state
Transformation Architects
Where this ends: your own people can run this without us. We build the skill and hand it over.
Where to start
Ways of Engaging
One body of work. Start with your own thinking, with one leader, or across the whole company.
The peer room
The Consortium
The Commercial Excellence Consortium™: leaders with the same job, comparing notes honestly. No sponsors, no pitches.
See it clearly first
Diagnostic & Roadmap
A clear look at where your transformation is stuck and why. Then a plan: what to change, in what order.
Build the leader
Fellowship™
A year beside operators and peers who have done it. You learn to lead this way of working on the mandate you already own.
Build the organization
Accelerator / Academy
Teams of your people solve real business problems with a coach beside them, cohort after cohort. Results now, and a company that keeps producing them.
Most enterprises are over-engineered for control and under-engineered for adaptation.
TransformationOS™ exists to change the question — from “How do we implement this transformation?” to “How do we build an organization that gets better at transforming itself?”