Drop Night
Every high-demand release is checked before it opens, graded after, and fixed before the next.
The job
Treats every scheduled high-demand moment, such as an episode release, ticket sale, flash sale, pre-order, registration opening or allocation result, as a launch. Each gets a go or no-go check, a grade and a fix list that must be confirmed before the next one.
The moment
60 minutes before derby tickets go on sale, the team replays the first minutes of the last derby release and what customers said.
1,800 said the payment page timed out, 900 said tickets sold out in 40 seconds, and 400 said the bot told them to refresh.
Two of those problems are marked fixed. The payment fix is still unconfirmed, so the release stays on red until its owner signs it off.
The morning after, the release gets a B+ grade. Timeout complaints are down 80% on the last derby, and the grade history goes to the board.
What it does
- Register a drop and its plan
- Sign off an open fix at the gate
- Fire the bot line or holding message
- Send a fix card to Jira
- Apologise to affected customers
What you see
Sneaker-drop countdown with a rehearsal gate, a graded drop card per release and a season-long drop league
What it moves
Customer complaints about each failure per release, per 1,000 expected buyers, how grades trend across a season, and the share of fixes confirmed before the next release.
Built for
- Product & digital
- Operations
