Capstone — End-to-End Operations Sprint

The COO has asked you to build the operations intelligence layer from scratch in one working day. You are the newly appointed Operations Manager at a 200-person professional services firm. The organisation has no systematic vendor tracking, no current SOP library, an unmapped compliance obligation landscape, a change process that approves changes but does not track them, and no operational metrics framework.

By end of day, the COO wants: a vendor audit with a renewal calendar, two critical SOPs, a compliance obligation map, an audit-ready evidence assessment, an operational risk register, an incident post-mortem for the last major incident, a metrics framework, four deployed agents, and an intelligence brief synthesising everything into a single, decision-ready document.

This sprint exercises everything from Lessons 3-13. Not as a test of memory — as a test of operational execution. You will choose your scenario, run nine phases in sequence, apply a quality gate after each phase, and synthesise the outputs into a COO-ready intelligence brief.

The intelligence layer you build in 90 minutes is not hypothetical. It is the pattern you will use every time you enter a new operational role.

Plugin Setup Reminder

This capstone requires both the Operations plugin (official) and the Operations Intelligence plugin (custom). All commands from both plugins are used across the nine phases. If you have not installed both, follow the instructions in the Chapter 38 prerequisites before continuing.

Choose Your Scenario

The sprint framework is the same for all three scenarios. What changes is the operational context — which shapes the data you use, the risks you prioritise, and the focus of your final brief.

Scenario	Context	Primary Stresses	Best For
A: Subsidiary Acquisition	Your firm has just acquired a 40-person consultancy. You inherit their vendor portfolio (22 vendors, unknown state), their processes (partially documented), and their compliance obligations (two additional jurisdictions). You have 90 days to integrate.	Vendor management, compliance mapping, risk assessment	Finance professionals, M&A specialists, operations generalists
B: ERP Migration	The firm is migrating from a legacy ERP system to a modern platform over the next 6 months. This is the largest change in the organisation's history — 47 vendors have integration dependencies, 12 SOPs reference the old system, and the migration has already slipped three weeks.	Change management, process documentation, incident readiness	Technology managers, project managers, IT operations professionals
C: Regulatory Change	The FCA has issued new guidance on client money handling that affects 8 of your compliance obligations. You have 60 days to demonstrate compliance. Three of the affected obligations are currently PARTIAL. One is GAP.	Compliance mapping, audit preparation, risk register	Compliance officers, risk managers, finance professionals in regulated industries

Choose your scenario now. Read its context carefully — it will shape the data you use in every phase.

The Sprint Map

Phase	Duration	What	Plugin Commands	Source Lesson
1. Vendor audit	15 min	Portfolio audit + top 3 contract extraction	/vendor-review + /contract	L03 + L04
2. Process documentation	10 min	2 critical SOPs + gap analysis	/process-doc + /runbook	L05
3. Change assessment	10 min	Impact assessment for one major change	/change-request	L06
4. Compliance map	10 min	Obligation map for primary regulatory framework	Natural prompt (compliance-tracking auto-skill)	L07
5. Audit preparation	10 min	Mock review for highest-risk obligation	/audit	L08
6. Risk register	10 min	10+ risks scored, top 3 mitigated	Natural prompt (risk-assessment auto-skill)	L09
7. Incident post-mortem	10 min	Post-mortem for one historical/hypothetical incident	/incident	L10
8. Metrics framework	10 min	5-10 metrics with thresholds	/metrics + /status-report	L11
9. Agent deployment	5 min	Configure 4 agents with schedule	Agent configs (custom plugin)	L12
Final brief	(in parallel)	Intelligence brief synthesising all outputs	/status-report + /metrics synthesis	L13

Total: 90 minutes. Set a timer. The time pressure is intentional.

Quality Gates

After each phase, evaluate your output against the quality gate criteria before proceeding. Mistakes compound in a sprint — a vendor audit that misses a key renewal creates a risk register gap in Phase 6, which creates an incomplete brief in the final synthesis. Catch problems at their phase, not at the end.

