Pretend you are the internal comms lead so cascade gaps, channel theater, and message blur fail before a comms package absorbs them.
Optimistic internal packages optimize for "one email will land." The internal comms lead seat does the opposite. It asks which cascade invents manager readiness people ops never funded, which channel dual-counts the same staff as informed and as opted out, which "required" town hall is already optional in practice, and which region still lacks a named owner. A neat message calendar is not evidence that next week's cascade will clear.
Cast with a real mandate
Name a real job: underwrite a cascade without inventing manager capacity, clear a readership claim that people ops can reconcile under load, or defend a channel cut without dual-counted open rates. Give constraints: the evidence standard for cascade readiness, the audiences you will refuse to leave unowned, and the reach claims you will not teach when manager briefs are not ready. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in an all-hands review, a layoff cascade fight, or a dispute over who owns regional translation.
Prompt example: "Internal comms lead: list the top reasons to delay this message package, the audience with the weakest owner, the reach claim that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
Keep these outputs
- Top reasons to challenge, delay, or rewrite this message package.
- The reach or cascade claim that looks strongest and is least evidenced.
- The region, role, or channel that would break first under a forced send.
- What would make you accept residual message risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real audience map, channel inventory, manager brief pack, 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 all-hands or a regulatory notice, run this seat after legal and people ops attacks so it can use earlier objections as ammunition.
When the plan leans on a single Slack channel, a single "managers will cascade themselves" promise, or a single hero writer, force the seat to price concentration risk in writing. Ask what happens if the message board still hosts retired owners, if comms still lacks a named on-call for rumor spikes, or if leaders keep teaching talking points comms already retired. Pair with war-game an all-hands message, war-game an internal memo, war-game a layoff comms plan, pretend you are the executive assistant, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a reorg or a values statement rewrite, ask the internal comms lead seat to map every claim that still assumes last quarter's channel ownership. Contractor lists, partner portals, and regional Slack spaces count. A comms memo that looks clean in a slide while managers still pin to retired talking points will fail on the first rumor wave.