Where strategy loses momentum: 12 execution pitfalls and how to avoid them

An Emergent Africa perspective

A strategy can be commercially sound, supported by the board and enthusiastically presented to employees, yet still fall short of its intended results.

The breakdown often happens gradually. Priorities multiply. Decisions wait for agreement. Projects report progress without demonstrating business impact. Managers protect departmental targets. Financial assumptions become outdated, while the original business case continues to circulate unchanged.

Eventually, leadership faces an uncomfortable question: why is the organisation so busy, yet making so little progress on the outcomes that matter?

Answering that question requires examining how strategy translates into everyday decisions, resource commitments, working relationships and performance reviews. Execution depends on the quality of these connections. When they weaken, even capable people can spend considerable effort moving in different directions.

This article draws on published work from five leading global consulting firms: McKinsey & Company, Boston Consulting Group, Bain & Company, Deloitte and PwC’s Strategy&. Their research and perspectives provide useful reference points. The practical recommendations that follow represent Emergent Africa’s synthesis for executive teams seeking to improve execution.

Some of the cited research concerns major transformations rather than every form of strategy implementation. Its lessons are relevant, but transformation findings should not be treated as universal failure rates for all strategies.

For leaders, the most useful starting point is to identify where execution is losing momentum and strengthen the management practices that can restore it.

1. Mistaking ambition for an executable strategy

Statements such as “accelerate growth”, “become more customer focused” and “lead through innovation” communicate intent. They provide limited guidance when managers must choose between competing investments, customers, products or operational demands.

The problem becomes visible when different departments interpret the same strategic statement differently. Sales pursues volume, finance protects margin, operations reduces complexity and technology prioritises standardisation. Each team can defend its actions, yet the combined result may undermine the intended strategy.

PwC’s Strategy& captures a useful principle in Strategy That Works: “Translate the strategic into the everyday.” Its accompanying discussion emphasises building distinctive capabilities that allow the organisation to put its chosen identity into practice.

How to avoid it

Translate each strategic priority into a clear business outcome and the choices required to achieve it. Specify the customers or markets involved, the capabilities needed, the resources available and the activities the organisation will stop or deprioritise.

Consider a hypothetical distributor seeking profitable growth. An executable priority might involve improving availability for selected customer segments while reducing exposure to products that consume working capital without adequate returns. This gives commercial, procurement and operational teams a common decision framework.

Ask managers to explain how the strategy changes a decision they expect to make this month. If they cannot identify one, the strategy needs further translation.

Clarity should reach the point where people can distinguish an attractive opportunity that fits the strategy from one that would distract the organisation. Without that distinction, ambition becomes permission to pursue almost anything.

2. Allowing priorities to exceed organisational capacity

Every initiative can appear worthwhile when assessed independently. The difficulty emerges when all of them compete for the same specialists, executive attention, funding and operational capacity.

A business may simultaneously pursue a technology implementation, a new customer proposition, procurement savings, process redesign and market expansion. Each programme has its own sponsor and timetable. Several depend on the same finance team, data specialists or operational managers.

The portfolio therefore contains a contradiction: individual plans appear feasible, but the combined workload is not.

How to avoid it

Assess priorities together. Examine their total resource requirements, dependencies and demands on the people expected to deliver them.

For every proposed initiative, ask what will be delayed, stopped or simplified to create capacity. Require a clear answer before approval. Adding work without removing or rescheduling anything should be recognised as an explicit capacity decision.

Sequence initiatives according to business value and practical dependencies. A customer analytics project, for example, may require reliable customer definitions and ownership before sophisticated modelling can deliver useful results.

Protect scarce skills by giving critical specialists clear allocations and escalation routes. When five sponsors believe they have first call on the same person, the organisation has created a conflict that the individual cannot resolve.

Portfolio discipline also requires revisiting existing commitments. An initiative that made sense six months ago should compete for resources against current priorities.

A shorter, achievable portfolio can create more value than an impressive list that leaves teams continually starting work and rarely completing the changes that matter.

3. Assigning responsibility without decision authority

An executive is named as the owner of an outcome. Several departments must contribute. Progress stalls because the owner cannot resolve disagreements over resources, standards, timing or scope.

The organisation responds by creating another steering committee. Meetings increase, but the underlying uncertainty remains: who can make the decision?

Bain’s RAPID framework distinguishes the roles involved in recommending, agreeing, performing, providing input and deciding. Bain states: “When teams and organizations use RAPID correctly, they execute strategy at pace.”

How to avoid it

For material execution decisions, identify the decision maker, the people whose input is required, any mandatory approvals and the team responsible for implementation.

Separate consultation from approval. People can contribute essential expertise without every participant holding an unrestricted veto.

Give outcome owners defined authority, access to relevant information and an escalation route for issues beyond their mandate. Accountability becomes credible when people can influence the conditions necessary for delivery.

