Drift by Degrees: Auditing the Small Approvals That Move a Strategy Off Route

On a glacier, the crevasse is not usually the dramatic feature. It is a narrow line in the snow, easily stepped over, invisible from twenty paces away. The danger lies in what it becomes once a few of them link up, and in the fact that each crossing felt trivial at the time.

Strategic drift behaves the same way. Very few organisations decide to abandon a plan. What happens instead is a sequence of small, defensible approvals — each one sensible in its own context, each one granted by someone with the authority to grant it — that collectively relocate the work somewhere the leadership team never agreed to go. The route has changed beneath the team, and nobody can point to the moment it did.

The mechanics of incremental consent

Scope creep is often described as a discipline problem, as though the answer were simply to say no more often. That framing misses the point. In growing UK organisations, the pressure to absorb extra work is structural, not personal.

Scale-ups typically have a strategy that is deliberately loose, because the market is still being discovered. Mid-market firms have a strategy that is deliberately broad, because they serve several customer segments and cannot afford to disappoint any of them. In both settings, the plan functions as an intention rather than a specification, and intentions are easy to reinterpret when a customer, a partner or a senior sponsor asks for something adjacent.

Add the commercial context — tight delivery windows, key accounts that carry disproportionate revenue, integration work following acquisition — and each concession starts to look like commercial maturity rather than drift. The person approving it is not being weak. They are being responsive, which is exactly what they were hired to be.

Four patterns worth recognising

The service exception. A valued client requests something outside the agreed scope. Refusing risks the relationship; agreeing costs a few days. The few days become standard, and the delivery model now includes an element that was never costed.

The helpful addition. A team building a new capability adds a reporting layer, an extra integration or a compliance check because it seems obviously useful. Each addition is small. Together they extend the timeline by a quarter and consume the contingency that was meant for the difficult part.

The absorbed acquisition. Following a purchase or merger, the integration plan quietly expands to include system consolidation, cultural work and customer migration, none of which was in the original case. The strategy is now larger than the one that was signed off, and the resources have not moved.

The migrating metric. The measures of success shift as new reporting becomes available. The team begins optimising for something measurable rather than something strategic, and the plan follows the metric rather than the other way round.

A simple audit for tracing where the plan changed

Drift is diagnosable. The exercise below can be run in a single working session by a leadership team, and it tends to produce an uncomfortable but useful map.

1. Retrieve the baseline. Find the version of the plan that was formally approved — the paper, the business case, the operating plan. Not the living document, not the latest slide. The original.

2. Assemble the decision trail. Gather the approvals granted since: steering group minutes, change requests, email sign-offs, informal agreements confirmed in a call. Most organisations find that a meaningful proportion of decisions were never minuted at all.

3. Count and categorise. Sort the changes into four buckets: additions to scope, changes to sequence, changes to resourcing, changes to the definition of success. Volume matters less than concentration — a long tail of small additions in one area usually signals a structural problem.

4. Cost them. Express each change in the currency the organisation actually feels: delivery weeks, engineering capacity, senior attention, margin. Aggregate the total. The figure is frequently larger than any single approver imagined.

5. Attribute the decisions. Identify who approved each change and what authority they were exercising. This is not an exercise in blame. It usually reveals that the governance framework permitted drift by design — thresholds set too high, delegated authority too broad, or no requirement to view a change in the context of the whole.

6. Identify the missing conversation. For each cluster of changes, ask what the leadership team would have decided had it seen them together. Very often the answer is that some would have been approved enthusiastically, and others refused outright. The absence of that collective view is the actual failure.

Decision rules that protect the route

Rigidity is not the answer, and teams that refuse every request quickly become slow and unpopular. The aim is deliberate flexibility: a route that holds its shape while retaining the capacity to adapt where adaptation genuinely pays.

Set a change budget. Agree, in advance, how much capacity — in weeks, headcount or spend — may be absorbed by unplanned work in a period. Once the budget is drawn, further requests require an explicit trade rather than an implicit one.

Make trade-offs visible. No addition without a named subtraction. If a request is accepted, something else is paused, delayed or dropped, and both halves of that equation appear in the same record.

Lower the threshold for collective review. Individual changes below a certain size can be approved locally. But require that the cumulative total in any category is reviewed monthly, so that the pattern is visible even when no single decision was large.

Separate the requester from the decider. The person closest to the customer is often the least well placed to judge strategic cost. Route significant requests to someone who can see the whole plan, and make that routing routine rather than exceptional.

Define the non-negotiables. Identify the two or three elements of the strategy that will not be traded — the capability being built, the segment being served, the margin floor. Everything else can flex. Clarity about what is fixed makes flexibility elsewhere far easier to grant.

Review the definition of success. Revisit, at fixed intervals, whether the measures still describe the original intent. If the metric has moved, ask explicitly whether that was a decision or a drift.

Holding the line without standing still

Good expedition leaders are not inflexible. They change timing, adjust loads and reroute around conditions. What they do not do is allow the objective to be revised by a series of small conveniences, each negotiated by someone who cannot see the crevasse ahead.

For leadership teams, the equivalent discipline is modest and unglamorous: keep a baseline, record the changes, look at them together, and make the trade explicit. Organisations that do this rarely become slower. They become clearer about what they are actually building — and considerably harder to move off course without anyone noticing.