---

Phase 1 — Vendor Audit (15 minutes)

Commands: /vendor-review + /contract Source lessons: L03 (vendor portfolio) + L04 (contract analysis)

Step 1A — Portfolio audit:

/vendor-review
Run a vendor portfolio audit for our organisation.

[SCENARIO A: Include the inherited subsidiary vendors — 22 vendors,
unknown renewal dates, two jurisdictions. Total combined spend approx
£480,000/yr. Highlight any duplicate vendor categories where both
companies have separate contracts for the same capability.]

[SCENARIO B: Focus on vendors with ERP integration dependencies —
at least 10 vendors who integrate with the current system. Flag
renewal risk: any vendor whose contract expires during the 6-month
migration window.]

[SCENARIO C: Focus on vendors who are subject to FCA oversight or
who handle client money on our behalf. Identify any contract without
a current data processing agreement.]

[Paste or describe your vendor data based on your chosen scenario.]

Output: portfolio audit with spend-by-category, immediate attention
items, rationalisation opportunities, and renewal calendar.

Step 1B — Contract analysis for top 3 vendors:

/contract
Extract obligations from the top 3 vendor contracts by annual value.

[For each contract, describe: vendor name, contract value, key SLA
commitments, data handling clauses, notice period, auto-renewal
terms, any penalty or credit clauses]

For each contract, identify:
- SLA commitments and measurement method
- Auto-renewal terms and notice deadline
- Data processing obligations (GDPR-relevant)
- Exit rights and associated costs
- Any clauses that create financial risk

Quality gate — Phase 1:

• Does the portfolio audit flag the correct number of renewals in the next 90 days?
• Does the contract analysis identify all three types of obligation (SLA, data, financial risk)?
• For Scenario A: does the audit identify vendor category overlaps between the two companies?
• For Scenario B: are migration-window renewals clearly flagged?
• For Scenario C: are contracts without data processing agreements identified?

---

Phase 2 — Process Documentation (10 minutes)

Commands: /process-doc + /runbook Source lesson: L05

Step 2A — Create two critical SOPs:

/process-doc
Create a Tier 1 SOP for [choose one critical process from your scenario]:

[SCENARIO A: Client data handover process — transferring client
records from the acquired company to our systems. This is Tier 1
because it has GDPR implications if done incorrectly.]

[SCENARIO B: ERP migration rollback procedure — the steps to execute
if the migration must be reversed mid-deployment. This is Tier 1
because it has business continuity implications.]

[SCENARIO C: Client money handling procedure — the process for
segregating client funds in compliance with FCA requirements. Tier 1.]

Include: purpose, scope, prerequisites, step-by-step procedure with
RACI assignments, decision points, embedded controls, escalation paths,
review cycle, and owner.

/runbook
Create an operational runbook for [second critical process]:

[SCENARIO A: Vendor onboarding for newly discovered subsidiary vendors
— the process for reviewing, approving, and integrating each of the 22
inherited vendors into the approved vendor list.]

[SCENARIO B: Change window coordination — the process for scheduling
and coordinating the weekly ERP migration deployment windows, including
communications, validation steps, and rollback triggers.]

[SCENARIO C: Compliance evidence collection process — the procedure
for gathering, storing, and refreshing evidence for FCA-regulated
obligations during the 60-day remediation window.]

Include: trigger conditions, required inputs, step-by-step procedure,
expected outputs, failure conditions and responses.

Quality gate — Phase 2:

• Does the SOP include specific roles in the RACI (not "the team")?
• Are embedded controls present — steps that prevent the process from proceeding incorrectly, not just instructions to "check"?
• Does the runbook include explicit trigger conditions and failure responses?
• Would someone who had never done this process before be able to follow these instructions without asking questions?

---

Phase 3 — Change Assessment (10 minutes)

Command: /change-request Source lesson: L06

