Why Good Decisions Still Produce Bad Outcomes

---

Executive Summary

Post-mortems on failed transformation programs almost always look for a decision to blame. A vendor was chosen poorly. A timeline was too aggressive. A sponsor lost interest. Sometimes that story is true. More often, when you look closely, none of the individual decisions were wrong at all. Each one was well-reasoned, well-governed, and defensible on its own terms. What produced the disappointing outcome was not any single decision, but the interaction between several decisions that were never examined together — because no part of the organization was responsible for examining them together. This article looks at why that keeps happening, and why it is so much harder to see coming than a single bad call would be.

---

The audit that finds nothing wrong

When a major initiative disappoints — late, over budget, or quietly descoped until it no longer resembles what was promised — the instinct is to find out what went wrong. Usually, someone conducts a review. They pull the business case, the risk log, the steering committee minutes.

The unsettling discovery, in a large number of these reviews, is that nothing looks wrong. The business case was sound. The risks were logged and, individually, well managed. The governance process was followed. If you handed the file to an outside reviewer and asked them to find the decision that caused the failure, they would struggle, because no single decision in the file caused it.

This is a genuinely uncomfortable finding for most organizations, because it removes the easiest explanation. It is far more comfortable to conclude that someone made a mistake than to conclude that the process worked exactly as designed and still produced a bad outcome. But the second explanation is, more often than the first, the accurate one.

Three decisions, none of them wrong

Consider a pattern that recurs across industries, though the details vary: a technology modernization program is approved, on the strength of a genuinely strong business case. Some months later, a cost-reduction initiative is approved elsewhere in the organization, aimed at a completely different part of the business, sponsored by a different executive. Around the same time, a regulatory response program is greenlit, driven by an external deadline nobody controls.

Each of these three decisions, examined individually, holds up. Each was reviewed by a capable team, resourced sensibly, and justified on terms that would satisfy any competent governance committee.

A year later, all three initiatives are drawing on the same category of specialist delivery capability — the people who understand both the legacy systems and the regulatory requirements well enough to be trusted with either the modernization work or the compliance work. There were never enough of these people to do all three at once. Nobody planned for all three to need them simultaneously, because at the moment each initiative was approved, the other two either didn't yet exist or hadn't yet specified their resourcing needs precisely enough for anyone to notice the overlap.

The organization now faces an uncomfortable choice: quietly slow one initiative to protect the other two, or attempt all three and watch quality degrade across the board. Neither option was visible, or even meaningful, at the time any of the three decisions was made. The constraint didn't exist until all three existed together.

This is the pattern worth naming precisely, because it does not fit the story that governance failed. Governance worked. What was missing was any mechanism for asking whether these three good decisions, taken together, still produced a good outcome.

Why "individually rational" isn't the same as "collectively sound"

There is a reason this pattern is so persistent, and it isn't a lack of diligence. It's a structural feature of how large organizations make decisions.

**Decisions are usually evaluated one at a time, by the process best suited to evaluating one decision at a time.** A capital committee reviewing an investment proposal is, appropriately, focused on whether that proposal is sound — its costs, its risks, its expected return. It is not typically designed to ask what else is competing for the same delivery capacity that quarter, because that question requires visibility the committee usually doesn't have and wasn't set up to seek.

**The people making each decision are rarely the people who will discover the collision.** The executive sponsoring the modernization program and the executive sponsoring the compliance program may never sit in the same meeting. Each is confident their own initiative is well-planned, because it is — on its own terms. Neither has visibility into the other's resourcing assumptions, and in most organizations, no one is explicitly responsible for having that visibility across both.

**The interaction often doesn't exist yet at the moment either decision is made.** This is the least intuitive part of the pattern, and possibly the most important. When the modernization program was approved, the compliance program may not have existed. There was no interaction to evaluate, because there was nothing yet to interact with. The dependency became real only once both initiatives existed — by which point both were already funded, staffed, and underway.

**Sequence matters more than most planning processes acknowledge.** Had the compliance program been approved a quarter earlier, or had its specialist resourcing needs been identified sooner, this same set of three decisions might never have collided. The problem was not only which decisions were made. It was the order in which they were made — and order is rarely treated as something worth deliberately examining, as opposed to something that simply happens as proposals arrive.

Put together, these four conditions describe something closer to a structural blind spot than a failure of judgment. The decisions were individually rational. What was missing was any point in the process where the decisions were evaluated as a set, rather than one at a time.

Why this is worse than it sounds

It would be tempting to treat this as a minor coordination problem — something a slightly better meeting cadence or a shared calendar could fix. That undersells it, for three reasons.

