Your goal: find the cause of an ops metric move with a clean drill-down, prove it explains the
whole move, and say what you would do today and next month.
How this works (about 30 minutes)
- Victor is a BizOps interviewer. He holds a data sheet, made up for the exercise. Ask for the cut you
want, one at a time; he won't volunteer. A cut he doesn't have comes back flat.
- A shared notepad is there if you want to sketch your tree. 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
- Pinning down the metric, the size and the shape of the move before any theory
- Cheap checks first (is it real, is it expected), then cuts that localise
- Saying why you are cutting that way, and ruling branches out out loud
- Proving the cause explains the whole move, with arithmetic
- A fix for today, a fix for good, and a note someone could act on
Tips
- Take BizOps Coach · Root Cause first.
- Say the plan before you ask for data: "I'll check the data, then us, then outside."