Why telling won’t sell strategy implementation: How to engage your organization to make strategy real

For successful strategy implementation, C-suite leaders must engage the organization in translating high-level visions into actionable plans.

June 11, 2024

min read

Subscribe to the BTS newsletter

Follow BTS on Linkedin

Authors

Anne Wilson

SVP & Partner, Head of Change & Transformation COE – North America

Dillon Lee

SVP, Head of Strategy & Business Modeling

Scott Seiffer

So much time, energy, analysis and thought go into building a strategy to ensure your organization grows and thrives. It’s your role as a C-suite leader to set a vision and ensure a broad enough perspective. It’s the organization’s job to take that vision – and figure out how to get it done. Isn’t that what your functional leaders and their teams are there to do?

The high failure rate of strategy implementations suggests that in fact this is not a recipe for success. And further, one of the 3 leading reasons why strategy implementations fail is because company leaders place the burden on employees to figure out for themselves how to make the strategy actionable, rather than engage them to figure it out together.

By their nature, long-term strategies are necessarily high level, as painting a multi-year vision for a complex organization to grow, evolve, and thrive requires a certain altitude and necessary lack of details. Most C-suites leave it to the next levels of leadership to “connect the dots,” and make it real for their teams. This is often done through a “cascade” process of breaking down the activities required at each level of the organization to execute on the strategy, communicating those activities and then measuring progress.

The challenge is that the communication, which focuses on broadcasting a mandated case for change, typically flows in one direction. And that’s a big mistake for two reasons:

It’s a long way down. The standard approach to communicating down through the organization is like the world’s largest game of telephone, but with a fairly weak signal to start. That initial message about what to do differently is often as high level as a managers’ script with talking points, which poses a real challenge to the next layer of managers, who are left to translate abstract concepts into practical, real-world changes. They often feel accountable for, but unprepared to answer, inevitable questions from their teams yet also feel ill equipped to take action to figure things out.
It misses out on all the important intelligence. One way communication down in the organization overlooks the people closest to the customer and the actual work. These are the people who are most likely to see potential gaps and risks in the new strategy. But these front-line workers, along with most of the rest of the organization, don’t see the strategy until after it has been “approved,” at which point the goal isn’t to get their feedback but rather to drive execution and accelerate results. By the time the strategy is cascaded out to the last person in the field or on the floor, it’s far too late to act on what they know.

The common thread is that leaders are waiting on employees throughout the chain of command to interpret and figure out what the new strategy means on a day-to-day basis, without first having brought them into a shared conversation up front. Not given a chance to wrestle with the trade-offs, test the assumptions, and participate in the dialogue, even the most enthusiastic employees are going to have a hard time figuring out what the strategic shifts mean to them personally, let alone how to execute them. Note that this is not about asking all 50,000 people in your organization to weigh in on what the strategy should be. Instead, it is about setting the direction, and then engaging them in the process to understand what the new direction means and how it translates for them. The key is creating the right environment to engage the organization most effectively.

3 ways to bring your leaders and teams into making strategy actionable

Make the new strategy real and tangible, as strategies must be experienced to be truly understood. When it comes to engaging people around a new strategy, it’s important to remember that a change in information does not mean a change in behavior. People don’t act until they understand what will be different in their day-to-day work. Senior leaders who can take the conceptual and make it concrete enable people at all levels in the organization to see themselves in the strategy and feel like active players in making it real.[1] Until you take people for a test drive to see and feel what actually changes about their job, you will have a challenging time making the strategy clear.

Take for example a financial services company who made a commitment to double the number of customers in three years by reaching entirely new customer groups with different needs. Frustratingly, efforts had stalled as the prevailing mindset amongst the troops was essentially “wait until someone tells us what to do.” We partnered with them to make the aspiration real and personal for people in the organization. How? For the operations team, for instance, achieving the goal meant that they would be servicing twice as many customers in just one year. We built a visceral experience for the team to see what it would take to handle that many new customers. This way, they could consider the various scenarios of dealing with such a huge increase and debate the most critical investments and process changes. Most importantly, because the group built the new plan together, they were able to move significantly faster in implementation.

