Skip to main content

Business Case

A business case is the decision document that answers one question: should we commit real resources to this project now?

This is a major topic, and it varies by company, product or service type, and industry. A medical device launch, a software feature, and a plant automation project will not use identical logic or evidence. But all good business cases answer the same core issues.

Core requirements​

  • It has acceptable financial return for the risk level (for example ROI, NPV, payback, margin impact, or another approved company metric).
  • It supports the business strategy, not just a local team preference.
  • The company can afford it in the period required (cash, budget, and people capacity).
  • It is within company capability, including smart use of development partners where needed.
  • Capability includes both skill and capacity across technology development, project management, market understanding, and operations.

Additional checks that improve decision quality​

  • Compare real options, not just one preferred answer. Include a "do nothing" or "defer" baseline.
  • State assumptions explicitly (demand, cost, timing, partner performance, regulatory outcomes, etc.).
  • Test sensitivity: what happens if the most important assumptions move against us?
  • Define major risks and early triggers so leaders know when to replan or stop.
  • Assign benefits ownership: who is accountable for each promised benefit after launch?
  • Define how value will be measured during execution and after delivery.
  • Confirm governance path: who approves, who funds, and what decision gates apply?

Practical guidance for VPM teams​

A weak business case creates unstable projects. Teams start work, then lose resources, then renegotiate scope every few weeks. A strong business case prevents this by aligning leadership before planning starts.

At minimum, your case should make visible:

  • Why now
  • Why this option
  • Why this team
  • Why this level of investment
  • What we expect to gain
  • What would cause us to pause, change course, or stop

Business case quality test​

Before greenlighting the project, ask:

  • Can an executive explain the value in two minutes without reading slides?
  • Can finance trace where the return comes from and when it appears?
  • Can functional leaders confirm capacity and named owners?
  • Can the team explain what must be true for the case to remain valid?

If these answers are unclear, tighten the case before launching the full planning event.

Figure Placeholders​

Figure placeholder: "Business Case" overview visual showing the page's core concepts and flow. Figure path: /img/figures/planning-business-case-fig-01.png Figure placeholder: visual companion for "Core requirements" (framework, workflow, or real example). Figure path: /img/figures/planning-business-case-fig-02.png Figure placeholder: visual companion for "Additional checks that improve decision quality" (framework, workflow, or real example). Figure path: /img/figures/planning-business-case-fig-03.png Figure placeholder: visual companion for "Practical guidance for VPM teams" (framework, workflow, or real example). Figure path: /img/figures/planning-business-case-fig-04.png Figure placeholder: visual companion for "Business case quality test" (framework, workflow, or real example). Figure path: /img/figures/planning-business-case-fig-05.png