/change-request
Submit a change request and impact assessment for:

[SCENARIO A: Consolidating vendor contracts — migrating the acquired
company's CRM platform users (18 staff) onto our existing Salesforce
instance. Timeline: 4 weeks. Classification: MAJOR.]

[SCENARIO B: ERP migration — deploying the first module (finance) of
the new ERP platform. Timeline: this coming weekend. Classification:
CRITICAL. System downtime expected: 12 hours Saturday.]

[SCENARIO C: Updating the client money handling procedure — implementing
new account segregation controls required by the FCA guidance update.
Timeline: 3 weeks. Classification: MAJOR.]

For the change above, produce:
- Impact assessment: systems affected, staff affected, data affected,
  rollback trigger conditions
- Communications plan: who must be notified, when, by whom
- Rollback plan: specific steps to reverse the change if it fails
- Risk classification and approval authority required

Quality gate — Phase 3:

• Is the impact assessment complete — does it list specific systems, specific staff groups, and specific data affected?
• Does the communications plan identify who receives communications (not just "stakeholders")?
• Does the rollback plan describe specific steps — not just "reverse the change"?
• Is the risk classification and approval authority level correct for the change's impact?
• For Scenario B: does the CRITICAL classification trigger the appropriate approval authority?

---

Phase 4 — Compliance Map (10 minutes)

Command: Natural language prompt (compliance-tracking auto-skill activates from keywords) Source lesson: L07

Map our compliance obligations for a 200-person UK professional
services firm.

[SCENARIO A: Include two jurisdictions — UK (primary) and Pakistan
(subsidiary operations). Primary frameworks: UK GDPR, Companies Act,
employment law, AML. Pakistan additions: PDPA (if enacted in your
scenario), SECP requirements for the Pakistan entity.]

[SCENARIO B: Focus on the ERP migration's compliance implications.
Include: UK GDPR (data processing changes during migration), PCI DSS
(payment data in scope during migration), Companies Act (financial
records integrity during system changeover), employment law (any TUPE
implications if contractors are used for the migration).]

[SCENARIO C: Focus on FCA-regulated obligations. Include: client money
handling (CASS), UK GDPR, AML/KYC, conduct obligations. For the 8
obligations affected by the new FCA guidance, use current status:
5 CURRENT, 3 PARTIAL, 1 GAP. Identify which controls need updating.]

For each obligation include: framework, obligation description, owner,
current status (CURRENT/PARTIAL/GAP), evidence required, next review date.
Format as a compliance obligation map table.

Quality gate — Phase 4:

• Does the map include all obligation types — regulatory, contractual (from Phase 1 contracts), and standards-based?
• Does each obligation have a named owner (not a department)?
• Are the CURRENT/PARTIAL/GAP statuses assigned based on actual evidence state, not optimistic assumptions?
• For Scenario C: are the three PARTIAL and one GAP obligations correctly identified with specific remediation requirements?

---

Phase 5 — Audit Preparation (10 minutes)

Command: /audit Source lesson: L08

/audit
Prepare for a mock internal audit of our highest-risk compliance area.

[SCENARIO A: The FCA (or ICO for UK GDPR) is reviewing our data
handling practices for the newly acquired subsidiary. The most
vulnerable area is the data transfer process — we may have transferred
personal data across from the subsidiary without adequate GDPR controls.]

[SCENARIO B: An internal IT audit is reviewing the ERP migration
change controls. The auditor is specifically testing whether the change
risk classification process was followed correctly for the CRITICAL
deployment this weekend.]

[SCENARIO C: The FCA is conducting a supervisory review of our client
money handling practices. The review will specifically examine the GAP
obligation identified in Phase 4.]

For the audit above:
1. Identify the three areas of highest audit risk
2. For each area: list the evidence we need, its current state, and
   any gaps in our evidence pack
