When strategy disappears into day-to-day business.
How to translate strategic priorities into effective execution – and how to tell when the actions need correcting and when the strategy does.
Twelve new customers are planned. The capacity for them is not.
A B2B provider wants to win twelve new customers for a standardized offering within six months. Sales continues to pursue several different segments. Product development is fully occupied with custom requests from existing customers. The monthly review discusses the pipeline; a decision on free capacity is never taken.
The target has been agreed, but delivering it competes with work that has already been promised.
What does management have to decide first?
More sales activity will not resolve this conflict on its own. First the choice of target customers, the offering and the available resources have to fit together. Then a rhythm is needed in which execution, results and strategic assumptions are reviewed.
The case runs through the sections that follow. It shows which connection between strategy and day-to-day business has to be established – and how you can tell that it is actually working.
Five tasks. Two different return paths.
Kaplan and Norton connect strategy, operational planning and learning into a closed management system.1 The ScaleUP adaptation below makes execution visible as a phase in its own right and combines the translation of objectives with resource planning. Each phase produces a result that the next one can work with.
- 01
Decide the direction
Focus, value proposition and assumptions
- 02
Connect objectives and resources
Priorities, accountability and funded initiatives
- 03
Execute the changes
New processes, actual adoption and results
- 04
Review impact and steer
Decisions on actions and the use of resources
- 05
Test assumptions, develop the course
Confirm or change the strategic direction
The return paths show which level a correction is made at. Operational corrections can also happen directly in phase 3. In a running business the tasks overlap; they are not an annual waterfall process.
A missed target is a question, not yet a diagnosis.
Clarify the mandate, capacity, capabilities and decision rights.
Examine adoption, the assumed mechanism and the time to result. Take data quality and sample size into account.
Review the target segment, the offering or the business logic. Where necessary, change the target and the time horizon as well.
This distinction guards against two wrong reactions: abandoning a sound strategy because of an unresolved execution problem, or defending a disproven assumption with ever more activity.
Five decisions that close the loop.
The breaking points below describe typical difficulties in applying the model. Each one needs a concrete decision and visible evidence of improvement.
Define where growth is supposed to come from.
- Symptom
- Every function can justify its existing activities with the growth target.
- Cause
- A result target is no substitute for a strategic choice. Target customers, the relevant customer problem, the value proposition and what is deliberately given up all remain unclear.
- Decision
- Name one priority segment and offering. Record which opportunities will not be pursued for now and which existing tasks this removes.
- Evidence
- Sales, marketing and delivery resolve concrete trade-offs against the same priority.
In the example: The team concentrates on one segment with a common use case. Custom development outside the standard offering requires separate approval.
Release resources before delegating accountability.
- Symptom
- The initiative has an owner and a budget but barely moves forward.
- Cause
- The people required are already committed elsewhere. Cross-functional contributions and decision rights have not been agreed. An extra responsibility does not create capacity.
- Decision
- Confirm the result, the deadline and the available capacity together. Name the work that will be deferred; settle dependencies and escalation. If that is not possible, change the scope or the deadline.
- Evidence
- The commitment appears in the work plans of the functions involved. The owner can act within their mandate.
In the example: One custom extension is deferred so that the standard offering can be finished. At the same time, the capacity for onboarding new customers is checked.
Make everyday adoption the test of execution.
- Symptom
- The playbook, the training and the CRM changes are complete. The way of working is almost unchanged.
- Cause
- Project completion, actual adoption and business impact are treated as the same thing. Nobody clearly owns the process going forward.
- Decision
- Agree three separate pieces of evidence: what was delivered? How is it being used? What impact do we expect, and by when? Make sure process ownership and team capability are in place.
- Evidence
- The new way of working is visible in real cases. Exceptions are explained and dealt with.
In the example: Opportunities are qualified against shared criteria. In the deal review, what counts is the customer problem, the buying process and the point of decision – not just a completed CRM field.
Connect metrics to interventions.
- Symptom
- The dashboard shows more contacts and more proposals. Whether the strategic priority is advancing remains unclear.
- Cause
- Activity is read as impact. Definitions, target values or the link to the result are missing. Commercial guardrails are considered too late.
- Decision
- Link one clear outcome measure to suitable leading indicators and guardrails. For material deviations, decide on an intervention – or first on the missing step of insight.
- Evidence
- The review ends with a decision, an owner and a date. At the next meeting the effect of the intervention is examined.
In the example: The team looks at target customers won and reliably qualified opportunities alongside the minimum margin and the onboarding capacity. A high number of conversations alone does not trigger a budget increase.
Test assumptions before they become dogma.
- Symptom
- The same deviations keep recurring. The team pushes back dates without examining the basis of the plan.
- Cause
- Expectations about willingness to pay, the length of the buying process or the ability to deliver were never written down explicitly.
- Decision
- Document the critical assumptions. Agree the observable signals, the review date and what would trigger an earlier review. Then deliberately continue, test, change or stop.
- Evidence
- Leadership can explain which insight changed which decision – or why the current course still holds.
In the example: Customer conversations point to a buying process of 150 days rather than the assumed 90. The team examines the evidence and, if necessary, adjusts its closing plan and time horizon.
The first decision is about capacity. The later one may be about the plan.
Without releasing the resources, the offering could not be delivered at all. Once it is launched, reliable insight into actual demand is needed. A longer buying process does not automatically disprove the choice of segment; initially it may simply call for different planning of time and capacity.
Sanity-checking the target also means doing the volume arithmetic: with twelve intended wins and an assumed win rate of 20 per cent, 60 comparably qualified opportunities would be needed that can be decided within the target period. The calculation makes an assumption visible. It is no substitute for a forecast with realistic closing dates.
Three purposes of conversation instead of one overloaded agenda.
Operational and strategic work require separate decision questions. The participants may overlap. The frequencies below are a starting point; they have to fit the business model, the sales cycle and the pace of change.
Coordinate execution
What is blocking the next committed step? Settle bottlenecks, responsibilities and short-term support.
Result: one concrete commitment with an owner and a date.
Review impact and priorities
Are the right measures moving? Decide on actions, trade-offs and the use of resources.
Result: continue, correct or re-prioritize.
& as events require
Test strategic assumptions
Do the assumptions about customers, market and economics still hold? Material changes trigger an earlier review.
Result: confirm the direction, test specific points or adjust.
An operational problem belongs in the strategic discussion as soon as it touches a strategic assumption or a material resource decision.
Other operational topics get an owner and an appropriate date for resolution. This keeps the strategic agenda workable without shutting out relevant signals from day-to-day business. Data is circulated beforehand; the meeting is for interpreting it and deciding.
For your next leadership meeting.
Pick a strategic initiative that is not moving despite regular meetings. Settle the following together:
- Is what is missing a clear priority, available capacity or a reliable assumption?
- Which decision can the responsible team not take itself?
- What does management have to release, change or stop now?
Write the decision down: what is decided, who implements it and by when? At the next review, examine what changed as a result.
In the example: Management defers one custom extension and releases capacity for the standard offering. At the next review it checks whether the committed capacity was actually available and whether development of the offering moved forward.
Quality shows up in the consequences.
Strategy, planning and reporting are necessary building blocks. The system becomes effective when priorities are given capacity, when initiatives change everyday work and when new insight leads to concrete decisions.
The demanding work lies in the trade-offs: who gives up resources? What gets stopped? Which deviation is acceptable? When does the course have to change? That is exactly where a management model turns into operational leadership.
Which priority is not moving in your company?
ScaleUP Advisory combines strategic clarity with operational responsibility for revenue, growth and go-to-market. In a first conversation about an engagement, the starting point is one concrete gap between target, resources and execution.
Bring a strategic priority that is stalling despite regular reviews. Together we can establish which cross-functional leadership decision is missing and where operational support makes sense.
Discuss an engagement ↗Basis and attribution
1 · Robert S. Kaplan and David P. Norton: Mastering the Management System, Harvard Business Review, January 2008. Adapted for practice with a modified phase structure; not an unaltered reproduction of the original model.
Starting point: Ronny Steinhagen, “Management mit System”, 13 September 2024. The running B2B case and its figures are fictional. The working rules and review rhythms are recommendations for application and are adapted to each company’s situation.