If the executive summary is the “front door” to your business case, the problem/opportunity and strategic context section is the foundation it stands on. Everything else—options, economics, risks, roadmap—assumes that you have accurately described (a) what is going on today, (b) what pain or opportunity that creates, and (c) why this matters in the context of the organization’s strategy and objectives.
Done well, this section lets decision-makers say, “Yes, that is the right problem to solve and the right opportunity to consider.” Done poorly, you invite debate about framing instead of substance, and reviewers will question every number that follows.
This chapter walks through how to define the baseline and pain/opportunity, anchor your case in strategy and OKRs, use evidence from customers and operations, and then write the section step by step—with a final checklist to pressure-test quality.
8.1 Defining the Baseline and Pain/Opportunity
The baseline is the “do nothing” world. It is what happens if you make no new decision beyond what is already committed. The pain/opportunity is the gap between that baseline and what you want or need to achieve.
You are not writing poetry here; you are defining the counterfactual against which all value will be measured.
What the baseline must capture
At a minimum, your baseline should make clear:
- Performance level: Where key metrics stand today (financial, customer, operational, risk) and how they are trending.
- Committed changes: What is already baked into plans (contracts, regulatory mandates, prior approvals) even if your case is not approved.
- Time horizon: Over what period the baseline is described (e.g., 3 years, 5 years), aligned to the modeling horizon.
- External assumptions: Any macro or market assumptions that matter (e.g., demand growth, inflation, regulatory deadlines).
The baseline is not “the past”; it is a projection of the status quo forward.
You usually need at least:
- A short narrative describing current performance and trends.
- 3–7 key metrics with their latest values and directions (up, down, flat).
- A sentence or two on external factors that are shaping the baseline.
Be explicit about what you treat as fixed versus variable: for example, existing contracts that cannot be exited without penalty, versus discretionary initiatives that could be slowed or stopped.
Defining the pain or opportunity
The pain is the cost, risk, or underperformance in the baseline. The opportunity is the upside you can realize versus that baseline.
You typically see pain or opportunity in a few recurring forms:
- Financial: Margin erosion, rising costs, revenue leakage, foregone growth.
- Customer or user: Dissatisfaction, churn, low adoption, poor experience.
- Operational: Bottlenecks, long cycle times, quality issues, safety incidents.
- Risk & compliance: Exposure to fines, outages, cyber incidents, regulatory breaches.
- Strategic position: Loss of share, disruption risk, inability to compete in a segment.
Your job is to make the stakes concrete:
- Quantify the pain or upside where possible (e.g., “costs growing 6% annually vs 2% volume growth”; “churn increased by 3 percentage points over 12 months”).
- Distinguish between symptoms (e.g., SLA breaches) and underlying drivers (e.g., capacity constraints, outdated systems).
- Describe the cost of inaction clearly: if we do nothing new, what gets worse, and how fast?
Common pitfalls
- No real baseline. A few anecdotes and a vague sense that “things aren’t great” are not enough.
- Wishful baselines. Assuming organic improvement without evidence (“we’ll probably get more efficient anyway”).
- Jumping to solutions. Turning the baseline section into an argument for a specific solution rather than a neutral description of reality.
- Overload. Drowning the reader in minor metrics that do not materially change the stakes.
If a decision-maker says, “I don’t recognize this description of our current situation,” stop and fix it. Alignment on baseline and pain/opportunity is a non-negotiable starting point.
8.2 Strategic Alignment and OKR Linkage
Once you have defined the baseline and the gap, you must show why this matters strategically. This prevents your case from looking like a local optimization or a pet project.
Linking to strategy
Strategy is a set of choices: where to play, how to win, and what capabilities and resources you will build to get there. Your case should:
- Name the strategic pillar(s) it supports (e.g., “digital customer experience,” “supply chain resilience,” “decarbonization”).
- Explain how addressing this problem/opportunity advances those choices (e.g., “allows us to win in the SME segment by cutting onboarding time in half”).
- Acknowledge any strategic tensions (e.g., cost efficiency vs. premium service, centralization vs. local autonomy).
This is not about copying bullets from a strategy slide; it is about showing that your initiative is one of the concrete moves that implement those strategic choices.
If your case appears to be in tension with stated strategy (e.g., proposing more customization when strategy favors standardization), be explicit. Either explain why this is a justified exception or how your case suggests that strategy might need updating.
Connecting to OKRs (or similar frameworks)
Many organizations use OKRs (Objectives and Key Results) or an equivalent performance framework. Use it to your advantage:
- Objective: Identify the one or two existing objectives your case contributes to (e.g., “Improve digital NPS for small business customers”).
- Key results: Map your case metrics to specific KRs (e.g., “Reduce onboarding time from 10 days to 3 days”; “Increase digital adoption from 40% to 70%”).
- Gaps: If current trajectories show that OKRs will not be met without additional action, say so; your case then becomes the vehicle to close that gap.
If you genuinely do not see a clear OKR linkage, consider:
- Is this initiative too small for a formal case?
- Are the OKRs incomplete or misaligned with strategy?
- Should you frame the case as an enabler of other OKRs rather than a direct driver?
In public sector or non-profit contexts, replace “OKRs” with mission goals and outcome metrics (e.g., outcomes for citizens, communities, beneficiaries). The logic is similar: show how the case moves the needles that matter.
Avoiding “strategy-washing”
It is easy to claim alignment to every strategic theme. That dilutes credibility. Focus on:
- One or two primary strategic links, not a laundry list.
- Clear causal stories (“this initiative will allow X, which directly supports Y strategic choice”) rather than generic language.
- Trade-offs, not just synergies. If pursuing this case means delaying or shrinking another strategic initiative, acknowledge it.
A short, honest paragraph on strategic alignment is far more convincing than a page of buzzwords.
8.3 Customer/User/Operational Evidence
You have framed the baseline and linked it to strategy. Now you must show that the problem or opportunity is real for customers, users, and operations—not just in your model.
Think of three lenses:
- Customer/user lens: How customers or users experience the current state.
- Operational lens: How internal processes and systems perform.
- External lens: How the environment or competitors behave.
Customer and user evidence
Customers and users are often the strongest proof that an issue matters:
- Quantitative measures such as NPS, CSAT, churn, usage/adoption, complaint rates, resolution times, abandonment rates.
- Qualitative evidence from interviews, surveys, support tickets, or frontline feedback.
- Behavioral data: what customers actually do (e.g., drop-off at step three, preference for competitor channels).
Good practice:
- Segment your evidence: by product, segment, geography, channel, or cohort if patterns differ.
- Show direction: trends over time, not just single snapshots.
- Use quotes sparingly to illustrate patterns if internal style allows, but do not rely on a handful of anecdotes.
Operational evidence
Operations tell you whether the organization can deliver on its promises:
- Volumes, throughput, cycle times, error/defect rates, rework, backlog size, SLA performance, overtime levels.
- Capacity utilization, bottleneck analyses, first-contact or first-time-right rates.
- Incident logs and root-cause analyses.
Connect operational data to customer or financial impact: for example, long cycle times leading to churn, or high error rates driving rework and cost.
Again, focus on the few metrics that really illuminate the pain or opportunity rather than cataloguing every KPI in the building.
External and benchmark evidence
External evidence can validate that your problem is real and that better performance is possible:
- Industry benchmarks for cost, productivity, or customer outcomes.
- Competitor behavior: features offered, service levels, pricing moves.
- Regulatory or market trends that increase urgency or create opportunity.
Use benchmarks judiciously:
- Make sure they are comparable (similar segments, geographies, business models).
- Present them as reference points, not absolute truths.
- Explain differences where they exist (“our mix is different; even so, the direction is clear”).
Common evidence mistakes
- Anecdote as proof. Using a few stories to stand in for the whole customer base.
- Average masking. Relying on averages that hide important segments (e.g., overall NPS flat, but key high-value segment deteriorating).
- Unattributed numbers. Presenting data with no clear source or owner, which finance or risk will later dispute.
- Misaligned metrics. Citing metrics that do not directly relate to the pain/opportunity you claim to address.
The goal is not to impress with the volume of data; it is to build confidence that your framing of the problem or opportunity is grounded in reality.
8.4 Step-by-Step Writing Guide
This section is where people often get stuck: they either write too much vague prose or fragment the story into unconnected data points. Use this simple sequence to draft a tight, compelling “Problem/Opportunity & Strategic Context” section.
Step 1 – Reconfirm the decision and category
Before drafting, remind yourself:
- What decision this case supports (from earlier chapters).
- Which category it sits in (Capex, growth, tech, operational, M&A, etc.).
This influences which baseline metrics and strategic pillars matter most.
Step 2 – Assemble the baseline facts
Collect:
- Current performance metrics (financial, customer, operational, risk) for the relevant scope.
- Trends over the last 12–36 months where available.
- Any committed changes already in motion that will affect the baseline.
Then write one short paragraph that:
- States where you are today in plain language.
- Notes the most important trend (improving, flat, deteriorating).
- Clarifies the time horizon for the baseline.
Avoid introducing any solution ideas here. You are simply stating the facts.
Step 3 – Quantify the pain or opportunity
Using the same data, plus any forecasts, articulate:
- The magnitude of the problem or opportunity (in monetary terms where possible, or in key KPIs).
- The direction of travel if nothing new is done.
- The cost or risk of inaction over the time horizon.
Write another short paragraph that makes the stakes clear:
- What happens to customers or users.
- What happens to economics or risk.
- How quickly things deteriorate or the window to capture opportunity closes.
This is where you make “why this matters” unavoidable, but you still do not recommend solutions.
Step 4 – Anchor in strategy and OKRs
Now connect to strategy:
- Identify the one or two strategic pillars this problem/opportunity touches.
- Show explicitly how failing to act would undermine those choices, or how acting would reinforce them.
- Link to specific OKRs or equivalent objectives where they exist.
Write a short paragraph that ties the earlier facts to strategy:
- Mention the named objective(s).
- Mention which key result metrics your case will move, in direction if not yet in precise magnitude.
- Acknowledge any major trade-offs or tensions.
Step 5 – Bring in customer/user/operational evidence
From your evidence base, pick 3–5 of the most compelling datapoints that support your narrative:
- At least one customer or user metric.
- At least one operational metric.
- Optionally, one external benchmark if it adds clarity.
These can be in a compact bulleted list if your format allows, or woven into the paragraphs. The key is to:
- Attribute each fact (source and timeframe).
- Show the link between the metric and the pain/opportunity.
- Avoid deep technical or methodological detail.
Step 6 – Keep solutions out (mostly)
Check for and remove:
- Specific solution names (vendors, systems, org designs) from this section.
- Detailed design features or implementation steps.
At most, you may hint at the nature of change required (e.g., “This will require a step-change in digital capability, not just incremental tuning”), but keep that high level. The next sections of the business case are where options and solutions belong.
Step 7 – Edit for clarity and brevity
Finally:
- Read the section as if you are a busy executive seeing it cold.
- Cut repetition; make sure each sentence adds new information.
- Replace jargon with plain language.
- Ensure the flow is: Baseline → Pain/Opportunity → Strategic alignment/OKRs → Evidence highlights.
Aim for:
- For a standard case: one to two pages total for this section.
- For an MVBC: half a page to one page.
If you find you need more space, push detail into an appendix and keep only the essentials here.
8.5 Context & Alignment Checklist
Use this checklist to test whether your “Problem/Opportunity & Strategic Context” section is ready. Adjust the depth by decision size, but do not skip the logic.
Baseline clarity
- The baseline describes the status quo projected forward, not just past performance.
- Time horizon and scope (business unit, geography, product, process) are clearly stated.
- At least 3–5 critical metrics are given with current values and trends.
- Committed changes already in motion are acknowledged.
Pain/opportunity and cost of inaction
- The pain or opportunity is quantified where possible (money, KPIs, risk exposure).
- The direction of travel if we do nothing is clearly described.
- The cost or risk of inaction over the horizon is explicit.
- Symptoms and deeper drivers are distinguished, at least at a high level.
Strategic alignment
- One or two specific strategic pillars or themes are named, not a generic “alignment to strategy.”
- The section explains how addressing this problem/opportunity advances those strategic choices.
- Any material trade-offs (e.g., cost vs. service, standardization vs. flexibility) are acknowledged.
- The initiative is positioned clearly as either core to strategy, enabling, or corrective (e.g., fixing a gap).
OKR or objective linkage
- Relevant objectives are named (business, mission, or policy objectives).
- The case links to specific key results or outcome metrics, not just general aspirations.
- Where trajectories show a gap to targets, the case positions itself as a way to close that gap.
- In public/NGO settings, the link to mission outcomes is explicit.
Customer/user/operational evidence
- At least one customer or user measure supports the pain/opportunity narrative.
- At least one operational measure supports it.
- External benchmarks or competitor moves are used sparingly and explained where necessary.
- Evidence is attributed (source, date) and not just “data says.”
- Averages do not hide important segment differences, or those differences are explicitly called out.
Neutrality of framing
- The section describes the problem/opportunity, not a specific solution.
- No vendor names, detailed technical designs, or org charts appear here.
- The tone invites multiple options to be considered; it does not assume a pre-chosen path.
Coherence and readability
- A senior reader could summarize the situation in 2–3 sentences after one read.
- The flow is logical: Baseline → Pain/Opportunity → Why now → Strategy/OKR link → Evidence.
- There is no obvious contradiction with the executive summary or other sections.
- The length is proportionate to decision size; detail that is not decision-critical has been pushed to appendices.
If you can tick these boxes, you have done the hard but often invisible work that makes the rest of the business case much easier to write—and much easier for decision-makers to trust.
