The Rollout Merry-Go-Round | Retail Project Management

Imagine this.

You're the CFO of a national retailer, mid-way through a multi million dollar store refurbishment programme.

Capital's tight. The board wants you to "make the numbers work". So you lean on the rollout team to trim costs.

They do as you ask.

They swap a few finishes.

They tweak a fixture spec.

They remove an element or two.

Nothing dramatic. Just enough to hit the revised number.

They bundle up the compromises and present them back to the leadership group.

Everyone nods along. It seems like we've got agreement.

Then a couple of weeks later the CMO walks into a store mid-build, looks around, and picks up the phone.

Not to the rollout team lead.

Straight to the store build contractor.

"You can't make those changes, this isn't what we signed off."

And just like that, the merry-go-round starts turning.

The rollout team is stuck in the middle, getting whiplash between two leaders asking for two different things at once:

• a return that stacks up financially, and

• a customer experience that still feels like the original vision.

Nobody's lying.

Nobody's incompetent.

The brand, the characters, the players are different in every company, but if you've spent any time in retail or transformation… you've probably seen this movie before.

On paper, it's a neat little optimisation exercise.

On the shop floor, it's a very expensive way to argue in slow motion.

Why retail transformation keeps hitting the same wall (and it's not just stores)

We don't lead store refurbishment rollouts. Our world is software – core systems, process changes, retail digital transformation projects.

But in retail project management, the steps and the dynamics are incredibly similar.

You've got:

• A big investment – 8-figure capex in stores, or a multi-million core system replacements & upgrades.

• A cross-functional team – finance, marketing, operations, IT, supply chain.

• A rollout plan – phases, sites, waves, go-lives.

And in both worlds – whether it's a store rollout or a retail transformation programme – you get exactly the same merry-go-round when the goals aren't aligned.

This isn't "one CMO versus one CFO".

It's what the research calls goal misalignment – really, a breakdown in leadership alignment – and it's one of the most common problems in retail cross-functional project teams.

One experiment published in the Journal of Business Logistics took 468 people, put them into simulated sourcing teams, and changed just one thing: whether the functions were aligned on goals or not.

When the goals were misaligned, something ugly happened:

• Task conflict – "we disagree about what to do" – turned into relational conflict – "we disagree with each other."

• That conflict spilled over into self-serving politics – people started playing games to protect their own function rather than delivering on the overall outcome.

And as the politics went up, the quality of team decisions went down.

Sound familiar?

In our store story, the CFO is optimising for ROI.

The CMO is optimising for brand experience.

The rollout team is optimising for "please can we just get the job done".

Three legitimate goals.

Zero shared agreement about where the trade offs happen.

Private scorecards: why "good work" still feels like failure in retail projects

There's another piece of research that explains why these projects feel so frustrating even when the delivery team does good work.

Benefits Realisation Management looks at what happens when each stakeholder holds a personal view of what "project value" actually means.

The finding is blunt:

Performance suffers not because the work is bad, but because success is being judged against different, unspoken (stealth) scorecards.

In our store story, the scorecards look like this:

• The CFO's scorecard says: "cost per square metre and ROI hurdle."

• The CMO's scorecard says: "does this feel like our brand to a customer who walks in cold?"

• The rollout team's scorecard says: "open on time, no disasters, no career-limiting phone calls."

No one's wrong.

They're just not playing the same game.

And this isn't just happening in physical stores.

It shows up just as often in retail ecommerce and software projects:

• Finance is asking, "Did we hit the business case?"

• Marketing is asking, "Can we execute the offer the way we planned?"

• Store ops is asking, "Does this work easily when I've got a queue of customers?"

• IT is asking, "Is it stable and secure?"

The implementation partner and project team can hit every milestone.

The system can go live.

But if half the room feels like the project failed because it didn't hit their version of value.

Then that's benefits failure by misalignment, not by incompetence.

Misalignment disguised as agreement in retail leadership teams

Here's the really dangerous part.

Goal misalignment doesn't show up as screaming matches in steering meetings.

Most of the time, it looks like polite agreement.

There's a phrase from transformation work I like: "misalignment disguised as agreement."

In the leadership room, everyone nods at the compromise pack.

The deck gets signed off.

Actions are assigned.

Minutes are written.

But then when it comes to execution, people hesitate.

The CMO vetoes the change in store.

The regional manager vetoes the new process at their stores.

The ecommerce manager deprioritises a notification that redirects traffic to physical stores.

Nobody says, "I reject your goals."

They just enforce their own scorecard in the one place they have leverage – in their store, their region, their channel.

And every time that happens, the merry-go-round picks up a bit more speed.

The research on cross-functional teams backs this up: teams usually fail because their work is set up in a way that creates these challenges – unclear goals, ambiguous decision rights, and no shared lens for what "good" looks like.

What leadership alignment actually is (and isn't)

So what do we do with this?

First, let's be clear about what alignment is not.

Alignment is not:

• The CFO and CMO going shopping together and agreeing on every fixture and finish.

• Or in a software context, sitting in every design workshop and debating every field on every screen.

That's unsustainable.

They have day jobs.

Alignment also isn't getting everyone to pretend they care about the same thing. The very reason that we bring cross functional teams together is because they do have different priorities.

The CFO should care about return.

The CMO should care about customer experience.

Ops should care about stores running smoothly.

Alignment is simpler – and harder – than that.

Alignment – real strategic alignment – is a shared commitment, made in the same room, to what "success" actually looks like for this project, and to the rules for making trade-offs when those goals collide.

Before the contractor orders materials or the implementation partner spins up a sandbox.

That looks like asking and answering three questions:

1. Which project/ business goal wins when there's a clash?

Are we prioritising financial return, customer experience, speed to market, risk reduction… or a defined balance between them?

2. Who has the decision rights on which trade-offs?

In project terms, who gets to say, "We accept this cost for that experience", or "We accept this UX compromise for that timeline"?

3. What gets escalated, and what doesn't?

What stays with the rollout team or the project team, and what absolutely must go back to the CFO and CMO together?

Strategic trade-off guidance is the clarity we seek: when teams know the business priorities and the rules of the game, they make better decisions faster, with less politics, less noise and fewer needs for intervention.

Once project governance is clear, the merry-go-round stops

Here's the payoff.

Once a team is empowered with those answers, they can just get on with it.

Your people will see a problem and say:

• "Under our rules, this is a brand-first decision, so we protect the customer experience and find the savings somewhere else."

  OR

• "We agreed that usability for store teams beats elegance in the back office for this release, so we'll keep this feature and cut that one."

They're no longer guessing which invisible scorecard matters most this week, or which senior leader will ring them from site and overturn the last decision.

Until then, everything they do is just another lap of the merry-go-round:

• More steering meetings.

• More rework.

• More frustrated teams and suppliers.

And very little hope of consistently hitting any goal.

Because when you haven't agreed how to make trade-offs, the project doesn't optimise for ROI or customer experience or reliability.

It optimises for whoever last decided.

Where 6R fits into retail project management

This is where a systems and process partner earns their keep.

Most executive leadership teams hear "alignment" and think culture, soft skills, personality types.

In our world, alignment is architecture:

• Clear, shared goals that the cross functional project team plus the operational teams understand the same way.

• Decision rights and trade-off rules mapped to those goals, so your project team isn't guessing.

• Retail systems implementation and retail change management plans that bake those rules how we make decisions.

We are not store rollout experts.

But whether you're rebuilding stores or replacing core systems, retail leadership teams see the same pattern:

If you don't set the rules for trade-offs up front, you will ride that merry-go-round of compromises every single time – and this is usually where the reasons why retail projects fail actually start.

If you do set the rules up front – and stick to them when the pressure hits – you give your teams permission to deliver projects that work:

stores that open on time, on budget, on brand;

systems that go live, are adopted, and actually create the business value you promised.

And that's what your C-suite is really asking for.

Not perfection.

Rather, a project that works, and a story they're proud of.

If you imagine your next big systems project, what's the one trade-off you most want to define up front – financial return, customer experience, or operational resilience?

Retail improvement, made practical.
Leadership thinking that drives change.

Sign up to receive new articles and strategic guidance.