The Invisible Cost of Strategic Drift

Six months into a major platform migration, a CTO we work with ran an exercise she’d been putting off. She pulled her strategic roadmap , the one the board had approved , and mapped every active workstream against it. The result was sobering: roughly 40% of engineering effort had no clear connection to any strategic objective. Not hostile work, not waste in the traditional sense. Just drift.

The teams were busy. Sprints were full. Velocity was healthy. But the organisation had quietly wandered off course, one reasonable-sounding decision at a time.

This is strategic drift. And it is far more common , and far more expensive , than most leadership teams realise.

What Strategic Drift Actually Is

Strategic drift is the gradual, often imperceptible divergence between what an organisation says it is doing and what it is actually doing. It is not a crisis. It is not a failure of competence. It is the natural entropy that occurs when strategy lives in one place and execution lives in another.

Every organisation experiences some degree of drift. The question is whether you can detect it early enough to correct course, or whether you discover it six months later in a boardroom post-mortem.

The term was originally coined in academic strategy literature to describe how organisations slowly move away from their environment. But in practice, the more immediate problem is internal: the gap between strategic intent and operational reality.

Drift does not announce itself. There is no alert in your project management tool. No one sends a Slack message saying “we have drifted 15 degrees off strategy.” It accumulates in the spaces between meetings, in the small scope changes that seem perfectly reasonable in isolation, in the new priorities that emerge from customer escalations and technical debt.

Five Signs Your Organisation Has Drifted

1. Your roadmap and your backlog tell different stories

Pull up your strategic roadmap. Now pull up your sprint backlogs across all teams. If you cannot draw a clear line from the majority of active work items to a strategic objective, you have drift. This is not about perfect traceability , some operational work will always exist. But if the ratio of strategic to non-strategic work surprises you, that is a signal.

2. Teams can describe what they are building but not why it matters strategically

Ask any team lead: “Which strategic objective does your current sprint advance?” If the answer requires more than ten seconds of thought, or if it sounds like a post-hoc rationalisation rather than a driving motivation, the connection between strategy and execution has weakened.

3. New initiatives appear without retiring old ones

One of the most reliable drift generators is the “additive” culture , where new priorities are layered on top of existing commitments without ever removing anything. If your portfolio of active work has grown steadily over the past year without corresponding growth in capacity, drift is almost guaranteed. Something is being deprioritised implicitly rather than explicitly, and it is probably not the right thing.

4. Status reports focus on activity rather than alignment

Review your last board report or executive summary. Does it describe what was delivered, or does it describe progress against strategic objectives? Activity reporting , “we shipped 47 features this quarter” , tells you nothing about alignment. It is the organisational equivalent of measuring distance travelled without checking the compass.

5. Strategic reviews produce surprise rather than confirmation

If your quarterly strategic review regularly surfaces work that leadership did not know about, or reveals that expected progress has not materialised despite healthy velocity metrics, your feedback loop is broken. Strategic reviews should largely confirm what you already know from ongoing measurement. Surprise is a symptom of drift.

Why Jira, OKRs, and Your PMO Do Not Catch It

This is where most organisations get stuck. They have tools. They have processes. They have an entire Programme Management Office. And yet drift persists. Why?

Jira tracks tasks, not alignment

Jira is an excellent tool for managing work in progress. It was never designed to answer the question “is this work strategically aligned?” You can add labels, custom fields, and epic hierarchies to create a loose connection between tickets and objectives. But this requires manual discipline that degrades over time, and it provides no mechanism for measuring the strength or accuracy of those connections.

A Jira board with every ticket marked “strategic” is no more useful than one with no strategic labels at all. The tool measures flow, not direction.

OKRs track targets, not execution reality

OKR frameworks are valuable for setting direction. But they operate at a level of abstraction that makes them poor drift detectors. A key result that says “Increase platform reliability to 99.9%” does not tell you whether the work being done to achieve it is the right work, whether the effort is proportionate, or whether other work is quietly displacing it.

OKRs also suffer from a refresh problem. They are typically set quarterly and reviewed quarterly. Drift happens weekly. By the time your OKR review reveals a problem, you have lost months of execution time.

