A decision can still be in force long after the conditions that made it sensible have changed.
The work carries on. People continue to organise around it. Dates, dependencies and commitments still assume it holds. Yet more time and management attention are being spent making that decision fit the situation as it now exists.
Nothing has necessarily failed. Something has simply stopped fitting.
A supplier can no longer meet the original timetable. A dependency has moved. Available capacity is lower than expected. A commercial assumption has changed. Another programme has altered the sequence. What was affordable six months ago may now be harder to justify.
The original decision may have been perfectly reasonable. The difficulty comes when delivery continues to be shaped by it after the circumstances around it have moved.
The decision can still look settled
Once a decision has been made, it becomes part of the landscape.
Plans incorporate it, dates depend on it and budgets reflect it. Teams organise around it. Other decisions are then made on top of it.
That makes an old decision surprisingly difficult to see.
Nobody necessarily says, “We need to reconsider this.” Instead, a question that seemed settled comes back into a meeting. A dependency needs another conversation. A commitment acquires a qualification. A team waits before acting because it is no longer certain the original direction will hold.
Formally, the decision is still there. In practice, people have started treating it differently.
This is where decision drift becomes visible.
What this usually looks like in practice
The clearest signal is often not simply that decisions are taking too long in projects. It is that apparently settled decisions keep returning.
The same point is discussed again because something around it has changed. Work continues in the meantime, but commitments become more cautious. Teams hold options open or create contingencies around something that was previously considered fixed.
The effects tend to appear elsewhere first.
A decision is revisited and another part of the plan needs adjusting. A dependency is reopened because the dates no longer align. Delivery waits for confirmation that everybody thought had already been given.
The decision path becomes less stable even though the formal position has not changed. Across a large programme, that behaviour can be spread across several teams before anybody sees it as one underlying condition.
The work starts compensating for the decision
Delivery rarely stops simply because the basis of a decision has weakened. People compensate.
They find another route, sequence work differently, hold additional conversations or keep two options alive. Checks, caveats and temporary arrangements appear so that progress can continue.
Each response can be perfectly sensible on its own. Together, they absorb capacity.
An apparently intact decision can therefore consume increasing time and effort without producing an equivalent amount of progress. The decision has not formally failed; more work is simply required to keep it functioning.
That distinction matters because the additional effort can easily be mistaken for ordinary delivery complexity.
The team is busy. Work is moving. Nothing has reached the point of obvious failure. Yet some of that activity now exists only because the conditions supporting the original decision no longer do.
The commercial effect starts before anyone reopens the decision
The first visible cost is often time.
Questions take longer to settle. Work waits. Commitments remain provisional. More people become involved because confidence in the original position has weakened.
Then the cost spreads.
Rework appears when something built around the earlier assumption has to change. Management attention shifts towards resolving issues that were thought to be closed. Capacity is tied up maintaining alternatives rather than progressing the chosen route.
None of this needs to appear as a discrete budget problem. The cost can sit inside the work, alongside the delay.
As more delivery decisions are made around the existing position, commitments also become harder to reverse.
Left unchecked, this usually becomes more embedded before it becomes easier to see.
Decisions can keep moving without landing
There is a useful distinction between a decision being made and that decision continuing to stabilise delivery.
The first can be recorded in minutes, governance logs or plans. The second shows up in behaviour.
People act without repeatedly reopening the point. Dependencies settle around it. Commitments hold. Delivery can accumulate rather than continually preserving optionality.
When that stops happening, decisions keep moving but do not land.
That does not automatically mean the original decision was poor. It means the organisation is now spending effort around a decision whose relationship with current conditions has weakened.
This is also where the effect can begin to show up in delivery confidence. Formal reporting may remain broadly intact while the people closest to the work become less certain that commitments will hold without further adjustment.
Visible failure has not arrived, but the cost of carrying the position already has.
The decision may not be the thing people are questioning
By this point, the conversations often remain focused on delivery.
Why has this dependency moved again? Why is the team waiting? Why has the same decision returned? Why is a commitment that looked settled suddenly conditional?
Those are the visible symptoms. Less obvious is how much of the organisation is still operating around conditions that have already changed.
That is why the pattern can persist. The decision itself still looks familiar while the friction appears somewhere else.
The longer the organisation compensates for that difference, the easier it becomes to treat the additional work, delay and uncertainty as normal.
The useful pressure point is therefore not whether an earlier decision can now be judged right or wrong. It is whether the conditions that made it sensible still exist.
Which decisions are still shaping delivery because nobody has explicitly checked whether the conditions beneath them still exist?
For the wider relationship between decision behaviour, governance and delivery stability, see Decision and Governance Clarity.
Related Observations
When decisions stop settling the work around them
Repeated revisiting can become an operational condition in its own right, even while formal decisions continue to be recorded.
When confidence changes before delivery visibly fails
People closest to the work can start qualifying commitments well before formal reporting shows a material problem.
When added coordination does not create greater stability
Increasing oversight can coexist with less certainty about whether decisions and commitments will hold.