Design Software: Shaping Architecture's Limitations

Edition 55: Tools Whisper Their Own Limits

The Idea

Something I’ve noticed with new buildings is that you can almost tell which software they were designed in. For instance, if you take Revit, it’s very hard to freely create non-orthogonal, non-linear geometries, and it’s very easy to create repetitive elements, so it lends itself to a particular way of building.[1]

Who said it (and the context)
This observation comes from Tatiana von Preussen, co-founder of London practice vPPR Architects, and appears in Barnsworth Burning’s Tools collection. It highlights how digital tools, like any craft implement, carry built-in biases that quietly steer what creators can easily imagine and execute. The site presents it as a prompt to notice the invisible hand of our instruments.[1]

A small expansion
Every tool arrives with its own grain—its favored moves, its resistance points, its shortcuts. Revit rewards right angles and repetition because its underlying logic was built for efficient documentation of standard construction. The result is not neutral: buildings start to look like they were born in that software. The same holds for design programs that make certain curves effortless and others laborious, or code editors that nudge toward modular, reusable patterns. Makers who stay unaware of these leanings risk letting the tool finish their sentences. Awareness turns the tool from a hidden director into a visible collaborator—one whose tendencies can be accepted, resisted, or deliberately subverted.

Another lens on the idea
Marshall McLuhan’s famous line “the medium is the message” offers a broader frame. Where von Preussen points to a specific software’s geometry bias, McLuhan reminds us that every technology reshapes not just what we make but how we think about making. The hammer does not merely split stone; it changes what a sculptor sees as possible in that stone. Digital tools do the same at scale: they compress time, multiply options, and embed assumptions about efficiency and repeatability. The thoughtful designer learns to read the tool’s unspoken preferences the way a carpenter reads wood grain—then decides whether to follow or cut across it.[1]

Why this matters across art and design

  • Studio art & craft: Choosing a brush, chisel, or tablet app is never neutral; each surface and implement invites certain marks and discourages others.
  • Product & UX design: Prototyping tools that favor quick iteration can quietly discourage radical structural rethinking.
  • Architecture: Software defaults influence everything from floor-plate shapes to façade rhythms.
  • Visual identity & branding: Font tools, grid systems, and motion libraries steer toward particular aesthetics unless the designer intervenes.

Two quick drills

  1. Tool Audit (15 minutes)
    Pick a recent project. List the three main tools you used. For each, note one thing it made easy and one thing it made hard. Then sketch or describe one alternative approach that would have required fighting the tool’s grain.

  2. Medium Swap (ongoing)
    For your next small exploration, begin in an unfamiliar medium or app for the first 20 minutes. Notice what new possibilities (or frustrations) appear. Carry one of those discoveries back into your usual workflow.

Thread to remember
This edition deepens the newsletter’s ongoing conversation about attentive making by turning attention to the instruments themselves—the silent partners that shape every mark we make.

Sources

  • Central idea drawn from the Tools collection on Barnsworth Burning.[1]
  • Complementary perspective informed by McLuhan’s media theory, referenced across multiple site collections.[1]

Try this today:
Before opening your usual software, pause and ask: “What does this tool want me to make?” Then decide whether that’s what you actually want.