a builder's codex
codex · patterns · No-decision-as-competitor vs. battle-card-driven competitive workflows

No-decision-as-competitor vs. battle-card-driven competitive workflows

Position A — The real competitor is no-decision

Position B — Battle cards as workflow primitive; sameness is a barrier requiring competitor-aware differentiation

Conditions distinguishing them

Resolution / synthesis

Not a contradiction at the strategic level — both can be true in the same pipeline at different stages. The genuine contradiction is in resource allocation: where to spend PMM hours.

Dunford's argument implies under-investing in battle cards (they fight the wrong battle). Gartner's argument implies battle cards are first-class. Resolution: allocate PMM time by deal-stage shape of your pipeline:

Run a quarterly loss-reason audit to know which stage is leaking. Most teams default to battle cards because they're more legible — Dunford's claim is that for many products this is mis-allocation.

Open the interactive view →