Methodology · 7 min read

Category Design

A point of view on a different category and the work needed to establish it.

Al Ramadan, Dave Peterson, Christopher Lochhead and Kevin Maney · View sources ↓

At a glance

Use this when
An existing market category limits how buyers understand the problem you solve.
What you will work towards
A point of view on a different category and the work needed to establish it.
Bring to the reading
A specific decision from your work and the customer evidence you have so far.

What it is

Category design is a discipline for defining, developing, and dominating a new market category, rather than competing for share inside an existing one, developed by Al Ramadan, Dave Peterson, Christopher Lochhead, and Kevin Maney in Play Bigger (2016). Its central claim is that in a crowded or commoditised market the largest returns go not to whoever wins the most share of an existing category, but to whoever legitimately creates and owns a new category that reframes the buyer's problem: buyers stop asking "which vendor in this category is cheapest" and start asking "who invented the thing that solves this problem I didn't have a name for." The methodology runs in three continuous phases: Define (name the "Legendary Problem", the big, urgent problem the market has not yet recognised or named, and the "Point of View", or POV, that reframes it, positioning your product as the origin of the new category), Develop (build the proof, content, and flagship customers that make the category credible rather than a marketing invention), and Dominate (sustain and defend the category over years as competitors and imitators try to ignore or co-opt the vocabulary). It differs sharply from the other tools in this category: Bowman's Strategic Clock, the Perceptual Map, and Product Differentiation Strategy all help a company find or defend the best position inside an existing category; category design questions whether the existing category is the right container at all, and if not, sets out to build a new one.

When to use it

  • Every deal is decided on price or a feature checklist, and win/loss interviews show the market cannot tell you apart from several close competitors, no matter how the Perceptual Map or Bowman's Clock is redrawn.
  • Your product solves a problem meaningfully differently from how the existing category defines it, and forcing it into that category's comparison criteria consistently undersells what it does.
  • Analysts, press, or investors keep asking "so who do you take share from?" and the honest answer sounds defensive, a sign the existing category is capping the ceiling regardless of how much share you win within it.
  • Leadership is weighing a genuinely novel go-to-market bet, not a messaging refresh, and has the multi-year budget and executive sponsorship a real category claim requires.
  • A well-funded new entrant is attempting to define a new category around a problem adjacent to yours, and doing nothing risks ceding that framing to them by default.

How to run it

  1. Test whether category design is actually warranted before starting. Most companies should not attempt this: it is a multi-year, executive-sponsored bet, not a campaign. The test is whether winning more share inside the existing category would still leave you with a capped ceiling; if out-executing competitors inside the current category would solve the problem, use Product Differentiation Strategy instead.
  2. Name the Legendary Problem from evidence, not internal narrative. Source it from win/loss interviews, Voice of the Customer signal, and discovery calls: the big, urgent problem buyers describe unprompted that no existing category's vendors are built to solve, not a problem your team has decided the market should care about.
  3. Draft the Point of View. Write what is broken about how the market currently frames the problem, why now (the trend that makes the old frame obsolete), and the new category name and definition, positioning your product as the category's point of origin rather than a challenger within an old one.
  4. Build proof before claiming the category publicly. Produce category-defining content (a report, original research) that demonstrates the Legendary Problem is real and widely felt, not just asserted; a category claim with no evidence behind it reads as a marketing wrapper the moment anyone tests it.
  5. Align every internal function on the same vocabulary before it goes external. Sales, support, and product should all describe the problem and the category the same way; a company that markets a new category while sales still pitches the old one confuses buyers rather than reframing anything.
  6. Seed the category through analysts and flagship customers, not advertising. Brief analyst firms on the vocabulary ahead of their research cycles, and recruit two or three flagship customers willing to speak publicly about it, since a category becomes real to a buyer once a peer they trust uses the term, not when a vendor coins it.
  7. Measure unprompted category-term usage, not just brand awareness. Track how often prospects, press, and analysts use your category name unprompted, in inbound enquiries, analyst reports, or a competitor's own marketing; this is the real signal the category is taking hold.
  8. Sustain the category for years, not one launch cycle. Treat Dominate as an ongoing programme: keep evangelising, defend the term as imitators start using it, and refresh the POV as the market evolves; ownership of a category name lapses the moment a company stops actively reinforcing it.

Cadence & ownership

PMM or marketing leadership originates and maintains the Point of View in direct partnership with the founder or CEO; a category claim only carries credibility with visible executive sponsorship, not a marketing team acting alone. Treat this as a multi-year programme, reviewed at least annually and whenever a new entrant attempts to co-opt the vocabulary, not a single campaign with a launch date and an end date. Analyst relations and content or PR functions execute the ongoing seeding cadence; the Quarterly PMM Planning Framework is the natural mechanism for tracking unprompted term-usage share each quarter and deciding whether the POV needs refreshing.

Example

Fictional workplace-safety compliance company Ridgeline had competed for three years inside the crowded "EHS (environment, health, and safety) software" category, where a dozen near-identical vendors sold checklist and incident-tracking tools and every deal came down to price; win rate held flat near 22% and average deal size had not moved in two years. Win/loss interviews found the real unmet problem was not "we need EHS software" but that safety leaders were held accountable for incidents no existing software gave any warning of; Ridgeline's product used sensor and behavioural data to flag risk before an incident occurred, a capability the EHS category's own vocabulary had no room to describe. Rather than continuing to compete as a better EHS tool, PMM and the CEO built a POV naming the Legendary Problem as reactive safety management leaving companies blind to preventable incidents, and defined a new category, "Predictive Safety," with Ridgeline positioned as its origin. They published a "State of Predictive Safety" research report surveying 200 safety leaders, 68% of whom described a preventable incident their existing software gave no advance warning of; briefed two industry analyst firms on the vocabulary ahead of their annual research cycle; and secured three flagship customers, a logistics operator, a manufacturing plant, and a construction firm, willing to speak publicly about switching from reactive to predictive safety. Within a year, unprompted use of "predictive safety" in inbound demo requests rose from zero to 34% of qualified pipeline, average deal size rose 41% as procurement stopped benchmarking Ridgeline against checklist-tool pricing, and win rate in deals where the prospect used the term unprompted reached 61%, more than double the 24% rate still recorded in deals framed as generic EHS software.

Pitfalls

  • Declaring a category with no Legendary Problem behind it. A category name invented from internal ambition rather than evidenced buyer pain reads as a marketing wrapper the first time a prospect or analyst tests it, and reps quietly revert to the old, familiar language because buyers do not recognise the new term. Recovery: revalidate the Legendary Problem against fresh win/loss and Voice of the Customer evidence; if buyers do not recognise the problem unprompted, the claim is premature and the budget should return to Product Differentiation Strategy instead.
  • Fully resourcing Define and Develop, then abandoning Dominate. Companies often invest heavily in the initial launch, then stop, and a well-resourced competitor either ignores the new term or co-opts it without doing the underlying work. Recovery: budget category design as a standing multi-year programme with a named owner and a fixed cadence, and track unprompted term-usage share as an ongoing metric, not a launch-week result.
  • Confusing category design with a rebrand. Swapping a homepage headline to a new category name without the Legendary Problem evidence and a flagship customer reference fools no one, and can damage credibility when a sceptical buyer tests the claim and finds nothing behind it. Recovery: gate any external category claim on the evidence base, the published POV, and at least one flagship reference being ready before the term appears in copy.

How the ideas connect

Choose where to go next

Make it useful

Bring it back to your work.

Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.

Check your understanding

Practise applying Category Design in five short scenarios.

5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.

Sources

← All entries in Competitive Strategy · Try the category quiz