teaching-systems-thinking

Category Design Fundamentals

Also known as:

Understanding that markets, professions, and movements are structured by named categories — and that creating or redefining a category is more powerful than competing within an existing one.

Creating or redefining a category is more powerful than competing within an existing one.

[!NOTE] Confidence Rating: ★★★ (Established) This pattern draws on Play Bigger / Category Design.

Section 1: Context

Markets, professions, movements, and knowledge systems don’t emerge randomly—they crystallise around named categories that shape how participants think, compete, and organise. A teaching system fragments when educators, learners, and institutions lack a shared frame for what they’re building toward. In corporate settings, teams chase “innovation” without naming what category of innovation matters. In public service, policy-makers respond to problems without recognising they’re defending outdated category boundaries. Activists organise around symptoms rather than naming the category shift required. In tech, products proliferate within crowded categories (another “AI assistant,” another “project management tool”) while the most valuable breakthroughs happen when someone redefines the category entirely (personal computer, smartphone, container orchestration). The teaching-systems-thinking domain sits at the root: practitioners need to see how categories themselves are designed, named, and defended—not just work within them. Without this literacy, energy scatters. With it, energy concentrates into movements that reshape their fields.

Section 2: Problem

The core conflict is Category vs. Fundamentals.

Teams and organisations face a binary trap. They can either:

  1. Accept the category as given and compete ferociously on fundamentals—better features, lower cost, faster delivery, cleaner theory. This is exhausting, zero-sum, and rarely decisive.

  2. Question the category itself and invest in redefining it—risking that the fundamentals won’t matter if the frame itself is wrong.

Most practitioners oscillate between these, wasting energy. They optimise products within “project management” while a Slack redefines the category as “async team presence.” They publish papers within established academic categories while missing that the real breakthrough requires naming a new field. They advocate within existing policy categories while a genuine shift requires redefining what the problem even is.

The tension breaks systems when:

  • Organisations compete on fundamentals so fiercely they miss that the category is shifting beneath them.
  • Movements pour energy into perfect execution within an outdated frame.
  • Teaching systems mistake category literacy for cynicism and default to “just teach the content.”
  • Teams optimise the wrong metrics because they’ve inherited—not designed—their category.

The pattern teaches practitioners to recognise that category design itself is a design discipline. It’s not cynical. It’s foundational.

Section 3: Solution

Therefore, name the category you are stewarding explicitly, map how it is currently bounded and defended, and consciously choose which fundamental breakthroughs require category redesign versus excellence-within-frame.

This pattern works by making the invisible visible. Most organisations are already doing category design—they’re just doing it unconsciously, inherited from competitors or tradition. The shift happens when practitioners:

  1. Name the category openly. Not as a marketing label, but as a living boundary that shapes what problems are recognised, who gets to participate, what success looks like, and which fundamentals matter most. A teaching system that names itself as “systems-thinking education” (rather than implicitly competing in “STEM pedagogy” or “adult learning”) signals what’s actually being stewarded. A public health programme that names itself “community epidemic response” (not just “disease prevention”) reframes which stakeholders matter and which fundamentals get funded.

  2. Map the roots. Every category has a history—the assumptions, breakthroughs, and constraints that created it. Play Bigger calls this “category DNA.” Mapping it reveals which fundamentals are sacred (usually defensible) and which are inherited cargo (often quietly obsolete). A tech team discovering their “productivity software” category emerged from factory-floor metaphors will suddenly see why real-time collaboration and presence matter differently than task completion and reporting.

  3. Distinguish growth moves from category moves. Growth within a category comes from fundamentals excellence: faster, cheaper, cleaner, deeper. Category moves come from redefining boundaries, participants, success metrics, and which problems the category solves. A corporate division might grow 30% by improving fundamentals. It might grow 300% by redefining its category—but that requires different resources, risk tolerance, and leadership. Teaching systems thrive when practitioners know the difference viscerally.

The living systems aspect: categories are ecosystems. They have predator-prey dynamics (competitors within), symbiosis (adjacent categories), and succession (categories that replace each other). When you design a category consciously, you’re stewarding that ecosystem. You’re choosing what gets to flourish, what gets constrained, and how the system renews itself. Done well, this generates resilience: the category becomes coherent enough to resist noise but porous enough to adapt as the world shifts.

Section 4: Implementation

For Corporate Settings: Conduct a “Category Definition Sprint” with your product, strategy, and customer-facing teams. Ask: What category are we actually playing in? (Not the marketing answer—the lived answer. What do customers compare us to?) Map the fundamentals that drive competition within that category. Then ask: Which market shifts would require us to redefine the category, not just win within it? Assign one team to track category-level signals (new entrants that don’t compete on current fundamentals, customers asking for something the category doesn’t name, adjacent categories colliding). This team briefs quarterly—not to abandon your current category, but to give leadership signal-to-noise on when a category shift is becoming unavoidable. Unilever’s success with “purpose-driven brands” didn’t come from competing better on detergent fundamentals; it came from redefining the category from “cleaning products” to “values alignment.” Make that decision explicit.

