Running a drop is a discipline, not a day. One named person owns each drop. Before it ships, the whole thing is rehearsed end to end on staging, with the real content, until it's boring. On the day, it runs from one war room, hands-on, by people who already know what's supposed to happen because they've watched it happen before.
An example, to show the difference.
Nobody in the room has seen it work before it has to work.
Everyone in the room has already watched it work.
Sam and Guy run Top Shot drops. Tristan and Jordan run Disney Pinnacle drops. One named person makes each call for their drop, so nobody is guessing who decides.
Before the drop ships, run one or more full rehearsals on staging, with the drop's real content, end to end. Every route: each lock and the priority allocation and draw it opens, every pack, every quest, the reveal, and the messages. Run it in a war room where all of engineering and all of growth are present and click through it themselves. Stop rehearsing only once it's boring.
If a step depends on a person doing something by hand on drop day, it will get missed. Only ship systems that are automated, or that can be, before drop day arrives.
Give a small group of engaged collectors specific missions on staging — lock a set, enter a draw, redeem a quest — before drop day. They find what a generic test script won't: what a collector who actually cares will try to do.
Partner approval from NBA and Disney takes time, and silence isn't approval. Get formats approved once, then submit each drop's content into them, and work backward from the drop date so there's always [N] left for a response.
Everyone is around the table, hands-on, treating the day as critically important; the owner makes the go/no-go call at launch control. If something breaks, tell collectors what's happening before it's fixed — one named person owns that message, and the fix never changes the terms of the deal (Chapter 9). Within days, file a short written review of what happened, segment by segment, against the hypothesis the drop started with.
Examples of the move, not plans.
Sam and Guy run it before it runs itself.
Tristan and Jordan run it before it runs itself.
Most of this chapter happens before any collector sees anything. The table says who's there, and what — if anything — a collector hears.
| Who | What they do | When |
|---|---|---|
| The owner (Sam & Guy, or Tristan & Jordan) | Makes the go/no-go call, and owns the message if something breaks | The rehearsal, and launch control on drop day |
| Engineering and growth | Click through every route themselves, end to end | The rehearsal, on staging, before drop day |
| A small group of engaged collectors | Run specific missions on the real content | On staging, ahead of drop day |
| NBA and Disney | Approve formats once, then sign off on content in writing | Across the lead-up, planned backward from the drop date |
| All collectors | Hear nothing extra — unless something breaks, then what's happening, before it's fixed | In-app, push or social, from the named owner |
A hypothetical, inside our own products. Imagine a drop ships without a full rehearsal, because the content looks like last time's. On drop day, a quest doesn't unlock the pack it's supposed to. Nobody owns the message, so nothing goes out while engineering investigates, and by the time an explanation ships, screenshots of the stuck quest are already on social media. Someone suggests quietly lowering the quest's requirement so collectors can get through — changing the deal to cover the problem.
The fix: rehearse the exact route that broke, on staging, with the real content, until it's boring — that's what the rehearsal is for. And have a named owner ready to say what's happening before the fix lands, without changing a single term of the deal to get there (Chapter 9).