Pretend you are the community manager so moderation gaps, launch theater, and trust erosion fail before a community package absorbs them.
Optimistic community packages optimize for "engagement will rise." The community manager seat does the opposite. It asks which launch invents goodwill the guidelines will not support, which metric dual-counts the same thread as healthy and as unresolved, which "required" escalation is already optional in practice, and which cohort still lacks a named moderation owner. A neat Discord screenshot is not evidence that next quarter's trust will clear.
How to cast the seat
Name a real job: underwrite a guidelines change without inventing volunteer capacity, clear a launch claim that moderators can enforce under load, or defend a channel split without dual-counted active-user counts. Give constraints: the evidence standard for harm reports, the channels you will refuse to leave unowned, and the launch claims you will not teach when staffing is not ready. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a trust review, a launch gate, or a fight over who owns regional channels.
Prompt example: "Community manager: list the top reasons to delay this community package, the channel with the weakest owner, the trust claim that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
What to demand from the pass
- Top reasons to challenge, delay, or rewrite this community package.
- The engagement or trust claim that looks strongest and is least evidenced.
- The channel, cohort, or region that would break first under a launch spike.
- What would make you accept residual moderation risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real guidelines draft, staffing plan, escalation ladder, 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 launch, run this seat after legal and support attacks so it can use earlier objections as ammunition.
When the plan leans on a single volunteer cohort, a single "mods will cover weekends" promise, or a single hero channel, force the seat to price concentration risk in writing. Ask what happens if the guidelines still host retired definitions, if escalation still lacks a named on-call, or if brand still celebrates a meme the trust team already banned. Pair with pretend you are the community mod, pretend you are the brand lead, war-game a community guidelines change, pretend you are the support director, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a product launch or a pricing change, ask the community manager seat to map every claim that still assumes last quarter's talk tracks. Pinned posts, partner Discords, and social replies count. A community plan that looks clean in a slide while the forum still teaches retired SKUs will fail on the first launch week.