How Do I Ensure My Strategy Is Executed Across Departments?
The pattern is familiar. A strategy is agreed, the leadership team is aligned, departments nod. Months pass. Marketing has interpreted the goals one way, operations another, and finance has built measures loosely connected to either. Nobody disobeyed anything. The strategy simply did not survive contact with the organisational chart.
This is usually described as a communication problem, which makes it sound solvable by explaining more clearly. It is a coordination problem, and coordination between departments has specific mechanics that either exist or do not.
Kaplan and Norton built the Balanced Scorecard around the same observation: companies fail more often on aligning people, processes and resources than on the strategy itself. What follows is what alignment actually consists of.
The four mechanics of failure
Unowned handoffs. Most cross-functional work passes between departments several times, and the join belongs to nobody. A launch needs legal review, a security certification and a pricing decision; it slips on whichever of the three nobody chased. Each function completed its part and the sequence failed anyway.
Conflicting incentives. Sales measured purely on closed revenue and delivery measured purely on margin will produce discounted, awkward contracts. That is not a culture problem. It is what the measurement system asked for, and it will continue until the measurement changes.
Undefined decision rights. Two directors hold opposite views, neither can overrule the other, and there is no agreed route to settlement. The question sits for six weeks and eventually escalates by accident, usually in a meeting about something else. Most damaging delay comes from this rather than from disagreement itself.
Unbudgeted capacity. Strategic work is added to functions already fully committed to running the business, and nothing is removed to make room. The new work then competes with the work people are measured on, and loses.
Notice that none of these is fixed by better communication.
Coherence, not uniformity
The goal is coherence: each function pursuing its own version of the strategy in its own terms, in a way that adds up.
Finance should not operate like research and development. What is required is that finance's objectives and research's objectives, pursued fully, produce the intended enterprise outcome rather than cancelling each other.
That distinction matters because attempts at alignment often reach for uniformity: the same template, the same measures, the same cadence for every function. It feels orderly and it produces measures that are meaningless in half the organisation, which teaches everyone that the exercise is administrative.
Shared outcomes
Start with three to five enterprise outcomes, each with a named executive owner. Not financial results, which are consequences, but the cross-functional achievements that produce them: reduce time from order to delivery, raise retention in the enterprise segment, bring the new product to market by the second quarter.
Each function then defines its own contribution, in its own terms, and proposes it rather than receiving it.
Where an outcome genuinely depends on two functions, both should carry it. A measure owned by one function but dependent on another is a mechanism for producing blame: the owner cannot deliver it alone and the other party is not accountable for it.
Direction cascades, content mostly does not
This is the point where conventional advice goes wrong, and it is worth being explicit because the alternative is widely recommended.
Mechanical decomposition, in which each level breaks up the objectives above and passes fragments down, produces three predictable problems. It is slow, because each level waits for the one above. It produces objectives written for the layer above rather than for the customer, because that is the audience. And it discards the knowledge of the people who actually know what is achievable.
The pattern that works is different. Leadership sets direction and constraints. Teams propose what they will take on and how it will be measured. The two are reconciled in a short negotiation, and roughly half the final content originates below the executive layer.
What should be immediate and universal is distribution: when direction changes, every affected function knows quickly and knows which of their commitments is now in question. What should stay local is translation: what this function should therefore do differently.
Decision rights
The most underused mechanism in cross-functional work, and among the cheapest.
For the ten questions most likely to arise between functions, write down who decides, who must be consulted and who is informed. Pricing exceptions above a threshold. Roadmap trade-offs between a large customer's request and the general plan. Resource moves between departments. Scope changes on a shared programme.
Then add an escalation rule with a clock: any cross-functional decision unresolved after a stated number of days goes to a named person. The clock matters more than the person. Unresolved questions do not announce themselves; they simply sit.
Organisations that do this typically find that the friction they attributed to personalities was structural.
Dependencies
A dependency register is unglamorous and removes a large proportion of slippage.
Every cross-functional dependency listed with what is needed, who owns it on each side, the date, and current status. Reviewed in the same meeting every month, with attention on the ones that have moved.
The reason this works is that it converts an invisible risk into an owned commitment. Before the register, the handoff belonged to nobody and its failure surprised everyone. After it, two named people have agreed a date in front of their peers.
Incentives
Where two functions are measured on things that cannot both improve, no amount of collaborative intent will resolve it. The remedy is structural.
Introduce a shared measure that both carry, adjust the weightings so the conflict is bounded, or change what one function is paid for. All three are uncomfortable and all three work, which is more than can be said for a workshop on breaking down silos.
Before redesigning anything, establish that the conflict is real. Often the two functions could both succeed and are simply arguing about a decision nobody has authority to make, in which case the problem is decision rights and the incentive system is fine.
Capacity
Every strategic initiative lands on people who already have jobs.
Making room requires an explicit answer to what stops, what is deferred, or what gets additional resource. Where no answer is given, the strategic work loses to the operational work, because the operational work is what people are measured on weekly and the strategic work is reviewed quarterly.
This is also the point at which strategic ambition meets arithmetic. A leadership team that will not remove anything is a leadership team that has not prioritised, whatever the strategy document says.
The rhythm
Monthly cross-functional review. Structured around decisions, not status. What is blocked, what needs settling, who settles it, by when. Reviews in which each function narrates progress in turn produce a feeling of coordination and no coordination.
Quarterly objective review. Revisit the outcomes themselves. What has been achieved and can leave the list, what is no longer relevant, what has emerged.
Annual reset. Rebuild the outcome set, with the evidence from the year.
The monthly meeting is the one that decays first and matters most. When it becomes a reporting meeting, cross-functional execution stops working within a quarter, and the cause is rarely diagnosed correctly.
What to measure
Decision latency. How long a cross-functional question sits before it is settled. Easy to track once escalations are logged and startling the first time it is measured.
Dependency slippage. The proportion of handoffs missing their agreed dates, and where they cluster.
Resource movement. How much budget and how many people actually moved between priorities. Allocation that mirrors last year's allocation means the strategy did not change anything.
Consistency of statement. Whether the executive team can state the current priorities consistently without opening a document. The strongest single indicator, and almost nobody measures it.
What technology does and does not do
Platforms make the gap visible. They collect data from source systems, aggregate measures, flag variance and surface dependencies that have gone quiet, which shortens the distance between something going wrong and somebody noticing.
They do not settle priorities, resolve conflicts between functions or move resources, because each requires authority a system does not have.
The sequence therefore matters. An organisation that buys a platform before settling shared outcomes and decision rights acquires a well-instrumented view of its own incoherence, which is more expensive than the previous arrangement and no more effective.
The point
Strategy fragments between departments for structural reasons: handoffs nobody owns, incentives that pull apart, decisions with no route to resolution, and capacity that was never freed.
Each has a specific remedy. Shared outcomes with joint ownership. Written decision rights with an escalation clock. A dependency register reviewed monthly. Incentive changes where the conflict is real. An explicit answer to what stops.
None of it is sophisticated. All of it is work the executive team has to do itself, because it concerns authority, measurement and money, and none of those can be delegated to a document or a platform.
