Pretend you are the ops lead so soft capacity math and heroic runbooks fail before the real operating room hears them.
Optimistic plans optimize for the slide that shows green utilization. The ops-lead seat does the opposite. It asks which queue actually absorbs the spike, which handoff is still tribal knowledge, which on-call page is unread, and which vendor SLA would break first if volume doubles for two weeks. A clean process diagram is not evidence that the system can absorb a bad Monday.
This is one of the core moves in a launch, migration, or support war game: after you describe the upside, seat a careful operations owner and make them try to decline. The output you want is not a pep talk. It is a short list of material objections, the exhibits each needs, and the edits that would survive them.
How to cast the seat
Name a real mandate: keep a named SLA without burning the team, absorb a launch week without silent overtime, or underwrite a migration without inventing spare capacity. Give constraints: staffing you will not pretend away, tools you will not invent mid-week, and residual risk you will not accept. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear.
Write the seat into the prompt as a named role with a mandate. Example: "Ops lead: list the top reasons to pause this plan, the assumption with the weakest source, the handoff or runbook gap that worries you most, and the ten diligence questions you would send after the meeting. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to delay, cut scope, or add buffer capacity.
- The assumption that looks strongest and is least sourced.
- The queue, vendor, or handoff mismatch that would worry you most.
- What would make you approve instead.
- The ten hardest diligence questions you would send in writing.
Run that brief in Pingpong against the real capacity model, runbooks, and incident notes. Follow with a home-team response pass so you leave with edits and named owners, not only fear. When the decision sits near a launch or SLA change, run this seat after support and finance attacks so it can use earlier objections as ammunition.
When the plan leans on a single person, a single vendor, or a single queue, force the seat to price concentration risk in writing. Ask what happens if that person is out, if the vendor misses, or if the backup queue is already full. Concentration that only appears in an appendix still counts. Pair with pretend you are the COO, war-game a capacity plan, war-game a support escalation ladder, stress-test an on-call rotation change, and the war-game decisions hub. See how to run a Pingpong.