4.1 Business Case Purpose, Objectives & Key Concepts

4.1 Business Case Purpose, Objectives & Key Concepts

Practitioner Core Mandate: In PRINCE2 7, a project is never an end in itself—it is an investment vehicle designed to deliver business change and measurable value. The Business Case practice provides the vital governance mechanisms to evaluate whether a project is desirable, viable, and achievable before funds are committed, and ensures that investment justification persists until formal closure.

---

Purpose and Strategic Role of the Business Case Practice

The primary purpose of the Business Case practice in PRINCE2 7 is to establish mechanisms to judge whether the project is and remains desirable, viable, and achievable as a means to support decision-making in its continued investment.

Every project commits scarce organizational resources—capital, personnel, time, and commercial reputation. Without structured business justification, organizations risk falling victim to "pet projects", technical vanity initiatives, or runaway expenditures that deliver no tangible return. The Business Case acts as the commercial compass of the project, establishing the benchmark against which every stage gate authorization, scope change, and exception decision is evaluated.

                    THE BUSINESS JUSTIFICATION TRIAD

   ┌─────────────────────────────────────────────────────────────────┐
   │                           DESIRABLE                             │
   │ Is the investment worth it? Do forecast benefits significantly  │
   │ outweigh the total costs, ongoing overhead, and dis-benefits?   │
   └───────────────────────────────┬─────────────────────────────────┘
                                   │
   ┌───────────────────────────────┴─────────────────────────────────┐
   │                            VIABLE                               │
   │ Can the organization afford it? Does the financial return,      │
   │ payback period, or regulatory necessity meet corporate thresholds│
   │ within the project's operational and financial constraints?     │
   └───────────────────────────────┬─────────────────────────────────┘
                                   │
   ┌───────────────────────────────┴─────────────────────────────────┐
   │                          ACHIEVABLE                             │
   │ Can the products actually be delivered? Do the organization and │
   │ contracted suppliers have the capability, capacity, and skills? │
   └─────────────────────────────────────────────────────────────────┘

The Investment Appraisal Triad: Desirable, Viable, and Achievable

To maintain business justification under PRINCE2 7, the Project Board must confirm that the initiative satisfies three distinct criteria:

1. Desirable: Evaluates the balance of costs, benefits, and risks. The business outcome must provide sufficient tangible or intangible advantage to justify the disruption, capital expenditure, and risk exposure.
2. Viable: Evaluates whether the project can be completed within financial, technical, and operational limits. A project may be highly desirable (e.g., constructing a private satellite network) but unviable due to lack of capital, unsustainable operational maintenance costs, or unacceptable payback horizons.
3. Achievable: Evaluates delivery capability. It confirms whether the project management team, the operational user community, and the external supply chain possess the organizational maturity, technical competence, and resource capacity to deliver the outputs and adopt the resulting operational changes.

---

The Causal Value Chain: Outputs, Outcomes, Benefits, and Dis-benefits

A central focus of the PRINCE2 7 Practitioner examination is the ability to diagnose and map the Causal Value Chain. Candidates must never confuse the physical deliverable with the business change or the measurable value realized.

                       THE CAUSAL VALUE CHAIN
   
   ┌──────────────┐     ┌──────────────┐     ┌──────────────┐     ┌──────────────┐
   │   PROJECT    │ ──> │   PROJECT    │ ──> │  OPERATIONAL │ ──> │  MEASURABLE  │
   │  ACTIVITIES  │     │    OUTPUT    │     │   OUTCOME    │     │   BENEFIT    │
   └──────────────┘     └──────────────┘     └──────────────┘     └──────────────┘
                                                    │
                                                    ▼
                                             ┌──────────────┐
                                             │ MEASURABLE   │
                                             │ DIS-BENEFIT  │
                                             └──────────────┘

Deconstructing the Core Value Chain Terms

• Output: A specialist product that is handed over to a user (or users). Outputs are the tangible or intangible deliverables produced during the project. Outputs represent new capabilities created by the project team.
  • Example: A new cloud-based electronic health record (EHR) system, mobile clinician tablets, and verified integration APIs.
