Your goal: design a fair test for an ops change, read the results with the cost in mind, and make
a launch call you can defend.
How this works (about 30 minutes)
- Victor is a BizOps interviewer. First you design a pilot. Then he gives you results, made up for the
exercise, one fact at a time as you ask.
- A shared notepad is there if you want to sketch your design. Ask Victor to open it, and tell him when
you've written something.
- Lots of follow-ups, one curveball, then a shorter question.
- No hints and no scores during the call. Your report comes after.
What scores well
- A hypothesis with a mechanism, and a reason for the unit you pick
- Knowing when customers cannot be randomised, and what to use instead
- One primary metric, guardrails on cost and the people doing the work, a stop rule set in advance
- Reading results with their range, the weekly trend and any spillover
- A launch call with the cost per result, and a next step
Tips
- Take BizOps Coach · Experiments first.
- Say the plan before the details: "hypothesis, unit, metrics, size, rule."