Decision Analysis
Should I Approve This Project?
Project approvals are among the most consequential decisions leaders make. You are committing budget, people, and time based on a business case built on assumptions. Incertive shows you the probability that those assumptions hold up - and what happens when they do not.
The Project Approval Problem
A project proposal lands on your desk. The business case looks solid: $500,000 investment, 18-month timeline, projected ROI of 40%. The team has done their analysis, the numbers add up, and there is organizational momentum behind it. Your job is to decide whether to approve, delay, modify, or kill the project.
The challenge is that every number in that business case is an estimate. The $500,000 budget assumes no scope changes, no surprises, and no delays. The 18-month timeline assumes resources are available when needed and that nothing else competes for those resources. The 40% ROI assumes market conditions, customer behavior, and competitive dynamics all play out roughly as expected. Each assumption introduces uncertainty, and when multiple assumptions are optimistic simultaneously - which is common because of the planning fallacy - the actual outcome can be very different from the business case.
Research on capital projects consistently shows that budgets overrun and timelines slip more often than not. This is not because project teams are incompetent - it is because they are systematically optimistic about the variables they can control and underweight the variables they cannot. The result is that project approval decisions are made with a false sense of precision that masks the real risk.
Key Uncertainties in Project Approval
Budget and cost estimation
Project costs are estimates, not facts. Materials prices change, labor costs vary, scope evolves as the project progresses, and unforeseen complications arise. The actual cost typically exceeds the initial estimate, and the degree of overshoot is itself uncertain.
Timeline and schedule risk
Projects depend on sequential and parallel tasks, each with their own duration uncertainty. Resource availability, dependency delays, regulatory approvals, and technical challenges all affect the schedule. A delay in one critical path task cascades through the entire timeline.
Scope changes and requirements evolution
Requirements rarely stay fixed from approval to completion. New information emerges, stakeholder priorities shift, and market conditions change. Each scope change affects both cost and timeline. The probability of significant scope changes increases with project duration.
Return on investment uncertainty
The projected ROI depends on revenue assumptions, market adoption, competitive dynamics, and operational efficiency - all of which are uncertain. Even if the project delivers on time and on budget, the returns may differ from projections because the market responds differently than expected.
Resource availability and competing priorities
Projects compete for people, budget, and management attention. A key engineer might be pulled to another project. Budget might be redirected mid-year. Strategic priorities might shift. These organizational uncertainties affect project outcomes independently of the project is own execution risk.
How It Works With Incertive
You describe the project and its business case in plain language. For example:
Incertive models the uncertain variables and runs Monte Carlo simulation across thousands of scenarios. The output includes:
Interpreting the Results
The simulation might show that the project has an 82% probability of positive ROI within 4 years, but the budget has only a 40% probability of staying within the initial $750,000 estimate. The 80th percentile budget is $980,000 and the 95th percentile is $1.15 million. This means you should plan for approximately $1 million in total spend - not the $750,000 the project team proposed - and set aside an additional $150,000 in contingency.
The sensitivity analysis might show that WMS integration complexity is the single largest risk factor. If integration goes smoothly, the project is highly profitable. If integration proves difficult, both cost and timeline suffer significantly. This insight shifts the approval conversation: instead of "should we approve this project?", the question becomes "can we de-risk the integration before committing the full budget?" - perhaps through a paid technical assessment or a small proof-of-concept.
The phased variant might show that starting with one warehouse zone, proving the integration, and then expanding to the full facility has a slightly lower total ROI but a dramatically higher probability of success. This phased approach converts a single large go/no-go decision into a series of smaller decisions, each informed by real operational data from the previous phase.
Frequently Asked Questions
How does Incertive help with project approval decisions?
Incertive models the key uncertainties in any project - budget, timeline, resource availability, scope changes, and expected returns. Instead of approving projects based on a single business case, you see the probability distribution of outcomes. You learn the odds of the project finishing on budget, the probability of delivering the expected return, and which risk factors matter most.
What types of projects can Incertive evaluate?
Any project where you commit resources now in exchange for uncertain future returns. Capital projects like facility expansions and equipment upgrades. Technology projects like software implementations and infrastructure migrations. Business initiatives like market entry, product development, and organizational restructuring. The common thread is investment under uncertainty.
How does the analysis handle the risk of budget overruns?
Budget overruns are one of the most common project risks and one of the most poorly modeled. Incertive treats the budget not as a fixed number but as a range - the project might cost $800,000 or it might cost $1.2 million depending on scope changes, vendor performance, and unforeseen complications. The simulation shows the probability of exceeding various budget thresholds, giving you realistic contingency numbers.
Can I compare different versions of the same project?
Yes. Plan variants might include a full-scope project, a phased approach, a reduced-scope version, or an outsourced alternative. Each variant has its own cost and return profile, and Incertive shows the probability-weighted outcomes for each. You might find that a phased approach has a lower maximum return but a much higher probability of positive ROI.
How do I use Incertive results in a project approval meeting?
The output gives you concrete talking points: the probability of positive ROI at different time horizons, the budget range you should plan for (not just the estimate), the key risk factors that could derail the project, and alternative approaches with their own probability profiles. This replaces the typical "here is our business case" presentation with "here are the odds, here are the risks, and here are the options."
Know the Odds Before You Approve
Describe your project and get a probability-backed assessment of budget risk, timeline risk, and ROI likelihood. Make approval decisions based on realistic ranges, not optimistic single-point estimates.
Get Started