When a company changes strategic direction, the goals get updated in a session that takes an afternoon. The work underneath them keeps running for months. Nobody issues a stop order, because at task level the connection back to the strategy was never maintained, so there is no channel the signal could travel down.
The result is real hours, spent competently, aimed at an objective the company already walked away from.
How it happens without anyone being careless
In Q1 leadership picks a direction: move up into the mid-market. It becomes an objective with a revenue target and a product-readiness milestone. Teams open projects, cut them into epics, and start shipping.
In Q2 a competitor lands a strong enterprise product and leadership swings round to defending the enterprise base. The mid-market objective is archived quietly, or its targets are softened. That conversation happens in a leadership session and a follow-up thread. It is a good decision, made quickly, which is what you want.
Underneath, engineering has three sprints of mid-market features queued. Marketing has a campaign in production. Sales enablement is halfway through a new deck. None of those people were in the session. Their backlog does not know a goal changed, and the objective it was created for does not appear anywhere in the tickets. So the work proceeds, and it proceeds well: tasks close, sprints end, status stays green.
This is the silent pivot, and it compounds. A team still serving the old priority is a team not yet serving the new one, so the cost is paid twice.
Why tagging initiatives to priorities does not fix it
The common remedy is an annual exercise where every initiative gets tagged to a strategic priority. It is better than nothing and it fails for two reasons.
The tag is set once, at creation, and never revisited. When the priority changes, nobody walks the tags backwards. The initiative keeps its label and the label keeps it looking aligned.
And the tag asks the wrong question. It asks which priority this initiative relates to, not whether this initiative is the best available way to move that priority, or whether it should be worked at all. Almost any project can be related to almost any strategic priority with a sentence of effort, which is how a portfolio ends up fully tagged and still misaligned. The initiative slide deck usually documents this state rather than correcting it.
What it looks like when you go looking
One of our customers found roughly a fifth of one region's active pipeline work still pointed at SMB accounts, a segment leadership had deprioritised the previous quarter in favour of a mid-market push in DACH. The reporting showed a healthy pipeline, because the deals were open and moving. Nobody had told the reps to stop. Their pipeline was healthy in the wrong direction.
That shape repeats across functions. Engineering capacity on a platform investment whose business case expired. A content programme aimed at a persona the company stopped selling to. A hiring plan built for the previous quarter's model. In each case the work is being done properly, which is precisely why nothing raises a flag.
Finding it without another survey
Asking teams whether their work is still aligned produces optimistic answers, because everyone can construct a rationale for what they are already doing. The findable version is a data question, and it needs the goal layer joined to the work layer at task level.
Three checks surface most of it:
Goals that changed, work that did not. For every objective whose target, scope, or status changed in the last two quarters, list the work still connected to the prior version. Anything with activity in the last three weeks is a live decision waiting to be made.
Work with no current goal. Active tasks and projects that cannot be traced to any objective the company is pursuing this quarter. Some of it is legitimate keep-the-lights-on work, which is worth naming as such. The rest is a choice nobody made.
Effort distribution against stated priority. Where hours actually landed by objective, compared to what the strategy says the ranking is. The mismatch is usually larger than anyone expects, because nobody adds up where the time went.
None of the three needs a status update from anyone. They need the connection between effort and goal to exist as data, which is the whole subject of why companies still struggle to turn strategy into results.
Making the stop order routine
The fix is procedural once the data is there. When a goal is archived, softened, or re-scoped, the work connected to it gets reviewed in the same week rather than discovered in the next quarterly review. Each connected item gets one of three outcomes: reassign it to a current goal, finish it because stopping costs more than completing, or stop it.
Most organisations already have the meeting where this could happen. What they lack is the list, and the list can only be generated by a system that kept the connection between the goal and the work alive after the offsite ended.