Product

War-game a product principle before you publish it

War-game a product principle before teams treat a soft slogan as a decision rule that will hold under shipping pressure.

Product principles fail when they conflict with each other, when they cannot decide a real tradeoff, when exceptions become the real policy, and when support and sales still promise the opposite. A polished phrase on a wall is not evidence that the next roadmap cut will be clearer.

Freeze the scenario

State the principle in one sentence, the decisions it is meant to settle, the audience that must use it, and the success metric you will honor. Name the product areas and release trains that will feel it first. If the memo mixes a principle, a values rewrite, and a packaging change, 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 kill criteria: the contradiction rate, exception volume, or support confusion that would force a rewrite within a stated window.

Seats that matter

  • Product. Tradeoffs the principle actually settles versus slogans it only restates.
  • Design. Flows that become inconsistent if the principle is applied literally.
  • Engineering. Cost and complexity the principle quietly demands.
  • Support and sales. Promises that still conflict with the new rule.
  • Skeptic. The claim that looks strongest and is least tested on a real decision.

Attach the same source pack to every seat: draft principle, three recent decisions it would have changed, support themes, and the exception policy you actually intend to use. Secret data for one seat creates fake agreement.

Loop the review

Feed Pingpong the principle draft, decision examples, and seating briefs. First pass steelmans the rule. Later passes attack from design, engineering, and support seats. Final pass turns surviving objections into clearer wording, tests, or a hold. Agreement across passes is not proof. Keep the objections that still have evidence gaps.

Force each seat to apply the principle to one live roadmap cut and one live support edge case. If the principle cannot choose, or if every seat invents a different exception, rewrite before publish. A principle that only works when people already agree is decoration.

When the principle will be printed in hiring or sales materials, force people and GTM seats to find the first place it will be quoted out of context. If the quote still needs a long footnote to stay true, the wording is not ready for public use.

Pair with war-game a values statement, pretend you are the CPO, pretend you are the design lead, war-game a roadmap cut, and the war-game decisions hub. See how to run a Pingpong.