Imagine an initiative to reduce customer onboarding time. Commercial teams, compliance, operations and technology may all contribute. A named owner needs a workable method for settling disagreements about acceptable process changes while respecting regulatory obligations.

Set decision deadlines that reflect commercial urgency. An unresolved question should have an owner and a date, rather than remain a recurring item in meeting minutes.

Finally, record the decision and its reasoning. Reopening settled matters without new evidence consumes capacity and creates uncertainty for the people implementing them.

4. Delegating execution away from the leadership agenda

Senior leaders understandably expect managers to deliver. However, strategic execution involves choices that often exceed the authority of individual departments.

These include reallocating investment, changing incentives, resolving competing objectives and deciding whether new evidence warrants a change in direction.

BCG makes the leadership requirement explicit: “Leaders cannot simply set the broad vision for a transformation and then delegate its execution.” Its discussion combines clear direction and accountability with team involvement and honest feedback.

How to avoid it

Keep strategic execution on the executive agenda through a regular review of outcomes, obstacles and decisions.

The purpose of leadership involvement is to resolve issues that delivery teams cannot settle themselves. Executives should ask where progress depends on a resource choice, a policy change or cooperation between business units.

Sponsors should understand the business logic of their initiatives well enough to challenge assumptions and support corrective action. Attending a monthly presentation provides limited value if difficult decisions remain unresolved afterwards.

Leadership behaviour also establishes priorities. When executives repeatedly cancel strategy reviews or introduce urgent requests outside agreed processes, employees learn which commitments receive attention.

Maintain continuity when sponsors change roles. Transfer the rationale, commitments, risks and unresolved decisions, alongside project documentation.

Execution benefits from leadership that remains accessible and decisive. Teams need room to act, combined with confidence that senior leaders will address the organisational barriers they encounter.

5. Confusing completed activities with realised value

A project can meet its milestones while failing to deliver its commercial purpose.

A system goes live, but employees continue using spreadsheets. A training programme finishes, but working practices remain unchanged. A new product launches, but customer acquisition costs exceed the assumptions in its business case.

The project report may be accurate about delivery while giving an incomplete picture of strategic progress.

How to avoid it

Define success at three levels: what will be delivered, what will change in the business and what measurable benefit should follow.

For a customer service initiative, delivery might mean introducing a new case management process. Operational change might mean fewer transfers and faster resolution. Business benefits might include lower service costs, stronger retention or improved customer satisfaction.

Track these connections explicitly. If the expected operational change does not occur, investigate before assuming the financial benefit will arrive.

Use leading indicators that provide early evidence of adoption or performance, alongside financial and customer outcomes. Select indicators because they inform decisions, rather than because they are easy to collect.

Avoid adding so many measures that the important signals disappear. Each metric should help answer a management question.

Completion should trigger a benefits review, particularly where value depends on behaviour after implementation. The delivery team may finish its assignment before the organisation has secured the intended return.

Recognising this distinction helps leaders celebrate progress while remaining honest about what has actually changed.

6. Keeping finance separate from execution

Business cases establish expectations at approval. Those expectations can become detached from reality as implementation progresses.

Costs rise. Adoption takes longer. Benefits overlap with another initiative. Revenue growth reflects market conditions rather than the intervention. Savings appear in a presentation without reducing expenditure or releasing usable capacity.

The resulting gap weakens confidence in the entire strategic portfolio.

How to avoid it

Involve finance throughout execution, with clear responsibility for benefit definitions, baseline agreement and validation.

Distinguish different forms of value. Reduced expenditure, avoided future costs, released working capital and additional capacity have different implications. They should not be combined as if they all represent cash savings.

For example, automation may release employee time. The commercial benefit depends on what happens next. The organisation might absorb growth without additional recruitment, improve service or reduce overtime. Each outcome requires evidence and an appropriate financial interpretation.

Maintain an updated forecast alongside the original business case. Preserve the original assumptions so that leaders can see what changed and why.

Prevent double counting where several initiatives contribute to the same outcome. Agree how benefits will be allocated before competing teams claim them.

Finance should also help identify options when performance falls behind expectations. The conversation should consider whether to change scope, timing, investment or the operating approach.

This creates a more useful relationship between financial discipline and delivery: one that helps leadership improve future outcomes while explaining past performance accurately.

7. Treating employee engagement as a communication exercise

A strategy launch can explain the destination without helping employees understand the journey.

People need to know how expectations affect their own work, what support is available and how competing demands will be resolved. They also hold practical knowledge about customers, systems and processes that may be missing from executive discussions.

McKinsey puts the requirement directly: “People need to understand what these goals mean for their day-to-day jobs”. Its transformation research also highlights the importance of involving line managers and frontline employees.

How to avoid it

Move from general communication to practical conversations about work.

