Irreducibility

The property of a system where the behavior or function CANNOT be simplified without loss—it requires all of its components and their specific interactions. An irreducible system is one where removing any component destroys the function. Analogies: a three-legged stool with one leg removed (collapses), a key with one tooth removed (doesn't open the lock). As a mental model: irreducibility identifies the MINIMUM VIABLE SYSTEM—the smallest configuration that still produces the desired function. Below this threshold: the system doesn't work at all. Above it: additional components may improve but aren't essential. The practical import: irreducible systems have NO SLACK—every component is critical, making the system both elegant and fragile.

When to use it

When identifying minimum viable systems or products; when distinguishing between essential and optional system components; when fragility assessment requires knowing which components are irreducible; when the tradeoff between elegance (irreducibility) and resilience (redundancy) needs explicit management.

How it can help

Identify whether your systems are irreducible or have reducible slack. For irreducible systems: every component is critical—invest in reliability and redundancy because any single failure is catastrophic. For reducible systems: identify the essential core and the optional additions. The practice: (1) For each component: what happens if it's removed? If the system breaks: irreducible component. If it degrades: reducible but valuable. If nothing changes: unnecessary. (2) Design for the right level of irreducibility: too irreducible = fragile; too much slack = inefficient. For MVPs: find the irreducible core that delivers the essential function.