**It compounds silently.** Each individual decision that contributes to the eventual collision looks completely fine at the time it's made. There is no moment where an alarm reasonably should have gone off, because no single decision, viewed alone, contains the problem. The problem exists only in the combination, which nobody was looking at.

**It is discovered late, and lateness is expensive.** By the time the resourcing collision becomes visible — often in a steering committee, sometimes not until a delivery milestone is missed — all three initiatives are already funded, staffed, and committed. The options at that point are narrow and expensive: descope, delay, or accept degraded quality. The moment when the collision could have been avoided cheaply, before any of the three initiatives fully committed resources, is long past.

**It survives good people and good process.** This is perhaps the most important point, and the one most likely to be resisted, because it implies that hiring better people or tightening governance further will not, on its own, solve it. The pattern recurs in organizations with strong talent and disciplined governance precisely because the gap is structural: no part of the standard process is designed to ask "what does this decision do to the decisions that come after it, elsewhere in the organization?" Strengthening the parts of the process that already exist does nothing to fill a gap the process was never built to cover.

What the accounting misses

Here is the sharpest way to state the underlying issue. Most organizations evaluate a decision by asking what it will produce: what will this investment return, will this project finish on time, is this risk acceptable. These are legitimate questions, and most organizations have gotten reasonably good at answering them.

Almost no organization routinely asks a second, different question: what does approving this decision do to the realistic options available for the *next* decision? Not its cost. Not its risk. Its effect on what remains genuinely feasible once it is committed.

This second question is not a variant of risk management, and it is not a variant of portfolio prioritization, even though it borrows from both. Risk management, as usually practiced, catalogs individual risks and, at best, some pairwise dependencies between them — it rarely asks how three unrelated decisions, none of them a "risk" in the conventional sense, jointly consume a resource none of them individually appeared to threaten. Portfolio prioritization, as usually practiced, ranks initiatives against each other at a single point in time — it rarely asks how the *sequence* in which approved initiatives are executed changes what remains possible six or twelve months later.

The gap sits between these disciplines, in a space neither one is quite responsible for. It is the space this article has been describing: not what a decision produces, but what it does to the decisions that follow it.

Naming the problem precisely

None of this is an argument that organizations are badly run. Quite the opposite — the pattern described here shows up most clearly in organizations that already do the fundamentals well, which is exactly why it is so easy to miss. If governance were sloppy, individual bad decisions would explain the outcome, and the review would find something to point to. It is precisely because each decision passes scrutiny on its own that the collective effect goes unexamined.

We use the term Decision Space Analytics to describe the deliberate practice of looking not only at what a decision produces, but also at how it reshapes the decisions that remain realistically available afterwards. It is worth being precise about what that label does — and does not — claim. It is not a new theory of decision-making, and the underlying phenomenon it examines has been described, in different forms, by researchers working on organizational path dependency and systems thinking for decades. It is simply a name for a more deliberate habit: before committing to a decision, asking not only what it will deliver, but what it will do to the decisions still to come.

That habit is not complicated to describe. It is only uncommon to practice, because almost nothing in how large organizations are structured asks anyone to practice it. The three decisions in the scenario above did not need a better governance process. They needed someone, at some point, to ask what all three would mean for the organization if approved together — a question that, structurally, belonged to no one.

---

Key Takeaways

- Failed initiatives are often diagnosed by looking for a single bad decision. In many cases, no single decision was wrong — the outcome emerged from the interaction of several individually sound decisions that were never evaluated together.

- This pattern is structural, not a failure of talent or diligence: decisions are typically evaluated one at a time, by processes built to evaluate one decision at a time, often by people with no visibility into parallel decisions elsewhere in the organization.

- The interaction between decisions frequently doesn't exist at the moment any single decision is made — it becomes real only once multiple decisions coexist, which is exactly why it is invisible until it is already a constraint.

- Sequence, not just selection, matters: the same set of decisions made in a different order can produce a materially different outcome.

- Strengthening existing governance and risk processes does not close this gap, because the gap sits between disciplines that were each built to answer a narrower question.

- Decision Space Analytics is a term we use to describe the deliberate practice of examining not only what a decision produces, but also how it reshapes the decisions that remain realistically available afterwards. It is not presented as a new theory, but as a practical analytical perspective on a familiar management problem.

---

The most expensive strategic constraint is rarely the one an organization can see today. More often, it is quietly created by decisions that seemed entirely reasonable when they were made. Organizations cannot avoid difficult choices, but they can become better at recognising how today's decisions quietly reshape tomorrow's possibilities. Learning to see those interactions before commitments accumulate may become one of the most valuable strategic capabilities an organization can develop.