Pretend you are the implementation lead so soft timelines and heroic dependency charts fail before a customer, board, or exec pack absorbs them.
Optimistic packages optimize for the sell. The implementation lead seat does the opposite. It asks which dependency is assumed but unowned, which cutover has no rollback, which staffing plan is a wish, and which milestone only works if nothing else slips. A fluent Gantt is not evidence that the program can survive a careful read under pressure.
This is one of the core moves in a serious delivery or migration war game: after you describe the upside, seat a careful implementation perspective and make it try to delay. The output you want is not theater. 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: ship a cutover without silent gaps, protect production during migration, or underwrite a customer go-live. Give constraints: the staffing you will honor, the evidence standard for "done," and the residual risk you will not invent away. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a design review or kickoff.
Write the seat into the prompt as a named role with a mandate. Example: "Implementation lead: list the top reasons to delay this plan, the claim with the weakest schedule evidence, the cutover risk that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to challenge, delay, or reject this package.
- The claim that looks strongest and is least evidenced.
- The dependency or cutover path that would worry you most.
- What would make you accept a narrower scope instead.
- The ten hardest diligence questions you would send in writing.
Run that brief in Pingpong against the real plan, dependency list, and staffing exhibits. Follow with a home-team response pass so you leave with edits and source packs, not only fear. When the decision is customer-facing, run this seat after sales and product attacks so it can use earlier objections as ammunition.
When the plan leans on a single vendor, a single migration weekend, or a single on-call owner, force the seat to price concentration risk in writing. Ask what happens if that owner is unavailable, if the vendor slips, or if sampling finds gaps in the runbook. Concentration that only appears in an appendix still counts.
Pair with stress-test a migration plan, war-game an acquisition integration, pretend you are the CTO, pretend you are the COO, and the war-game decisions hub. See how to run a Pingpong.