Ask teams which decisions will change, which tasks will stop, what new skills they require and what could prevent successful adoption. Treat their responses as implementation evidence.

Middle managers deserve particular attention. They translate strategy into schedules, customer commitments, performance conversations and resource choices. If they receive additional responsibilities without the authority or capacity to fulfil them, the strategy becomes difficult to deliver consistently.

Equip managers with clear explanations, practical tools and access to answers. Allow them to raise genuine concerns without being labelled resistant.

Test new ways of working with the people who will use them. A process that looks efficient in a workshop may create avoidable complexity during a busy operating shift.

Measure understanding through decisions and behaviour. Recalling a strategic slogan tells leaders much less than seeing employees apply the intended priorities when handling an actual customer or operational problem.

8. Expecting new outcomes from unchanged incentives and behaviours

An organisation may encourage collaboration while rewarding only departmental performance. It may promote innovation while penalising every unsuccessful experiment. It may ask employees to raise risks early while reacting defensively when they do.

These contradictions make execution harder because people must choose between the stated strategy and the behaviours that protect their standing.

Deloitte observes: “Culture and engagement are living things that need to be reinforced and adjusted over time”. Its discussion connects this ongoing work to changes in strategy, circumstances and people.

How to avoid it

Identify the behaviours that each strategic priority requires and examine whether current practices support them.

If growth depends on sharing customers across business units, review how revenue credit and recognition are allocated. If faster decisions matter, examine approval layers and the consequences of making a reasonable decision with incomplete information.

Be specific about desired behaviour. “Improve collaboration” is difficult to assess. Joint planning, shared customer reviews and agreed handover standards provide observable evidence.

Leaders should model the same expectations. Publicly requesting honest reporting while privately rewarding optimistic updates creates predictable results.

Review incentives carefully so that changes do not introduce fresh distortions. A single shared measure rarely captures every legitimate responsibility.

Culture becomes visible in routine decisions: who gets recognised, which problems receive attention and how leaders respond when delivery becomes difficult. Improving those moments makes strategic expectations more credible.

9. Allowing departmental success to conceal enterprise failure

A procurement team negotiates a lower unit price, but larger order quantities increase inventory and obsolescence. A service department reduces handling time, but customers make repeated calls because their problems remain unresolved.

Each department can achieve its target while the organisation experiences a worse overall result.

This pitfall is especially important where strategic outcomes depend on several functions. Customers experience the combined service, irrespective of how internal responsibilities are divided.

How to avoid it

Assess important outcomes across the full process.

Identify where one team’s choices create costs, delays or risks elsewhere. Make those relationships visible during planning and performance reviews.

Use a combination of functional measures and shared outcomes. Procurement should retain responsibility for commercial discipline while participating in measures that reflect availability, working capital and total cost.

Agree the obligations between teams. A dependency should specify what is needed, who will provide it, when it is required and how problems will be escalated.

Jointly examine recurring failures at handovers. Often, the issue is an unclear standard, incompatible definition or missing decision rather than a lack of effort.

Executives must be willing to resolve trade offs in favour of overall business value. That may mean accepting a weaker result on one departmental metric to improve the enterprise outcome.

Without this intervention, departments have a rational incentive to defend local performance, even when everyone understands that the collective result is disappointing.

10. Building dashboards that create confidence without clarity

A dashboard can be visually persuasive and operationally misleading.

Different teams may use different definitions of completion. Data may be several weeks old. Status colours may reflect personal judgement. A project may remain green because its timetable is intact, even though its expected benefit has deteriorated.

When these weaknesses are hidden, reporting can delay intervention.

How to avoid it

Define the meaning, source, owner and update frequency of important measures.

Separate delivery status from benefit status. An initiative can be on schedule while carrying a material risk to its commercial outcome.

Establish common thresholds for escalation, allowing appropriate judgement where numerical measures cannot tell the whole story. Record the reasoning behind significant status changes.

Make uncertainty visible. If a forecast depends on an untested assumption, leaders should see that assumption rather than receive an apparently precise number.

A useful review should answer practical questions: what changed, what evidence supports the assessment, what could happen next and what decision is required?

Reduce time spent manually reconciling competing versions of the same information. Agree which record governs executive decisions and who maintains it.

Most importantly, create an environment where reporting a problem early is useful. If employees expect punishment for showing a red status, the organisation may receive reassuring reports until recovery becomes expensive.

Reliable reporting combines sound information with leadership behaviour that encourages candour.

11. Continuing to execute after the assumptions have changed

Disciplined implementation becomes counterproductive when leaders defend a plan despite evidence that its underlying logic has weakened.

Customer demand may differ from expectations. A supplier may become unreliable. The economics of a proposed investment may change. A capability may take longer to develop than the strategy allows.

Teams can continue delivering the agreed plan while moving further away from the intended result.

