Pretend you are the COO so soft capacity claims and heroic timelines fail before the real ops room has to absorb them.
Optimistic plans optimize for the operator who wants to ship. The COO seat does the opposite. It asks which handoff is unnamed, which queue already runs hot, which metric is least sourced, and which commitment you would cut first without theater.
This is one of the core moves in a serious launch, reorg, or process change war game: after you describe the upside, seat a careful operator and make them try to decline. The output you want is not a performance. 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: protect service levels, hit a throughput target, or underwrite a launch without unpaid overtime as the plan. Give constraints: max queue depth, staffing floor, and concentration 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: "COO: list the top reasons to pause this plan, the assumption with the weakest source, the handoff risk 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 or narrow this plan.
- The assumption that looks strongest and is least sourced.
- The capacity, handoff, or vendor risk 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 memo, staffing model, and runbooks. Follow with a home-team response pass so you leave with edits and source packs, not only fear. When the decision is a launch or freeze exception, run this seat after finance and customer attacks so it can use earlier objections as ammunition.
When the plan leans on a single team or a single vendor, force the seat to price concentration risk in writing. Ask what happens if that bench is out, that SLA slips, or that queue doubles. Concentration that only appears in an appendix still counts.
Pair with pretend you are the CTO, pretend you are the CFO, stress-test a migration plan, war-game a reorg, CEO decision review, and the war-game decisions hub. See how to run a Pingpong.