How to use this Learning Map

Executive summary

Each Learning Map topic is a reference chapter: definitions, frameworks, worked examples, multi-industry scenarios, practice artefacts, interview questions and negative cases. Read to understand, practise to retain, and file artefacts into a personal pattern library before you need them on a live engagement.

When to use this page

• Before a new engagement when you must close a capability gap fast.
• When preparing for manager / partner interviews or case discussions.
• When a Guide page tells you what to do, but you need how the underlying skill works.
• When reviewing a junior’s artefacts and you need a shared standard of quality.

What “reference depth” means

Earlier stubs listed vocabulary. Reference-depth pages teach you to produce decisions and artefacts.

Element	Stub (old)	Reference depth (current)
Learn	Bullet list of terms	Subsections: definition → engagement use → pitfalls → worked example
Scenarios	One short paragraph	At least two industries with measurable outcomes
Practice	One exercise	Primary + stretch with explicit artefact criteria
Questions	Three prompts	10–15 client- and interview-ready questions
Failure modes	Missing	Dedicated negative cases section
Links	“Guide link” placeholders	Named deep links to Guide, Framework, Roadmaps, Models

Target length for numbered topics (01–35) is roughly 5,000–8,000+ words. Stage hubs are shorter briefings (~2,000–4,000 words) that navigate the stage without duplicating every topic.

Page contract (every topic 01–35)

Every competency page keeps this shell:

1. Frontmatter — title, description, slug.
2. Executive summary — business value in a few sentences.
3. When to use — when to study this topic.
4. Audience split — executive vs technical reading path.
5. Why this matters — role-specific (not generic filler).
6. Learn (expanded) — teaching subsections for each concept cluster.
7. Frameworks and methods — named models, when to apply / not apply.
8. Architecture or operating-model notes — where relevant (diagrams welcome).
9. Real-world scenarios — at least two industries.
10. Practice exercises — primary + stretch.
11. Questions you should be able to answer — 10–15.
12. Negative cases — what breaks if this capability is weak.
13. Expected outputs — DeliverableBox artefacts.
14. Practice checklist — go / no-go items.
15. Related playbook content — named deep links (never “Guide link”).
16. Key takeaways — topic-specific.
17. Next steps — next topic + optional Guide / app link.

Expansion checklist (author or learner)

Use this when deepening a page further or when auditing your own notes:

• Every former Learn bullet has a subsection with definition, use, pitfalls and example
• At least two industry scenarios with numbers or measurable outcomes
• Primary and stretch practice exercises with artefact acceptance criteria
• Ten or more questions you could answer in a partner review
• Negative cases section present
• Related links use real Guide / Framework / Roadmap titles
• Key takeaways are specific to this topic (no template filler)
• No vendor-first framing; tools appear only after the problem is clear

How to study one topic (90–180 minutes)

1. Read ExecSummary + Why this matters (5 min)
2. Skim Learn headings; mark gaps (10 min)
3. Deep-read the gap subsections + frameworks (40–60 min)
4. Work both scenarios on paper (20 min)
5. Produce the primary practice artefact (30–45 min)
6. Self-quiz with the Questions list (15 min)
7. File artefact + notes in pattern library (10 min)

Do not “finish” a topic by scrolling. Finish when you have a written artefact you would show a senior reviewer.

Weekly practice loop

Day	Action
Mon	Pick one topic from your gap list (or the next stage topic)
Tue–Wed	Deep-read Learn + frameworks; annotate pitfalls
Thu	Complete primary practice artefact; start stretch if time
Fri	Run VALUE on the artefact; file it; note open questions

For large topics (RAG, security, FinOps), split across two weeks: week one concepts, week two practice + negative cases.

Stage hubs vs topic pages

Surface	Purpose	Depth
Stage hubs	Outcome, entry/exit criteria, failure modes, practice sequence	Briefing
Topic pages 01–35	Full teaching + practice	Reference chapter
Business Learning	Domain fluency packs and vocabulary	Mixed (some book-length)
Project Management	PMBOK-aligned delivery literacy	Mixed

Study order: stage hub → topic pages in recommended sequence → Business Learning packs when Stage 1 needs industry depth.

Integration with the rest of the playbook

Surface	Role
Learning Map	Build capability and produce practice artefacts
Guide	Run an engagement step (discovery → adoption)
8D / VALUE	Gate quality and stage advance
Roadmaps	Ordered career / platform journeys
Models	Model landscape and selection depth
App	Workshops, compare, FinOps, ConsultAI OS

Deep-link, do not duplicate. When a Learning Map topic overlaps a Guide chapter, teach the capability here and link the delivery playbook there. Example: Retrieval-Augmented Generation teaches chunking, ACL retrieval and faithfulness evaluation; RAG Guide walks the engagement delivery pattern.

How managers should use this map

1. Map each team member to stages 1–6; mark red / amber / green per topic.
2. Assign one topic per week with a required artefact review.
3. Use the Questions sections in 1:1s and project reviews.
4. Refuse to staff “AI chatbot” work until Stage 1 artefacts exist for the opportunity.
5. Keep a shared pattern library of anonymised good artefacts.

Common study failure modes

Failure	Symptom	Fix
Passive-only learning	Can recite terms, cannot produce a scorecard	Force the practice exercise before marking complete
Vendor-first study	Starts with product names	Re-read Why this matters; ban vendor names until problem is framed
Skipping negative cases	Designs happy path only	Write three failure scenarios before architecture
Ignoring finance	Technical design with no payback	Complete topic 01 / 07 artefacts first
Orphan artefacts	Notes scattered in chat	File into pattern library with date, client type, topic ID

Personal pattern library (minimum fields)

For every completed practice exercise, store:

• Topic ID and title
• Date and industry context
• Artefact type (scorecard, architecture sketch, risk register, etc.)
• One-paragraph decision summary
• Open risks / questions
• Link to related Guide page used

Topic Personal Effectiveness defines the operating system for this library.

Competency proof

When you believe a stage is complete:

1. Produce the artefacts listed on the stage hub.
2. Pass the self-check questions for each topic.
3. Sit the Competency test prompts for that stage.
4. Ask a peer or manager to challenge one artefact with VALUE.

Recommended first month

Week	Focus
1	Stage 1 hub + topics 01–02
2	Topics 03–05 + Business Learning domain sprint
3	Topics 27–28 (stakeholders + executive communication)
4	Stage 1 competency review + start Stage 2

Adjust if your gap is technical: still do topic 01 (business fundamentals) before deep AI topics so designs stay tied to P&L.

Key takeaways

• Reference-depth pages are chapters, not glossaries — finish with artefacts, not highlights.
• Stage hubs navigate; topic pages teach; Guide pages deliver.
• Study in a weekly loop with VALUE review and a filed pattern-library entry.
• Negative cases and multi-industry scenarios are mandatory, not optional polish.

What to do next

1. Return to the Learning Map overview.
2. Begin Business and consulting.
3. Keep Core deliverables open while you practise.