Pretend you are the CPO so soft adoption claims and heroic roadmap bets fail before customers, sales, and engineering inherit them.
Optimistic product plans optimize for the operator who wants to ship. The CPO seat does the opposite. It asks which bet lacks a clear customer job, which packaging claim outruns the evidence, which dependency still sits with another team, and which kill criteria would force a cut mid-quarter. A fluent roadmap slide is not evidence that the portfolio can carry the bet.
This is one of the core moves in a serious launch, packaging, or roadmap war game: after you describe the upside, seat a careful product 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 activation quality, hit a ship window without silent debt, or underwrite a packaging change without churn theater. Give constraints: segment focus, staffing you will not invent, and metrics you will honor after thirty days. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a product review.
Write the seat into the prompt as a named role with a mandate. Example: "CPO: list the top reasons to delay this bet, the assumption with the weakest source, the adoption 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 product bet.
- The assumption that looks strongest and is least sourced.
- The adoption, packaging, or dependency 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, roadmap notes, and usage evidence. Follow with a home-team response pass so you leave with edits and source packs, not only fear. When the decision is a packaging or pricing move, run this seat after finance and sales attacks so it can use earlier objections as ammunition.
When the plan leans on a single segment or a single partner feature, force the seat to price concentration risk in writing. Ask what happens if that segment slows, if that partner slips, or if support load spikes after launch. Concentration that only appears in an appendix still counts.
Pair with pretend you are the CMO, pretend you are the CTO, war-game a product launch, war-game a roadmap cut, war-game a packaging change, and the war-game decisions hub. See how to run a Pingpong.