ROI leakage rarely starts in the spreadsheet
When a transformation underdelivers, the explanation usually comes later: the scope changed, the vendor misunderstood, the business was not aligned, the governance process was too slow, or the execution teams interpreted the decision differently.
Those explanations are real, but they often describe symptoms. The deeper issue is that the decision did not remain operationally intact after it was made. The business case may have been approved, but the decision behind it was not preserved as something traceable, owned, governed, and executable.
That is why ROI drainage is not only a finance problem. It is a decision-readiness problem.
The six places value starts to leak
FSA looks at decision readiness across six dimensions: decision ownership, context traceability, governance discipline, dependency visibility, execution continuity, and narrative risk.
When ownership is weak, nobody is clearly responsible for carrying the decision into execution. When context is not traceable, teams remember fragments of the rationale instead of working from a shared record. When governance focuses only on status, trade-offs happen without enough decision review.
When dependencies are invisible, value is delayed by blockers that should have been anticipated. When execution continuity is weak, alignment depends on a few informal integrators. And when narrative risk is high, scope starts living in meeting memory, stakeholder interpretation, or vendor assumptions instead of traceable decisions.
Why readiness should be checked before more execution pressure
The common response to slow transformation is to increase pressure: more meetings, more reporting, more escalation, more delivery discipline. Sometimes that helps. But if the decision layer underneath is weak, more pressure can simply accelerate confusion.
A Decision Readiness Score helps leaders see where the execution environment is most exposed before they add more motion. It does not claim to calculate exact ROI loss. It surfaces where value leakage may be forming so leaders can decide what to clarify first.
The goal is simple: before asking teams to execute faster, make sure the decision is still clear enough to execute correctly.