• Outcome: The result of the change, normally affecting real-world behaviour and/or circumstances. Outcomes are desired when a change is carried out to achieve benefits. Outcomes occur when operational staff use the project's outputs in their day-to-day work.
  • Example: Clinicians and nursing staff access and update patient medical charts in real time at the bedside rather than batch-transcribing paper charts at central nursing stations.
• Benefit: The measurable improvement resulting from an outcome that is perceived as an advantage by one or more stakeholders. Benefits represent the realization of business value.
  • Example: A 30% reduction in medication administration errors, a 45-minute decrease in patient discharge processing time, and $1,200,000 in annual paper storage and transcription savings.
• Dis-benefit: A measurable decline or negative consequence resulting from an outcome that is perceived as a disadvantage by one or more stakeholders. Dis-benefits are accepted as the cost of achieving the desired outcomes.
  • Example: An initial 15-minute increase in documentation time per nursing shift during the 6-month transition period, resulting in $250,000 in transitional overtime expenses.

Comprehensive Value Chain Comparison

---

Critical Distinction: Dis-benefits vs. Project Risks

One of the most frequent traps on the PRINCE2 7 Practitioner examination is confusing Dis-benefits with Project Risks. Selecting a risk response when asked how to manage a dis-benefit (or vice versa) results in immediate lost marks.

   DIS-BENEFIT vs. RISK: THE CERTAINTY DIVIDE

   ┌─────────────────────────────────────────────────────────────────┐
   │                   PROJECT RISK (Uncertainty)                    │
   │ • An uncertain event or set of events                           │
   │ • Probability: Between 0% and 100% (May or may not happen)      │
   │ • Impact: Threat (negative) or Opportunity (positive)           │
   │ • Management: Managed via Risk Practice (Risk Register)         │
   │ • Example: "Third-party cloud vendor may suffer a major outage" │
   └─────────────────────────────────────────────────────────────────┘
                                   VS
   ┌─────────────────────────────────────────────────────────────────┐
   │                 DIS-BENEFIT (Definite Consequence)              │
   │ • An actual, expected negative outcome                          │
   │ • Probability: 100% (Certain to occur if outcome is achieved)   │
   │ • Impact: Strictly negative consequence perceived by stakeholder│
   │ • Management: Factored into Business Case investment appraisal  │
   │ • Example: "Decommissioning local servers causes $50K scrap fee"│
   └─────────────────────────────────────────────────────────────────┘

Comparative Analysis: Dis-benefit vs. Risk

---

Business Case Perspectives and Investment Archetypes

Projects are commissioned for diverse organizational motivations. PRINCE2 7 recognizes that the structure, depth, and appraisal criteria of a Business Case depend heavily on the project's strategic perspective:

1. Mandatory / Regulatory / Compliance Projects

• Context: Commissioned to satisfy statutory legislation, legal mandates, industry regulations (e.g., GDPR data compliance, aviation safety standards, financial reporting rules), or health and safety directives.
• Investment Rationale: Failure to comply results in severe financial penalties, criminal liability, loss of operating licenses, or immediate corporate shutdown. The primary "benefit" is risk avoidance, legal continuity, and safeguarding corporate reputation.
• Appraisal Focus: Investment appraisal does not focus on generating new commercial revenue. Instead, it evaluates options analysis to identify the most cost-effective, compliant, and sustainable solution (e.g., comparing "minimum compliance" versus "future-proof automated compliance").

2. Operational Cost Reduction / Efficiency Projects

• Context: Commissioned to optimize existing business-as-usual operations, streamline workflows, eliminate supply chain waste, or automate manual labor.
• Investment Rationale: Measurable operational savings. Justification is driven by financial metrics such as Payback Period, Net Present Value (NPV), and Internal Rate of Return (IRR).
• Appraisal Focus: Rigorous comparison of current operating costs (baseline) against projected post-implementation operational costs, including hardware/software maintenance, license fees, and transitional retraining overhead.

3. Revenue Generating / Commercial Growth Projects