3. Generate a mock auditor question set (5 questions per area)
4. Provide suggested responses to each question
5. Identify where our responses would be weakest and what we should
   do before the audit to strengthen our position

Quality gate — Phase 5:

• Are the three audit risk areas specific to the scenario (not generic "IT audit risks")?
• Does the evidence gap analysis identify specific documents, records, or controls that are missing?
• Are the mock auditor questions the kind of questions an experienced auditor would actually ask?
• Do the suggested responses sound defensible — or do they sound like they are avoiding the question?
• Would we pass this mock audit, or are there areas where the honest answer is "we cannot demonstrate this control is effective"?

---

Phase 6 — Risk Register (10 minutes)

Command: Natural language prompt (risk-assessment auto-skill activates from "risk", "risk register", "mitigation") Source lesson: L09

Build an operational risk register for our organisation.

Context: 200-person UK professional services firm.

[SCENARIO A: Include acquisition-specific risks: data migration risk,
vendor portfolio integration risk, staff retention risk (acquired
employees), regulatory compliance risk in new jurisdiction. Plus
baseline operational risks.]

[SCENARIO B: Include migration-specific risks: ERP system failure risk,
data loss risk during migration, business continuity risk, integration
failure risk (47 vendors with dependencies). Plus baseline operational
risks.]

[SCENARIO C: Include regulatory risk: FCA enforcement action risk,
client money loss risk, regulatory change risk (further FCA guidance
expected). Plus baseline operational risks.]

For each risk, provide:
- Risk description
- Inherent score (likelihood × impact, 1-5 scale)
- Current controls
- Residual score (post-controls)
- Risk owner
- Mitigation action (if residual score >9)
- Escalation threshold

Include at least 10 risks. Flag any risk above your configured
threshold (residual score >12 = HIGH).

Quality gate — Phase 6:

• Does the risk register include BOTH inherent AND residual scores?
• Are the current controls described specifically (not "we have a policy")?
• Are mitigation actions assigned to named owners with deadlines?
• Does the register include leading indicators — measures that will warn if a risk is increasing before it materialises?
• For Scenario-specific risks: are the highest-rated risks actually the scenario's most material risks?

---

Phase 7 — Incident Post-Mortem (10 minutes)

Command: /incident Source lesson: L10

/incident
Run a post-mortem for the following incident:

[SCENARIO A: During the data migration from the acquired subsidiary,
130 client records were temporarily accessible to the wrong team for
approximately 4 hours before the error was detected and corrected.
This is a potential GDPR personal data breach. Date: last week.
No client harm confirmed but notification obligation assessment required.]

[SCENARIO B: During a trial run of the ERP migration on a test
environment, the rollback procedure failed — the rollback took 6 hours
instead of the planned 2 hours because a database restore script had
an error. The production go-live is this weekend. Date: 3 days ago.]

[SCENARIO C: During a routine client money reconciliation, a
£47,000 discrepancy was found in the segregated client account. The
discrepancy was caused by a delayed bank transfer and resolved within
4 hours, but the FCA notification threshold was briefly breached. Date:
last month (before the new FCA guidance was issued).]

Post-mortem requirements:
1. Timeline reconstruction (what happened, when, who knew)
2. Five Whys root cause analysis (go to at least WHY 4)
3. Contributing factors (beyond the immediate cause)
4. Corrective actions (specific, owned, with deadlines — not "improve the process")
5. Lessons for the operations team
6. For Scenario A/C: assess whether FCA/ICO notification is required

Quality gate — Phase 7:

• Does the Five Whys reach a systemic root cause — not a symptom?
• Are the corrective actions specific (e.g., "write and test a rollback script for the specific database version") rather than vague ("improve rollback procedures")?
• Does the timeline reconstruction identify the earliest point where the incident could have been prevented?
• For Scenarios A and C: does the post-mortem include a notification assessment with a clear recommendation?
• Would this post-mortem prevent the incident from occurring again — or would the same conditions produce the same incident?

---

