Structured Business Case Development

Purpose

Translate A1.1–A1.4 analytical outputs into a decision-ready organisational justification that enables governance bodies to make informed approval decisions. The business case answers three executive questions: Why does this need matter now? What resources are required? What returns and risks are we accepting?

Unlike A1.4 Need Exploration Reports—which synthesise analytical findings for innovation teams—the business case restructures the same evidence into decision language: strategic rationale connecting need to organisational objectives, financial projections quantifying opportunity and risk, and resource specifications enabling commitment verification. The pyramid principle governs structure: lead with recommendation, support with key arguments, back with evidence.

When to Use

Use structured business case development when:

• A1.4 recommends Pursue—the need requires governance approval and resource allocation before entering A2 Ideation
• Initiative requires budget allocation, dedicated team members, or executive sponsorship (not exploratory / self-funded)
• Governance body (I2) requires formal submission with financial analysis and risk assessment
• Multiple stakeholders must align on problem significance, resource commitment, and success criteria before solution development begins
• Portfolio impact assessment is needed—approval affects organisational capacity, balance, or dependencies (I1)

Do NOT use when:

• Initiative is small enough for delegated approval (50K, 3 FTE, 3 months)—use abbreviated 2-page brief instead
• A1.4 recommends Decline—no business case needed; document rationale in A1.4 report
• Executive champion with full authority has already committed resources—business case may still be wise (precedent, accountability) but is not gatekeeping
• Exploratory work within existing team capacity—does not require governance approval

Sample Size and Duration

Participants: 2–4 people

• Essential: Innovation Manager (author, accountable for quality), domain expert (financial modelling input)
• Recommended: Executive sponsor (strategic framing, governance positioning), finance analyst (ROI validation)

Duration by complexity:

• Fast-track (precedent exists, template reuse): 2–3 days
• Standard (new case, financial modelling required): 5–7 days
• Extended (complex financials, supplemental research needed): 8–10 days

Typical time allocation:

• 30% Financial modelling (Step 3)
• 25% Strategic rationale (Steps 1–2)
• 20% Risk assessment (Step 5)
• 15% Resource specification (Step 4)
• 10% Executive summary and review (Steps 1, 7)

Prerequisites

• A1.4 Need Exploration Report: Strategic fit scorecard, feasibility assessment, white-space analysis, Pursue recommendation
• A1.2–A1.3 artifacts: User research findings, problem definition brief, need statement, success criteria
• Financial data: Organisational discount rate, budget cycle timing, comparable initiative costs (if available)
• Portfolio context: I1 current portfolio utilisation, balance targets (70/20/10), capacity model
• B1 strategic priorities: Current strategic themes, resource allocation guidelines
• Participants: Innovation Manager (author), domain expert (financial modelling input), executive sponsor (strategic framing guidance)
• Time: 3–10 days depending on complexity (see Sample Size and Duration)

Complete Procedure

Step 1: Structure the Document Using Pyramid Principle (1–2 hours)

Apply top-down storytelling : start with the governing recommendation, support with 3–4 key arguments, and back each argument with A1.1–A1.4 evidence.

Standard business case sections:

Executive summary quality test: Can a governance member make an informed Go / No-Go decision reading only the executive summary? If not, revise until decision-sufficient.

Step 2: Draft Strategic Context (2–4 hours)

Connect the need to organisational strategy and portfolio :

1. Link need to specific B1 strategic priorities (quote priority language, not generic “aligns with strategy”)
2. Show portfolio fit: where does this initiative sit in core / adjacent / transformational mix? Does approval move portfolio toward or away from 70/20/10 targets?
3. Describe competitive context: what happens if organisation does not address this need? (competitor advantage, market window closing, customer attrition)
4. Position relative to existing portfolio: does this reinforce a strategic theme (clustering amplifies impact) or open a new one (resource spread)?

Step 3: Build Financial Analysis (4–8 hours)

Apply Method: Scenario-Based Financial Modelling (the referenced method). Produce the financial analysis section of the business case: 3-scenario ROI table, sensitivity analysis, documented assumptions, and minimum viability threshold.

Step 4: Specify Resource Requirements (2–3 hours)

Convert vague resource needs into commitment-ready specifications :