Build two-way communication at scale. Instead of broadcasting goals, project plans, and checklists, intentionally build two-way communication into your campaign for strategy alignment. This approach will help leaders source ideas and input from those closest to customers. But it will also help those on the ground feel that they are active members on the front lines of the push forward (because they actually are).

A telecommunications company created a retail store strategy around selling more, higher margin products such as accessories. The company told the retail managers to prioritize those sales, but revenues barely budged. The strategy didn’t catch fire until the company asked the managers to become deeply involved in determining the tactics and actions that would make a difference. Once the retail side got fully engaged, sales of accessories easily jumped 20%.

Expect all leaders to be leaders of the new direction. The responsibility for revamping your organization shouldn’t fall on the shoulders of a small number of champions. The scale and pace of change for most organizations requires that all managers, from the C-suite to the middle ranks to the factory floor and retail aisle, see change leadership as their first job and have a change-ready mindset. After all, it’s usually the people closest to the work who have the best ideas about how to change it. The job of a change leader is to know how to engage their teams in co-creating the future together so that they can collaborate to solve problems in new ways. All leaders, not just a select few, have to bring a change-ready mindset to the task, so that they can maintain the motivation to bring their teams with them as they lead the charge.

Our work with thousands of leaders and organizations has revealed a core disconnect that can undermine even the best of strategies in the most focused of companies. The disconnect is both simple: Strategy creation and strategy execution are seen as two separate activities, rather than what they should be—an integrated, iterative process that generates a new reality over time for the company and for the people in it. And one of the 3 most important ways to make that process real is by more deeply engaging the people who will have to implement that strategy, and to bring them into the process, and keep them there, from the earliest days to the very end. (Check out this white paper to find out more about the other two.) Start by building engagement from the very beginning. You’ll be well on your way to making your strategy actionable.

[1] Oreg, S., Vakola, M., & Armenakis, A. (2011). Change Recipients’ Reactions to Organizational Change: A 60-Year Review of Quantitative Studies. The Journal of Applied Behavioral Science, 47(4), 461–524.

^{Learn how to design conversations that actually move decisions forward.}

Download the report

What it felt like inside the flywheel.

When the simulation team went live with their first clients on the new way of working, the lead person hit a wall. Their words:

“You’re asking too much. You’re making me be a full-stack developer. Up until this point I did a small part, and I sent it to the team, and they built off the back end, and they brought it back. And now I have to end-to-end soup to nuts, basically alone.”

There was graphic UI work nobody had been trained for, the fear of delivering quality below what BTS expects of itself, and the weight of not having a playbook. This was not the joyful adoption story most consultancies tell.

Then something shifted. Six members showed up for product testing, where the usual was two or three. The work created teamwork I hadn’t seen at BTS in years. The breakthrough was not an instantaneous change from skepticism to celebration. It was a breakdown in confidence, then rally, then bonding. If we didn’t make room for the breakdown, we would have lost the rally.

The other breakthrough was global teamwork; not yet a BTS core strength. Our culture is beautiful: high-freedom and entrepreneurial. But people’s first identities are to their countries. Almost every prior attempt we’ve made at a global initiative has failed. The one exception was Covid. So, when I say what happened next surprised me, I mean it.

I asked to join the simulation team’s Slack channel rather than pulling them into status meetings. What I got to watch in the mornings was someone in South Africa waking up, posting “I tried this and got stuck,” then London adding on, then San Francisco weighing in, then a surprise breakthrough overnight from Tokyo. We didn’t engineer that. Curious and determined BTS’ers did. The problem was interesting enough that the org chart didn’t matter. It was amazing to see and a glimpse into the next evolution of the BTS culture.

The pattern: Explore, expand, institutionalize, renew.

What we’ve now seen play out, both inside BTS and with clients, follows the same four-step pattern. Each step asks a specific decision of the leader.