Phase 8 — Metrics Framework (10 minutes)

Commands: /metrics + /status-report Source lesson: L11

/metrics
Design an operational metrics framework for our organisation.

[SCENARIO A: Include acquisition integration metrics: vendor portfolio
integration progress (% of 22 vendors assessed), staff onboarding
completion rate, data migration accuracy (% records migrated without
errors), compliance map completion rate for new jurisdiction.]

[SCENARIO B: Include ERP migration metrics: migration progress (% of
modules deployed), change success rate (no rollbacks), system performance
comparison (pre vs. post migration for each deployed module), data
integrity rate, integration availability (% of 47 vendor integrations
operational).]

[SCENARIO C: Include FCA remediation metrics: compliance current rate
overall, specifically FCA-regulated obligations current rate, evidence
freshness rate (% of obligations with evidence <6 months old), open
GAP obligation days (how long each GAP obligation has been open).]

Plus standard operational metrics for all scenarios:
- Vendor SLA compliance rate
- Change success rate
- SOP currency rate
- Risk register review completion rate
- Incident response time (P1/P2)

For each metric include: definition, data source, measurement frequency,
Green/Amber/Red thresholds, owner, and leading vs. lagging designation.
Then produce the metrics dashboard for the current period.

Quality gate — Phase 8:

• Does the framework include leading indicators (metrics that warn of future problems) as well as lagging indicators (metrics that measure past performance)?
• Are the Red thresholds specific enough to trigger escalation — or are they vague enough to allow indefinite Amber status?
• Do the scenario-specific metrics actually measure the scenario's primary risks (not generic operational metrics relabelled)?
• Is the data source for each metric achievable — or does it require a system integration that does not yet exist?

---

Phase 9 — Agent Deployment (5 minutes)

Commands: Agent configuration (custom Operations Intelligence plugin) Source lesson: L12

Configure all four operations agents for our 200-person UK professional
services firm based on the operational context we have built in this sprint.

Vendor Watchdog:
- Monitor the vendor portfolio from Phase 1 (including scenario-specific additions)
- Renewal threshold: 90 days; escalation for >£50,000 contracts
- Schedule: Monday 07:00

Process Health:
- Monitor the SOP library we built in Phase 2 plus any pre-existing SOPs
- Review cycles: Tier 1 annual, Tier 2 18 months, Tier 3 24 months
- Schedule: First Monday of each month

Compliance Monitor:
- Monitor the compliance map from Phase 4
- Jurisdictions: [UK primary; add Pakistan or FCA-specific as per scenario]
- Evidence age threshold: 12 months standard; 6 months for FCA-regulated obligations
- Schedule: Monday 08:00

Change Tracker:
- Monitor the change log, starting with the change assessed in Phase 3
- PIR requirements: Major/Critical — 4 weeks; Significant — 6 weeks
- Schedule: Friday 16:00

For each agent: confirm configuration, confirm first run schedule,
and produce the first simulated check output based on the data from
this sprint.

Quality gate — Phase 9:

• Are all four agents configured with data sources that reference the actual artefacts built in this sprint (Phase 1 vendor data, Phase 2 SOPs, Phase 4 compliance map, Phase 3 change log)?
• Does each agent confirm escalation contacts — or will alerts go into a void?
• Does the simulated first check produce at least one meaningful alert per agent?
• Are the agents monitoring the scenario's specific risks — or are they configured with generic defaults?

---

Final Brief — Operations Intelligence Brief (Synthesis, Running Throughout)

The final brief synthesises all nine sprint phases into a single, COO-ready document. Do not leave this entirely to the end — begin the synthesis as you complete each phase by noting the most important output from each.

Synthesise the operations intelligence layer I have built during this sprint.

