Readiness Roadmap

Phases are gated by answers, not dates. Each phase lists its exit criteria — don’t start the next until they’re met.

flowchart LR
  P0[0 · Define the offer] --> P1[1 · Curriculum architecture]
  P1 --> P2[2 · Build pilot content + labs]
  P2 --> P3[3 · Instructor dry-run]
  P3 --> P4[4 · Pilot workshop]
  P4 --> P5[5 · Package for white-label]
  P5 --> P6[6 · Scale]

Phase 0 — Define the offer

• Answer 🔴 questions in Questions (Q-015 to Q-018, Q-004, Q-005)
• Map the Microsoft stakeholders and their approval path (^q-016); track the staffing issue
• Define the trial program: size, firm, role mix, dates (^q-014)
• Pick the delivery model for scale before the content is built (Scale and Capacity Model)
• Write the program brief for Microsoft → draft: Trial Program Brief: who it’s for, credential structure, format, outcomes, delivery capacity, pricing/funding model
• Decide the credential structure → Certification and Assessment Design
• Validate with 1–2 target firms (e.g. a PwC practice lead): would they nominate people? Would they pay? Exit: Microsoft has approved the program brief in principle and one firm has committed to the pilot cohort.

Phase 1 — Curriculum architecture

• Learning outcomes per persona (verbs: build, ship, evaluate, not understand)
• Module map across tracks → Curriculum Map
• Pick the capstone scenario that threads all tracks (one fictional company, one problem)
• Define content versioning approach (products change monthly) → Content versioning Exit: module list with outcomes, durations, and lab per module.

Phase 2 — Build pilot content + labs

• Build the pilot workshop only (likely 1–2 days: HVE + Copilot core, one Foundry or Fabric module)
• Slide masters on the Microsoft brand kit, brand as a swappable layer → Brandable assets
• Submit pilot content for Microsoft review early; budget for revision cycles
• Lab environment + provisioning script + teardown → Environment
• Learner pre-work + setup checker on the course platform
• Assessment for the pilot module(s) Exit: a stranger can complete every lab from the written instructions alone.

Phase 3 — Instructor dry-run

• Full timed run-through with internal “learners”
• Facilitator guide with timings, talk track, failure recovery → Instructor Readiness
• Fix everything that broke Exit: labs finish within planned time for the median learner.

Phase 4 — Pilot workshop

• One consulting firm, Microsoft stakeholders observing, explicit feedback agreement
• Pre/post skills measurement; NPS; capstone completion rate
• Debrief within 48h → meeting note in 05 Meetings/ Exit: success measures in Success measures (draft) met or a clear fix list.

Phase 5 — Scale the program

• Credential operations: badge issuance, public registry, renewal → Certification and Assessment Design
• Deployment-phase support model (if adopted) (^q-018)
• Instructor hiring/onboarding for cohort volume → Instructor Readiness
• Repeatable Microsoft review cadence for content updates → Partnership and Agreements

Phase 6 — Scale

• Remaining tracks, advanced levels, quarterly content refresh cadence, partner #2+