Load-bearing

Any element, narrative, visual, or technical, that carries structural weight rather than serving as decoration. The test is removal. If the system collapses, it was load-bearing. If nothing changes, it was decoration.

Last updated March 2026

What It Is

A load-bearing element is any element, narrative, visual, or technical, that carries structural weight. Remove it and the system collapses. Leave a decorative element out and nothing changes. That distinction is the test.

The term comes from construction. A load-bearing wall carries the weight of the structure above it. You can take down a partition wall and the building stands. You take down a load-bearing wall without proper support and the ceiling comes down. The wall looks like the other walls. The difference is invisible until it matters.

Design systems work the same way. A visual choice can look significant and carry nothing. Another can look incidental and hold the whole thing up. The error is treating the two as interchangeable: adding decoration without knowing what is structural, or removing an element without knowing what it was holding.

Load-bearing status is not a property of the element itself. It is a property of the system the element lives inside. Photography is decorative in a product catalog where the brand is established by other means. The same photography is load-bearing in a brand where the visual quality is the only proof of the product’s quality. Same photographs. Different structural role.

Where It Comes From

My father ran construction sites. He held the whole picture while fifty trades worked their piece. He knew which walls were bearing weight and which were partition. Which pours were structural and which were finish. Which connections between trades had to happen in sequence or the whole phase slipped.

That picture, knowing what was holding what, was the job. Not the credentials. Not the authority. The picture.

I recognized the same requirement in every system I’ve worked inside since. An enterprise codebase. A brand identity. A photography system. A narrative. The question is always the same: which elements are holding weight, and which are just there?

The test is removal. Pull the element out, mentally or literally, and watch what happens. If the system holds, the element was decoration. If the system collapses, or reveals that it was propped up against something that is now gone, the element was load-bearing.

This is not the same as asking whether an element is good, important, or worth keeping. Decorative elements can be good. Load-bearing elements can be ugly. The distinction is structural, not evaluative.

How It Works

Identifying load-bearing elements requires running the removal test against each element in the system, in context.

The test has two parts. First: remove the element and ask what changes. Second: ask what was depending on it that is now exposed. The second question is usually harder. The thing the element was holding often becomes visible only after it is gone, which is too late.

In practice, this means asking the structural question before building, not after. What is this element doing? What is it carrying? What depends on it? If you cannot answer those questions, the element is probably decorative, or it is load-bearing in a way you have not thought through. Either way, that is information.

The mistake is designing for surface coherence: making things look right without tracking what each element is holding. A brand system can look complete and still be fragile. Every element does its visual work. None of them carry weight in a way that would survive the removal of any one piece. When something changes, the whole thing goes sideways because everything was decorative.

A resilient system has identifiable load-bearing elements and knows which ones they are. The people working inside the system know what not to touch without understanding the consequences. They know which decisions carry weight and which ones are available for revision.

Three Applied Examples

Photography Direction (Aiden Jae)

The photography in the Aiden Jae jewelry brand is not a style choice. It is the only evidence that the product’s quality claim is true. The brand operates at a price point between fast fashion and traditional luxury. The sustainability is real. The recycled gold is real. The responsible sourcing is real. None of that is visible to a stranger buying through a screen unless the photograph shows it.

Lighting that shows how gold actually catches light, how a stone sits in a setting, what the texture looks like up close. No retouching that hides the hand-finishing. No color grading that promises something the piece cannot deliver. The photograph is the proof.

Remove the photography direction (replace it with generic product shots, or inconsistent shots across the catalog) and the brand collapses into a generic Shopify template. The identity system, the custom platform architecture, the typography: they all assume a photograph that proves the claim. Without the proof, everything else performs a claim it cannot substantiate.

The photography is load-bearing. Not because it is beautiful, though it is. Because the entire brand argument rests on it.

Hand-drawn Marks (Altrueism)

The first round of explorations for Altrueism went where most craft brands go: script fonts, cursive motion, the visual language of handmade warmth. It looked right. It matched the category. It was the wrong answer.

Script fonts say handmade. They do not prove it. The client made handcrafted objects with sustainable ethics. Their world was communal craft, care, rhythm, slow making. A script font performs an emotion the client did not actually have. Warmth as a category signal, not warmth as the truth of the work.

The breakthrough was the hand-drawn mark system. Scanned originals, intentional irregularity, weathered stone textures. The roughness says: we do not hide behind polish. We show our work. The marks are visual evidence of human choice, not an aesthetic gesture toward the idea of human choice.

Remove the hand-drawn marks and replace them with smooth vectors and the transparency claim disappears. The copy can still say it. The visual system no longer proves it. The element was load-bearing because it was doing the proof work, not the decoration work.

Design System as Governance Structure (Encore)

Twelve years on an enterprise platform. The SCSS design system was not a style guide. It was a set of constraints encoded in the code itself. If a color value was not in the variables file, it did not belong. If a component was not built from existing patterns, the code made that visible.

The system held the original intent legible through every handoff. It was the structure that made it possible for hundreds of engineers to touch the same product over a decade without producing something nobody designed. The variables file was the artifact: a design system encoded as constraints that held the line so the people inside it could focus on work that required their judgment.

Remove the design system (or let it degrade, which amounts to the same thing) and drift fills the space. Hundreds of reasonable decisions accumulate into something nobody chose. Each one fine in isolation. The cumulative effect: a product that stops feeling like one product. The design system was load-bearing. Its presence was the condition under which coherence was possible.

Connected Concepts

  • Drift — Drift removes load-bearing elements without anyone noticing, because the removal was never a single decision. It happens through accumulation.
  • Fidelity — The gap between what was meant and what survived. Load-bearing elements are what fidelity depends on.
  • Accommodation Design — Identifying what a system actually needs. Load-bearing analysis is the structural version of that question.
  • FormWork — The coordination harness that holds tools in position while the work is wet. FormWork itself is load-bearing during the process.
  • Scaffold — A scaffold is temporary and is supposed to become unnecessary. A load-bearing element is permanent: removing it is a structural event, not cleanup.

Go Deeper