Explore.

Stay stubborn on the aspiration and fluid on the path. Our breakthrough wasn’t the path we originally took. We changed tools and approaches. Nobody could have foreseen that. And if the team had taken the first six months of learnings from AI as their definitive “this is the detailed path we will follow,” we never would have gotten the disruption. Five different tool combinations were tried before we found the one that worked. Companies that lock into a single path or tool too early are betting against compounding capability that doubles roughly every seven months. That is not a bet I’d take.

Expand.

Run the old way and the new way side by side. When the simulation team’s breakthroughs got real, the instinct was to retreat into more internal testing. We did the opposite. They ran old way and new way in parallel on 6 or 8 live client projects across all three geographies. Every single one ended up going live the new way. The backup was always there. They didn’t need it.

Institutionalize.

Burn the boats. The simulation team committed that no new client work would be done the old way after January 1. The other practice leads then committed to dates within Q1, even though most of them had not yet experienced the new way themselves. They had to trust their colleagues. If you can do it for the most complex thing, you could probably do it for the less complex ones. By February 15, we had approaching 90% global adoption across 24 countries, across all practices. I was shocked and proud. We had spent years failing at exactly this kind of global rollout.

Renew.

Treat your agents as contractors. People on our diamond teams are now managing 30+ agents they built themselves. Our teams give agents performance feedback. We terminate their contracts when they don’t deliver. We expand the responsibility of agents when they outperform. The frontier question we’re wrestling with now is token budgeting. Two friends of mine running engineering-heavy companies believe that within 6 - 9 months, their token cost per engineer will exceed the cost of the engineer. Whether that’s the right framing is open. The question is real, and every CEO will be asked some version of it within the year.

What had to be true for this to scale.

Once we achieved this amazing global innovation, the leadership sat down to figure out what made it work. We named five things. None of them were about the technology.

Real pain points as the starting point. We had so many people frustrated from those ways of working, all the back and forth and all the wasted time, that this was gold for them. The old way was already painful. The new way wasn’t a forced disruption; it was relief. Find the workflow where the pain is loudest and start there.

The diamond unlocked creativity, it didn’t constrain it. This was the most differentiated insight, and the one most leaders miss. It wasn't "here's the new tasks and rules." It was, "once you learn how to do this, the sky's the limit. You can be even more creative." If your rollout feels like a new set of rules constraining your people, you’ve built the wrong thing.

Pair deep expertise with fresh eyes. The disproportionate share of our breakthroughs came from a tenured tinkerer with total command of the work, paired with someone new to the role who hadn’t yet built the muscle memory of how it had always been done. Without that pairing, you get incremental improvements to the work you already know how to do, instead of a reinvention.

Refuse the “people are too busy” reflex. When I brought the rollout to the global leadership team, the excuses came fast. “Our people are too busy. They’re burnt out. Q1 is going to be busy. No one’s going to have time.” My response: “This is a chance to eliminate the tasks you dread and expand what you love. I know it is a short push of extra work, and I think after the fact you and your team will feel joy and pride and say it was the best time we ever spent.” This is the moment most AI rollouts die.

Senior leaders must lead by example and do the work themselves. This is not middle manager’s job. This is not something you delegate. Even though you don’t build simulations anymore, you must know what this is. One of our partners proactively put time on senior leaders’ calendars and forced them to do the work. Once they started building, the excitement grew, and they could advocate for the rollout because they understood it. If your executives haven’t put their hands on the keyboard, you don’t have a rollout. You have a memo.

What we’re seeing across clients.

We’re now running this play with client organizations across industries and geographies. The companies whose flywheels are accelerating paired their A-players with their early-career talent, pulled IT and legal into the working sessions, refused the “too busy” reflex, and put their senior leaders’ hands on the keyboard. The companies whose flywheels are stuck almost always have a leadership pattern at the center of the stall. Not a tooling pattern. Not a governance pattern. A leadership pattern.

If this resonates, let’s talk.

