Creative Process Is Construction
conceptual-metaphor Architecture and Building → Creative Process
Categories: systems-thinkingarts-and-culture
What It Brings
The default metaphor for making things. So embedded it barely registers as metaphor. Of course you build software, construct an argument, lay the foundation for a project. The construction frame is the water we swim in.
Key structural parallels:
- Sequential phases — design, foundation, framing, finishing. Creative work gets organized into analogous stages: research, outline, draft, polish. The metaphor provides natural milestones and a sense of progress.
- Blueprints precede construction — you’re supposed to know what you’re building before you build it. Requirements, specifications, wireframes, outlines. The metaphor treats planning as a prerequisite, not an ongoing activity.
- Structural integrity — some elements are load-bearing and can’t be removed without collapse. This maps powerfully onto software (“load-bearing code”), arguments (“foundational assumptions”), and any complex artifact with internal dependencies.
- Scaffolding — temporary support structures that enable construction but are removed from the finished work. One of the metaphor’s best gifts: permission to build ugly temporary things in service of the final structure. Scaffolding in education (Vygotsky), scaffolding in code, scaffolding in writing.
- Specialists and trades — architect, engineer, builder, inspector. The construction frame naturally decomposes complex work into roles with clear responsibilities.
Where It Breaks
- Construction assumes you know what you’re building — this is the metaphor’s deepest limitation. A building that “discovers its purpose mid-construction” is a catastrophe. But creative work (a novel, a research program, a startup) often must discover its goal through the process of making. The construction frame makes this feel like failure rather than method.
- Buildings don’t grow, adapt, or reproduce — once constructed, a building is static. Software, organizations, and creative works evolve. The construction metaphor has no concept of organic change: post-construction modification is always “renovation” or “demolition,” never growth.
- The architect/builder split creates false hierarchies — in construction, the architect designs and the builder executes. When mapped onto creative work, this privileges “visionary” thinking over craft. In practice, the best creative work happens when thinking and making are the same activity.
- “Done” is a construction concept — buildings are finished. Creative works, software systems, and organizations are never finished — they’re abandoned or maintained. The construction frame makes ongoing evolution feel aberrant.
- Construction is subtractive risk — you reduce uncertainty over time. Creative work often increases uncertainty before resolving it. The metaphor makes the messy middle feel like a structural failure rather than a necessary phase.
Expressions
- “Building a feature” — implementing as construction
- “Laying the groundwork” — prerequisite work as foundation
- “Scaffolding” — temporary supporting structure (Vygotsky borrowed this for educational theory; programmers borrowed it back)
- “Blueprint” — a detailed specification preceding implementation
- “Architectural decision” — high-level structural choices that constrain all subsequent work
- “Load-bearing code” — code that cannot be removed without system collapse
- “Demolish and rebuild” — total rewrite as controlled destruction
- “Technical foundation” — the base layer upon which everything depends
- “Constructive feedback” — criticism framed as material contribution to the structure (as opposed to destructive criticism, which tears it down)
- “Back to the drawing board” — return to the blueprint phase after structural failure
- “This won’t scale” — structural inadequacy, as a building designed for three stories that someone wants to make into thirty
Origin Story
Brian Eno framed the distinction in his “Gardening vs. Architecture” talks, arguing that Western creative culture defaults to the architectural/construction model: conceive, plan, build, finish. He proposed gardening as the alternative (see creative-process-is-gardening). We use “construction” rather than “architecture” here because “architecture” has become its own rich metaphorical domain in software, and conflating the two creates confusion.
The construction metaphor for creative work predates Eno considerably. “Building an argument” appears in English rhetoric from at least the 18th century. Software adopted construction language from its earliest days. “Software engineering” was coined at a 1968 NATO conference precisely to import engineering’s rigor and predictability into programming. Whether that import succeeded is still debated.
References
- Eno, B. “Composers as Gardeners,” talk at Edge Foundation (2011) — the counter-frame
- NATO Software Engineering Conference (1968), Garmisch, Germany — the origin of “software engineering” as construction metaphor
- Brooks, F.P. The Mythical Man-Month (1975) — explores why the construction metaphor misleads software project management
- Vygotsky, L.S. Mind in Society (1978) — “scaffolding” as educational metaphor (coined by Wood, Bruner & Ross based on Vygotsky’s zone of proximal development)