• Context: Commissioned to capture new market share, launch innovative products, expand into international territories, or create new commercial revenue streams.
• Investment Rationale: Commercial profitability, cash flow generation, customer acquisition, and Return on Investment (ROI).
• Appraisal Focus: Commercial market forecasts, sales adoption curves, competitor sensitivity analysis, pricing elasticity, and marketing customer acquisition costs.

4. Strategic / Organizational Capability Projects

• Context: Commissioned to implement foundational organizational capabilities, corporate cultural transformation, or enterprise digital platforms.
• Investment Rationale: Strategic positioning, business agility, and enablement of future initiatives that cannot deliver standalone immediate financial returns.
• Appraisal Focus: Strategic fit, contribution to corporate scorecards, and enablement of secondary operational capabilities across business units.

   ALIGNING THE BUSINESS CASE TO ORGANIZATIONAL STRATEGY

   ┌─────────────────────────────────────────────────────────────────┐
   │                   CORPORATE / PROGRAMME STRATEGY                │
   │  Long-term vision, annual operating plans, ESG & growth targets │
   └───────────────────────────────┬─────────────────────────────────┘
                                   │ Mandates & Sets Tolerances
                                   ▼
   ┌─────────────────────────────────────────────────────────────────┐
   │                    PROJECT BUSINESS CASE                        │
   │  Investment justification, options analysis, cost-benefit ratio │
   └───────────────────────────────┬─────────────────────────────────┘
                                   │ Governs Delivery
                                   ▼
   ┌─────────────────────────────────────────────────────────────────┐
   │                  BENEFITS MANAGEMENT APPROACH                   │
   │  Measurement timelines, indicators, baselines, benefit owners   │
   └─────────────────────────────────────────────────────────────────┘

Strategic Alignment and Commercial Customer-Supplier Environments

The Business Case must explicitly document how the project contributes to the strategic objectives of the business layer. If a corporate priority is achieving net-zero carbon emissions by 2030, a project Business Case cannot be justified purely on short-term financial savings if the underlying delivery method breaches sustainability policies.

In commercial customer-supplier environments, there are typically two distinct business cases:

• The Customer's Business Case: Justifies spending capital to purchase or procure specialist deliverables from an external supplier to achieve internal business outcomes and benefits.
• The Supplier's Business Case: Justifies committing supplier resources, personnel, and production capacity to execute the contract, aiming to achieve commercial profit margin, cash flow, referenceable intellectual property, and market reputation.

On the Practitioner exam, candidates must identify which party's perspective is being evaluated. The Project Board's Project Executive always represents the customer's business interest, while the Senior Supplier protects the supplier's commercial viability.

---

Guidance for Effective Management for the Business Case Practice in PRINCE2 7

To claim that a project is being managed in compliance with PRINCE2 7, the project management team must fulfill specific PRINCE2 7 guidance for effective business case management. Ignoring any of these points requirements invalidates the method's application:

   MANDATORY MINIMUM REQUIREMENTS: BUSINESS CASE PRACTICE

   ┌─────────────────────────────────────────────────────────────────┐
   │ Requirement 1: CREATE & MAINTAIN JUSTIFICATION                  │
   │ Establish and maintain an acceptable business justification for │
   │ the project, typically documented within a formal Business Case.│
   ├─────────────────────────────────────────────────────────────────┤
   │ Requirement 2: REVIEW & UPDATE DYNAMICALLY                      │
   │ Continuously review and update the business justification in    │
   │ response to decisions, emerging risks, issues, & stage gates.   │
   ├─────────────────────────────────────────────────────────────────┤
   │ Requirement 3: DEFINE BENEFITS MANAGEMENT APPROACH              │
   │ Define how and when benefits will be measured, confirmed, and   │
   │ realized, both during delivery and post-project operations.     │
   ├─────────────────────────────────────────────────────────────────┤
   │ Requirement 4: ASSIGN CLEAR GOVERNANCE ROLES                    │
   │ Define accountabilities: Project Exec. owns Business Case;      │
   │ Senior User commits to and specifies benefits realization.      │
   └─────────────────────────────────────────────────────────────────┘

Permissible Tailoring vs. Governance Violations

