Technique Masterclasses

Business Paper 3 — Business Decisions and Strategy

Outcomes Guide

Provenance (written 2026-09-29). Built from research/veridian/WBS13-verified-facts.md (read in full — 2,057 lines, 12 located series Oct 2021–Oct 2025, mark schemes and examiner reports mined to varying depth per that file's own source table) and cross-checked against every file already in content/veridian/technique-hub/wbs13/ and the eight lesson files in content/veridian/curriculum/wbs13/ before writing a word, specifically so this document does not retread ground several sibling documents already cover in depth. ~/Downloads/FINSTO/ was checked directly for a WBS13 equivalent of the raw "THE DEFINITIVE GUIDE TO BUSINESS OUTCOMES" draft that forge-business-outcomes-guide.md (WBS12) verified against — none exists; that folder holds an outcomes-guide draft for WBS12 only (THE DEFINITIVE GUIDE TO BUSINESS OUTCOMES — WBS12.md), plus a macro-outcomes guide for WEC12 (Economics). There is therefore no raw WBS13 source to verify here — this document is built directly from primary-verified material, not a checked transcription of someone else's draft, so it carries no "what failed verification" ledger the way the WBS12 sibling does.

What is already covered elsewhere, and is not repeated here at the same depth: the specific discipline of matching a labour-turnover argument to the turnover mechanism rather than the productivity/motivation one (forge-vocabulary-precision-list.md Part 3, signal-topic-brief- assessing-competitiveness.md, codex-deep-dive-assessing-competitiveness.md — three separate documents already narrate this at length); the conceptual distinction between a margin ratio (divides by revenue) and ROCE (divides by capital employed) (codex-deep-dive-assessing-competitiveness.md §3d); the risk-assessment-vs-risk-mitigation split within contingency planning, already taught with its own worked contrast (British Airways vs Tesla) directly in managing-change.ts's teach block and flashcard deck; the breadth-vs-depth discriminator on stakeholder and SWOT questions (codex-deep-dive-business-objectives-and-strategy.md, codex-deep-dive-influences-on-business- decisions.md, codex-definitions-and-application-bank.md); EMV as a decision-tree output and its sensitivity to the underlying probability estimate (codex-deep-dive-decision-trees-cpa-and- contribution.md §1.4–1.6); and the full Stellantis and Five Guys worked chains (forge-chains-guide.md). Each is cited below, briefly, rather than re-narrated. This document's own contribution is the organising lens itself — no existing WBS13 document collects the paper's real outcome-categories (financial, growth/competitive, human-capital, risk/continuity, decision- technique) onto one page and states, category by category, what actually has to be said for an outcome to reach the top band — plus one specific synthesis (§4) connecting three separately-taught mechanism-matching traps into a single, named discipline, and an honest account of where the primary- source evidence for this framing genuinely runs out (closing section).

Business Outcomes — WBS13

A cross-cutting reference, not a re-teach: how examiners want a financial, operational, human, or competitive consequence actually landed — stated with the right unit, compared against something, and tied to the specific business in the extract rather than asserted generically. This assumes the curriculum files' spec content and the technique-hub's existing tariff/chain/precision documents; it does not restate any of them.

1. What "landing on an outcome" means on this paper

WBS13's level descriptors use the same verified language as every other Business unit: a response needs "chains of reasoning… showing cause(s) and/or effect(s)," and the higher levels need those chains "developed" and the assessment "balanced… showing an awareness of competing arguments." Two facts specific to this paper change how that plays out in practice:

The consequence for an "outcome" specifically: a chain that reaches some named business consequence is not the same as a chain that reaches the one the question names. Two real examples, from opposite ends of the paper, show this isn't a stylistic preference:

2. Financial performance outcomes — a number is not yet an outcome

The paper's calculation questions (gearing, ROCE, current ratio, labour productivity, ARR, YED) each carry their own well-documented unit-precision traps — omitting the % sign, omitting ×100, missing a specified decimal place, using the wrong unit name. These are real, examiner-confirmed, and already compiled in one place (forge-vocabulary-precision-list.md Part 2); this document does not repeat them.

What is worth stating here, because no existing WBS13 document states it directly: a correctly- stated ratio is still not a landed outcome until it is compared against something, and this paper's own primary sources give far less to compare against than WBS12's do. WBS12's mark schemes state a Pearson-sourced "ideal" range for the current ratio (1.5:1–2:1) and the acid test ratio (at or above 1:1) directly. No equivalent Pearson-stated benchmark for any WBS13 ratio — gearing, current ratio, ROCE, or the profitability margins — was found anywhere in this course's mined material. This is a genuine, checked absence, not an oversight in what to search for: the facts bank's own quantitative- formulas table records worked figures (Spotify's gearing at 45.03%; Five Guys' ROCE at 21.15%; Brompton Bikes' current ratio at 3.26) but never a stated "this is high/low/healthy" threshold to read them against. A chain that states "gearing is 45.03%, which is high" is asserting a judgement this paper's own sources do not hand you for free — the only comparators this paper's mark schemes actually supply are relative ones already in the specific extract: a prior year's figure, a named competitor, or a stated trend. Two real instances confirm this is the pattern examiners reward: the Peloton exemplar (§3 below) succeeds by setting one operating-margin figure (3.73%) against the scale and cost of a specific acquisition, not against an abstract benchmark; the Stellantis chain succeeds by setting one CEO's pay against a named rival's, not against a stated "reasonable pay" figure. The transferable rule: when this paper gives you a ratio, look for the comparator already sitting in the same extract before reaching for an external rule of thumb — because for WBS13 specifically, unlike WBS12, there usually isn't one to reach for.