For Government/Public Service: Policy frameworks are categories. Rename them. Instead of defending “healthcare delivery,” ask: are we stewarding “individual health episodes” or “population health systems” or “community resilience”? Each category produces radically different spending, metrics, and which stakeholders matter. Map your policy’s current category boundaries. Then trace: where are citizens and frontline workers already operating outside that boundary? Where are they naming problems the category doesn’t have language for? A public safety department that recognises it’s stewarding “incident response” (not “law enforcement”) suddenly sees prevention, mental health response, and community safety as fundamentals—not optional add-ons. Run a “boundary mapping” workshop: have frontline workers (not executives) draw the actual problem space. Most public sector decay happens because the category and the reality have silently diverged.

For Activist/Movement Settings: Movements lose power when they accept the opponent’s category framing. “Climate activists” accept the category as “environmental issue.” The deeper category redesign: “Climate is a values/justice/economics issue.” Civil rights movements didn’t win by competing better within the “racial hierarchy” category; they won by redefining the entire category to “human dignity.” Activists should name their category explicitly and defend it against co-option. Create a “category integrity check”: every six months, ask whether your movement is still stewarding the category you named, or whether it’s been pulled into a narrower frame. Document where the dominant narrative tries to redraw your boundaries. Publish that. A tenant union that names its category as “housing as commons” (not “fair rental prices”) changes which solutions make sense and which partnerships matter. Make the category redesign explicit to members.

For Tech/Product Settings: Don’t ship a feature until you’ve answered: does this strengthen our current category fundamentals or does it signal we’re playing a different category? Slack’s early decisions (persistent presence, searchable history, integration marketplace) weren’t “better messaging” fundamentals—they were building a category of “async team presence” instead of competing in “real-time chat.” Map your product roadmap against a “category coherence” matrix: which features defend your named category, which dilute it, which hint at a new category emerging? Use Play Bigger’s “category pyramid” discipline: define your category’s non-negotiables (the 3–5 fundamentals that must be true), the category creates (what it makes possible), and the category enables (what adjacent categories it depends on). This prevents feature creep that erodes category coherence. When you feel tension between two product directions, the tension often reveals a category choice that needs to be made explicit—and made once, not fought repeatedly.

Section 5: Consequences

What Flourishes:

When practitioners develop category literacy, energy concentrates. Teams stop hedging bets across incompatible fundamental improvements. A teaching system that clearly names “systems thinking education” (and accepts that this means certain pedagogies, certain metrics, certain stakeholder groups) suddenly runs with coherence. Decisions speed up because the frame is stable. Paradoxically, this also increases adaptability: teams can respond fast to signals that the category itself is shifting because they’re watching for that signal explicitly. Movements that name their category gain power to recruit, align, and defend—because members know what they’re stewarding. Market leadership often follows not from better execution, but from category design so clear that execution almost becomes secondary. The value creation score (3.5) reflects this: the pattern doesn’t generate new value types, but it focuses existing value creation intensely. Composability score (4.5) is high because once a category is well-defined, it becomes modular—other people can build within and adjacent to it with clarity.

What Risks Emerge:

This pattern carries real failure modes. Rigidity is the primary risk. Once a category is named and defended, practitioners can become so invested in its fundamentals that they miss when the category is obsolete. The pattern warns against this in its vitality reasoning: it “contributes to ongoing functioning without necessarily generating new adaptive capacity.” Teams can use category clarity as an excuse to not adapt. They defend the category so fiercely that they become the last defenders of a dying frame. Kodak understood film photography fundamentals perfectly; they didn’t fail on execution, they failed because they couldn’t imagine the category had changed. A second risk: false consensus. Naming a category creates the appearance of agreement while stakeholders may understand it entirely differently. An activist movement that names a category can fragment the moment that category is tested in conflict. A corporate category definition that the C-suite agrees to privately but doesn’t live into publicly becomes hollow. A third risk: category capture. The first team to define a category often gains disproportionate power over its boundaries. Movements can be co-opted when powerful actors redefine categories in ways that serve them. The Resilience score (3.0) reflects this: clear categories can actually reduce resilience if they become too brittle. Watch especially when stakeholder_architecture is also 3.0—a well-defined category with ambiguous or centralised ownership often fails under stress.

Section 6: Known Uses

Slack (Tech/Product Translation): Before Slack, the category was “enterprise messaging”—competing on features like encryption, compliance, integration count. Slack didn’t win that competition. Instead, they redesigned the category to “team presence and async work.” This meant archivability, searchability, and threadedness were non-negotiables (not add-ons). It meant integrations were part of the category’s core value (adjacent systems feeding into presence) rather than upsells. The category redesign allowed them to out-execute Skype, HipChat, and Microsoft Teams not because they were better at fundamentals within those competitors’ categories, but because they were playing a different game entirely. The category design was so coherent that employees began demanding Slack adoption—it solved a problem those competitors weren’t even naming.