PRINCE2 allows extensive tailoring of how the Business Case is presented, but never whether justification exists:

• Permissible Tailoring: In a small internal project, the Business Case may be a 2-page summary or a slide deck; in a major commercial venture, it may be a multi-volume financial and technical dossier. In an agile environment, justification may be documented via a Lean Value Canvas or iterative benefit hypothesis backlogs.
• Governance Violations (Exam Traps): Proceeding without a documented business justification; delegating Business Case ownership from the Project Executive to the Project Manager; treating the Business Case as a static document that is filed after initiation and never updated.

---

Practitioner Scenario Analysis

Scenario 1: The Regional Transit Automated Ticketing System

The MetroTransit Board is commissioning the SmartFare project to replace magnetic paper turnstiles with contactless biometric and mobile ticketing scanners across 45 rail stations. The initial project proposal includes the following items:

1. Installation of 250 automated biometric smart gates across all stations.
2. Station commuters tap mobile phones or transit cards, speeding passenger throughput by 40%.
3. A $3,800,000 annual reduction in station cash-handling, printing, and ticketing booth labor costs.
4. An estimated 25 station customer service agents will be made redundant, incurring $650,000 in severance and causing a 3-month dip in station staff morale.

Practitioner Evaluation:

• Item 1 is an Output: It is the specialist deliverable (hardware and infrastructure) constructed and installed by the supplier.
• Item 2 is an Outcome: It describes the real-world behavioral change in how end-users (commuters) interact with transit infrastructure.
• Item 3 is a Benefit: It is the quantifiable, positive financial advantage realized by MetroTransit operations.
• Item 4 is a Dis-benefit: It is a known, certain negative consequence (financial redundancy expense and operational staff disruption) resulting from the outcome, which must be subtracted from the net benefit calculation.

Scenario 2: Anti-Money Laundering (AML) Compliance

Apex Global Bank is facing a binding directive from the financial regulatory authority mandating automated transaction surveillance for international wires by December 31. Failure to comply will result in an immediate $50,000,000 regulatory fine and suspension of Apex's international banking license. The project manager prepares a Business Case showing that the project will cost $8,000,000 to deliver and will generate $0 in direct commercial revenue or cost savings. The Project Executive considers rejecting the Business Case because the Net Present Value is negative.

Practitioner Evaluation:

• The Project Executive's assessment violates PRINCE2 principles for mandatory/regulatory projects. In a compliance scenario, return on investment is evaluated against risk avoidance and business survival.
• The $8,000,000 cost avoids a certain $50,000,000 fine and prevents catastrophic license revocation. The Business Case is fully justified on a mandatory compliance basis.
• The Project Board must focus on verifying whether the $8,000,000 option represents the most cost-effective and achievable compliance approach among viable alternatives.

---

Practitioner Exam Traps & Common Pitfalls

• Trap 1: Output Bias (Deliverable as Benefit): Scenario questions often present a statement like "The main benefit of the project was delivering the new warehouse by November 15." Delivering a facility is an output; the benefit is the advantage realized from using it (e.g., "Reducing regional freight transit costs by 22%"). Always reject options that confuse physical delivery with business benefits.
• Trap 2: Treating Dis-benefits as Project Risks: When a scenario describes a certain, unavoidable negative consequence (such as transitional disruption, scrap costs, or customer retraining downtime), exam distractors will suggest "logging this threat in the Risk Register and calculating contingency funds." Dis-benefits belong in the Business Case and Benefits Management Approach, not the Risk Register.
• Trap 3: Assuming Mandatory Projects Need No Business Case: Candidates often assume that because a project is legally required, a formal Business Case is unnecessary. PRINCE2 requires business justification for all projects. In mandatory initiatives, the Business Case justifies the selected delivery option and verifies that the cost of compliance does not exceed the cost of non-compliance.
• Trap 4: Conflating Customer and Supplier Business Cases: In commercial contracts, exam questions often test who owns which investment calculation. The customer's Project Executive owns the Business Case justifying the organizational investment; the supplier's Project Manager or Account Executive operates under a separate commercial business case ensuring contract profitability.