The Rollout You Can Actually Support
You are the program manager at Merrow Field Services, the field service company from the Practice challenge. Merrow’s COO wants AI-drafted repair quotes rolled out to all six regions in nine weeks. Today, a technician diagnoses a problem…
Create a free account to upload your work. Your progress saves as a draft until you submit.
What You'll Be Doing
You are the program manager at Merrow Field Services, the field service company from the Practice challenge.
Merrow’s COO wants AI-drafted repair quotes rolled out to all six regions in nine weeks. Today, a technician diagnoses a problem on site, calls it in, and a human estimator builds the quote from a parts catalog and a labor table. The AI version drafts the quote from the technician’s notes, the equipment record, and the parts feed.
The current state, and the pilot:
| Measure | Today (all six regions, human estimators) | Pilot (one region, 5 weeks, AI-drafted) |
| Quotes per month | 3,800 | 610 |
| Median quote turnaround | 26 hours | 4 hours |
| Quote accuracy (final invoice within 10% of quote) | 88% | 71% |
| Quotes requiring rework after customer pushback | 6% | 14% |
| Estimator headcount | 12 | 12 (unchanged during pilot) |
| Disputed invoices in the period | 2 | 3 |
| Customer-reported satisfaction with quote speed | — | up sharply, per the regional manager |
The pilot region’s manager wants it everywhere tomorrow. The VP of Finance has read the 71% and wants it stopped.
You have to make the call: roll out on the nine-week timeline, phase it, or hold. Then defend it.
Constraints to consider
- Your team for this is one operations analyst and half an engineer. You cannot hire and you cannot borrow from the platform team.
- The parts pricing feed refreshes nightly and is owned by the ERP team, who will not change its cadence this year.
- The three largest chain customers — roughly 44% of revenue — have contracts requiring a named human estimator’s sign-off on any quote over $10,000. That clause is not negotiable this contract year.
- Regional managers’ quarterly bonuses are tied to quote accuracy. Two of the six have already said they will not adopt.
- Merrow freezes all process changes from November 15 to January 5 for peak season. Week 9 lands November 10.
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
Make an explicit roll out / phase / hold decision under a fixed constraint set and defend it
Design an AI-first workflow that routes work between automated and human steps by rule
Sequence a rollout so the riskiest assumption is tested before the expensive commitment
Treat adoption resistance as a design input rather than a communication problem
Communicate a decision to an audience split between an enthusiastic operator and a skeptical finance leader, in five minutes
How Your Work Will Be Scored
What to Submit
File 1 - Rollout Recommendation
Format: .pdf, .doc, .docx, .rtf, .txt, .md
Your decision, your reasoning, and the nine-week plan you are committing to. Lead with the decision. Show the plan as weeks with owners, not prose.
Sign in to upload files
File 2 — README Document
Format: .pdf, .doc, .docx, .rtf, .txt, .md
Three required sections:
- Section A — Written analysis: the trade-offs behind your call, the strongest argument against it, and why you made it anyway. Address the two regional managers who said they will not adopt. 300–400 words.
- Section B — Workflow and gate: describe the AI-first quote workflow you would actually run — which quotes are drafted automatically, which route to a human estimator and on what rule, and what the estimator sees when they get one. Then state the single go/no-go gate: the metric, the threshold, when it is measured, and who calls it.
- 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
Format: .mp4, .mov, .webm
Record as MP4 or MOV and upload directly on the Provn platform as a separate file. Cover: (1) your decision and the one-sentence reason, ~45 sec; (2) the workflow — what is automated, what stays human, and the routing rule, ~90 sec; (3) your go/no-go gate and what you cut from the nine weeks, ~60 sec; (4) the mandatory AI question, ~60 sec; (5) how you handle the two regional managers who won’t adopt, ~30 sec. Speak naturally — we assess the quality of your reasoning, not verbal polish.
Sign in to upload files
Create a free account to upload your work. Your progress saves as a draft until you submit.
On this page