Three Weeks From Missing

You have taken over One Dispatch, Merrow’s largest program: consolidating six regional dispatch centers onto a single AI-assisted platform. Two regions are live. Four go live in three weeks, on October 24 — a date chosen because Merrow…

National AI Competition
Wave 2
Program Manager / TPM / AI Ops Career Ladder
Estimated Time:
40 minutes
Difficulty:Intermediate
Status:Not started
Start this challenge

Create a free account to upload your work. Your progress saves as a draft until you submit.

What You'll Be Doing

You have taken over One Dispatch, Merrow’s largest program: consolidating six regional dispatch centers onto a single AI-assisted platform. Two regions are live. Four go live in three weeks, on October 24 — a date chosen because Merrow freezes all change on November 15 for peak season, and the program was funded on the assumption that the new platform absorbs peak volume. 

Here is the program as you inherited it. 

Workstream status 

WorkstreamOwner% completeState
Platform engineeringEng Manager, 4 engineers88%On track. Two open defects, neither blocking
Data migrationData lead, 2 contractors62%31,400 open work orders unmapped across the four remaining regions. Contractors end October 31
Field enablement / trainingOps trainer, 1 FTE37%410 of 1,100 technicians trained. Sessions run 90 min, max 25 techs, trainer runs 4 per week
Customer communicationsUnassigned0%Not started. Three chain customers (44% of revenue) require 30 days’ written notice of a process change under contract

What the two live regions look like 

MeasureRegion A (live 5 weeks)Region B (live 2 weeks)Company baseline
First-time fix rate71%64%68%
SLA compliance (P1 response)95%79%92%
AI triage accuracy94%91%—
AI parts recommendation correct93%88%—
Repeat truck rolls per week (wrong or missing part)93418 (six-region average)
Dispatcher headcount5 (was 8)6 (was 9)—
Escalations to regional manager, last 7 days446—

A repeat truck roll costs Merrow $340 in labor and vehicle cost and burns SLA clock on the next call. 

Region A’s manager has been running the platform since August and has built a private spreadsheet of 60 “known bad” parts recommendations that her dispatchers check against. She has not told anyone. You found out yesterday. 

Diagnose the program and tell leadership what you are doing. 

Constraints to consider 

  • You get no new headcount and no budget increase. The data migration contractors end October 31 and cannot be extended. 
  • The October 24 date can move, but not past November 15 — no change goes live during the freeze, and the program’s funding case assumed peak volume runs on the new platform. 
  • You cannot roll Region B back to the old platform. Its old dispatch instance was decommissioned two weeks ago. 
  • Any change affecting the three chain customers requires 30 days’ notice, which means anything customer-visible in the remaining four regions had to be noticed by yesterday. 
  • The AI triage and parts models are vendor products. You can change thresholds, routing, and what a dispatcher sees. You cannot retrain them. 

AI Usage Guidance 

We expect you to use AI tools. We evaluate how you use them — not whether you use them. Evidence of iteration, redirection, and critical evaluation scores higher than a polished output with no process documentation. 

The single highest-signal indicator: your video answer to the mandatory AI question. If you cannot name a specific moment where you redirected AI output, evaluators will assume you did not. 

Mandatory AI question for your video: Walk me through one moment where you disagreed with, pushed back on, or redirected what the AI gave you — and what you did instead. Name the specific moment. Explain what the AI produced that didn’t meet the bar, what you did differently, and why. 

Communication clarity matters for this role. We assess structure, stakeholder awareness, and ability to simplify complex ideas — not presentation style or accent.

What You'll Accomplish

Diagnose which workstream in a multi-team program is the real constraint, using throughput arithmetic rather than percent-complete

Separate a delivery problem from an operational quality problem when both are present

Build a recovery plan that reallocates rather than requests resource

Convert an undocumented local workaround into a system-level control

Communicate a recovery position, including a date change, to leadership without losing their confidence

How Your Work Will Be Scored

Program Recovery & Execution AI-First Operations Design Cross-Functional Judgment & Sequencing Video Walkthrough & Communication AI Fluency

What to Submit

File 1 — Recovery Plan

Document · 2 pages maximumRequired

Format: .pdf, .doc, .docx, .rtf, .txt, .md

Your diagnosis, your recommended go-live position for the four remaining regions, and the three-week plan with owners. Show the plan as a schedule, not prose. State explicitly what you are descoping.

Sign in to upload files

File 2 — README Document

DocumentRequired

Format: .pdf, .doc, .docx, .rtf, .txt, .md

Three required sections: 

  • Section A — Written analysis: which workstream is the binding constraint and why, shown with arithmetic. Then: what Region B’s numbers tell you that Region A’s do not, and what you cannot yet distinguish from the data you have. 350–450 words. 
  • Section B — Controls and escalation: (i) the control you would put in place for the parts recommendation problem, stated with a trigger, a threshold, an action and an owner — and how you would turn Region A’s private spreadsheet into something the whole company runs on; (ii) your escalation: what you are telling leadership, what decision you need from them, and by when. 
  • Section C — AI Usage Log (Mandatory): This is not a trick. We want to see how you work with AI — not whether you used it. In a short section of your README, document your AI collaboration process. For each significant interaction with an AI tool, briefly note: what you asked the AI to help with / what it gave you / what you kept, changed, or rejected — and why. Three interactions documented is sufficient. The log does not need to be exhaustive.

Sign in to upload files

File 3 — Video Walkthrough

Video · 5-6 minutesRequired

Format: .mp4, .mov, .webm

Record as MP4 or MOV and upload directly on the Provn platform as a separate file. Cover: (1) your diagnosis in one sentence, ~30 sec; (2) the arithmetic behind the binding constraint, ~90 sec; (3) your recommended go-live position and what you are descoping, ~90 sec; (4) the mandatory AI question, ~60 sec; (5) what you are least sure about, ~45 sec. Speak naturally — we assess reasoning, not verbal polish.

Sign in to upload files