PMOs track governance, not ground truth

Programme Management Offices excel at process compliance, risk registers, and dependency management. They are less effective at answering the question “is what we are actually doing aligned with what we said we would do?” PMO reporting tends to reflect what teams report upward, which is itself filtered through optimism bias, political dynamics, and the natural human tendency to present work in the best possible light.

None of these tools are bad. They simply were not designed to solve the alignment problem. Asking Jira to detect strategic drift is like asking a speedometer to tell you if you are driving in the right direction.

The Cost Nobody Calculates

Strategic drift is expensive, but the cost is almost never quantified because it manifests as opportunity cost rather than direct loss.

Consider an engineering organisation of 200 people with an average fully-loaded cost of £120,000 per engineer per year. If 30% of effort is misaligned , not wasted, just directed at things that do not advance the strategy , that represents £7.2 million per year of misdirected investment. Not money lost to incompetence, but money spent building the wrong things well.

Now multiply that by the compounding effect. Misaligned work does not just consume resources today; it creates maintenance obligations, technical dependencies, and organisational expectations that consume resources tomorrow. A feature built outside the strategic direction still needs to be supported, documented, and eventually either maintained or deprecated.

The true cost of drift is not the labour spent building the wrong things. It is the labour spent building the wrong things, plus the labour spent maintaining the wrong things, plus the opportunity cost of the right things that were never built.

What Evidence-Based Alignment Actually Looks Like

Detecting and correcting drift requires a fundamentally different approach from what most organisations currently use. It requires continuous, evidence-based measurement of the relationship between strategic intent and operational execution.

This means several things in practice:

Automated connection, not manual tagging. The link between work items and strategic objectives should be established and maintained programmatically, not through manual labels that degrade over time. When an engineer creates a ticket, its strategic relevance should be inferred from its content, its position in the hierarchy, and its relationship to other work , not from whether someone remembered to add the right tag.

Confidence-weighted measurement, not binary status. Alignment is not a yes/no question. It is a spectrum, and it should be measured with appropriate uncertainty. A work item might be “probably aligned” or “weakly aligned” or “aligned to an objective that has itself drifted.” Good alignment measurement acknowledges this uncertainty rather than collapsing it into a green/amber/red traffic light.

Continuous monitoring, not periodic review. Drift happens between reviews. If you only measure alignment quarterly, you are guaranteed to discover problems too late. Alignment should be measured continuously, with anomalies surfaced as they emerge rather than accumulated for a quarterly post-mortem.

Cross-tool visibility, not single-tool dependence. Strategy lives in documents and presentations. Execution lives in Jira, Azure DevOps, GitHub, and a dozen other tools. Alignment measurement must span these boundaries, comparing intent (as expressed in strategy documents) with reality (as expressed in execution tools) without requiring teams to change their workflows.

Evidence, not narrative. The answer to “are we on track?” should be grounded in data, not in the most persuasive storyteller’s account of progress. This does not mean eliminating qualitative judgement , context always matters. But it means starting with evidence and adding interpretation, rather than starting with interpretation and looking for supporting evidence.

The Shift That Matters

The organisations that manage drift effectively share one characteristic: they treat alignment as a measurable property of their execution system, not as an aspirational quality of their culture.

They do not assume alignment because their planning process was good. They verify alignment because they know entropy is constant. They do not wait for quarterly reviews to discover problems. They instrument their execution environment to surface drift as it occurs.

This is not about buying a tool or hiring a consultant. It is about accepting that the gap between strategy and execution is a permanent, structural challenge that requires permanent, structural measurement.

The CTO who discovered her 40% misalignment did not have a bad team or a bad strategy. She had a normal organisation operating without the instrumentation to detect a normal problem. Once she could see the drift, correcting it was straightforward.

The invisible cost of strategic drift is not that it is unsolvable. It is that it is undetected. And the first step to solving any problem is making it visible.

---

BAS TrustDesk helps organisations measure the alignment between strategic intent and operational execution. If you are curious about what your alignment data actually says, we should talk.