Business and consulting foundations

Executive summary

Stage 1 is where AI Solution Engineering separates from “model enthusiasm.” Before you judge RAG chunk sizes or agent orchestration, you must explain why an organisation should invest, what strategic theme the investment serves, who decides and cares, and how success is measured in language finance already uses. Completing this stage means you can walk into a CFO or COO conversation with a value hypothesis, strategic alignment, discovery artefacts, and stakeholder map—not a demo.

Outcome

Primary outcome: You can explain why a client should invest in an AI solution—with credible linkage to strategy, P&L or risk metrics, stakeholder interests, and delivery realism.

Secondary outcomes:

• Produce Stage 1 core deliverables (value hypothesis, alignment statement, problem definition, opportunity shortlist, stakeholder map, executive summary) without vendor-first framing.
• Pass a peer or manager challenge session using the question lists from topics 01–05 and 27–28.
• Know when to stop or defer a use case based on weak economics or strategic misalignment—not only technical infeasibility.

Stage 1 does not require you to build production AI. It requires you to earn the right to design it.

Who Stage 1 is for

Profile	Typical gap	Stage 1 fix
Strong engineer, weak commercial	Can build RAG; cannot size payback	Topics 01, 07, Business Learning
Strong consultant, weak AI realism	Great slides; vague feasibility	Topics 04, 05, then Stage 2
Domain expert, weak exec communication	Deep insurance/banking; loses room at 10 min	Topics 27, 28
New to big-four delivery	Unfamiliar with steering committees	Topics 04, 27, consulting Guide

Entry criteria

Start Stage 1 (or restart it) when any of the following are true:

• You cannot state how the client makes money and which three KPIs matter this year.
• A sponsor asks for “AI” without a problem owner, baseline metric, or budget line.
• Discovery workshops produce features, not jobs, metrics, and decisions.
• You are about to propose architecture (Stage 3) or models (Stage 2) without a value hypothesis and alignment statement.
• Stakeholder conflict is already visible (IT vs business, BU vs group, risk vs innovation).

Minimum entry artefact: one page on the client or practice sector—business model, strategic themes, top KPIs— even if sourced from public filings.

Exit criteria

Declare Stage 1 complete only when all exit checks pass:

Artefacts (minimum set)

Artefact	Source topic	Pass test
Value hypothesis one-pager	01	Names P&L line, KPI, £ range, payback range
Strategic alignment statement	02	Tied to documented corporate/BU theme
Industry/context brief	03	Value chain, regulation, key roles
Problem definition / issue tree	04	Decision-focused, not solution-led
AI opportunity shortlist (scored)	05	Includes stopped ideas with reasons
Stakeholder map + comms plan	27	Power/interest, messages per audience
Executive summary (2 pages max)	28	Readable by COO/CFO in 5 minutes

Knowledge checks

• Answer ≥10/12 randomly chosen questions from topics 01, 02, and 05 without notes.
• Explain one negative case from topics 01 or 02 using a client-relevant example.
• Run VALUE gate self-check on value hypothesis—no critical gaps.

Behavioural checks

• You have not led with vendor or model names in the last two client readouts.
• A peer reviewer confirms artefacts are filed in your pattern library with date and sector tag.

Exit is not “I read the pages.” Exit is artefacts reviewed.

Capability map

Stage 1 spans seven numbered topics plus the Business Learning practice pack. Use this map to see how topics reinforce each other—not as a reading order only.

Topic 01 — Business Fundamentals

Capability: Translate AI into economics—business models, margin, CAPEX/OPEX, unit economics, ROI/NPV/payback, TCO, cost of delay, KPIs/OKRs/SLAs, CSAT/NPS, leading vs lagging indicators.

You know it when: You can size a servicing or claims opportunity in £ range with explicit assumptions and survive CFO questions on payback and adoption.

Core deliverables: Value hypothesis, baseline metric set, payback sketch.

Deep link: Business Fundamentals

Topic 02 — Business Strategy

Capability: Connect use cases to corporate and BU strategy—differentiation vs cost leadership, operating models, value chains, build/buy/partner, SWOT/PESTLE/Porter/BMC/JTBD/Wardley/Three Horizons/Playing to Win.

You know it when: You can stop a misaligned use case with strategy logic and draft a one-page alignment execs recognise.

Core deliverables: Strategic alignment statement, opportunity map, build-vs-buy note.

Deep link: Business Strategy

Topic 03 — Industry and Domain Knowledge

Capability: Speak the sector language—value chains, regulatory bodies, typical roles, domain metrics (e.g. combined ratio, cost-to-serve, AHT, loss ratio), and competitive dynamics.

