Embrace Complexity for True Simplicity
Edition 54: Simplicity on the Other Side of Complexity
The Idea
“I would not give a fig for the simplicity this side of complexity, but I would give my life for the simplicity on the other side of complexity.”
— Oliver Wendell Holmes Jr. (via Barnsworth Burning)
The idea
Many makers chase an easy, surface-level simplicity by stripping away details too soon. The deeper, more valuable kind arrives only after you have fully engaged the messy reality of a problem—its contradictions, constraints, and hidden relationships. Only then can you return to something that feels effortless because it has earned its clarity.
Who said it (and the context)
Oliver Wendell Holmes Jr. (1841–1935) served as an Associate Justice of the U.S. Supreme Court for nearly three decades. A Civil War veteran and influential legal thinker, he brought a pragmatic, experience-based approach to law. The quote appears in Barnsworth Burning’s “Simplicity” collection, where it sits alongside reflections on restraint, subtraction, and the hard-won elegance that follows deep engagement with complexity.[1]
A small expansion
In practice, this means resisting the urge to simplify prematurely. A visual identity designer might first explore dozens of directions, contradictory briefs, and cultural references before distilling to a single mark. A product team might prototype the full, tangled user journey before carving it down to the essential flow. An architect might wrestle with site forces, material behaviors, and program needs until a single gesture resolves them all. The resulting work feels light not because nothing was added, but because everything unnecessary has been tested and removed.
Another lens on the idea
Christopher Alexander’s pattern language offers a parallel path. Rather than imposing a simplistic grid or hierarchy on a city or building (what he called a “tree” structure), he advocated for overlapping, semilattice relationships that reflect real human life. The apparent simplicity of a well-resolved design emerges only after mapping the rich, interconnected needs of its inhabitants. Where Holmes speaks of passing through complexity, Alexander shows how living systems naturally generate that deeper order when allowed to unfold.[2]
Why this matters across art and design
- Visual identity: Logos and systems gain lasting power when they resolve competing tensions rather than ignore them.
- Product & UX: Interfaces become intuitive only after the team has lived inside the full complexity of user contexts.
- Architecture: Enduring buildings feel simple because their forms have absorbed and answered the full range of site, material, and human forces.
- Studio art: Works that resonate often hide years of struggle behind a seemingly effortless surface.
Two quick drills
Complexity Pass (30–60 minutes)
Take a current project. Spend time deliberately adding complexity—extra constraints, contradictory requirements, or unexpected references. Then strip back. Notice what remains stronger because it survived the test.After-the-Fact Audit (ongoing)
Review a finished piece. Ask: “What complexity did this simplicity resolve?” Document one instance where wrestling with mess led to clearer results.
Thread to remember
This edition deepens the ongoing thread of attentive making by showing how restraint is not the absence of effort but the reward that follows full engagement. It builds on prior explorations of constraints, emergence, and the Design Squiggle’s journey from chaos to clarity.
Sources
- Central idea drawn from Barnsworth Burning’s “Simplicity” collection, featuring Oliver Wendell Holmes Jr.’s observation on simplicity beyond complexity.[1]
- Connection to Christopher Alexander’s “A City Is Not a Tree,” referenced in the site’s Cities and Design collections.[2]
Try this today: In your next sketch or prototype, intentionally complicate one aspect before simplifying. Observe what the deeper clarity reveals.