Customer

War-game a customer council before you invite the first members

War-game a customer council before invitations lock a charter that still has soft NDAs, mixed incentives, and no owner for follow-through.

Customer councils fail when members expect roadmap vetoes you will not grant, when sales treats the room as a pipeline event, when legal never cleared disclosure rules, and when product leaves without a change log of what was heard. A polished invitation is not evidence that the company can run the room without leaking strategy or burning trust.

Freeze one charter

Write the council purpose, membership criteria, meeting cadence, what members get in return, and the decisions the council will never make. Then write the owner for agenda, notes, and follow-ups. If you cannot name the owner or the non-goals, the council is decoration.

Freeze the charter, NDA and disclosure rules, the invite list criteria, the feedback loop into roadmap, and the sales boundaries. Attach prior advisory history, competitive conflicts, and residual risk you will accept. Split any secondary customer advisory board relaunch into a separate decision if the mandates differ. One customer council under fire at a time.

Hostile seats

  • Product seat: feedback that never becomes owned work, or work that becomes quiet vetoes.
  • Legal seat: disclosure, competition, and quote rights that are soft or missing.
  • Sales seat: pipeline theater that crowds out honest critique.
  • Customer seat: time cost, access promises, and what happens when advice is declined.
  • Skeptic seat: the claim that looks cleanest and has the least evidence.

Ask each seat for material objections, missing exhibits, and the smallest change that keeps the intent without the theater. Optional security seat if demos or previews expose unreleased systems.

Private pass

Run that package in Pingpong. Sequential review helps because an early pass can defend the learning thesis while later passes try to kill soft NDAs and sales capture. Keep a change log of charter edits, invite criteria tightened, and residual risks accepted. If survival requires silence about a competitive conflict on the invite list, stop. Rewrite the charter or delay invitations.

Publish the operating calendar inside the package: when invites go out, when NDAs are due, and when product reports back on what changed. A customer council without dated follow-through is a listening tour with catering. Ask product and customer seats to break that calendar before anyone sends the first invite.

Related: war-game a customer advisory board, war-game a customer interview plan, pretend you are the largest customer, pretend you are the enterprise buyer, and AI for high-stakes decisions. Mechanics: how it works.