Why Data Rarely Changes the Decision

The issue is rarely the absence of data. It shows up, many times too late, in the wrong format, or without the organizational permission needed to challenge a direction that has already been chosen. By the time the data arrives, the decision has already been made. What follows is not analysis. It is justification.

The Sequence Problem

The instinct to move fast on a solution is understandable. Problems carry pressure, and pressure generates action. A direction gets chosen, often based on past experience, executive preference, or what worked somewhere else. Then the data gets gathered. Then it gets used to confirm what was already decided.

This is called due diligence. It produces the appearance of rigor without the substance of it. The data filters through the decision rather than shaping it, and anything that does not support the chosen direction gets quietly set aside.

The problem is not usually data quality. It is sequencing. Scope the problem before the evidence arrives, and everything else is framed to confirm the assumption. That is not a measurement failure. It is an intentional failure to follow the process.

Where the Problem Actually Originates

Before any solution is designed, one question has to be answered with evidence rather than opinion: where in the value stream does the problem originate?

Not where it was reported. Not where it is most visible. Not where the loudest stakeholder sits. Where the data says it starts.

That distinction matters more than most organizations recognize. The place where a problem surfaces is almost never the place where it begins. A quality failure at the end of a process usually has its origin three or four steps upstream. A backlog in one function is often the downstream result of a handoff failure in another. Reporting the symptom and scoping to the symptom produces a solution for the wrong location.

Which is why the diagnostic sequence has to run before scoping.

What Decision-Laundering Costs

Decision-laundering costs show up across the initiative in predictable ways: delays, resource time, rework, and downstream remediation efforts that were never budgeted for.

The most visible cost is a solution that meets documented business requirements but still does not deliver the business capabilities the organization actually needed. Requirements written without a process-level understanding capture what people do. They rarely capture what the business needs the system to enable. The system works as designed. The problem persists.

That is recoverable, with significant effort. The indirect costs are harder to recover from.

Credibility erodes first. When an initiative closes and the metric does not move, trust degrades, and it rarely lands where it belongs. The functions that were never set up to succeed carry the consequences of a scoping decision that was made before the evidence arrived, and the blame game cycle begins.

Organizational patience goes next. Every failed or partial initiative consumes the appetite for trying again. That appetite is not unlimited. Organizations that cycle through the same problems without resolution do not become more willing to invest in structured approaches. They become more cynical about them. The window for doing the work correctly gets narrower each time.

The Political Problem No One Talks About

Here is the part that does not make it into most frameworks: the sequence problem is often not a methodology problem. It is a power problem.

A senior leader has already signaled a direction in a steering committee. A vendor has been selected. An initiative has been announced internally. Now the diagnostic data comes back and points somewhere else. The question is not whether the organization has good data. The question is whether anyone has the standing to act on it.

In many organizations, the answer is no. The data gets noted, qualified, and filed. The original direction holds. The initiative proceeds on the assumption that was set before the evidence arrived. And six months later, the post-mortem cites execution issues.

This is why diagnostic authority has to be structural, not personal. It cannot depend on one practitioner being willing to stand in front of a senior leader and say the scope is wrong. That conversation happens once, maybe twice, before it stops happening. The gate has to be built into the process itself, with explicit requirements for what evidence is needed before scoping is finalized, and explicit governance for who can authorize moving forward when that evidence is incomplete or contradictory.

Without that structure, data-driven decision making is a cultural aspiration. With it, it becomes an operational standard.

Where This Lives in FORGE

The Filter phase is where this discipline is formalized. Before a single initiative hour is committed, Filter requires a defined problem statement grounded in operating data, not assumption. It is also where the business process, not just the workflow, is examined to understand not only what is happening but why: where decision authority breaks down, where handoffs fail, and where system capabilities are missing or actively competing with the process they are supposed to support.

That distinction matters for scoping. Requirements written without process-level understanding capture what people do. They rarely capture what the business needs the system to enable. Filter closes that gap before a single requirement is written.

The value stream analysis that identifies origin points, not symptom locations, happens here. The scoping decision does not move forward until the diagnostic evidence supports it. That is not a bureaucratic requirement. It is the control that prevents the organization from spending six months solving the wrong problem, building the right system for the wrong process, and calling it progress.

The question worth asking before the next initiative launches is not whether you have data. It is whether the data arrived before or after the direction was chosen.

Part of an ongoing series on operational design, process transformation, and what it takes to make change endure.