bentleystrategy.com

How to Keep Your Marketing Transformation from Stalling

Boardroom alignment is essential for a successful transformation, but securing it and actively owning it are two different things. A five-step playbook for closing the gap between strategic commitment and operational reality.

There's a particular feeling of accomplishment that follows a successful boardroom presentation to initiate a major transformation initiative. The story landed. Leadership is aligned. The CEO is supportive, the CFO has a number to work with, and the CTO is nodding. You leave the room feeling like something has finally shifted.

But that feeling can soon turn into confusion when progress seems to stall. And in my experience, it stalls more often than it should. Not because of a lack of ambition or talent, but because securing senior leadership alignment and actively owning the transformation are two very different things.

In this article

• A real example of the gap between strategic alignment and operational reality, and what it took to close it.
• The warning signs that a transformation initiative is dying quietly.
• Why stalling is almost always structural, not motivational.
• Five moves to make this week to create the conditions for real momentum.

Leadership commitment doesn't always match operational realities

In a major transformation initiative I was leading, I made a discovery that changed how I thought about cross-functional leadership. I had been reporting monthly to the CEO on the project's progress. The initiative was a stated top priority. Leadership was engaged and supportive.

Then I found out this major initiative was ranked 26th on the IT team's formal prioritization queue.

The queue had been set during the previous planning cycle, before this initiative existed, and to change it before the next cycle would require an act of congress. The C-suite was talking about the project as a top five priority, but the teams doing the work were operating off a completely different list. It's no wonder that everyone working on the project was frustrated.

This is a gap that kills transformation initiatives. Not the drama of a failed launch or a leadership conflict. The quiet, gradual drift that happens when strategic commitment and operational reality are never brought into alignment.

Warning signs

The signs are easy to rationalize in the moment, which is what makes them so dangerous. You can go weeks hearing a different version or symptom of the same root problem before you realize you haven't been addressing the core issue and have lost weeks of progress. Do these sound familiar?

• Status meetings that feature roadmaps and plans but no demos, no working examples, no early results. Slide decks that describe what will happen, week after week.
• Updates full of open dependencies and yellow indicators that never seem to turn green. "As soon as engineering completes X" or "once Finance confirms the budget," and those conditions keep moving.
• Conflicting accounts of progress when you talk separately to the PM, the IT lead, and your own team. The story changes depending on who you ask.
• The language of non-urgency: "we're addressing that next week," "the meeting fell on a holiday," "that person got pulled onto something urgent." Days and weeks going by with no forward movement because one team is waiting on another.

Any one of those things might be fine in isolation. Together, they're a pattern: people are working on this initiative alongside everything else they're doing, not treating it as a true organizational priority. If you don't catch these signs early enough, you'll end up rebooting the initiative and losing months in the process.

It's not a motivation problem

Transformation initiatives almost always get layered on top of existing work. Marketing is running campaigns. IT is managing a development backlog built during the last planning cycle. Finance is tracking commitments made months ago. Nobody who got assigned to work on this had an empty calendar when the C-suite agreed it should be a priority, and you probably didn't end that meeting with an agreement that another strategic initiative should be deprioritized to make room for this new one.

The initiative gets announced. Teams get briefed. And the first question from the people who actually have to do the work is almost always the same: "What comes off my plate to get this done?"

It's not resistance. It's math. And unless someone has a clear answer, the initiative starts competing for time with everything else. That "everything else" usually has more immediate consequences for missing a deadline.

There's a second layer that compounds this. These initiatives almost always require something new: a new technology to integrate, a new approach to the problem, skills the team hasn't fully developed yet. But the teams assembled to work on them are rarely new. Same org structures, same reporting relationships, same dynamics. Asking existing teams with existing constraints to drive fundamentally different outcomes is a significant ask, and it takes active leadership to make it work.

What active ownership looks like

The CMO who gets the boardroom alignment and then waits for a status update to tell them how it's going will almost always be disappointed. Not because the teams aren't capable, but because the structural conditions for success don't create themselves.

Active ownership doesn't mean project managing the initiative yourself. It means making sure the conditions exist for others to succeed, staying close enough to the work to find the friction before it becomes a crisis.

One place to start is to commit your own organization to the initiative. Going back to my own story, I asked our team to make ROI measurement of the project their first priority. I pushed my team to be early adopters and testers of the new capabilities being developed even though I knew it would make their existing work more difficult. I pushed my operations team to get training on a new platform before the contract was even signed. The message? We are all in on this initiative, it will be a critical piece to how we run our business, and there is no going back to the status quo. This ensured people were actively working the transformation, not just waiting for it.

