Ops Lead
OperationsmediumFree
Where Did the Orders Go?
Reverse-engineer a fulfillment process that's quietly failing
FFrontier Labs 4.3 (655) 4,585 taken 30m Ops Lead
The situation
Customer complaints are climbing, NPS is bleeding, and roughly one in eleven orders is shipping late or wrong — but nobody can say why. The process spans three systems, two warehouses, and a handoff that lives entirely in one person's head. You have a week and a frustrated team that's tired of firefighting. Map the real flow, find where it breaks, and propose a fix that survives the person who built it going on vacation.
What you'll practice
Map the true end-to-end flow across systems and sites
Map the true end-to-end flow across systems and sites. Show it clearly — with evidence a reviewer can point to.
Locate the actual failure point with evidence, not blame
Locate the actual failure point with evidence, not blame. Show it clearly — with evidence a reviewer can point to.
Propose a fix that removes the single-person dependency
Propose a fix that removes the single-person dependency. Show it clearly — with evidence a reviewer can point to.
Win the warehouse lead's buy-in, not just compliance
Win the warehouse lead's buy-in, not just compliance. Show it clearly — with evidence a reviewer can point to.
The room
3 autonomous AI coworkers, each with their own agenda. They won't all agree.
H
Hannah Ortiz
Warehouse Lead
Wants: Defend her team; the handoff lives in her head and she likes it that way.
Style: Capable, territorial, suspicious of process people.
D
Devon Pruitt
Customer Support Manager
Wants: Stop eating the complaints; wants root cause, not band-aids.
Style: Burned out, data-rich, blunt.
S
Sam Okoro
Systems Analyst
Wants: Suspects a sync gap between systems but can't prove it alone.
Style: Methodical, under-heard, quietly correct.
Your workspace
Real tools, pre-seeded with context. You're not roleplaying, you're working.
Docs / wiki Kanban board Team chat Email
Scored on
Root-causeProcess designTrade-offsRollout