War-game a content ops handoff before CMS roles, publish rights, and review SLAs harden into who can change live pages.
Content ops handoffs fail when the outgoing owner keeps quiet admin rights, when review SLAs exist only in a slide, when SEO and legal gates disappear under publish pressure, and when "we transferred the Notion" stands in for access, backups, and incident ownership. A shared folder is not evidence.
What must be frozen
State which surfaces move, who gains and loses publish rights, the review path for legal and brand, the rollback owner for a bad publish, and the success metric after two publish cycles. Attach CMS role maps, redirect ownership, analytics access, and the kill criteria if quality or incident response degrades. If marketing, web ops, and legal disagree on who can ship without review, reconcile before seating.
Name the decision you will make if the war game finds nothing new, and the delay criteria if any live surface lacks a named publisher after the flip.
Failure modes
- Ghost admins: former owners who retain write access "just in case."
- Review theater: gates that vanish when a launch calendar tightens.
- SEO orphans: redirects and canonicals nobody owns after the move.
- Incident blur: no one owns a bad publish outside business hours.
- Tool fiction: analytics, CMS, and DAM access that still sits with the old team.
Optional counsel seat if regulated claims or health claims ride on the pages. Optional security seat if CMS accounts share SSO with privileged systems.
Run it
Feed Pingpong the handoff memo, role map, and open risk list. Early passes steelman the RACI. Later passes attack from outgoing owner, incoming publisher, legal, SEO, and web ops seats. End with a pass that turns surviving objections into tighter access cuts, clearer review SLAs, or a hold. Delete invented "knowledge transfer complete" claims and dual-counted review hours.
Ask marketing and web ops seats to price the first bad-publish story under the new ownership. If day-one language promises review that capacity cannot clear, publishers will ship around the gate. Write the intended review path, the emergency publish exception, and the language you will refuse, then attack whether quality still holds under that discipline.
Force a day-after narrative: what happens if a redirect breaks overnight, if the outgoing owner is unreachable, or if legal volume spikes on one ambiguous claim. If those stories are stronger than your mitigation plan, fix the handoff before you flip rights. Related: war-game a docs overhaul, war-game a brand voice guide, pretend you are the product marketing lead, war-game a tooling consolidation, and the war-game decisions hub. Process: how to run a Pingpong.