War-game a values statement before employees, candidates, and customers treat a soft draft as the official culture contract.
Values statements fail when slogans outrun operating reality, when hard tradeoffs are buried in inspiration, when hiring and performance systems ignore the words, and when a single memorable line becomes the only thing anyone quotes against you. A fluent poster is not evidence that the message will survive a careful and hostile read.
Freeze the statement
State the audience, the behaviors the values must change, the tradeoffs you will stand behind, and the outcomes you will not invent. Attach the draft, any related code of conduct, the hiring and review hooks, and the distribution plan. If the statement mixes brand marketing, a compliance policy, and a culture speech, split them. A war game needs one move under fire at a time.
Write the decision you will make if the war game finds nothing new. Also write the delay criteria if a material claim still lacks an operating example.
Seats that matter
- Employee. What feels evasive, hypocritical, or unfair after prior messages.
- Candidate. Which lines will be tested in interviews and early weeks.
- Customer or partner. Promises that sound newly fragile when delivery slips.
- Journalist or leak seat. The line that becomes the headline if contradicted.
- Skeptic. The claim that looks strongest and is least evidenced in ops.
Attach the same source pack to every seat. Secret exceptions for leadership only create fake calm.
Loop the review
Feed Pingpong the draft and operating exhibits. First pass steelmans the narrative. Later passes attack from employee, candidate, customer, and leak seats. Final pass turns surviving objections into cuts, clearer behaviors, or a hold. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
If the statement only works with a private side channel that softens the hard parts, force the review to surface that before publish. A public values page that depends on whispered exceptions trains people to ignore the written word. Write the hiring hooks, the manager FAQ, and the contradiction response path into the package, then ask the employee and leak seats to attack those plans.
When the statement announces a hard tradeoff, force employee and candidate seats to invent the FAQ you will need within a week of publish. If you cannot answer those questions with the same facts as the statement, the package is not ready. Add the FAQ owner and the first-week channel plan before you hit publish.
Pair with war-game a community guidelines change, war-game an all-hands message, war-game a founder letter, war-game a brand repositioning, and the war-game decisions hub. See how to run a Pingpong and how it works.