The Civil Rights Movement (Activist Translation): Early civil rights organising worked within the dominant category: “racial integration within existing institutions.” Marginal gains, constant resistance. The category redesign—”human dignity” and “systemic justice”—reframed which fundamentals mattered. It wasn’t about getting black students into white schools faster (fundamentals competition). It was about whether a human being could live with dignity (category shift). This redesign unified disparate struggles (voting rights, housing, employment, criminal justice) under one coherent frame. It also recruited allies who cared about dignity more than specific policy wins. The power of category redesign became visible: competing better on “school integration logistics” would have generated marginal progress for decades. Redefining the category generated a movement.

Patagonia (Corporate Translation): Patagonia emerged into a “outdoor apparel” category already crowded with competitors optimising on price and distribution. Rather than compete on fundamentals, the founder Yvon Chouinard redesigned the category to “values-aligned gear for environmental stewards.” This meant certain fundamentals became non-negotiable: durability (so products lasted), transparency (about supply chains), and activism (the company took political stances). Competitors could outspend on marketing and outsource manufacturing cheaper. Patagonia couldn’t compete on those fundamentals—and didn’t need to, because they’d redefined what the category even meant. The category design also clarified who belonged to the community (values-aligned humans) and who didn’t. Over decades, this category coherence converted to market leadership, not despite lower volume, but through it. The clarity itself became the moat.

Section 7: Cognitive Era

In a networked, AI-enabled commons, category design becomes both more powerful and more fragile.

More Powerful: AI excels at pattern-matching across existing categories. It will optimise fundamentals relentlessly—faster, cheaper, more variants of the category’s core value. This means human category designers become the actual scarcity. The practitioner who can ask “should we even be in this category?” becomes more valuable than the analyst who optimises within it. Movements and organisations that invest in collective category literacy—not just following AI-driven optimisations—will resist capture and drift. For products: if AI can generate 100 design variants of “productivity software,” the strategic win goes to whoever defined the category itself. The meta-layer (category design) becomes where human judgment concentrates.

More Fragile: AI also makes category boundaries more porous and fluid. Recommendation algorithms and large language models can synthesise across categories, creating “category collapse.” A user asking an AI “what should I use to manage my team’s async communication?” gets answers that blur boundaries between Slack, Notion, Discord, and email—all serving similar functionality within different categories. This erodes the clarity that category design provides. Organisations clinging to category coherence while AI demolishes category boundaries risk becoming irrelevant. A teaching system that says “we are systems-thinking education, not STEM” might find that AI tutors teach both simultaneously, forcing a category redefinition. Second risk: algorithmic category capture. AI systems trained on category definitions crystallise them. If an LLM is trained on “healthcare = medical episodes,” it will perpetually reinforce that category even as communities try to shift toward “health = wellbeing systems.” Practitioners need to name which category the AI is being trained to optimise, not accept it as natural.

Leverage point: In the AI era, category design becomes a commons governance problem. Who decides the category boundaries that AI systems optimise within? This pattern, applied to AI governance, is critical. Open-source movements that name their categories explicitly (Linux as “collaborative infrastructure,” not “free software”) have held power better than those that accepted the dominant category frame. The same applies to AI: name the category before the AI system is trained to optimise it.

Section 8: Vitality

Signs of Life:

Observe for these markers that the pattern is working:

  1. Category language appears in casual conversation. Practitioners reference “our category” or “that’s outside our category” without sounding scripted. Leadership doesn’t need to repeat the category definition because it’s become the operating frame. This is visceral adoption, not compliance.

  2. Decisions refer back to category coherence, not just fundamentals metrics. You hear: “That feature makes sense if we’re in the ‘individual health’ category, but we redefined as ‘population health’ last year, so it doesn’t fit.” The category is actively constraining choices in a healthy way.

  3. Boundary conflicts become explicit and discussable. When a new opportunity comes that might pull the category in a new direction, teams name it: “This could work, but it would require us to shift our category.” That conversation is healthy. The alternative (silent drift) is decay.

  4. Stakeholders self-select into and out of the system based on category alignment. Employees who fit the category stay and recruit friends. Partners who understand the category deepen their work with you. This is vitality: the system reproduces itself through clarity.

Signs of Decay:

Watch for these patterns indicating the system is failing:

  1. Category definition becomes a wall decoration. It’s printed in the office, never referenced, and every decision violates it quietly. This is hollow category design. It looks good to outsiders but generates cognitive dissonance internally.

  2. Defenders become more rigid as the category loses relevance. Teams “protect the category” by defending it against new evidence, new stakeholders, new markets. This is a panic response, not stewardship. A tech company that says “we’re a ‘mobile-first’ company, period” while users shift to voice and ambient interfaces is defending category coherence against reality.

  3. Category is used to exclude rather than clarify. “That’s not our category” becomes a way to dismiss legitimate problems or shut down dissent. This collapses ownership—people experience the category as arbitrary gate-keeping rather than shared framing.

  4. Stakeholders outside the system don’t recognise the category frame. Customers, partners, and regulators use different language to describe what you do. This signals the category isn’t actually coherent in the world—it’s internally comfortable but externally misaligned.

When to Replant:

When the boundary mapping reveals that your category and reality have silently diverged—