You know it when: You use correct KPI names and definitions in workshops; you do not confuse retail banking with investment banking metrics.

Core deliverables: Domain context brief, glossary, process sketch for target value stream.

Deep link: Industry and Domain Knowledge

Topic 04 — Consulting and Problem Solving

Capability: Structure ambiguity—issue trees, hypotheses, interview guides, workshop facilitation, decision criteria, and meeting outputs that drive decisions not discussion.

You know it when: After your workshop, the sponsor can name the decision, options, and next step—not only “great insights.”

Core deliverables: Problem definition, issue tree, workshop notes with decisions.

Deep link: Consulting and Problem Solving

Topic 05 — AI Opportunity Discovery

Capability: Facilitate ideation → prioritisation with scoring dimensions (value, feasibility, risk, strategic fit, time-to-value); pre-filter before deep technical spike.

You know it when: Opportunity backlog includes scores, owners, and killed ideas—not a flat list of 40 GenAI wishes.

Core deliverables: Scored opportunity backlog, discovery summary, recommended next phase.

Deep link: AI Opportunity Discovery

Topic 27 — Stakeholder Management

Capability: Map power, interest, incentives; anticipate blockers (risk, finance, unions, data owners); build coalitions; manage steering committees without surprise objections.

You know it when: You predicted two objections in advance and pre-wired responses with allied sponsors.

Core deliverables: Stakeholder map, engagement plan, RACI for decisions.

Deep link: Stakeholder Management

Topic 28 — Communication and Executive Articulation

Capability: Craft executive narrative—pyramid principle, 2-page summaries, board-safe language, Q&A prep, slide discipline (headline messages, not bullet dumps).

You know it when: A time-boxed 5-minute COO readout lands the ask and metric without demo dependency.

Core deliverables: Executive summary, steering deck outline, Q&A sheet.

Deep link: Communication and Executive Articulation

Topics in this stage (quick index)

1. Business Fundamentals
2. Business Strategy
3. Industry and Domain Knowledge
4. Consulting and Problem Solving
5. AI Opportunity Discovery
6. Stakeholder Management
7. Communication and Executive Articulation

Practice pack: Business Learning

Stage 1 theory lives in topics 01–05 and 27–28. Business Learning adds sector fluency, vocabulary, briefing depth, and workbook practice—use it when:

• You are engaging financial services, insurance, retail, or health and need credible domain shorthand fast.
• You want a downloadable workbook to rehearse KPI and process exercises before client workshops.
• Your gap is vocabulary under pressure (exec meetings, steering committees), not framework theory.

Recommended Business Learning path during Stage 1:

Step	Resource	Purpose
1	Business Learning overview	Navigate packs and method
2	Business briefing	Sector economics and AI context
3	Business Keywords	Fast reference for meetings
4	Domain Knowledge workbook	Excel practice—metrics and processes

Do not treat Business Learning as a substitute for topic artefacts—it deepens topic 03 and reinforces topic 01 KPI language.

Recommended practice sequence

Sequence A — Standard (4 weeks, ~6–8 hours/week)

Week	Focus	Outputs due
1	Topics 01–02 + Business Learning keywords skim	Value hypothesis + alignment statement for practice client
2	Topics 03–04 + domain workbook sprint	Domain brief + issue tree
3	Topic 05 + stakeholder pre-work	Scored opportunity backlog (≥8 ideas, ≥2 stopped)
4	Topics 27–28 + VALUE self-check	Stakeholder map + 2-page exec summary

Sequence B — Live engagement crash (2 weeks)

Use when staffed on a client with weak Stage 1 artefacts:

1. Day 1–2: Topic 01 payback sketch on live KPI (even rough).
2. Day 3–4: Topic 02 alignment + kill misaligned scope.
3. Day 5: Topic 27 stakeholder map and comms plan.
4. Week 2: Topics 04–05 workshops; topic 28 exec readout prep.
5. Parallel: Business Learning keywords for sector.

Rule: No architecture review until value hypothesis and alignment exist in writing.

Sequence C — Interview prep (2 weeks)

1. Topics 01, 02, 05 — scenarios + questions only.
2. Topic 28 — 5-minute narrative practice.
3. Business Learning briefing — sector story.
4. Mock case: 90-minute “should the bank fund this AI programme?”

Integration with Guide and 8D

Stage 1 maps to early 8D and Guide chapters—study capability here, execute patterns there.

Stage 1 capability	Guide / framework
Value hypothesis, payback	Business case
Problem framing, workshops	Discovery, Consulting
Quality bar for value evidence	VALUE gate
Methodology spine	8D Framework — Define, Diagnose

