Companies are spending millions on transformation. New strategy. New platforms. New AI.

The rollout happens on schedule. Execution doesn’t. 

Transformation is execution at scale, under constant change. AI doesn’t fix execution. It amplifies whatever is already there. It scales success — or failure. 

The problem is that most organizations don’t know which one they’re scaling. Almost no leader I talk to can answer three basic questions about the transformation they're funding:

‍Who's ready? 
‍
What's working? 
‍
What's changing?

‍Your CRM tells you the deal closed, not whether the team was prepared. Your project tool tells you the milestone was hit, not what the winners did differently. Your dashboard tells you what already happened, not how the market is moving underneath it.

We train and test people before the work, but test-ready isn't job-ready. Then we review business performance after the fact, when it's already too late.

‍Everything in between is invisible. Execution is the blind spot.

‍The answers to those three questions don't live in another dashboard. They're already in the field — in the people who've built the capability, what someone figured out last Tuesday, and what the market is teaching your field faster than it reaches your strategy deck.

So here's what has to shift.
‍

‍1. From decks to muscle memory

The question this answers: Who's ready?
‍
‍Most organizations measure transformation by what people consumed. Training completed. Certification passed. Town hall attended. Ninety-four percent completion rate, reported to the board as a measure of success.

None of that is readiness. It's attendance.

If reading a cookbook made someone a great chef, we'd all cook like professionals. If reading a playbook created champions, every team would win. Strategy creates alignment. It doesn't create capability.

Readiness comes from doing. Trying, getting feedback, adjusting, trying again. That's how pilots train, how surgeons improve, how athletes build muscle memory. Execution is a muscle, not a memo, and no one has ever built a muscle by reading about one.

The shift is simple: stop asking whether people finished the material and start asking for evidence they’ve done the reps. Can this seller actually handle the objection they'll hear on Thursday? Can this engineer run the new workflow when the customer is watching? You find out by having them do it before the consequences are real, not after.
‍

‍2. From defining best practice to curating it

The question this answers: What's working?

‍In the AI era, best practice is no longer in HQ. It's out there in someone's head — and it’s a moving target.

A seller who found a better prompt. An engineer who solved a customer problem in a way nobody documented. A manager who cut cycle time in half with a workflow that never went through approval.

Best practice used to be authored once and distributed. Now it's continuously discovered in the field. 

That changes the role of the organization. The job is no longer to write the playbook. It's to find what works, validate it quickly, and spread it. The Center of Excellence becomes the Curator of Excellence.

This isn't a soft preference. In our own data, peer-to-peer best practices earn 4x the engagement of company-generated content, because people trust what worked for someone doing their actual job this week over what was approved six months ago. It’s the same reason many of us reach for YouTube before the product manual.

Transformation doesn't only flow top down. It flows sideways.
‍

3. From annual cycles to continuous loops

The question this answers: What's changing?

‍Imagine if software development worked like this. You write the code, ship it, wait six months, then review what happened. No staging, no monitoring, no patches. No serious engineering organization would build software that way.

Yet that's exactly how most enterprises manage transformation. Rollout. Train. Review. 

The stack — AI models, workflows, software — runs on a continuous cycle. Meanwhile, the people expected to use it don’t. So the faster we upgrade the stack, the further execution falls behind.

The shift isn’t faster rollouts. It’s faster learning loops. Small increments. Real feedback. Fast iteration. What worked? What broke? What changed? What do people — and AI — need to know by Monday morning? Not from stale content or synthetic data, but from real-world execution.
‍

‍From managing people to managing execution

‍Who's ready isn't answered by a certificate. What's working isn't captured in a playbook. What's changing won't wait for the annual review.

All three are execution questions. They point to the work in between — not the training before it or the results after it. That's the shift. Not away from people. Toward continuously improving execution.

For decades, we've managed people through passive, lagging metrics. Training completed. Performance reviewed. Revenue achieved. But no other discipline waits until the end to find out what's working. Not engineering. Not finance. Not marketing. They test, they measure, they adjust. Transformation is the last management discipline that still runs on faith.

We've built our management systems around what happens before the work and after the work. It's time to build them around the work itself. 

‍We think people are the bottleneck. They're not. The metrics are.

‍Every transformation that ever worked did so because someone in the field did something differently on a Tuesday. Strategy is where transformation begins. Execution is where it spreads. And execution spreads through people.