3. Growth and competitive-positioning outcomes — landing on a named consequence, not a generic one

Two real questions on inorganic growth show the same structural requirement WBS12's own outcomes guide found for its paper: a chain has to land on a stated consequence for this business, not a generic "problems will occur." Both worked examples already exist at full length elsewhere (codex-deep-dive-business-growth.md), so only the landing discipline they demonstrate is drawn out here:

A third, structurally different case is worth flagging on its own terms: the same fact can be credited as evidence for two opposite outcomes, depending which strategic lens frames it. Superdry's real range cut (from 4,000 to 1,600 clothing items — verified as exactly a three-fifths reduction) is double-credited in the October 2025 Porter's Strategic Matrix question (Q2, 20-mark Evaluate): the same cut supports a differentiation argument (sharper focus on fewer, more distinctive pieces) and a cost-leadership argument (lower production and operating cost) simultaneously, and either conclusion — differentiation or cost leadership as "the better strategy" — is credited. This is already taught in business-objectives-and-strategy.ts as an instance of "stuck in the middle" theory; the outcomes-level point worth adding is narrower and general: when one fact in an extract can support either of two opposing outcomes, the mark is not for picking the "right" one — it is for stating explicitly which outcome that fact is being used to support, and following that specific chain through, rather than citing the fact once and leaving its implication for either side unstated.

A related caution from the same topic area: Porter's five forces, applied to Apple Watch against Google/Fitbit's smartwatch share (June 2023 Q2, 20-mark Evaluate), reaches a real, credited limitation that the framework alone "doesn't give us a good idea about the market conditions" — an 18/20 exemplar pairs it with PESTLE rather than treating the five-forces outcome as sufficient on its own. The transferable point: some frameworks on this paper produce an outcome (a competitive-position assessment) that the mark scheme itself flags as incomplete without a second, named framework — Porter's five forces needing PESTLE is one confirmed instance; SWOT needing Ansoff's Matrix or Porter's Strategic Matrix (Bosch, Summer 2024 Q1d) is a second, independently confirmed instance of the identical pattern on a completely different question.

4. One discipline, three names: matching the outcome-word to what the question actually asks

Three separate spec areas — human resources, risk management, and stakeholder/SWOT breadth — each carry an examiner-confirmed trap that, read side by side, is the same underlying discipline stated three different ways. As far as this course's existing WBS13 material shows, no document currently states this as one connected principle; each is taught, correctly, inside its own topic. Naming the connection is this section's contribution — not a new fact, a new synthesis of three already-verified ones:

  1. Human resources (already covered in depth: forge-vocabulary-precision-list.md Part 3, codex-deep-dive-assessing-competitiveness.md). A question naming labour turnover is not credited for a chain that reasons correctly to productivity or motivation instead — confirmed, in near-identical examiner wording, on two separate real questions (Lush's employee share ownership, June 2023; Five Guys' financial rewards, Oct 2023). The Mears Group consultation question (Oct 2025 Q3) is the useful contrast case: it names productivity specifically, and its own indicative content correctly stays on the productivity mechanism throughout — the same discipline working in the other direction.
  2. Risk management (already covered in depth: managing-change.ts's own teach block and flashcard). Spec point 3.3.6.2 splits into two named stages — risk assessment (identifying a threat before it happens) and risk mitigation (having a plan once it's identified). British Airways' contingency-planning question (Oct 2021 Q1d) is a mitigation-stage question; Tesla's loss- of-key-staff question (Oct 2025 Q1d) is squarely an assessment-stage one — asking candidates to assess how far a risk assessment could have prevented those specific departures. A chain built for one stage does not automatically transfer to the other: BA's real limitation is that a plan, once built, still "cannot cover every eventuality"; Tesla's is that some departures are driven by personal factors "a risk assessment might not be able to predict" in the first place — a limitation on what the assessment stage can discover, not on maintaining a plan once a risk is already named. Naming the wrong stage's limitation for the question actually asked is the same category of error as arguing productivity into a turnover question.
  3. Breadth vs depth (already covered: codex-deep-dive-business-objectives-and-strategy.md, codex-deep-dive-influences-on-business-decisions.md). Two unrelated real questions — Bosch's SWOT analysis (Summer 2024 Q1d) and Lush's stakeholder-impact assessment (June 2023 Q1e) — each independently confirm that covering every category (all four SWOT quadrants; every stakeholder group in the extract) is not what the mark scheme rewards. The Bosch examiner report states plainly that covering all four aspects was "not necessary… to achieve level 4"; the Lush mark scheme correspondingly does not count the number of stakeholder groups addressed. In both cases, the discriminator moves from how many categories a response touches to how far one chain of reasoning is developed — a third, independently-confirmed instance of the same pattern: the outcome the mark scheme wants is not the one that looks most thorough on the page.