If you read Part 1 and asked yourself whether your flywheel was turning, the question I’d add now is sharper: do you have the conditions in place for a diamond to appear? If yes, you’re already moving. If no, the technology will not save you.

Here's where we're starting with clients: a working session, half day to a full day, with a small group that owns one of your highest-friction processes. Together we map where your first diamond is most likely to land, how to set up the side-by-side trial, and what your version of "burn the boats" should look like.

The destination, if we do this right, is a self-reliant culture of applied AI inside your company. 5, 10, 15 diamonds compounding into a fundamentally different way of operating. From what I have experienced this is a once in a career opportunity for dramatic shareholder value creation if you get that muscle going. I say that because I'm watching it happen, in real time, inside our own company and across our client base.

If you want to get your flywheels spinning and map your first diamond, start here. Bring your hardest workflow. We'll bring the playbook.

Blog Posts

August 22, 2025

min read

6 things you can do to shift your culture without a massive change effort

Six practical actions leaders can take to shift culture and align with strategy—without a major change initiative.

Learn more

Most leaders focus on strategy—not because they undervalue culture, but because strategy feels concrete. It has structure, timelines, metrics, and deliverables. It’s visible and defensible. When pressure is high, strategy gives leaders something they can point to and steer. Culture doesn’t always feel that way. It’s harder to define, harder to measure, and often lands in the “important, but not urgent” pile. That’s not a leadership flaw. It’s a gap in how we’ve equipped leaders to lead.But if you want to change how your organization operates, you have to start with what people experience every day.

Below are six no-fluff actions from our recent event, , designed to help you leave your team stronger than you found it.

‍Culture Without the Fluff→ Don’t miss events like these! Sign up for our newsletter or visit our events page to see what’s coming.

1. Build shared habits

If strategy defines where you’re going, culture determines whether you’ll get there. Strategy can shift quickly, with a new market, goal, or CEO. Culture can’t. It’s shaped by the beliefs, habits, and norms that don’t pivot on command—and that’s where friction starts. The disconnect doesn’t usually show up in big moments. It shows up in how decisions get made, what’s prioritized under pressure, and whether feedback is honest or avoided. These daily behaviors signal what really matters, regardless of what the strategy says. That’s why high-performing organizations go beyond communicating direction. They turn strategy into clear expectations for how people should work, lead, and collaborate—and then reinforce those expectations through routines, incentives, and leadership behavior.

Try this:

Pick one strategic priority and ask: What should people be doing differently if this is truly our focus? If you’re not seeing those behaviors, there’s a gap. Ask yourself: Do our daily habits match the future we’re trying to build?

2. Use the levers you already own

Culture change doesn’t have to start with a massive initiative. It can start with the levers you already own. Culture lives in the mechanics of your team’s work: how meetings are run, how frontline decisions are made, how failure is treated, and what behaviors leaders model. These small signals shape big beliefs. That’s why abstract values and vision statements alone often fall flat. They’re not wrong, but without action behind them, they’re just words on a page. Real change starts by zooming in on specific moments that shape how work gets done, and making small, intentional shifts. Want a culture of accountability? Focus on what happens after meetings. Want more innovation? Look at how failure is handled during team reviews.

Start here:

Pick one lever (like how meetings are run) and ask:

What messages are we sending through how we meet?

Who speaks up? Who stays silent? What actually gets decided?

Then make small adjustments that reinforce the culture you want—not the one you’ve inherited.

3. Avoid the tempting pitfalls

If you’ve ever rolled out a new set of values, launched a culture initiative, or shared a bold new vision, only to see behavior stay exactly the same, you’re not alone. Most culture efforts stall not because leaders don’t care, but because they start with what’s visible and familiar: messaging, posters, kickoff events. These feel like the right moves. But they rarely shift what people actually do, and rarely resonates in a meaningful and lasting way In our recent webinar, we shared six common traps that organizations fall into often with the best intentions. Here are three that come up again and again:

Relying on values to do the heavy lifting. Most teams have clear values, but that’s not the problem. The challenge is turning those values into real habits. If the way you run meetings, make decisions, and give feedback doesn’t reflect what’s on the wall, people notice—and disconnect.
Expecting HR or culture champions to lead the culture shift alone. HR and champions play a big role in culture, but they can’t do it without leaders. People take their cues from credible influencers in the business: what gets rewarded, what gets ignored, and how leaders show up under pressure. That’s where real culture change starts.
Announcing culture change before actually changing anything. This is a classic case of show don’t tell. When leaders talk about change without shifting the day-to-day experience, people become skeptical. They’ve heard it before. What earns their belief and commitment is seeing leaders act differently in ways that directly affect their work.

P.S. We’ve rounded up 3 more pitfalls worth avoiding. See them here.

Start here:

Surface the unspoken. Ask: What do people believe they’ll be rewarded for today? What would they have to believe to behave differently?Culture change requires shifting the mental models that shape behavior.

4. Shift the beliefs beneath the behaviors

You can’t shift behavior without understanding the beliefs behind it. If teams aren’t collaborating across silos, it’s probably not because they don’t want to—it’s because they’re rewarded for competing, not collaborating. If leaders aren’t taking smart risks, it might be because failure has been punished, not treated as a learning moment. These everyday behaviors are just the surface—what’s driving them are deeper, often invisible beliefs that probably outlast the tenure of some of your employees.

Start here:

Ask: What are the unspoken rules here? What would someone need to believe for this behavior to feel natural, safe, and worth it? Until you name and shift those beliefs, culture efforts will stay stuck at the surface.

5. Don’t let your culture fall behind your tech

Honestly, the real surprise would be if AI wasn’t reshaping your culture. Some organizations are going all-in on experimentation. Others are still figuring out what their approach will be. But wherever you are on the curve, one thing’s clear: this moment feels a lot like the wild west. And your talent is picking up on that. Leaders are signaling the need to adapt and innovate—but rewards and incentives often tell a different story. Without clear signals from the culture that it’s safe to try, valuable to learn, and worth the risk, even the smartest tools won’t be used to their full potential.

Ask yourself:

How are we capturing what’s working with AI—and making those insights visible and usable across the organization?

What are we taking off people’s plates to give them the time and space to learn, experiment, and adapt?

Have we updated the priorities, deliverables and expectations to reflect the new reality—or are we layering AI on top of an already full workload?

Are leaders helping people see the personal value in this shift—so AI feels like a path to growth, not a threat to their role?

6. Start small, scale fast

Most leaders assume culture change has to be slow and sweeping. But it doesn’t.We’ve seen major progress start with one small shift—the kind that’s visible, repeatable, and high-impact. The key? Start where the energy already is: a team that's eager, a leader who's ready, a process that’s stuck. Then focus on one behavior that’s holding things back—and change it. From there, scale what works.

Start here:

Use this simple 3-step exercise to find a small, high-impact place to start:

Pinpoint a stuck spot: Where is strategy getting delayed, deprioritized, or lost in translation? Common areas include:
- Team meetings that always run long but lead to no decisions
- A new tool or process people aren’t adopting
- A frontline team disconnected from the broader strategy
- An area with low engagement or slow execution
Identify the blocker behavior:
- What specific habit, mindset, or expectation is in the way? (e.g., defaulting to top-down decisions, rewarding speed over learning, fear of trying something new)
Make one shift—and scale what works
- Change that behavior in one team, one moment, or one process.
- Capture the impact. Then share the story and replicate what worked.

Change spreads through stories. Show people what’s possible, and they’ll move with you.

Culture change is hard. Doing it alone? Even harder.

We work with teams around the world to:

Spot what’s working—and what’s getting in the way

Test small shifts that create big ripple effects

Keep momentum going as change starts to spread

Reach out to us to start a conversation!

Woman in a brown dress using a digital tablet in a modern office with glass walls.

Blog Posts

July 7, 2025

min read

How to avoid the AI fizzle