Deep-link rule: Learning Map teaches skill; Guide walks delivery steps. Do not duplicate full Guide chapters in your notes—link and practise artefacts.

Common failure modes

Failure mode	How it shows up	Fix
Skip to Stage 2	Architecture and model debates with no KPI	Block technical deep dive until topic 01 artefact exists
Vendor-first discovery	Opportunities are product features	Ban vendor names in first two workshops
Strategy wallpaper	Alignment claims without doc citation	Quote annual report themes verbatim
KPI tourism	Metrics listed but not owned or baselined	KPI dictionary with owner + cadence
Stakeholder surprise	Risk/finance veto at gate 2	Topic 27 map before business case
Exec summary as tech spec	20 slides on embeddings	Topic 28: 2 pages, pyramid structure
Reading without artefacts	“Done” checkboxes, empty pattern library	Manager review of filed outputs
Domain cosplay	Jargon without definitions	Business Learning + topic 03 brief
Opportunity hoarding	30 ideas, zero stopped	Scoring template with kill column
Consulting theatre	Workshops with no decision log	Topic 04 decision record template

Stage 1 anti-pattern: the demo-led sell

A team opens with a polished assistant demo. Sponsors engage emotionally. Finance asks payback; team mentions “efficiency.” Strategy office asks alignment; team mentions “innovation.” Risk asks about conduct; team mentions “guardrails” without design. Programme enters pilot purgatory—£400K spent, no scale criteria.

Stage 1 antidote: Demo after value hypothesis, alignment, and stakeholder map—demo illustrates named KPI movement, not capability tourism.

Manager review rubric (Stage 1 gate)

Use in weekly artefact review:

Dimension	Red	Amber	Green
Economics	No P&L line	Range without adoption	£ range + payback + sensitivity
Strategy	Generic “digital”	Theme named, weak KPI link	Theme + KPI + stopped ideas
Domain	Wrong metrics	Correct terms, shallow	Brief with value chain + regulation
Consulting	Unstructured notes	Issue tree partial	Decision log with options
Discovery	Idea list only	Scores without kills	Scored backlog + owners
Stakeholders	Missing risk/finance	Map without plan	Map + messages + RACI
Communication	Tech-led deck	Exec summary too long	2-page summary + Q&A

Green on ≥5/7 dimensions → recommend Stage 2 start for that workstream.

Competency proof

When claiming Stage 1 complete:

1. Submit artefact pack (table above) to peer or manager.
2. 30-minute challenge session: economics, strategy, stakeholders, negative cases.
3. Optional: Competency test prompts for Stage 1.
4. File anonymised artefacts in team pattern library.

What comes next

Stage 2 asks: Is the prioritised use case technically feasible with data, models, and evaluation discipline? Do not advance until Stage 1 exit criteria are met—or document explicit risk acceptance by sponsor (rare, logged).

Output

Stage 1 portfolio deliverables (engagement pack minimum):

• Value hypothesis one-pager (topic 01)
• Strategic alignment statement + stopped ideas log (topic 02)
• Domain context brief (topic 03)
• Problem definition and issue tree (topic 04)
• Scored AI opportunity backlog (topic 05)
• Stakeholder map and comms plan (topic 27)
• Two-page executive summary + Q&A sheet (topic 28)

Stage 1 completion checklist

• I can explain how the client makes money and name three executive KPIs
• Value hypothesis and alignment statement written and reviewed
• At least two misaligned use cases stopped with documented rationale
• Domain brief covers value chain and regulation for target sector
• Discovery backlog scored; owners assigned for top opportunities
• Stakeholder map includes finance, risk, data, and business sponsor
• Executive summary readable in 5 minutes without demo
• Artefacts filed in pattern library; VALUE self-check completed
• Business Learning workbook or keywords used for sector fluency

Key takeaways

• Stage 1 outcome is investment rationale, not model literacy—earn architecture conversations with economics and strategy.
• Topics 01–05 build the what and why; 27–28 ensure the right people hear it the right way.
• Business Learning accelerates domain credibility but does not replace topic artefacts.
• Exit criteria are artefact-based—reading reference chapters without outputs does not clear the stage.
• Common failure is demo-led selling; antidote is hypothesis-led discovery with explicit stopped ideas.
• Stage 2 feasibility work without Stage 1 invites pilot purgatory and steering committee distrust.

What to do next

1. If new to the map, read How to use this Learning Map for study method (90–180 min per topic).
2. Begin with Business Fundamentals and Business Strategy in week one.
3. Deepen sector fluency via Business Learning overview and the Domain Knowledge workbook.
4. When exit criteria pass, continue to AI and data foundations.