Emergence

The phenomenon where a system exhibits properties, behaviors, and patterns that NONE of its individual components possess—the whole is genuinely different from (not just greater than) the sum of its parts. Wetness emerges from H2O molecules (no individual molecule is wet). Consciousness emerges from neurons (no individual neuron is conscious). Traffic jams emerge from individual drivers (no individual driver is a traffic jam). Markets emerge from individual traders. As a mental model: emergence reveals that REDUCTIONISM HAS LIMITS—you cannot fully understand the system by understanding the components, because the system-level properties arise from INTERACTIONS between components that don't exist at the component level.

When to use it

When system-level properties can't be explained by component analysis; when interaction design matters more than component design; when reductionist analysis is missing emergent properties; when understanding that the whole is different from the sum of parts would improve system design.

How it can help

When analyzing complex systems: look for emergent properties that exist ONLY at the system level and cannot be predicted from component analysis alone. The diagnostic: could you predict this system property by studying individual components in isolation? If not: it's emergent. For organizations: culture is emergent—it arises from interactions between individuals and cannot be reduced to any individual's behavior. For products: user experience is emergent—it arises from the interaction between features, not from any single feature. The practice: design for INTERACTIONS, not just components, because emergent properties arise from interactions.