Delivering Business Solutions
Why good decisions weaken after approval as ownership, authority and dependencies come under pressure.
A good organisational decision can remain formally approved while losing practical force. As ownership, authority, incentives and dependencies pull in different directions, executive intent separates from operational behaviour. This matters because Decision Drift consumes capacity in clarification, escalation and rework long before delivery plans show that the original decision is no longer governing execution.
Are decisions repeatedly losing force in your programme?
Within the wider Organisational Decision Dynamics territory, this article examines the specific journey from approval to dependable organisational behaviour. The cornerstone context is set out in Organisational Decision Dynamics.
Most organisations assume the difficult part of decision-making is reaching agreement. Executive meetings, steering committees and governance forums exist to evaluate options, reconcile competing views and establish a clear direction. Once consensus has been reached and recorded, there is an understandable assumption that the hard work is over.
In reality, that moment marks the start of a decision’s journey rather than its conclusion.
Approval creates intent, but intent alone does not change organisational behaviour.
From that point onwards, the decision has to survive contact with the organisation that is expected to deliver it. Every function, team and individual must interpret what has changed, understand what has not, and adjust their own priorities accordingly. Funding has to align with the new direction. Capacity has to be available. Dependencies need to become explicit rather than assumed. Technology, operations and commercial teams all have to reinforce the same outcome instead of quietly preserving the old one.
None of these changes happens automatically; they depend on the organisation reinforcing the decision through everyday behaviour.
This distinction matters because organisations frequently confuse a declared decision with a governing decision.
A declared decision is documented in meeting minutes, governance papers and executive communications. It confirms that agreement has been reached.
A governing decision is something more enduring. It continues to influence behaviour when priorities compete, budgets tighten and difficult trade-offs become unavoidable. Its strength is tested not when everyone agrees, but when something else demands attention.
That test usually arrives much sooner than many organisations expect.
Perhaps two strategic initiatives suddenly require the same specialist resource. Funding becomes constrained. Delivery milestones begin to overlap. Operational stability competes with strategic change. In those moments, one question matters more than any other:
The more revealing question is which decision ultimately survives.
Many organisations eventually discover they have accumulated far more declared decisions than decisions that genuinely govern behaviour.
The consequences rarely appear immediately. Strategy still looks coherent. Governance papers continue to reflect the intended direction. Programme plans remain broadly aligned with executive intent. Only gradually does operational reality begin to diverge.
The weakening rarely begins with a dramatic failure. More often it emerges through a sequence of entirely reasonable decisions.
An assumption remains unspoken because everyone believes it is shared. A dependent team agrees in principle but never incorporates the work into its own commitments. A programme owner is made accountable for an outcome without having the authority needed to protect it. A temporary workaround is accepted to preserve an important milestone. A commercial opportunity reshapes priorities without anyone explicitly considering what must now give way.
Viewed individually, none of these decisions appears especially significant.
Taken together, however, they begin to separate executive intent from operational behaviour.
The same pattern often emerges in resource planning. A transformation is declared the organisation’s highest priority, yet existing commitments remain untouched. Capacity is expected to absorb both because making an explicit trade-off feels more difficult than maintaining the appearance that everything remains achievable.
Performance measures can reinforce exactly the same behaviour. A leader may be expected to support an enterprise-wide transformation while continuing to be measured primarily on protecting local revenue, departmental costs or service performance. Formally, the organisation has chosen one direction. In practice, it continues rewarding another. Behaviour that appears resistant is often entirely consistent with the incentives that never changed.
The organisation has not consciously rejected its original decision.
Instead, different parts of the business gradually begin working to slightly different interpretations of what was originally agreed.
Ibcrus describes this gradual separation between intent and execution as Decision Drift.
Decision Drift rarely begins with disagreement. Most people continue acting professionally and making rational choices based on the information available to them. Operations protects service continuity. Technology protects architectural integrity. Finance controls expenditure. Commercial teams focus on customer commitments. Programme teams protect delivery dates.
From the perspective of each function, these behaviours remain entirely rational.
The difficulty is that those responsibilities are no longer being shaped by one consistently understood decision.
Different parts of the organisation begin working from subtly different interpretations of what the original decision now requires. The effect is rarely dramatic, but it is commercially significant. Increasing effort is spent maintaining alignment rather than creating progress. Clarification meetings become more frequent, governance revisits issues that were thought to be settled, dependencies require repeated negotiation and delivery absorbs growing amounts of coordination.
Work continues across the organisation, but progress gradually loses its ability to compound.
Traditional governance assumes organisational success depends primarily on making good decisions. There is truth in that, of course. Poor decisions can be expensive, and weak judgement at senior level rarely improves through execution.
Yet many organisations still struggle despite making sensible strategic choices and investing considerable effort in delivering them.
The underlying weakness often lies elsewhere, because good decisions create value only when they continue shaping behaviour throughout delivery.
That demands more than executive agreement. It requires clear ownership, recognised authority, explicit dependencies and operating practices that reinforce, rather than undermine, the original intent. It also requires incentives that continue rewarding the behaviours the decision was designed to create.
Without those conditions, organisations rarely abandon the original strategy in any obvious sense.
Instead, they adapt incrementally, often without recognising that those adaptations are gradually reshaping the decision itself.
One exception leads to another. Temporary workarounds remain in place long after the original pressure has passed. Local adjustments become accepted practice, gradually reshaping the operating model without anyone deliberately choosing a different direction.
By the time leaders recognise what has happened, the organisation may still be reporting against the original strategy while behaving according to something quite different.
This explains why well-considered decisions can still produce disappointing outcomes. The strategy itself may have been sound. The business case may remain valid. Executive debate may have been thorough and disciplined.
The real difficulty is that the organisation failed to preserve the decision once execution was underway.
For that reason, the quality of a decision cannot be judged solely by the meeting that produced it. Its real strength becomes visible much later.
A useful indicator is whether people across the organisation can still explain what the decision requires, whether neighbouring teams continue making compatible choices without continual intervention, whether ownership remains clear as work progresses, whether performance measures continue reinforcing the intended direction, and whether leaders can distinguish between a deliberate strategic change and a gradual adaptation that nobody explicitly approved. Taken together, these indicators reveal whether an organisation possesses durable decision capability or simply an effective process for reaching agreement.
The distinction becomes more important as organisations grow.
Every new function, supplier, technology platform, governance layer or acquisition introduces another point through which executive intent must pass. Each additional boundary creates opportunities for different interpretations, competing priorities and local optimisation. None of these is inherently problematic, but together they increase the likelihood that decisions will gradually weaken as they move through the organisation.
Where those pathways remain strong, value compounds naturally. Teams make compatible decisions without continual reassurance, governance spends less time reconnecting fragmented work and more time discussing genuinely strategic issues, and progress builds on itself because the organisation continues moving in one direction.
Where those pathways weaken, something different begins to emerge.
The executive view of the organisation remains coherent. Delivery plans appear reasonable. Operational teams continue protecting services, commercial teams continue protecting customers and technology teams continue protecting architecture. Each perspective makes sense in isolation, yet they no longer describe quite the same organisation.
The earliest signs rarely appear in financial results; they tend to emerge first in the effort required to keep the organisation aligned.
Clarification becomes routine. Dependencies become increasingly difficult to manage. Decisions require repeated escalation. Coordination grows, reporting expands and executive intervention becomes more frequent. The organisation remains busy, but confidence in future commitments begins to decline.
Many experienced leaders recognise this pattern long before they can clearly explain what is causing it.
Work remains visible everywhere, meetings stay full and plans continue to move forward, yet every significant commitment seems to require more reassurance than the last.
The organisation has not lost its ability to make decisions;
it has begun losing its ability to preserve them.
Decision rights are often documented as if authority were a static property. A committee approves investments above a threshold. A product owner controls scope. A functional leader owns resources. A sponsor accepts programme risk. The arrangement may be perfectly clear on paper and still fail when the organisation encounters a choice that crosses several of those boundaries at once.
The practical strength of a decision right lies in whether it can be exercised without requiring the organisation to reconstruct authority around each difficult issue. A leader may technically own the decision but lack access to the information needed to make it. They may control the budget but not the people. They may be accountable for the outcome while another function can withhold approval without accepting the consequence. The right exists, but it is not usable.
Pressure exposes these gaps. When a date, customer, regulatory obligation or cost target cannot all be protected, several legitimate authorities collide. If the organisation has not established which outcome governs the trade-off, the decision moves upward or outward. More stakeholders are added, more evidence is requested and the issue waits for a person with enough positional authority to absorb the conflict.
Repeated escalation is therefore not always evidence that senior control is working. It may show that lower-level decision rights were designed for ordinary activity but not for the moments that determine delivery. The organisation has delegated tasks while retaining consequential choice.
Usable decision rights contain three elements. The boundary of authority is understood. The evidence required to act is available. The consequence of acting is accepted by the wider system. Remove any one of these and apparent delegation becomes conditional. People may still act, but they do so cautiously because they cannot be sure the organisation will hold the decision when results, costs or objections become visible.
The commercial effect appears as latency and defensive coordination. Choices take longer than their analytical complexity justifies. Papers become larger because the author is trying to secure protection as well as approval. Teams seek unanimous agreement where a clear owner should be sufficient. Opportunities narrow while the organisation establishes who is permitted to accept the downside.
Clear decision rights do not mean that one person acts without challenge. Challenge improves judgement when it tests evidence and consequence. It weakens execution when challenge becomes an unbounded route for reopening settled choices. Healthy dynamics distinguish between new information that justifies revision and continuing discomfort with a trade-off already accepted.
This is why the quality of decision rights can be seen in what happens after disagreement. Does the organisation leave with one operative answer, named assumptions and an owner capable of carrying the consequence? Or does each participant return to their area with a different interpretation of what was agreed? The meeting may have ended in both cases. Only one has produced a decision the organisation can use.
Dependencies are often presented as items on a plan: a system must be ready, a contract must be signed, a policy must be approved or a team must release capacity. This representation is useful but incomplete. A dependency is a promise between owners. One part of the organisation is relying on another to make or sustain a decision at the time and quality required.
That promise contains more than a date. It contains assumptions about scope, priority, authority, acceptance criteria and consequence. A technology team may agree to provide an interface by September, while the business assumes the interface includes data quality remediation and the technology team assumes it does not. Both can report the dependency as understood. The disagreement only becomes visible when the promised output can no longer support the intended outcome.
At portfolio level, these promises compete. Several programmes may rely on the same architecture team, operational experts, release window or executive decision. Each plan can be internally credible while the combined set is impossible. The failure is not within any one schedule. It lies in the organisation’s inability to make the cross-portfolio decision about which promise will govern when shared capacity cannot satisfy them all.
Dependencies also have direction. Some are requests made by a programme to the organisation; others are commitments the organisation has already embedded in the programme without recognising them as such. A regulatory interpretation, a procurement lead time, a data ownership choice or a business-readiness assumption may sit outside the formal plan while determining whether the plan is possible. What is omitted from the dependency map can be more consequential than what is recorded on it.
Healthy handshakes make the promise explicit. The receiving owner knows what will be provided, when, on what assumptions and what happens if those assumptions change. The providing owner understands the commercial consequence of failure, not merely the task. Each side knows who can renegotiate the commitment and how the wider plan will be adjusted.
Weak handshakes create Dependency Accumulation. Individual dependencies may appear manageable, but their uncertainty compounds. A decision delayed in one area narrows the options available elsewhere. A workaround introduced to protect one milestone creates operational support elsewhere. A late commercial choice compresses testing, training or customer preparation. The organisation continues to carry each dependency as a separate line item even though they are interacting as a system.
This interaction explains why programmes can appear broadly on plan until they deteriorate quickly. The late stage does not necessarily introduce the problem; it removes the remaining room to absorb it. Decisions that were previously independent become coupled by time. Several manageable uncertainties become one unmanageable sequence.
The commercial cost is not limited to the final delay. Capacity is reserved and released repeatedly. Suppliers are extended. Interim processes remain in place. Revenue moves while fixed cost continues. Teams spend time managing interfaces that should have been stable. The closer the organisation gets to a fixed event, the more expensive each unresolved handshake becomes.
For leaders, the practical implication is to look beyond the number of dependencies and examine their decision quality. A long list of explicit, owned promises may be safer than a short list of vague ones. The important question is whether the organisation knows which commitments can still move, which cannot and who is authorised to accept the consequence.
Ownership is one of the most frequently used and least consistently defined words in delivery. A person may own a workstream, a risk, an action, a budget or an outcome. Those labels can create the appearance of accountability while leaving the decisive authority elsewhere.
Real ownership is revealed when conditions change. Can the owner make the trade-off required to preserve the outcome? Can they secure the capacity on which the commitment depends? Can they refuse an incompatible priority? Can they accept a consequence on behalf of the part of the business they represent? If not, they may be coordinating the work rather than owning the decision.
The most consequential ownership gaps therefore occur at transitions. Who owns the decision after the programme closes? Who accepts the residual workaround? Who decides whether an expected benefit is still achievable after scope changes? When these questions remain open, the organisation can complete delivery administratively while leaving the commercial outcome effectively unowned.
Ownership also has a time dimension. The person authorised to approve an initiative may not be the person who must live with its operational consequences. The programme sponsor may move on before benefits are realised. A founder may delegate delivery while retaining customer or financial risk. Unless ownership transfers explicitly as the decision moves from design to implementation and then into operation, accountability can disappear precisely when the commitment becomes hardest to reverse.
This distinction matters because coordination can be highly active and still leave decisions unresolved. The coordinator brings people together, tracks actions and escalates concerns. Everyone participates, but no one carries the full consequence of saying yes, no or not yet. Shared ownership then becomes a polite description for distributed veto.
In large organisations, the problem often appears across functional boundaries. A programme owns the delivery date, but technology owns release approval, operations owns service acceptance, finance owns funding and the business owns benefit realisation. None of this is inherently wrong. The weakness appears when no one owns the handshake between those decisions or the trade-off when they cannot all be satisfied.
In a smaller business, the same dynamic may sit around the founder. Managers are encouraged to take ownership but know that significant choices may be reversed. The founder expects initiative while continuing to act as the final source of reassurance. Decisions move quickly when the founder is available and stall when they are not. What once felt like control becomes a capacity constraint.
The commercial implication is that ambiguous ownership creates hidden waiting. People delay action because they are unsure whether their authority will be supported. They seek additional agreement to protect themselves. Decisions are framed as recommendations rather than commitments. The organisation sees cautious behaviour or lack of pace, but the behaviour may be a rational response to decision rights that do not hold.
Organisational Decision Dynamics therefore treats ownership as a relationship between authority and consequence. The owner is not simply the person named against the item. The owner is the person expected and enabled to preserve the decision when pressure makes preservation costly.
Organisations rarely lose momentum because people stop making decisions. More often, decisions continue while their authority weakens across ownership boundaries, dependencies and competing priorities. The commercial effect appears as latency, rework and coordination long before a plan formally fails.
The decisive test is not whether a decision was approved. It is whether the organisation can continue acting on it when pressure makes another answer more convenient.
Where weakening decisions begin to drive more reporting and executive intervention, the next useful specialist route is Why Governance Creates Visibility Without Control.
If approved decisions are repeatedly returning, or ordinary commitments depend on senior intervention to hold, Decision & Governance Clarity sets out the relevant programme context.
Are decisions repeatedly losing force in your programme?
Yes. A decision can remain in minutes, plans and executive communications while losing its ability to govern behaviour. This is Decision Drift: the organisation continues to acknowledge the decision, but later trade-offs, exceptions and local choices progressively weaken its practical effect.
Approved decisions often return when the organisation has not preserved the conditions needed to apply them. Unclear decision rights, unresolved dependencies, competing incentives or weak ownership make ordinary execution dependent on renewed interpretation. Governance then becomes the place where the decision is repeatedly reconstructed rather than simply monitored.
Nominal accountability identifies a person against an action or outcome. Decision ownership also requires usable authority, access to the relevant dependencies and responsibility for the consequences when conditions change. A named owner who cannot resolve trade-offs or secure commitments may carry accountability without being able to preserve the decision.
A decision should change when evidence or conditions justify a conscious revision of intent. Healthy decision preservation is not rigidity: it makes the reason for change explicit and maintains continuity between the original decision, the new evidence and the revised choice. Decision Drift is different because the outcome changes gradually without a clear organisational decision to change it.
Shows how apparently settled choices return when delivery has stopped stabilising around them.
Shows how ownership ambiguity becomes operational delay.
Connects decision weakness to cost displaced into rework, delay and management effort.
Extends Decision Drift into changing assumptions and outdated conditions.