Most steering committees aren’t looking for reasons to approve your proposal; they’re looking for reasons it might fail, and that changes how ROI should be presented.
Too many business cases are built around persuasion rather than credibility; benefits are polished, downside risk is softened, and assumptions are presented as stone-cold certainties. Ironically, the result is actually often the opposite of what was intended, as experienced stakeholders who have danced this dance before become more skeptical, not less.
Most steering committees have seen optimistic forecasts before, and they’ve then watched delivery timelines slip, adoption rates stall, and projected savings quietly disappear after approval. So when a business case arrives claiming strong ROI with perfect confidence, critical stakeholders naturally start looking for what's been overlooked.
The strongest ROI presentations, therefore, aren’t the ones that sound the most confident, but the ones that feel the most trustworthy. That means acknowledging uncertainty, showing how assumptions were tested, and demonstrating that risks have been thought through before the committee raises them.
This is where many organisations struggle, not because the investment lacks value, but because the ROI story is presented in a way that creates doubt instead of confidence.
ROI skepticism is usually earned
Steering committees rarely become skeptical in isolation, so in many organisations, that skepticism is a learned response from years of overpromised outcomes and underdelivered value. A few common patterns tend to be immediate red flags:
🔢 Benefits that appear too precise despite limited evidence
👤 Savings projections without operational ownership
📈 Aggressive adoption assumptions presented as guaranteed outcomes
⚠️ ROI calculations that ignore delivery risk or implementation complexity
🔀 Business cases that only show one “expected” scenario
Experienced stakeholders will be very aware that uncertainty exists in every investment decision, so what creates concern is when the business case pretends that uncertainty doesn’t exist. Ironically, trying to make ROI look stronger often damages credibility.
For example, presenting a projected 187% ROI over three years may sound compelling internally. But if there’s no explanation of how the assumptions were validated, how variability was considered, or what happens if adoption is slower than expected, that impressive-looking 187% quickly starts to feel fragile.
A skeptical steering committee isn’t necessarily rejecting the investment itself; often, they’re just reacting to how the investment is being framed.
Strong ROI presentations focus on confidence, not certainty
One of the biggest mistakes teams make is treating ROI as a fixed answer rather than a range of possible outcomes. In reality, most investments involve uncertainty across areas such as delivery timelines, adoption rates, operational readiness, vendor performance, market conditions, internal change fatigue, competing priorities, and a whole host of others. Pretending these variables don’t exist (particularly when the list is almost endless) significantly weakens the business case.
A stronger approach is to show that uncertainty has been actively considered, which immediately changes the tone of the discussion. Instead of:
“This project will deliver $2.4M in savings.”
the discussion becomes:
“Based on current assumptions, expected savings are between $1.8M and $2.6M depending on adoption speed and process compliance.”
The second example feels substantially more credible because it reflects how real organisations operate.
This is also where scenario modelling becomes incredibly valuable, as showing a best-case, expected-case, and downside scenario demonstrates that the team has pressure-tested the investment rather than simply cherry-picking the most attractive numbers. After all, a steering committee doesn’t expect perfect prediction; it expects evidence of disciplined thinking, and that distinction matters.
Anticipate objections before they’re raised
Many ROI presentations become defensive because teams wait for objections to appear before addressing them, but the strongest presenters do the opposite; they proactively surface likely concerns and explain how they’ve been evaluated. For example:
If adoption risk is high
Don’t hide it away, acknowledge it directly, so for example explain:
How adoption assumptions were estimated
Which teams were consulted
What change management activities are planned
What happens if adoption is slower than expected
If projected savings depend on behavioral change
Steering committees generally become skeptical when operational reality is hidden beneath financial projections, so be explicit about operational dependencies. For example:
Are managers expected to enforce new processes?
Does success rely on process compliance?
Will legacy systems continue operating in parallel?
If benefits are difficult to quantify
Separate measurable and non-measurable outcomes clearly, because trying to artificially quantify every benefit often weakens trust as some strategic or risk-reduction benefits are inherently directional rather than precise. For example:
Reduced regulatory exposure
Improved decision visibility
Faster escalation management
Better cross-functional alignment
Presenting these honestly is usually more persuasive than forcing unreliable financial estimates, as overconfidence can often be interpreted as a lack of rigor.
Show how assumptions were validated
One of the fastest ways to strengthen ROI credibility is to explain where assumptions came from. Many business cases include impressive numbers but very little traceability behind them, when really, steering committees want to understand:
Who validated the assumptions
Whether operational teams support them
What historical evidence exists
Which external benchmarks were used
How sensitive the model is to change
This is especially important when assumptions materially impact ROI outcomes. For example, if the entire business case depends on 85% user adoption, a 30% productivity improvement, and a 40% reduction in manual effort then those assumptions should be treated as critical decision variables, not background detail.
A practical way to improve credibility is to classify assumptions by confidence level, so for example:
Assumption Type | Confidence Level | Validation Source |
Current operational costs | High | Historical finance data |
Adoption rate | Medium | Pilot feedback and stakeholder interviews |
Productivity uplift | Medium-Low | Vendor benchmark estimates |
Risk reduction savings | Low | Directional estimate |
This immediately changes the tone of the conversation from “trust us” to “here’s what we know, what we estimate, and where uncertainty remains”, and that transparency builds trust.
Avoid presenting ROI as a sales pitch
One of the easiest ways to lose a steering committee is to sound like a vendor presentation. Business cases should help decision-makers evaluate trade-offs, not pressure them into approval, so that means avoiding:
Inflated language
Unrealistic certainty
One-sided framing
Selective data presentation
“Guaranteed” outcomes
Instead, focus on balanced evaluation, so a credible ROI discussion should include:
Expected benefits
Key risks
Operational dependencies
Sensitivity to assumptions
Alternative scenarios
What success realistically requires
The goal isn’t to remove uncertainty, it’s to demonstrate that uncertainty is understood and manageable.
This is also where risk-adjusted ROI becomes important. Two investments with identical projected ROI may have very different risk profiles, so a steering committee evaluating capital allocation decisions needs visibility into both expected return and delivery uncertainty. Without that context, ROI alone can become misleading.
Practical ways to make ROI presentations more credible
If your steering committee is highly critical or financially cautious, small presentation changes can make a major difference.
💡 Lead with assumptions, not just outcomes: Start by explaining the key drivers behind the model before presenting headline ROI figures, as this helps stakeholders understand how the conclusion was reached.
📉 Include downside scenarios: Don’t only present the “expected” outcome, as showing downside and sensitivity scenarios demonstrates both maturity and realism.
🧮 Separate controllable and uncontrollable factors: Clarify which variables the organisation can directly influence versus external dependencies outside operational control.
📊 Quantify confidence where possible: Even directional confidence scoring helps stakeholders understand where assumptions are strongest or weakest.
💬 Acknowledge uncertainty directly: Avoid language that implies certainty where uncertainty clearly exists, as counterintuitively, this often actually increases stakeholder confidence.
⚠️ Make risks visible early: If significant implementation or adoption risks exist, don’t just hide them and hope they go away, waiting to see if the committee challenges them. The earlier concerns are acknowledged, the less defensive the conversation becomes.
Better ROI conversations lead to better decisions
A skeptical steering committee isn’t necessarily a problem, as in many cases, skepticism improves decision quality. The issue isn’t scrutiny itself, it’s when ROI presentations are built in ways that unintentionally trigger distrust.
The most effective business cases don’t try to eliminate every question, they create confidence that the organisation understands the investment, has tested its assumptions, and has considered what could go wrong alongside what could go right.
That’s what mature investment evaluation looks like. Tools like scenario modelling, risk-adjusted ROI, and structured assumption validation help organisations move beyond optimistic forecasting toward more credible decision-making. And in practice, credibility is often far more persuasive than confidence alone.