SPRINT OUTPUTS:
Phase 1 — Vendor audit: [describe top findings — renewals, risks, contract obligations]
Phase 2 — Process documentation: [describe SOPs created and gap analysis]
Phase 3 — Change assessment: [describe the change, classification, key risks]
Phase 4 — Compliance map: [describe obligation count, status distribution, key gaps]
Phase 5 — Audit preparation: [describe audit risks and evidence gaps]
Phase 6 — Risk register: [describe top 3 risks, inherent and residual scores]
Phase 7 — Incident post-mortem: [describe root cause, corrective actions]
Phase 8 — Metrics framework: [describe metrics, current RAG status]
Phase 9 — Agent deployment: [confirm all four agents configured]

SCENARIO CONTEXT: [State your scenario A, B, or C and its key constraints]

CROSS-PHASE CONNECTIONS TO SURFACE:
[Identify at least two connections across phases — e.g., a vendor risk from Phase 1
that appears in the risk register in Phase 6; or a compliance gap from Phase 4 that
connects to the audit risk in Phase 5]

Produce:
1. Executive summary (max 1 page — COO reads this only)
2. Sprint summary table (phase → key output → status)
3. Cross-phase intelligence (connections across the sprint)
4. Top 3 recommended actions (specific, owned, time-bound)
5. Agent monitoring schedule (what the four agents will monitor going forward)
6. 30-day operational priorities

Sprint Self-Assessment Rubric

After completing the sprint, evaluate your work against these quality criteria:

Phase	Quality Criterion	Self-Assessment
Phase 1: Vendor	Audit covers full portfolio; top 3 contracts have extracted obligations	☐ Complete / ☐ Partial / ☐ Missing
Phase 2: Process	SOPs include specific roles (RACI), embedded controls, escalation paths	☐ Complete / ☐ Partial / ☐ Missing
Phase 3: Change	Impact assessment lists specific systems/staff/data; rollback plan has specific steps	☐ Complete / ☐ Partial / ☐ Missing
Phase 4: Compliance	All obligation types covered (regulatory, contractual, standards); each has a named owner	☐ Complete / ☐ Partial / ☐ Missing
Phase 5: Audit	Evidence gaps are specific; mock questions are realistic; weak areas identified	☐ Complete / ☐ Partial / ☐ Missing
Phase 6: Risk	Inherent AND residual scores; specific controls; mitigation actions with owners	☐ Complete / ☐ Partial / ☐ Missing
Phase 7: Incident	Five Whys reaches systemic cause (not symptom); corrective actions are specific	☐ Complete / ☐ Partial / ☐ Missing
Phase 8: Metrics	Leading AND lagging indicators; specific thresholds; achievable data sources	☐ Complete / ☐ Partial / ☐ Missing
Phase 9: Agents	All 4 agents configured with sprint data; first check produces meaningful alerts	☐ Complete / ☐ Partial / ☐ Missing
Final Brief	Executive summary is 1 page; top 3 actions are specific + owned; cross-phase connections present	☐ Complete / ☐ Partial / ☐ Missing

What to evaluate across the sprint:

• Does the vendor audit cover the full portfolio — not just the most prominent vendors?
• Do the SOPs meet the quality standard — specific roles, embedded controls, specific steps that can be followed without interpretation?
• Is the change impact assessment at the correct classification level — CRITICAL changes require different approval authority than STANDARD changes?
• Does the compliance map include all three obligation types — regulatory, contractual (from the contracts in Phase 1), and standards-based?
• Does the risk register have both inherent AND residual scores — is the difference between them explained by the current controls?
• Does the post-mortem reach the systemic root cause — WHY 4 or WHY 5, not WHY 1 or WHY 2?
• Does the metrics framework include leading indicators — not just lagging metrics that measure what already happened?
• Are all four agents configured with data from this specific sprint — not with generic defaults?
• Does the final intelligence brief synthesise the nine phases into a coherent story — or does it list nine phase outputs without connecting them?

Sprint-to-Lesson Map

