Engineering teams often believe they can eliminate complexity through refactoring or new tools. In reality, essential complexity can only be moved, not removed. A caching optimization might reduce query times but introduces cache invalidation challenges.

This relocation behaves like physical conservation laws. Accidental complexity from poor abstractions can be reduced, but domain-required essential complexity remains. Authentication systems must verify identity; distributed systems must coordinate.

Six patterns consistently emerge: complexity relocation, knowledge relocation, decision relocation, failure mode transformation, testing burden relocation, and assumption visibility trade-offs. Teams should measure both sides of any trade-off.

Understanding these patterns helps architects make better decisions. Instead of asking 'how do I eliminate this?', ask 'where should this live?'. Recognizing irreducible complexity prevents chasing impossible simplifications while investing in lasting design patterns.