1 min lesson
Know when to escalate vs. drive consensus
Answer this. "An ML lead keeps resisting the GPU-budget cap your capacity program needs and you have no authority over them. You feel the urge to escalate to a founder. Is that the right first move?"
Step 1 of 2
Know when to escalate vs. drive consensustwo different tools
- Drive consensus yourself
- The disagreement is factual or about how: the data can settle it and the call is inside the teams' shared authority
- Escalate to a decision-maker
- It's a genuine priority tradeoff between teams, such as cost against velocity, that only a leader who owns both can adjudicate
- The tell you're escalating wrong
- You're escalating because consensus is uncomfortable, not because it's actually a leadership-level tradeoff
Escalating a fact you could've resolved with a query burns credibility. Failing to escalate a real cross-team priority call burns the timeline.
In the partner round, expect a question like "an ML lead won't commit to the capacity number you need. What do you do?" Don't reach for authority or escalation first. Show the sequence: understand their incentive, which is experiment headroom; put the tradeoff in a shared doc with explicit assumptions; find the routing-and-budget move that gives them headroom while hitting your cost target; and escalate only if it turns out to be a real priority tradeoff a leader has to own.