Operations Excellence & People Management
Most organisations are better at setting strategy than executing it. The gap is almost never about the quality of the plan — it is about the absence of a system that translates strategic goals into daily and weekly action. Here is one that works.
The problem with strategy is not usually the strategy itself. Most organisations have a coherent enough view of where they want to go. The problem is the gap between the strategy and what people actually do on Monday morning.
This gap is not a motivation problem or a leadership problem, though it is often described as both. It is a translation problem. Strategic goals are stated at a level of abstraction — "improve customer retention", "reduce operational costs", "accelerate growth in new markets" — that gives people no actionable direction. Without a system that translates these into specific work at the team and individual level, the strategy stays on the slide deck.
Consider a common strategic goal: improve customer retention. For the executive team, this is a coherent objective with clear commercial implications. For the customer success manager, it means something specific — but what, exactly? Which customers? By how much? Through what actions? By when?
Without answers to these questions, the customer success manager does what is reasonable given the ambiguity: they continue doing what they were already doing, perhaps with more urgency. The retention metric does not improve. The executive team concludes that execution is weak. The customer success manager concludes that leadership does not communicate clearly. Both are partially right.
For each strategic goal, define two or three specific, measurable outcomes that would indicate progress. Not outputs (activities you will complete) but outcomes (changes in the business that you can measure). "Reduce churn rate from 8% to 5% in 12 months" is an outcome. "Run monthly customer health reviews" is an output.
Each outcome needs a single owner — one person who is accountable for the result, even when the work involves multiple people. Shared accountability is usually no accountability. The owner does not have to do all the work. They have to ensure it gets done and flag when it is at risk.
For each outcome, identify two or three leading indicators — measures that predict whether you are on track before the final number is visible. For a retention goal, leading indicators might include: health scores for the at-risk segment, number of proactive outreach calls completed, percentage of customers with a documented success plan. These give you early warning, not just a post-mortem.
For each leading indicator, define the specific tasks that drive it, the frequency with which they need to happen, and the person responsible for each. This is where strategy finally meets Monday morning. The task is concrete, time-bound, and assigned. It is possible to know whether it happened.
Weekly: review leading indicators. Are we doing the things we said we would do? Monthly: review outcome progress. Are the things we are doing producing the results we expected? Quarterly: review assumptions. Are we working on the right outcomes? Annual: review strategy. Are the outcomes still the right ones?
In a team of 8 people, this framework might produce 3 strategic goals, 9 outcomes, 18 leading indicators, and 36 weekly tasks. That sounds like a lot until you realise that those 36 tasks are the specific things that will move the business — as opposed to the ambient activity that fills most weeks without producing measurable progress.
The first time you run through this exercise with a team, the most common reaction is relief. People know what they are doing and why. They have a way to prioritise when two things compete for their time. They can tell the difference between work that matters and work that merely feels busy.
That clarity is the point. Strategy becomes real when people know exactly what to do with it next Monday.
Book a 60-minute session and we work through your specific challenge — no templates, no generic frameworks.