Sprint Phase	Source Lessons	Core Command(s)	Key Output
Phase 1: Vendor audit	L03 + L04	/vendor-review + /contract	Portfolio audit + contract obligations
Phase 2: Process docs	L05	/process-doc + /runbook	2 SOPs (one procedure + one runbook)
Phase 3: Change assessment	L06	/change-request	Impact assessment + rollback plan
Phase 4: Compliance map	L07	Natural prompt → auto-skill	Obligation map (regulatory + contractual + standards)
Phase 5: Audit prep	L08	/audit	Evidence gaps + mock audit Q&A
Phase 6: Risk register	L09	Natural prompt → auto-skill	Risk register with inherent + residual scores
Phase 7: Incident post-mortem	L10	/incident	Five Whys RCA + corrective actions
Phase 8: Metrics framework	L11	/metrics + /status-report	Metrics dashboard + monthly report
Phase 9: Agent deployment	L12	Agent configs (custom plugin)	4 agents configured + scheduled
Final brief	L13	/status-report + /metrics synthesis	COO operations intelligence brief

Try With AI

Try With AI

Reproduce: Apply what you just learned to a simple case.

Run a condensed version of the operations sprint for a 15-person
professional services consultancy that has just moved to remote-first
operations. Run phases 1, 4, and 6 only:

Phase 1: Vendor audit for 8 vendors (AWS £45,000, Slack £3,000,
Notion £2,000, HubSpot £12,000, Xero £1,500, LinkedIn Recruiter £8,000,
Zoom £3,600, DocuSign £4,800). Identify renewal risks and rationalisation.

Phase 4: Map compliance obligations for UK GDPR, employment law,
and basic Companies Act compliance.

Phase 6: Build a risk register with at least 6 risks relevant to
a remote-first professional services firm.

After completing all three phases, write a 1-paragraph executive summary
connecting the key findings.

What you are learning: Running a condensed three-phase sprint on a simple organisation builds the sequencing muscle — you are practicing the dependencies (vendor data from Phase 1 feeds the risk register in Phase 6; compliance obligations from Phase 4 connect to risks in Phase 6) before attempting the full nine-phase sprint with a more complex scenario.

Adapt: Modify the scenario to match your organisation.

I am about to run the full operations sprint for my own organisation
([describe: size, industry, primary operational risks]).

Before I start, help me choose the right scenario (A: acquisition
integration / B: major system migration / C: regulatory change):

Which scenario most closely matches my organisation's current situation?
What should I emphasise in each phase for my specific context?
Which phases will take longer for my organisation than the time estimate?
Are there any phases where my organisation's data is likely to be
incomplete — and what can I substitute?

What you are learning: Choosing the right scenario requires judgment about your organisation's current risk profile. An organisation in the middle of a system migration is already living Scenario B. An organisation under regulatory scrutiny is already in Scenario C. Starting from the right scenario produces a sprint whose outputs are directly usable — not exercises.

Apply: Extend to a new situation the lesson didn't cover directly.

I have completed the full operations sprint and produced the intelligence
brief. The COO has read it and asked one question: "This brief tells me
what is wrong. It does not tell me what the operations function will look
like in 12 months if we address all of these issues. Write me a one-page
operational roadmap for the next 12 months."

Based on the sprint outputs, produce a 12-month operational roadmap that:
1. Identifies the three most important investments (people, process, or
   technology) the operations function should make in Q1
2. Describes what "good operations" looks like for our organisation by Q4
3. Identifies the success metrics that will show whether we are on track
4. Flags the risk that is most likely to derail the roadmap

[Paste your sprint's final intelligence brief here]

What you are learning: The sprint produces a diagnosis. The roadmap is the treatment plan. Moving from "here is what is wrong" to "here is what we will build" is the most important leap in an Operations Manager's role — it requires synthesising the sprint's findings, prioritising across competing demands, and committing to a direction. The intelligence brief makes this possible; the roadmap makes it actionable.

Flashcards Study Aid

---

Continue to Lesson 15: Chapter Summary and Quick Reference →