Pretend you are the CTO so soft delivery claims and heroic architecture bets fail before engineering, security, and customers absorb them.
Optimistic plans optimize for the operator who wants to ship. The CTO seat does the opposite. It asks what breaks under peak load, which dependency is least owned, which timeline hides integration debt, and which rollback story is missing. A fluent roadmap slide is not evidence that the system can carry the bet.
This is one of the core moves in a serious product, platform, or hire war game: after you describe the upside, seat a careful technology 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 reliability, hit a ship window without silent debt, or underwrite a migration without heroics. Give constraints: SLO floors, staffing you will not invent, and vendor risk you will not accept. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in an architecture review.
Write the seat into the prompt as a named role with a mandate. Example: "CTO: list the top reasons to pause this build, the assumption with the weakest source, the ops 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, narrow, or kill this build.
- The assumption that looks strongest and is least sourced.
- The reliability, security, or staffing 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 PRD, architecture notes, and staffing plan. Follow with a home-team response pass so you leave with edits and source packs, not only fear. When the decision is a migration or platform bet, run this seat after product and finance attacks so it can use earlier objections as ammunition.
When the plan leans on a single vendor or a single senior engineer, force the seat to price concentration risk in writing. Ask what happens if that vendor raises prices, throttles the API, or if that person leaves mid-quarter. Concentration that only appears in an appendix still counts.
Pair with pretend you are the CFO, stress-test a migration plan, stress-test a feature flag rollout, war-game a roadmap cut, stress-test an SLA change, and the war-game decisions hub. See how to run a Pingpong.