How to Confidently Defend Investment Cases

Complex, costly or difficult decisions can look strong on paper. But if the case has not been properly prepared, someone in the room is likely to ask the question that has not been answered.

What gets challenged

Across boards, regulators, and executive reviews, the same pressure points appear.

1. Is this the real issue?
   Or has the problem been shaped around a preferred solution?
2. What decision is actually being sought?
   Approval, endorsement, funding, procurement, advocacy, further investigation or acceptance of risk?
3. Why this option over the alternatives?
   Including staging, deferral, lower-cost options or doing nothing for now.
4. Why now?
   What makes the timing prudent, necessary and defensible?
5. Who benefits, who bears the burden, and what trade-offs are being accepted?
   This is where value-for-money, public value and legitimacy get tested.
6. Can the decision be explained in plain English under pressure?
   If it cannot be explained simply, the case is probably not ready for scrutiny.

Why most cases don’t hold up

Most teams do not set out to hide weaknesses.

The problem is usually more practical. The case is built to describe the project, not to defend the decision.

Assumptions sit in the background. Trade offs are implied rather than explained. Delivery risks are known by the team but not visible in the document. The preferred option may be obvious internally, but the logic is not clear enough for someone outside the project to defend.

That is the difference between asking:

“Does this read well?”
and asking:
“Would I be comfortable defending this in the room?”

In many organisations, decision documents are built from the bottom up. Technical inputs are gathered, sections are completed, compliance requirements are met, and the document grows.

But the real decision logic can remain hidden.

That becomes a problem when the case reaches someone who is not close to the project but is accountable for approving it.