
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 outcomes, and the asset beneath them
- 3The machinery that runs it
- 4The science it stands on
- 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 delivers, the order that works, the science it stands on, and where to start. 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 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, train people on it, done. An adaptive challenge asks people to change how they work, and you find the answer as you go. Most transformations are adaptive challenges.
Trouble starts when leaders treat an adaptive challenge like a technical one: buy the tool, run the training, wonder why nothing moves.
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.
That is useful news. Heavy resistance is a signal about how the change came at people, and you can design that differently.
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.
It is the most expensive kind of resistance because it looks like agreement, and the timeline slips a quarter at a time.
Why training is not enough
Knowing is not doing
Your people already know what to do. Many could teach the class. Then the quarter gets hard and old habits win.
That gap is about behavior, and more training is the wrong tool for it.
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.
The difference shows up a year later: adopted tools fade when the pressure comes off. Adapted teams keep finding the next answer.
Why the executive cares
Outcomes Delivered
Two results, produced together: the transformation moves faster, and the company finds growth on top of the plan it already has. Underneath both sits the asset that produces them: an organization that keeps getting better at change.
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.
Most of the time a transformation loses goes to waiting, not working: waiting for agreement, for rework, for the next relaunch.
The result
Breakthrough Growth
Growth on top of the current plan: new markets, new ways of selling, value that is still on the table.
It takes people who can do new things, and that is what the rest of this map builds.
The asset underneath
Adaptive Capacity
How well your people handle change: they respond when things don't go according to plan, solve problems with no playbook, and build whatever skill the strategy needs next.
Plans go stale fast. Adaptability is what keeps the company ready anyway, so we treat it like infrastructure: build it on purpose, measure it, maintain it.
Built in your people
Mental Toughness
Your people come out steadier than they went in: they keep their footing when things don't go according to plan and deadlines slip, and they recover faster from setbacks.
We measure it going in and coming out, with AQ® and GRIT™, so the gain is a number, and it stays after the program ends.
Built in your teams
Collective Problem Solving
Teams that can take on a problem too big for any one of them: name the real barrier, split the work, test, adjust, and land a result together.
Once a team has done that together, they keep doing it. The habit outlives the project.
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. Whatever your strategy needs, the pattern is the same: people build the skill by using it on a problem that counts.
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. Get the order wrong and you get shelfware.
First
Mindset
People need autonomy, a real say in the work; competence, getting visibly better at it; and relatedness, a team that counts on you.
Those three add up to intrinsic motivation, and it is what turns nodding in meetings into real motion.
The mindset that comes out the other side: adaptability, grit, resilience, and mental toughness.
Built in the work
Skillset
Skills built under pressure survive pressure. People develop them on the live problem, with a coach, at the moment they need them.
That timing is the trick: a skill taught before the team needs it fades before they use it.
Last, on demand
Toolset
Tools arrive when the work demands them. A team that just hit a pricing wall devours the pricing playbook it would have ignored in week one.
Hand out the same tools on day one 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. Each phase creates the conditions the next one needs.
Agree on the goal
Align
Leadership gets clear on the real challenge, the skills the strategy needs, and the room teams have to move.
Freedom works when the edges are clear. Align draws them.
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, and start to see their own part in it.
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 reality tests the belief, skills get real, and grit grows.
Pass it on
Scale
What worked spreads. The people who did it coach the next group, so the skill stays in the company.
Each round needs less outside help. That is the point.
What makes it work
The Mechanisms
Behind the five stages of AIRAS sit 24 mechanisms, each built to answer one question.
Stage 1 of 5
Align: 9 mechanisms
Agree on the goal. Nine mechanisms run in this stage.
Mechanism 1 of 24
Portfolio Review
How can we increase our impact on results?
Mechanism 2 of 24
Resistance Analysis
How can we convert resistance into momentum?
Mechanism 3 of 24
“Red Dot” Priority Alignment
How can we align on which capabilities matter most?
Mechanism 4 of 24
Executive Positioning Deck
How can we get approval to test a new approach?
Mechanism 5 of 24
Stakeholder Interviews
How can we involve the right people in the process?
Mechanism 6 of 24
Accelerator / Academy Program Plan
How can we design a pilot that can scale?
Mechanism 7 of 24
Pilot Region / BU Selection Process
How can we pick the right place to get started?
Mechanism 8 of 24
Cohort Participant Nominations & Invitation Roll-Out
How can we build genuine excitement and buzz?
Mechanism 9 of 24
Performance Management & HR Integration Plan
How can we make this part of how we operate?
Stage 2 of 5
Inspire: 4 mechanisms
Show what is possible. Four mechanisms run in this stage.
Mechanism 10 of 24
Expert Podcast Inspiration Videos
How can we inspire our people to take initiative?
Mechanism 11 of 24
Guided Discovery Individual Assignment
How can we get everyone’s ideas on the table?
Mechanism 12 of 24
AQ® & GRIT™ Psychometric Assessments
How can we show evidence that a mindset shift is happening?
Mechanism 13 of 24
Adversity Quotient® & GRIT™ Keynote
How can we reframe adversity from a threat to a fuel source?
Stage 3 of 5
Reflect: 4 mechanisms
Find the real problem. Four mechanisms run in this stage.
* CHAIN is Kurt Friedmann’s framework.
Mechanism 14 of 24
Psychologically Safe Environment Design
How can we create the conditions for people to be honest?
Mechanism 15 of 24
Core Challenges Accountability Builder
How can we get clear on what we’re up against?
Mechanism 16 of 24
Priority Challenges Voting Exercise
How can we build resolve and the will to act?
Mechanism 17 of 24
“CHAIN” Needs Definition Exercise*
How can we surface what we think we need?
Stage 4 of 5
Apply: 5 mechanisms
Do the work. Five mechanisms run in this stage.
Mechanism 18 of 24
Growth Squad Formation
How can we leverage each other’s strengths?
Mechanism 19 of 24
Growth Project™ Charter Definition
How can we clarify what we plan to do?
Mechanism 20 of 24
“Science Fair” Ownership Expo
How can we make our commitments public?
Mechanism 21 of 24
90-Day Growth Project Execution by Squads
How can we build skills while solving real issues?
Mechanism 22 of 24
On-the-Job Coaching by Operator-Coaches
How can we use obstacles to build tenacity and grit?
Stage 5 of 5
Scale: 2 mechanisms
Pass it on. Two mechanisms run in this stage.
Mechanism 23 of 24
Impact Reports + Roadblock Removal
How can we recognize progress and get support?
Mechanism 24 of 24
Growth Project Scale-Up Planning
How can we “double down” on what’s working?
What it stands on
The Sciences
The operating system runs on established science, and each body of it shows up as working parts on this map: adversity, motivation, grit, learning, and leadership.
Why pressure builds people
The science of adversity
How people respond when things go wrong, measured as AQ®. Hard moments, met with coaching and support, build resilience and mental toughness instead of burnout.
The research behind it is deep: forty years, more than 3,500 studies, and five million assessments across 137 countries. AQ® predicts who performs under pressure better than IQ or EQ, and Harvard, MIT, Stanford, Carnegie Mellon, and INSEAD teach it.
It is why the work in this system is real: adversity is the raw material.
Why people move
The science of motivation
The research on motivation keeps landing in the same place: people do their best work when they choose it (autonomy), get better at it (competence), and do it with people they care about (relatedness).
Meet all three and motivation lasts. Miss one and you are back to pushing.
Why persistence pays
The science of grit
People who stick with hard goals outperform people who are merely talented. The research also separates winning grit from stubbornness: persisting toward a goal that matters, and adjusting the route as you learn.
GRIT™ measures it. Growth Projects™ give people something worth persisting on.
Why real work teaches
The science of learning by doing
People learn fastest on real problems with real stakes, with a coach beside them. Classroom knowledge fades; skill built in the work sticks.
It is why the unit of this system is a project, not a course.
The four-factor unlock
The science of adaptive leadership
Adaptive challenges ask people to change, and the research on leading them keeps landing in the same place: leaders get further by creating the right conditions than by handing down answers.
McKinsey studied thirty thousand people across thirty countries and put numbers on those conditions. When adaptability and resilience meet real organizational support and a safe place to tell the truth, people are six times more likely to report high engagement and innovation.
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.
Roundtables, briefs, and a peer group that has seen your problem before.
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.
A stuck transformation usually has one real blocker underneath. Finding it is where the fix starts.
Build the leader
Fellowship™
Eight weeks beside operators and peers who have done it. You build a Transformation Acceleration Blueprint for the mandate you already own.
You bring the real thing you are accountable for, and the work happens on it.
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.
Each cohort leaves behind results, skilled people, and internal coaches for the next round.
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?”