1. Budget breakdown: major cost categories (development, infrastructure, launch, ongoing operations) with line-item estimates
2. Team composition: named roles (not “resources TBD”), FTE allocation, duration, sourcing department
3. Functional support: specific commitments needed from IT, Legal, Marketing, Sales, Operations—what, when, how much
4. Timeline: milestones from A2 start through A7 launch, with key dependencies and decision gates
5. Commitment verification: for each resource line, identify who must sign off (budget owner, functional leader, HR)

Specificity test: Can someone reading the resource section open a purchase order, post a job requisition, and book a conference room? If not, it is too vague.

Step 5: Conduct Risk Assessment (2–4 hours)

Apply Method: Risk and Assumption Mapping (the referenced method). Produce the risk section of the business case: top 5–8 risks with likelihood, impact, and mitigation; assumption register linking critical assumptions to A2 validation activities .

Step 6: Assess Portfolio Impact (1–2 hours)

Apply Method: Portfolio Impact Assessment (the referenced method). Produce a single-page portfolio impact summary: capacity before/after, balance before/after, key dependencies, and any trade-offs (de-prioritisation of existing projects).

Step 7: Internal Review and Presentation Deck (3–5 hours)

1. Team reviews for consistency with A1.1–A1.4 artifacts, financial accuracy, and executive-summary sufficiency
2. Verify all Gate A1.5-1 checklist items are addressed
3. Prepare 15–20 slide presentation deck mirroring business case structure for stakeholder engagement (A1.5 Step 3) and governance presentation (A1.5 Step 4; see also Method: Governance Presentation Design, the referenced method)
4. Rehearse presentation with executive sponsor; agree on negotiation boundaries (acceptable scope / budget adjustments)

Quality Criteria

Excellent business case demonstrates:

1. Decision-sufficient executive summary: Governance member can make informed Go / No-Go from summary alone—recommendation, rationale, ask, and risk all present
2. Strategic grounding: Need connected to specific B1 priorities using strategic language (not generic “aligns with strategy”)
3. Scenario-based financials: 3-scenario ROI present (see Method: Scenario-Based Financial Modelling, the referenced method)
4. Commitment-ready resources: Named roles, FTE counts, budget line items, functional commitments—not TBD
5. Comprehensive risk coverage: All four risk categories assessed (see Method: Risk and Assumption Mapping, the referenced method)
6. Portfolio awareness: Impact on capacity, balance, and dependencies explicitly addressed (see Method: Portfolio Impact Assessment, the referenced method)
7. Assumption transparency: Every key assumption listed with source, confidence level, and A2 validation plan
8. Problem-led framing: 80% problem justification, 20% solution direction—does not constrain A2 creativity

Theoretical Foundation

Seminal references:

• : Established the pyramid principle for executive communication— lead with recommendation, support with logically grouped arguments, back with evidence. Provides the structural logic for business case organisation: executives process information top-down, so documents must present conclusions before supporting detail. Originally published 1987; remains the standard for management consulting and corporate communication.
• : Defined the business case as the key deliverable at Stage-Gate decision points, establishing that effective gates require both a compelling case (strategic rationale, financial projections) and verified readiness (resources committed, risks assessed). Demonstrated that business case quality at gates is the single strongest predictor of new product success across industries.
• : Introduced the concept of the “heavyweight project manager” and the aggregate project plan, showing that resource specification in business cases must go beyond budget to include named individuals, functional commitments, and timeline dependencies. Projects approved with vague resources fail during execution.

Contemporary references:

• : Updated Stage-Gate research across 400+ firms, confirming that business cases with 3-scenario financial analysis, explicit risk mitigation, and commitment-ready resource specifications achieve 2.5× higher success rates than single-point ROI cases. Introduced “gates with teeth”— governance criteria that reject incomplete cases rather than approving conditionally.
• : Reframed strategy as a set of integrated choices (where to play, how to win), providing the logic for business case strategic context sections: cases must demonstrate not only that a need is valid but that it fits the organisation's strategic choice cascade.
• : Extended Lean Startup principles to business case development, arguing that early-stage business cases should foreground assumptions and validation plans rather than false-precision financial forecasts. Influences the assumption register and A2 validation linkage in Step 5.

Challenges and Solutions

Challenge 1: Comprehensiveness vs. Conciseness

Symptoms:

• 40-page business case that busy executives don't read
• OR 2-page summary leaving executives with unanswered questions that delay approval

Solutions:

• Apply pyramid principle : decision-sufficient executive summary (2 pages) + detailed body (8–12 pages) + appendices (reference only)
• Test: give executive summary to someone unfamiliar with the project—can they explain the recommendation and rationale?
• Keep main body under 15 pages; move all supporting analysis to appendices

Challenge 2: Vague Resource Requirements

Symptoms:

• “IT support as needed,” “a small team,” “budget TBD”
• Governance approves but no one can execute because commitments are unspecified

Solutions:

• Enforce specificity test (Step 4): named roles, FTE counts, budget line items, functional commitments with owners
• If exact figures unknown, provide range with assumptions (“3–5 FTE depending on build vs. buy decision in A2”) rather than TBD
• Gate A1.5-1 checklist should reject cases with unspecified resources

Challenge 3: Solution-Focused Instead of Problem-Focused

Symptoms:

• Business case describes what to build in detail but provides thin justification for why
• Prematurely constrains A2 ideation creativity

Solutions:

• Solution approach section should be 1 page maximum—high-level direction, not specification
• Lead with problem significance and strategic rationale (80% of case); solution approach is boundary-setting only
• Use language like “solution space includes…” rather than “we will build…”

Relationship to Other Methods

Structured Business Case Development receives input from:

• A1.4 Need Exploration Report: Strategic fit scorecard, feasibility assessment, Pursue recommendation
• A1.2 User Research: Customer evidence, market sizing, willingness-to-pay data
• A1.3 Problem Definition: Need statement, root causes, success criteria, boundary definition
• I1 Portfolio Management: Capacity data, balance targets, dependency map
• B1 Strategic Leadership: Strategic priorities, resource allocation guidelines

Structured Business Case Development calls:

• Scenario-Based Financial Modelling (the referenced method): Produces financial analysis section (Step 3)
• Risk and Assumption Mapping (the referenced method): Produces risk section (Step 5)
• Portfolio Impact Assessment (the referenced method): Produces portfolio impact summary (Step 6)

Structured Business Case Development provides input to:

• Stakeholder Analysis and Engagement Design (the referenced method): Business case is the artefact stakeholder engagement revolves around
• Governance Presentation Design (the referenced method): Business case content structures governance deck
• Project Charter (A1.5 Step 5): Approved business case becomes basis for charter
• A2 Ideation: Solution approach boundaries and success criteria frame ideation scope

Example: Digital Patient Engagement Platform

Context: Medical device company validated need for digital patient engagement in orthopaedic recovery (A1.2: 28 interviews, 12 observations). A1.4 scored 13/15 strategic fit, recommended Pursue.

Executive summary (condensed):

Recommendation: Approve 1.8M, 8-person team, 14-month programme to develop digital patient engagement platform for orthopaedic recovery.

Key arguments: (1) Validated clinical need—42% of patients miss rehabilitation milestones, 18% experience preventable complications (A1.2); (2) Strategic fit—aligns with B1 “Connected Care” priority, adjacent innovation extending device portfolio into digital services (A1.4: 13/15); (3) Market opportunity—340M TAM in EU orthopaedics, no dominant incumbent; (4) Feasibility confirmed—technical POC validated in A1.4, regulatory pathway identified (MDR Class IIa).

Ask: 650K Phase 1 (clinical validation + MVP, 8 months), with Phase 2 (1.15M, 6 months) contingent on Phase 1 clinical outcomes.

Resource specification (condensed):

Tools and Templates

• A1.5 Business Case Template (the referenced method)
• Gate A1.5-1 Checklist (the referenced method)
• Pyramid principle storyboarding : sticky notes or slide sorter for argument structure
• Comparable initiative database: prior business cases for benchmarking cost, timeline, ROI ranges

• A. G. Lafley & R. L. Martin (2013). Playing to Win: How Strategy Really Works. Harvard Business Review Press.
• B. Minto (2009). The Pyramid Principle: Logic in Writing and Thinking. 3rd ed. Pearson Education.
• D. J. Bland & A. Osterwalder (2020). Testing Business Ideas. Wiley.
• R. G. Cooper (2001). Winning at New Products: Accelerating the Process from Idea to Launch. 3rd ed. Basic Books.
• R. G. Cooper (2017). Winning at New Products: Creating Value Through Innovation. 4 ed. Basic Books.
• S. C. Wheelwright & K. B. Clark (1992). Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality. Free Press.