It also created accountability to the transformation. When your team members have a meaningful role in the initiative's success, and understand that their contribution will be part of how their performance is evaluated, they think about it every day, not just on the afternoon of the weekly status meeting. That's when the initiative starts to feel like a shared mission rather than a leadership priority they're being "voluntold" to support.

Actively seek out problems

The second part of active management is to actively seek out root causes rather than waiting for problems to surface. Real blockers on a cross-functional initiative are rarely presented in the executive status meeting. They live in working sessions three levels down, in quiet conversations with team leads who don't want to escalate, in the gap between what one team thinks another team is doing and what's actually happening. If you're only hearing about problems once they're critical, you're already behind.

In the case of our priority disconnect, the answer wasn't to escalate to the CEO and ask them to demand the CTO figure it out. That just adds pressure without adding resources, creates shortcuts that become tech debt, and erodes the CMO-CTO partnership you'll need for every initiative that follows this one. At a moment when AI is reshaping marketing technology faster than any planning cycle can anticipate, a strong CTO relationship is one of the most strategically valuable investments a CMO can make. I address the importance of a strong CMO-CTO partnership, and how to cultivate it, in a later article.

The answer in our case was to understand the root of the issue and propose an enterprise solution: working with the CFO to fund a dedicated group of engineers outside the normal IT queue, with the budget coming from a reallocation within Marketing. It solved the CTO's real problem, capacity, without stretching his team thin. And it sent a signal that Marketing was thinking about the enterprise, not just making requests of it.

The Five-One Playbook (five moves, one week)

If you're leading a transformation initiative and something feels off, whether progress is slower than it should be, the energy isn't right, or you're not sure what's really happening, don't wait another week hoping it will self-correct. These five moves will help you surface what's actually going on and create the conditions for real momentum.

1. Check operational prioritization against current leadership priorities. Talk to the teams actually doing the work, not just the leadership layer. Find out where this initiative sits in their real queue and how much of their time is genuinely allocated to it. The gap between what was agreed to in the boardroom and what's actually on people's plates is the first thing you need to know. It's information you can't act on if you don't have it.
2. Get a dedicated PM assigned and set up for success. Assign a strong project manager with cross-functional experience, enough bandwidth to treat this as their primary focus, and your visible support. If someone is already in the role but overextended, this is the week to change that, and reassign their other work if needed. Having another team member who has to say "I'll get to that next week" is not a recipe for progress. If your organization has a shared project management or transformation team, tap into those resources.
3. Set up root-cause check-ins with your PM and key project members. Create a separate, lower-pressure conversation where the real problems can surface. If you try to have this in the executive status meeting, most people will be reluctant to speak up. Your PM should be talking to working-level team members across functions, not just collecting updates from leads. Your job in these check-ins is to listen, ask why at least five times to get to root causes, and help remove blockers without escalating or assigning blame. When people trust that surfacing a problem leads to solutions rather than consequences, you'll get to the core issues faster.
4. Commit your own team and look at your own budget to solve the root issues. Meet with your leadership team this week. Clearly articulate why this initiative matters to the company and to them personally. Then ask each of them: what role can their team play in moving this forward, and what's currently on their plate that could be deprioritized to make room? Look at your budget for unspent dollars planned for later in the year. There is often real flexibility in Marketing spend, and reallocating budget to fund dedicated resources on the initiative, whether on your team or in IT, is one of the most effective signals a CMO can send. Make clear to your team that their contribution to this initiative's success will be part of how you evaluate their performance.
5. Bring the root problems to your peers, and come prepared. Once you know what's actually blocking progress, take it to the peers whose teams or budgets are part of the solution: your CTO, CFO, or relevant business unit lead. Don't show up with just a list of problems. Show up with what you've already done to address it, and be specific about what you need that only they can provide. That framing changes the conversation from a defensive, zero-sum exchange to a collaborative problem-solving session. You're not escalating. You're partnering. And you're giving them something concrete to respond to rather than asking them to figure out a problem you haven't fully diagnosed.

Time to lean in

CMOs who drive real transformation share something that goes beyond organizational influence or technical fluency. They stay in the game long after the C-suite presentation is over. They seek out friction before it becomes a crisis. They bring resources to the table rather than demands. And they keep telling the story, not just to their peers or in an all-hands meeting, but to their own teams, to their IT and Finance partners, and to anyone whose energy and commitment the initiative depends on.

In the first article in this series, I wrote about the story CMOs need to tell to get leadership aligned. You are the hero in that story, and leadership alignment is your challenge. Once you've succeeded there, your team and your cross-functional partners become the protagonists of the story. Listen to what they're telling you about what's working and what's not, and the obstacles they're struggling with.

Transformation initiatives don't fail because the team doesn't hear leadership saying it's a priority. They fail when leadership isn't actively listening to why their team is struggling with execution.