Learn why early AI efforts stall and how to design for lasting, scalable impact by separating scattered pilots from real transformation.

Learn more

In the 1990s, Business Process Reengineering (BPR) was the Big Bet. Companies launched tightly controlled pilot programs with hand-picked teams, custom software, and executive backing. The results dazzled on paper.

But when it came time to scale? Reality hit. People weren’t ready. Systems didn’t connect. Budgets dried up. The pilot became a cautionary tale, not a blueprint.

We’ve seen this before with Lean, Agile, even digital transformations. Now it’s happening again with AI, only this time, the stakes are different. Because we’re not just implementing a new solution, we’re building into a future that’s unfolding. Technology is evolving faster than most organizations can learn, govern, or adapt right now. That uncertainty doesn’t make transformation impossible, but it does make it easier to get wrong.

And the dysfunction is already showing up, just in two very different forms.

Two roads to the same cliff

Today, we see organizations falling into two extremes. Most companies are either overdoing the control or letting AI run wild.

Road 1: The free-for-all

Everyone’s experimenting. Product teams are building bots, prompting, using copilots. Finance is trying automated reporting. HR has a feedback chatbot in the works. Some experiments are exciting. Most are disconnected. There's no shared vision, no scaling pathway, and no learning across the enterprise. It’s innovation by coincidence.

Road 2: The forced march

Leadership declares an AI strategy. Use cases are approved centrally. Governance is tight. Risk is managed. But the result? An impressive PowerPoint, a sanctioned use case, and very little broad adoption. Innovation is constrained before it ever reaches the front lines.

Two very different environments. Same outcome: localized wins, system-wide inertia.

The real problem: Building for optics, not for scale

Whether you’re over-governing or under-coordinating, the root issue is the same: designing efforts that look good but aren’t built to scale.

Here’s the common pattern:

A team builds something clever.
It works in their context.
Others try to adopt it.
It doesn’t stick.
Momentum dies. Energy scatters. Or worse, compliance says no.

Sound familiar?

It’s not that the ideas are flawed. It’s that they’re built in isolation with no plan for others to adopt, adapt, or scale them. There’s no mechanism for transfer, no feedback loops for iteration, and no connection to how people actually work across the organization.

So, what starts as a promising AI breakthrough (a smart bot, a helpful copilot, a detailed series of prompts, a slick automation) quietly runs out of road. It works for one team or solves one problem, but without a handoff or playbook, there’s no way for others to plug in. The system stays the same, and the promise of momentum fades, lost in the gap between what’s possible and what’s repeatable.

We’ve seen this before

These aren’t new problems. From BPR to Agile, we’ve learned (and re-learned) that:

Experiments are not strategies. Experiments show potential, not readiness for adoption. Without a plan to scale, they become isolated wins; interesting, but not transformative.
Culture is the operating system. If the beliefs, behaviors, and incentives underneath aren’t aligned, the system breaks, no matter how advanced the tools.
Managers matter. Without their ownership and support, change stalls.
Behavior beats code. Tools don’t transform companies. People do.

Design thinking promised to bridge this gap with user-driven iteration and empathy. But in practice? Most efforts skip the hard parts. We tinker, test, and move on, without ever building the conditions for adoption.

AI and the new architecture of work

Many organizations treat AI like an add-on—as if it’s something to bolt onto existing systems to boost efficiency. But AI isn’t just a project or a tool; it changes the rules of how decisions are made, how value is created, and what roles even exist. It’s an inflection point that forces companies to rethink how work gets done.

Companies making real progress aren’t just chasing use cases. They’re rethinking how their organizations operate, end to end. They’re asking:

Have we prepared people to reimagine how they work with AI, not just how to use it?
Are we redesigning workflows, decision rights, and interactions—not just layering new tech onto old routines?
Do we know what success looks like when it’s scaled and sustained, not just when it dazzles?

If the answer is no, whether you’re too loose or too locked down, you’re not ready.

The mindset shift AI demands