How to avoid it

Document the assumptions behind major strategic choices and identify the evidence that would justify reconsideration.

Review those assumptions at a frequency appropriate to the exposure. A rapidly changing market may require closer attention than a stable internal improvement programme.

Define decision points in advance. Agree when to continue, expand, redesign, pause or stop an initiative.

For uncertain opportunities, fund learning in stages. Early work should test the factors most likely to affect commercial viability before the organisation commits the full investment.

Distinguish an execution problem from a strategy problem. Slow adoption may require better implementation, but persistent customer rejection may indicate that the proposition itself needs revision.

Avoid treating every difficulty as evidence that the strategy is wrong. Equally, avoid treating every challenge to the strategy as a lack of commitment.

Good governance enables leaders to change course with a clear explanation. It preserves accountability while allowing the organisation to respond intelligently to what it learns.

12. Expecting technology to solve unresolved management problems

A new platform can improve visibility and coordination. Its value is limited when priorities remain unclear, ownership is disputed or leaders do not act on the information it provides.

Digitising an inconsistent process can make the inconsistency more visible without resolving it. Adding another reporting tool can also increase workload if teams must maintain several versions of the same information.

How to avoid it

Define the management practices that technology must support before selecting or configuring the solution.

Agree how priorities are approved, how ownership works, how measures are defined and how decisions are escalated. Identify which existing reports or processes the new approach will replace.

Start with a meaningful part of the strategic portfolio. Test whether the system helps people make decisions, coordinate work and maintain reliable information.

Assess adoption through use in real management routines. A platform that is updated only before a reporting deadline may have become an administrative obligation.

Keep the commercial purpose visible. The intended value should include clearer accountability, earlier intervention, reduced duplication or stronger confidence in outcomes.

Assign responsibility for maintaining the quality of the information and the usefulness of the process. Technology needs ongoing ownership just as the strategy does.

The strongest implementation combines practical tools with explicit expectations about how leaders and teams will use them.

A practical 90 day reset

Organisations experiencing several of these pitfalls do not necessarily need to begin with another comprehensive planning exercise. A focused review of current commitments can reveal where immediate action will help.

During the first 30 days, establish a shared view of reality.

List the major strategic outcomes and initiatives. Identify accountable owners, current forecasts, outstanding decisions and the resources being used. Compare the portfolio with actual capacity.

Look for commitments with weak strategic relevance, duplicated effort or unclear benefits. Ask teams where work repeatedly waits and which reports require significant effort without improving decisions.

The aim is a credible view of the current position, including uncertainty.

During days 31 to 60, repair the most important connections.

Clarify ownership and decision authority. Resolve conflicting priorities. Agree benefit definitions with finance and identify the dependencies most likely to affect delivery.

Select a small number of measures that connect activity to operational change and business outcomes. Confirm the behaviours and capabilities required from the teams involved.

Create capacity by stopping, simplifying or rescheduling lower value work. This makes the reset tangible for employees.

During days 61 to 90, establish a workable review rhythm.

Use executive meetings to resolve exceptions and make decisions. Track whether those decisions are implemented and whether the expected effects follow.

Review assumptions as well as progress. Update forecasts when evidence changes. Capture lessons that should influence other initiatives.

At the end of the period, assess whether the organisation has become clearer about its priorities, quicker at resolving obstacles and more reliable in judging progress.

The test is whether management can act with greater confidence and whether teams can devote more attention to delivering the intended outcomes.

Making execution a lasting organisational capability

The commercial cost of weak execution extends beyond delayed projects. It can include wasted investment, missed customer opportunities, avoidable working capital, duplicated effort and declining confidence in leadership commitments.

There is also a human cost. Capable employees can become discouraged when priorities continually change, unresolved decisions block their work and additional reporting substitutes for practical support.

Addressing these problems creates benefits that reinforce one another. Clearer priorities improve resource allocation. Defined authority speeds up decisions. Reliable measures support earlier intervention. Stronger participation improves implementation. Financial discipline helps leadership distinguish activity from value.

These practices need to operate together and remain useful as circumstances change. They should form part of how the organisation manages its business every week.

For executive teams, the central question is whether they can follow a strategic commitment through to its owner, resources, assumptions, performance and required decisions. Where those connections are weak, execution is vulnerable.

Emergent Africa’s Meridian Strategy Execution Platform is designed to support this connected approach by bringing strategic choices, accountable owners, financial assumptions and performance reviews into a shared view.

Its role is to help organisations maintain the connection between what they intend to achieve and how they manage progress towards it. Combined with clear priorities, active leadership and disciplined reviews, Meridian can support a more consistent approach to turning strategic commitments into business outcomes.

To explore how your organisation can strengthen those connections, speak to Emergent Africa about the Meridian Strategy Execution Platform.