8.3 Business Case and Needs Assessment

Key Takeaways

  • A needs assessment maps the current state (as-is), defines the desired future state (to-be), and quantifies the gap the project must close
  • A situation statement names the problem, who it affects, the measurable impact, and the desired outcome — keep it specific and number-driven
  • The business case justifies the investment: problem, options (always including 'do nothing'), recommendation, financials, risk, strategic fit, and success metrics
  • Know the financial decision rules: NPV positive = pursue, BCR greater than 1.0 = pursue, IRR above the hurdle rate = pursue, shorter payback is better
  • The business case is a living document — revisit it at phase gates to confirm the investment is still justified before spending more
Last updated: June 2026

Pre-Project BA Work

Before a charter is signed, business analysis identifies the need, evaluates options, and builds the justification. This is the front end of value delivery and a heavily tested slice of Domain 4. The deliverable that authorizes spending is the business case, built on a needs assessment.

Needs Assessment

A needs assessment is a systematic look at the current situation to determine what must change. The six steps:

  1. Identify the problem or opportunity — what is happening, or failing to happen, that demands attention?
  2. Assess the current state (as-is) — how does work happen today; where are the pain points?
  3. Define the desired future state (to-be) — what should it look like after the project?
  4. Identify the gap — the measurable difference between as-is and to-be
  5. Evaluate options — what alternatives could close that gap?
  6. Recommend a solution — which option fits within the constraints?

The gap is the heart of the assessment: it defines what the project must accomplish. If you cannot quantify the gap, you cannot justify the spend.

Situation Statement

A situation statement frames the problem in a repeatable structure so stakeholders agree on what is being solved before solutions are debated.

ComponentContent
The problem/opportunity of[describe the issue]
Affects[who is impacted]
The impact of which is[measurable consequence]
A successful solution would[desired outcome]

Worked example: "The problem of manual data entry into three separate systems affects the operations team of 45 people. The impact is roughly 15 hours of wasted effort per week and a 12% error rate. A successful solution would integrate the three systems into one platform, eliminating redundant entry and reducing the error rate below 2%."

Notice the numbers — 45 people, 15 hours, 12% to under 2%. A vague statement ("data entry is annoying") cannot anchor a business case; a quantified one feeds straight into the financial analysis.

The Business Case

The business case documents why the organization should invest. It answers "Why this, why now, and what do we get back?"

SectionContent
Executive summaryThe recommendation in brief
Problem / opportunity statementThe business need being addressed
Analysis of optionsAlternatives considered, including 'do nothing'
Recommended solutionThe chosen option and rationale
Financial analysisCosts, benefits, ROI, NPV, payback
Risk assessmentKey risks and mitigations
Strategic alignmentLink to organizational goals
Implementation approachHigh-level execution plan
Success metricsHow outcomes will be measured

Financial Decision Rules — memorize the cutoffs

MetricWhat it isDecision rule
Payback periodTime to recover the initial investmentShorter is better
Net Present Value (NPV)Present value of future cash flows minus the investmentPositive = pursue; negative = reject
Return on Investment (ROI)(Benefits − Costs) / Costs × 100%Higher is better
Internal Rate of Return (IRR)Discount rate where NPV = 0Above the hurdle rate = pursue
Benefit-Cost Ratio (BCR)Total benefits / total costsGreater than 1.0 = pursue

Reading the numbers: An NPV of −$30,000 means the discounted benefits fall $30,000 short of the cost — the project destroys value and should be rejected on financials alone. A BCR of 0.85 (below 1.0) likewise fails. When comparing two positive-NPV projects, prefer the higher NPV; payback alone ignores cash flows after recovery, so it is a tiebreaker, not a primary rule.

Evaluating Options

The BA weighs each option across several dimensions:

FactorQuestion
ValueWhich option delivers the most stakeholder value?
CostWhat is each option's total cost of ownership?
RiskWhat risks does each carry?
FeasibilityIs it technically and organizationally achievable?
TimelineHow long to implement?
Strategic fitWhich best supports strategy?
DependenciesWhat external factors must hold true?

Most business cases evaluate at least three options:

  1. Do nothing — keep the current state as the comparison baseline
  2. Minimum solution — address only the critical needs at low cost
  3. Full solution — comprehensive, addresses all identified needs

Exam tip: Always include do nothing. It quantifies the cost of inaction, prevents "solution bias," and gives decision-makers a true baseline. A CAPM question that omits it from the options list is usually flagging the mistake.

Feasibility and the Living Business Case

Feasibility analysis checks whether the recommended option is technically, economically, operationally, and legally viable before resources are committed. Finally, the business case is a living document: it is revisited at phase gates and major milestones to confirm the assumptions still hold and the benefits are still worth the spend. If the business case no longer justifies the work, the right call may be to terminate the project — protecting the organization from sunk-cost thinking.

Test Your Knowledge

The primary purpose of a needs assessment is to:

A
B
C
D
Test Your Knowledge

A business case omits any 'do nothing' option. Why is this a problem?

A
B
C
D
Test Your Knowledge

Two projects each have a positive NPV. Project A's NPV is $40,000; Project B's is $90,000. With limited funds for only one, which is preferable on financial grounds?

A
B
C
D