TL;DR: When there’s no shared strategy execution system, every team builds their own. Marketing has a spreadsheet. Sales has a CRM dashboard. Product has a Notion page. Each one is well-intentioned and most are quietly incompatible with the others. The cost is real hours, opaque cross-team handoffs, and a profit-per-employee drag the executive team can’t trace. Here’s what’s actually happening, and how to fix it without ripping anything out.
You ask your COO a simple question. “How are we tracking on Strategic Pillar 2 this quarter?”
She pauses. She doesn’t actually know.
She knows what Marketing said in their last leadership update. She knows what Sales said in their pipeline review. She knows what Product said in their roadmap report. The problem is: those three answers don’t fit together. Each team brought their own format, their own definition of “on track,” and their own data.
There is no shared strategy execution system. There are five or six private ones, and your COO is doing the integration work in her head.
This post is the deep dive on one specific symptom of strategic planning that doesn’t reach goal achievement. The pillar piece covers the full bridge from strategy to execution. This one zooms in on what happens at the team level when the bridge is missing.
What is a strategy execution system? A strategy execution system is the shared operating layer that connects your strategic plan to weekly team-level execution. It includes the format teams use to write goals, the cadence they review them, the scoring system that defines “on track,” and the visibility that lets cross-team dependencies surface in time to act on. Without a strategy execution system, each team builds their own version, and the company runs on a patchwork no one can see whole.
How the DIY Problem Starts
The DIY system isn’t anyone’s fault. It’s a response to a vacuum.
The leadership team writes the strategic plan, hands down department objectives, and moves on. Department heads are left holding objectives they didn’t help write and given no shared method for executing them. The team that has to deliver the objective gets to choose how. So they do.
Marketing’s head of growth opens a Google Sheet and starts tracking pipeline contribution. Sales’ RVPs build a forecast model in Salesforce reports. Product’s PMs draft a “north star” dashboard in Notion. None of these are wrong. Each is a reasonable response to “here’s your objective; figure it out.”
The problem is: none of them talk to each other. Twelve weeks later, the executive team asks for a status update and gets six different shapes of answer.
What “Every Team Built Their Own” Actually Looks Like
When I work with an enterprise that doesn’t have a shared strategy execution system, the inventory of team-level systems tends to include:
- Three to five different goal-tracking tools. Spreadsheets, project management tools, CRM reports, BI dashboards, powerpoint decks, internal docs. Each team owns one.
- Two or three different scoring scales. Marketing reports “red/yellow/green.” Sales reports a 1-10 confidence number. Product reports “shipped/in flight/at risk.” There is no shared definition of “on track.”
- Inconsistent reporting cadences. Some teams check in weekly. Some monthly. Some only at the quarterly board-prep deadline.
- Custom definitions of progress. What counts as progress varies by team and sometimes by leader within the same team.
- Duplicate quarterly reviews. Each cycle, the same data gets reformatted four different ways by four different teams. The leadership team spends a full week reconciling.
None of this is malicious. Each piece is a sensible response from a department head trying to deliver. The chaos is structural, not individual. And the longer it runs, the more invisible it becomes – because each team’s system feels normal to the team that built it. Eventually, when this goes on long enough, each department’s individually built systems become their solidified process and they become attached to it. No one team wants to have to give up their system. Change becomes more and more difficult and costly until you even question if it’s worth it. But the real question is, what is the recurring cost quarter after quarter if we DON’T fix it? That cost compounds.
What a Missing Strategy Execution System Is Costing You
This isn’t a soft-cost problem. The numbers add up fast.
Duplicate process-building. Each team spends 5 to 15 hours per quarter setting up and/or maintaining its own tracker. Across six departments at an enterprise scale, that’s 30 to 90 hours of process work per quarter that produces nothing the customer pays for. In addition, the leadership team or department heads then need additional time each and every quarter bringing their data into a format that can be shared, analyzed across departments, and more. This double-handling of the data adds unnecessary admin time. Multiply by your team’s loaded hourly rate. The number is uncomfortable.
Cross-team opacity. Marketing’s lead-gen target depends on Product’s launch. Sales’ pipeline target depends on Marketing’s lead-gen. When each team tracks separately, dependencies surface as crises in week ten instead of agreements in week one. The cost of a crisis is multiples of the cost of an agreement.
Slower decisions. When the executive team can’t see weekly progress in a shared format, decisions wait for quarterly reviews. Quarterly reviews are too late to course-correct. The strategic plan stays “on track” by definition until it isn’t, and by then the quarter is over. This is the difference between actual OKR progress tracking and quarterly reporting.
Retention drag. Department heads who have to build and defend bespoke systems leave. They get tired of explaining their format to everyone above them. According to Bain’s Founder’s Mentality work, profit per employee is one of the most honest measures of company health. A fragmented execution layer drags directly on it.
McKinsey’s research on why transformations fail lands on the same point in different language. The technical work of writing a plan is the easy part. The organizational work of getting the company to actually run on the plan is where most transformations break.
What Does a Working Strategy Execution System Look Like?
A working strategy execution system is not complicated. It has four properties.
One format. Every team writes their team-level objectives and key results in the same structure. Same template, same fields, same scoring scale. This makes cross-team progress comparable without translation.
One cadence. Every team checks in on their objectives at the same frequency. Weekly is the cadence that works. Monthly is too slow. Quarterly is reporting, not execution.
One source of truth. All objectives, all check-ins, all scores live in one place. Not three. One. Anyone on the executive team can open it and see the company’s strategic execution in real time.
Co-developed ownership. Team objectives are drafted by the department heads who will deliver them, within the boundaries of the strategic pillar. Department heads and their teams have ground-truth context about the problems, weaknesses, strengths, and specific dynamics inside their team that the executive team writing on a whiteboard does not have. Co-development brings that context into the objective itself. Without it, the team feels their objectives are out of touch with reality and ownership erodes before the cycle starts. With it, the people who own the work own the objective.
OKRs run on this kind of operating system are what we mean by a working strategy execution system. Not OKRs in a spreadsheet. OKRs in a shared platform where the format, cadence, and visibility are designed in. This is also the structural fix that turns an execution culture into something more than a reporting culture.
Why Now: The Cost of Waiting
The fragmentation tax compounds. Every quarter your teams continue building their own systems is a quarter of inertia you have to overcome later. Each department head builds a process they’re emotionally invested in. Each one will have to give up something familiar to adopt a shared system.
The longer you wait, the higher the change cost. The earlier you install a shared strategy execution system, the cheaper the install. This isn’t dramatic. It’s just math.
The other reason to act now: the visibility you gain in week two of the new system is what saves Q3 from quietly slipping. Bad news in week two costs the executive team a fast adjustment. Bad news at the quarterly review costs you the quarter.
Strategy Execution System: Frequently Asked Questions
What’s the difference between a strategy execution system and project management?
A strategy execution system measures whether your strategic objectives are being met. Project management measures whether specific projects are getting delivered. They’re different layers. You can complete every project on the roadmap and still miss the strategic objective if the projects were the wrong ones. A strategy execution system asks “are we moving the strategic dial?” Project management asks “are we shipping what we said we’d ship?” Both matter, but they’re not interchangeable.
Can a strategy execution system work without OKRs?
In theory, yes. Some companies use other formats: V2MOM, Hoshin Kanri, strategic OKR variants. In practice, OKRs are the most widely-adopted format for a strategy execution system because they decouple destination (the qualitative objective) from progress measurement (the quantitative key results). What matters more than the format is whether the four properties are in place: one format, one cadence, one source of truth, co-developed ownership.
How do you get department heads to give up their existing systems?
Two things help. First, co-development. If department heads draft their own team objectives within the new system, they don’t experience it as “leadership taking away my tool.” They experience it as “I’m building my objectives in the same place everyone else is.” Second, visible executive use. When the CEO and COO actually open the shared system in real time during executive meetings, the system becomes obviously load-bearing. People defend tools their leadership actually uses.
How long does it take to install a strategy execution system across an enterprise?
A first cycle of 60 to 90 days is enough to prove out the format and cadence. By cycle two, the cadence is institutional and people stop asking “why are we doing this?” By cycle three, the bespoke trackers people built before start quietly disappearing because no one’s looking at them anymore. The enterprises I work with often underestimate how much of the first cycle is adoption work, not setup work. The setup is the easy part. Getting two hundred people to actually use the system weekly is the work.
You don’t need a transformation initiative. You need a shared strategy execution system. The strategic plan you wrote is fine. The piece below it is what’s costing you the quarter.
That’s what OKR Leader is built for.
