Pretend you are the platform PM so dependency gaps, capacity theater, and platform blur fail before a platform package absorbs them.
Optimistic platform packages optimize for "shared work will unblock everyone." The platform PM seat does the opposite. It asks which roadmap invents capacity eng never funded, which initiative dual-counts the same team as platform and as product, which "required" dependency is already optional in practice, and which consumer still lacks a named owner. A neat platform roadmap is not evidence that next quarter's shared work will clear.
How to cast the seat
Name a real job: underwrite a shared service without inventing consumer readiness, clear a capacity claim that finance can reconcile under load, or defend a platform cut without dual-counted adoption rates. Give constraints: the evidence standard for platform readiness, the consumers you will refuse to leave unowned, and the capacity claims you will not teach when headcount is not ready. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a roadmap review, a dependency fight, or a dispute over who owns shared infra.
Prompt example: "Platform PM: list the top reasons to delay this platform package, the consumer with the weakest owner, the capacity claim that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
Outputs worth keeping
- Top reasons to challenge, delay, or rewrite this platform package.
- The capacity or adoption claim that looks strongest and is least evidenced.
- The consumer, region, or service that would break first under a forced cut.
- What would make you accept residual platform risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real dependency map, capacity plan, consumer inventory, and open risk list. Follow with a home-team response pass so you leave with edits and source packs. When the decision is a public roadmap or deprecation claim, run this seat after eng and product attacks so it can use earlier objections as ammunition.
When the plan leans on a single shared service, a single "product teams will migrate themselves" promise, or a single hero squad, force the seat to price concentration risk in writing. Ask what happens if the dependency board still hosts retired owners, if platform still lacks a named on-call for consumer breaks, or if product keeps teaching migration language platform already retired. Pair with pretend you are the CTO, pretend you are the growth PM, war-game a roadmap cut, stress-test an API deprecation, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a schema migration or a multi-region cutover, ask the platform PM seat to map every claim that still assumes last quarter's shared contracts. Partner embeds, reporting jobs, and admin panels count. A platform memo that looks clean in a slide while consumers still pin to retired APIs will fail on the first traffic wave.