Investment decisions are often judged by the recommendation. Is the idea compelling? Does the financial case look attractive? Does the proposal feel urgent enough to approve?
But arguably, the better question is more practical: what evidence supports the decision?
A strong investment decision doesn’t need perfect evidence. Costs move, assumptions change, stakeholders disagree, and future outcomes are uncertain, so perfect evidence rarely exists anyway.
What matters is whether the evidence is clear enough to support a confident decision, and whether its source, quality, confidence level, and gaps are visible.
A decision can look polished while still being weak underneath. It may include a confident ROI figure, a neat summary, and a clear recommendation, but if the evidence is unclear, outdated, or untested, approvers are being asked to put their faith in the presentation, not the decision.
Good evidence helps people understand what’s known, what’s assumed, what remains uncertain, and what should be tracked after approval.
Evidence should explain the decision, not just support the answer
The first role of evidence is to make the decision understandable, so it shouldn’t only prove why one option looks attractive. It should explain the problem, the context, the options, and the likely consequences of doing nothing.
A credible investment decision usually needs evidence that shows:
📌 What problem or opportunity is being addressed
🧮 What financial impact is expected
🔍 What assumptions the decision depends on
⚠️ What risks could affect delivery or value
📊 What operational or stakeholder data supports the case
🧾 Where the information came from
This doesn’t mean that every decision needs a large formal business case, as the level of evidence should match the scale, risk, and reversibility of the decision. A smaller decision may only need a short justification with a few supporting figures and a clear owner, while a major investment may need deeper financial modeling, scenario analysis, risk review, and approval documentation.
Evidence isn’t there to make any decision slower, but to make decisions easier to review, compare, approve, challenge, and track.
Financial evidence should be traceable, not just impressive
Financial evidence is often the most visible part of an investment decision, although it’s also one of the easiest areas to make look stronger than it really is. That’s not to say that a large benefit number can’t create confidence, but it can only do so if people can see how it was calculated.
Useful financial evidence may include current costs, expected future costs, implementation and operating costs, expected benefits, timing of costs and benefits, and measures such as payback or ROI.
The figures matter, but the assumptions behind them matter just as much.
For example, a proposal may claim that a new system will save 1,000 hours a year. That figure becomes much more credible when it shows the current process volume, average handling time, affected teams, expected reduction, loaded labor cost, and confidence level.
Good financial evidence should also make uncertainty visible. Some numbers will come from invoices, contracts, or historical data, while others may come from stakeholder estimates, benchmark ranges, or vendor assumptions. Those sources aren’t equal.
A decision is stronger when it distinguishes between confirmed costs, estimated costs, modeled benefits, stakeholder assumptions, benchmarked values, and calculated outputs. This helps approvers understand which parts of the case are reliable, which are directional, and which need more validation.
Operational and stakeholder evidence keeps the decision grounded
Many investment decisions fail because the financial case is disconnected from operational reality. Even if the spreadsheet says the benefit is achievable, that doesn’t mean too much if the process data, frontline feedback, delivery capacity, or customer behavior tells a more complicated story.
Operational evidence helps test whether the proposed investment can actually work once it moves outside of the spreadsheet. Every company is different, but typical examples might include process volumes, cycle times, system usage, capacity constraints, support tickets, delivery timelines, or resource availability.
Stakeholder evidence adds another layer. It helps show whether the people affected by the decision actually recognize the problem, support the proposed change, and believe the expected outcomes are realistic. That evidence may come from interviews, workshops, surveys, sales conversations, customer feedback, or internal subject matter experts; it doesn’t need to be perfect, but it should be visible.
For example, if a customer success team says a reporting problem is creating renewal risk, that case is much stronger when that insight is connected to renewal data, customer examples, support tickets, or account notes, rather than purely being anecdotal.
The goal isn’t to collect evidence for its own sake, but to avoid decisions being built on isolated opinions.
Benchmarks, risks, and source records make uncertainty easier to manage
Some evidence helps prove the case, while other evidence helps people understand the uncertainty around the case.
Benchmarks can provide useful comparison points; they may come from previous internal projects, similar investments in another department, vendor implementation data, market comparisons, or historical performance from earlier initiatives.
But benchmarks need to be treated carefully. It’s important to realize that a vendor benchmark isn’t the same as verified internal data, and an industry comparison may provide direction, but it may not reflect your organization’s processes, systems, culture, or constraints. That doesn’t make benchmarks useless, it just means that their source and relevance should be clear.
Risk evidence is equally important. A decision can have a strong expected return yet may still be fragile if delivery risk is high, adoption is uncertain, or the benefit depends on conditions outside the team’s control.
Good risk evidence should explain what could prevent the expected outcome, how likely that risk is, how significant the impact could be, whether mitigation is possible, who owns the risk, and whether the risk changes the decision.
This is where assumptions become important. Every investment decision depends on assumptions, but weak decisions hide them, while strong decisions expose them.
If the expected value depends on adoption reaching 70%, then that should be clearly stated. If savings depend on removing manual work from three teams, that should be visible. If revenue uplift depends on sales teams changing behavior, that should be treated as an assumption, not a guaranteed result.
Source records help tie all of this together. The point isn’t to attach endless documentation, but to preserve where important evidence came from, so that the decision can be reviewed and trusted later.
This becomes especially valuable after approval, because when teams track whether outcomes were achieved, they need to compare actual results with the original assumptions, evidence, and expected benefits.
How to put evidence into practice
The practical challenge isn’t collecting every possible piece of evidence, but deciding what evidence is enough for the decision in front of you. A useful approach is to ask five simple questions:
🔎 What evidence supports the need for this decision?
🧮 What evidence supports the expected financial impact?
⚙️ What evidence supports the operational feasibility?
⚠️ What assumptions or risks could change the outcome?
🧩 What evidence is missing, weak, or still unvalidated?
Those questions make it easier for approvers to challenge the decision constructively. Instead of asking, “Do we believe this proposal?” they can ask which parts are well supported, which figures are estimates, which assumptions matter most, what needs validation before approval, and what should be tracked after approval.
This is also where structured decision data becomes valuable beyond the individual decision. When organizations capture evidence, assumptions, risks, financials, owners, and outcomes consistently, leaders can identify duplicated initiatives, weak evidence areas, recurring risks, over-optimistic benefits, delayed approvals, and investments that aren't being tracked after approval.
Tools like KangaROI can help by making evidence part of the decision process itself, rather than leaving it scattered across a multitude of spreadsheets, slide decks, emails, and meeting notes. The value isn’t just a stronger approval package, but a clearer decision record that can support review, approval, tracking, and organizational learning.
Conclusion
Investment decisions don’t need perfect evidence; they need evidence that is visible, relevant, traceable, and honest about uncertainty.
A strong decision shows what’s known, what’s assumed, where the numbers came from, what risks could change the outcome, and what still needs validation.
That kind of evidence helps teams make better decisions, gives leaders greater visibility, strengthens accountability, and creates a clearer path from expected value to actual results.
The best investment decisions aren’t the ones with the most supporting material, but the ones where the evidence is strong enough, transparent enough, and structured enough to support confident action.