The common thread across all three: this paper repeatedly rewards precision about which specific outcome a question names — a named HR effect, a named risk-management stage, or reasoning depth over category coverage — over a correct-but-adjacent outcome reached by otherwise sound reasoning. That precision is worth checking for explicitly before writing, on any topic, not only the three above.

5. Risk-and-continuity outcomes — the ceiling every stage shares

Beyond the assessment/mitigation split in §4, one further pattern recurs across every risk-management question this course's research has found, worth stating because it applies regardless of which stage the question names: the mark scheme itself credits the limitation that its own tool cannot fully close. British Airways' contingency plans still leave failures "still occurring." Tesla's risk assessment cannot predict a departure "influenced by personal factors." Succession planning at Pets at Home carries a stated cost (training time, finding a willing successor) that is real regardless of how well the plan is built. None of these questions credits a chain that treats its named tool as removing the risk outright — every one of them is credited for stating the tool's real limit, specific to the business in the extract, as part of the outcome itself. One further real data point worth flagging on relative difficulty: the Pets at Home succession-planning question scored measurably worse than the adjacent portfolio-analysis question in the same series, per the examiner report's own comparison — a signal that this specific outcome (weighing a mitigation plan's benefit against its real cost) is a harder landing for candidates than some of this paper's other 12-mark topics, not just an abstractly "hard" spec point.

6. Decision-technique outputs — when the outcome is a number, not a narrative

Two spec points produce a genuinely different kind of outcome from every category above: critical path analysis and decision trees each generate a specific calculated figure — a project duration, an Expected Monetary Value — and the mark scheme's own reward structure treats reaching that figure as only half the outcome. The calculation mechanics and the full worked sensitivity analysis already exist in codex-deep-dive-decision-trees-cpa-and-contribution.md; the outcomes-level point is what happens after the number:

The transferable rule for this category specifically: a correct number is the floor, not the outcome. The mark scheme's own indicative content pairs the number with a stated decision (which option; what to do with the float) and a stated limitation specific to how that number was produced (a probability that could go the other way; a network that doesn't transfer to a different site) — landing on the number alone, without either half, is not the outcome these questions are actually built to reward.

7. Matching the outcome to the question — a checklist, not a Pearson rule

Not attributed to Pearson — this document's own synthesis, offered as a checklist rather than a rule, built only from the verified anchors above and in the documents it cross-references:

  1. What outcome word, or risk-management stage, does the question itself name — turnover not productivity; assessment not mitigation; revenue not market share; differentiation not cost leadership (or vice versa, explicitly)? That word is very often the required landing point, and a chain that reasons correctly to a different, related outcome has not answered the question asked (§4).
  2. Does the ratio or figure you've calculated have a comparator already sitting in the same extract — a prior year, a named rival, a stated trend? WBS13's own sources rarely hand you an external benchmark to fall back on instead (§2).
  3. If two opposing conclusions could both use the same fact in the extract, have you stated which outcome that fact is supporting, and followed that specific chain through, rather than citing the fact once and leaving its implication unstated for either side (§3)?
  4. If your answer rests on a named tool (SWOT, a risk assessment, a contingency plan, CPA, a decision tree), have you stated the tool's own real limit for this business, rather than treating the tool as removing the problem outright (§5)?
  5. If the outcome is a calculated figure, have you paired it with a stated decision and a stated limitation specific to how that figure was produced — not left it standing alone as the answer (§6)?

What this document does not cover, and why

Per this course's standing rule against forcing content where the primary-source evidence has run out: three areas that would belong in a complete "outcomes" picture for this paper have no primary- source anchor in any series this course's research has mined, and are flagged rather than invented.

None of these is asserted to be untested by Pearson — only that this course's own research has not yet located a primary-source example for any of them, and a future mining pass (the Jan 2022 question paper, confirmed to exist and still substantially unread per WBS13-verified-facts.md's own Flagged Issues list, is the natural next target) is the honest way to close them, not a guess standing in their place here.