AI isn’t just a tech rollout. It’s a mindset shift that asks leaders to reimagine how value gets created, how teams operate, and how people grow. But that reimagination isn’t about the tools. The tools will change—rapidly. It starts with new assumptions, new stances, and a new internal leader compass.

Here are three essential mindset shifts every leader must make, not just to keep up with AI but to stay relevant in a world being reshaped by it:

1. From automation to amplification

Old mindset: AI automates tasks and cuts costs.

New mindset: AI expands and amplifies human potential, enhancing our ability to think strategically, learn rapidly, and act boldly. The question isn’t what AI can do instead of us, but what it can do through us—helping people make better decisions, move faster, and focus on higher-value work.

2. From efficiency to reimagination

Old mindset: How can we use AI to make current processes more efficient?

New mindset: What would this process look like if we started from zero with AI as our co-creator, not a bolt-on?

3. From implementation to opportunity building

Old mindset: Roll out the tool. Train everybody. Check the box.

New mindset: AI fluency is a core human capability that creates new realms of curiosity, sophistication in judgment, and opportunity thinking. Soon, AI won’t be a one-time training. It will be part of how we define leadership, collaboration, and value creation.

From sparkles to scale

In most organizations, the spark isn’t the problem. Good ideas are everywhere. What’s missing is the ability to translate those isolated wins into something durable, repeatable, and enterprise-wide.

Too many pilots are built to impress, not to endure. They dazzle in one corner of the business but aren’t designed for others to adopt, adapt, or sustain. The result? Innovation that stays stuck in the lab—or dies.

Designing for scale means thinking beyond the “what” to the “how”:

How will this spread?
What behaviors and systems need to change?
Can this live in our whole world, not just my sandbox?

It’s not about chasing the next use case. It’s about setting up the conditions that allow innovation to take root, grow, and multiply, without starting from scratch every time.

Here’s how to make that shift:

1. Test in the wild, not just in the lab

Skip the polished demo. Put your solution in the hands of real users, in real conditions, with all the friction that comes with it. Use messy data. Invite resistance. That’s where the insights live, and where scale begins. If it only works in ideal settings, it doesn’t work.

2. Mobilize managers

Executives sponsor. Front lines experiment. But it’s team leaders who connect and spread. Equip them as translators and expediters, not blockers. Every leader is a change leader.

3. Hardwire behaviors, not just tools

The biggest unlock in AI is not the model—it’s the muscle. Invest in shared language, habits, and peer learning that support new ways of working. Focus on developing behaviors that scale, such as:

Change readiness: the ability to spot opportunity, turn obstacles into possibilities, and help teams pivot.
Coaching: getting the best out of your AI “co-workers” just like human ones.
Critical thinking: applying human judgment where it matters most—context, nuance, and ethics.

4. Align to a future-state vision

To scale beyond one-off wins, people need a shared sense of where they’re headed. A clear future-state vision acts as an enduring focus, allowing everyone to innovate in concert. That alignment doesn’t stifle innovation. It multiplies it, turning a thousand disconnected pilots into a coherent transformation.

5. Track adoption, not just “wins”

Don’t mistake a shiny, clever prompt for progress. A great experiment means nothing if it can’t be repeated by many people. From day one, design with scale in mind: Can this be adopted elsewhere? What would need to change for it to work across teams, roles, or regions? Build for transfer, not just applause.

The real opportunity

AI will not fail because the tech wasn’t good enough. It will fail because we mistook experiments for solutions, or because we governed innovation into paralysis.

You don’t need more control. You don’t need more chaos. You need design for scale, not just scale in hindsight.

Let’s stop chasing sparkles. Let’s build systems that spread.

What it felt like inside the flywheel.

When the simulation team went live with their first clients on the new way of working, the lead person hit a wall. Their words:

“You’re asking too much. You’re making me be a full-stack developer. Up until this point I did a small part, and I sent it to the team, and they built off the back end, and they brought it back. And now I have to end-to-end soup to nuts, basically alone.”