Strategy is rarely the problem. Staying close to the field and executing with discipline usually are.
By Antoine Maccioni - Sep. 1, 2026
Strategy is rarely the problem. Staying close to the field and executing with discipline usually are.
Over the years, I have sat on both sides of the equation: building strategies at corporate level, and then being responsible for making them work across countries, stores, teams and P&Ls. That experience has made me increasingly cautious about one assumption: that once the strategy is clear, execution will somehow follow. It rarely does.
I have seen strong strategies lose impact as they travelled through an organisation. Priorities multiplied, functions added their own agendas, resources did not always follow the strategy, accountability became less clear, and local realities challenged central assumptions. Sometimes leadership also became too distant from the field to realise that the plan was no longer producing the expected result.
None of this necessarily means the strategy was wrong. It means that strategy and execution cannot really be separated. For me, the most important leadership work often begins after the strategy has been agreed: turning direction into a few real choices, making sure capital and resources follow those choices, staying close enough to operations to challenge assumptions, giving teams enough freedom to act, and being willing to change course when reality says something different.
"A strategy that cannot survive contact with the field is still only an ambition."
I have rarely seen an organisation suffer from a complete absence of strategy. Usually, there is plenty of it: growth priorities, digital priorities, customer priorities, productivity programmes, transformation initiatives and new capabilities to build.
The problem starts when all of them become important at the same time.
I have seen leadership teams genuinely agree on a strategy and still struggle to execute it because the organisation underneath was being asked to pursue too many things. Nothing was obviously wrong, which is precisely what made it dangerous. Projects were progressing, meetings were happening and teams were busy, but management attention and resources were being diluted across too many priorities.
Over time, I have learned that one of the most useful questions a leadership team can ask is not “What else should we do?” but “What are we prepared not to do?”
That is where strategy becomes uncomfortable. And, in my experience, that is often where it becomes real.
“The hardest strategic decision is often not what to start. It is what to stop.”
A strategy can be perfectly clear at the top and become surprisingly blurred as it moves through the organisation.
I have seen this happen more than once. The original direction is understood, but every function, country or business unit naturally translates it through its own priorities. Additional initiatives are added. Local interpretations emerge. Existing projects remain alive because nobody wants to stop them. After a few months, the organisation may still be working hard, but the connection with the original strategic choices has weakened.
This is where leadership has to keep simplifying.
For me, strategic clarity is not achieved when the strategy has been presented once. It is achieved when people across the organisation can explain, in practical terms, what matters most, what should change and what they are expected to do differently.
That requires repetition, but it also requires consistency. If leadership says there are three priorities and then continues funding fifteen, the organisation will believe the funding, not the presentation.
The same applies to decisions. Strategy becomes credible when resource allocation, capital, talent and management attention all point in the same direction.
I have learned that organisations rarely need more strategic messages. They usually need fewer messages that leadership is willing to reinforce consistently.
“Strategy loses credibility the moment the organisation sees a gap between what leadership says matters and where the business actually places its bets.”
One of the most useful disciplines I have found is to translate strategic ambition into economics as early as possible.
A strategy can sound convincing while remaining abstract. Grow market share. Accelerate digital. Improve customer experience. Simplify the organisation. Increase productivity. All of these may be right, but they only become truly actionable when the organisation understands what should move in the business as a result.
What should happen to revenue?
What should happen to gross margin?
What should happen to cost?
What should happen to working capital, cash or return on investment?
The purpose is not to reduce strategy to Finance. It is to make the consequences of strategic choices visible.
I have seen how much sharper the conversation becomes when teams can connect a strategic priority to an operating outcome and then to an economic result. It also makes trade offs easier. If two initiatives compete for capital or people, the leadership team has a clearer basis for deciding which one deserves priority.
This is also where weak assumptions become visible. Sometimes the strategy is sound, but the economics behind it are too optimistic. Sometimes the economics work, but the organisation does not yet have the capability to deliver them.
In both cases, making the value logic explicit improves the quality of the discussion.
“A strategy becomes much harder to hide behind once the economics are visible.”
This is probably the leadership lesson I feel most strongly about.
The further you move from the field, the easier it becomes to believe that reality looks exactly like the dashboard.
It rarely does.
Stores, branches, customers, suppliers and frontline teams often see problems before they appear clearly in the numbers. They also see opportunities that do not always travel upward through the normal reporting process.
That is why I have always valued direct exposure to operations. Not to bypass management teams, and not to micromanage, but to keep testing whether the assumptions behind the strategy still hold.
I have changed my mind more than once after spending time in a store, visiting a branch, speaking with customers or listening to local teams explain why something that looked obvious centrally was much harder in practice.
For me, that is not a weakness in leadership.
It is part of the job.
The risk comes when senior leaders become so invested in the strategy that every piece of field evidence is interpreted as resistance rather than information.
Proximity to the field is useful precisely because it can prove you wrong.
And when it does, the right response is not to defend the plan. It is to understand what the business is telling you.
“The field should not confirm the strategy. It should constantly test it.”
Staying close to the field does not mean centralising every decision.
In fact, I have generally found the opposite to be true.
Once the strategic priorities are clear, local teams need enough room to execute them in the reality of their markets.
Customers differ.
Competitive environments differ.
Labour markets differ.
Regulation differs.
Commercial practices differ.
A strategy that requires every market to behave identically can become unnecessarily rigid.
But decentralisation only works when the boundaries are clear.
I have seen local empowerment work very well when teams understood what was non negotiable and where they genuinely had freedom. The strategic direction, financial ambition, customer promise and certain operating standards may need to remain common. The way those outcomes are achieved can often be adapted locally.
The difficulty is finding the balance.
Too much central control slows decisions and weakens accountability.
Too much local freedom can fragment the strategy and create several different companies inside the same group.
For me, good execution sits somewhere between the two. Leadership defines the destination, the economic expectations and the critical boundaries. Local teams then have enough authority to make the decisions required to get there.
That is not loss of control.
It is controlled empowerment.
“The centre should be clear on the destination without pretending it knows every road.”
One of the clearest signs that a strategy is not yet embedded is when it requires a separate conversation to keep it alive.
The strategy meeting happens on Monday.
The operational review happens on Tuesday.
The financial review happens on Wednesday.
And somehow the three conversations do not fully connect.
I have seen that gap create enormous friction.
For strategy to become real, it has to enter the normal operating rhythm of the business. The same priorities should appear in performance reviews, resource decisions, talent discussions and capital allocation. When results are off track, the discussion should immediately connect back to the strategic assumptions and execution choices behind them.
This is where leadership discipline matters.
It is easy to launch new initiatives when something is not working. It is harder to stay focused on the few priorities already agreed, identify what is blocking execution and remove those obstacles consistently.
Over time, I have become more convinced that execution is less about creating more management processes and more about making the existing ones serve the strategy.
When that happens, the strategy stops being something the organisation discusses periodically.
It becomes the way the business is run.
“Strategy becomes real when it disappears into the operating rhythm of the business.”
One of the hardest balances in leadership is knowing when to step back and when to get closer.
Too much altitude, and leadership can lose touch with what is really happening.
Too much proximity, and the organisation can become dependent on senior intervention.
I have learned that both perspectives are necessary.
You need enough distance to see patterns, challenge priorities, allocate resources and keep the long term direction clear.
But you also need enough proximity to understand whether the operating reality still supports the assumptions behind the strategy.
That means going beyond dashboards.
Talking to teams.
Visiting operations.
Listening to customers.
Testing whether the organisation is interpreting the strategy the way leadership intended.
The point is not to manage every detail.
It is to stay close enough to reality to know when the details are telling you something important.
For me, the strongest leaders are not permanently in the weeds or permanently above them.
They move between the two.
“Leadership needs altitude to see the direction, and proximity to know whether the business can actually get there.”
At your next strategy review, do not start with the presentation.
Start with three questions:
What are the three priorities we are truly asking the organisation to deliver?
Where have we actually placed the resources, capital and leadership attention to support them?
What is the field telling us that does not fit the current strategy?
Then compare the answers.
If the priorities are clear but the resources do not follow, the strategy is not yet real.
If the resources are aligned but execution is not moving, the problem is probably operating discipline.
And if the field is consistently telling a different story, leadership needs to challenge its assumptions.
The point is not to create another management ritual.
It is to force a more honest conversation between strategy, execution and reality.
“The quality of a strategy review depends less on what confirms the plan than on what challenges it.”
This article builds on themes previously explored in a LinkedIn post.