What Is Symbiotic Design?

Ask most design conversations what a project is, and they will describe an object: a building, a product, a service, a poster. Ask the Symbiotic Design Framework the same question and it answers differently. A project is not a thing sitting still. It is a web of relationships, and the framework asks you to design those relationships on purpose, not leave them to chance.

## Relationships, not objects

The framework borrows its central idea from biology. In living systems, symbiosis describes how different organisms live together, and what each one does to the other by living close. The Symbiotic Design Framework takes that idea and applies it directly to design. {/* cite: concept-symbiosis | central logic borrowed from biology, applied to design */}

Its claim is simple to state and large in its consequences: every relationship inside a design, and every relationship a design has with the world around it, is not neutral. Relationships are dynamic. They evolve over time. And they can be read using the same principles biologists use to read symbiosis in nature, applied here to the messy, adaptive systems that human societies and creative work actually are. {/* cite: concept-symbiosis | relationships not neutral; dynamic, evolving; principles of symbiosis applied to complex adaptive systems */}

That is a deliberate shift of attention. The character of a design is not decided by its parts alone. It shows itself in how those parts relate to one another. {/* cite: concept-symbiosis | the character of a design system is revealed in the nature and quality of its relationships */}

## A working vocabulary, not a metaphor

Symbiosis could have stayed a nice comparison. The framework turns it into a working tool instead, naming six distinct patterns a relationship can take, from ones where everyone gains to ones that quietly cost one side. Those six patterns give a designer a genuine diagnostic vocabulary: a way to look at a real design system and name what is actually happening inside it, rather than assume every relationship is fine simply because nothing has broken yet. {/* cite: concept-symbiosis | operationalised through a practical typology of six primary relationship types for diagnosing interactions within any design system */}

## Where it starts: the human cornerstone

Every framework needs a starting point, a place its questions radiate out from. For this one, that starting point is not the object being designed. It is people.

The framework calls the Human component its absolute cornerstone, and gives it the first and most fundamental of its guiding questions, simply: Who? {/* cite: component-humans | the cornerstone, referential component of the framework; addresses the guiding question Who? */}

Who enacts design? Who experiences its outcomes? Whose values, needs, and aspirations shape its trajectory? Whose lives are impacted by its often-unseen consequences? {/* cite: question-0001 | the seed guiding question for the Human component, verbatim */}

Designer, author, and educator Victor Papanek put a version of the same point more bluntly: the only important thing about design is how it relates to people. The framework builds that conviction into its own structure, as the component everything else refers back to, rather than leaving it as a value to merely remember. {/* cite: component-humans | epigraph attributed to Victor Papanek, opening the framework's Human component */}

## What judges a relationship

Naming a relationship's pattern is only half the job. The framework also insists on judging it, and it gives four criteria for doing that, which it calls its four mottos.

Ethics comes first, and everything else answers to it. The framework treats ethics not as a fixed list of rules but as an ongoing pursuit of what is good for everyone, and it is explicit that the other three criteria are subordinate to it. It puts the consequence plainly: a relation cannot be deemed truly mutualistic, truly good for both sides, if it is ethically compromised, no matter what else it achieves. {/* cite: motto-ethics | foundational cornerstone; pursuit of good for all; other three mottos subordinate; a relation cannot be deemed truly mutualistic if ethically compromised */}

Sustainability asks whether a relationship protects ecological integrity and the interests of generations who are not in the room yet, the same obligation named in the well-known definition of meeting the needs of the present without compromising the ability of future generations to meet their own needs. {/* cite: motto-sustainability | profound ethical obligation across time; anchors in the Brundtland definition of intergenerational equity */}

Social responsibility asks whether a relationship upholds people's dignity and treats equity as an outcome to actually deliver, not just an opportunity to offer, actively working against injustice rather than staying neutral toward it. {/* cite: motto-social-responsibility | active, ongoing ethical commitment to collective well-being and substantive equity, challenging systemic injustice */}

And economics, reframed here as an ethical pursuit rather than a separate technical concern, asks whether a relationship creates shared prosperity and genuinely meets needs, on the understanding that economic systems are human constructs, which means they can always be redesigned. {/* cite: motto-economics | economics reframed as a profoundly ethical endeavour; shared prosperity and needs fulfilment; economic systems are human constructs, redesignable */}

## The lens, not the whole toolkit

None of this tells you yet how to size up the problem sitting in front of you, tame, wicked, or somewhere in between, before you choose a way to work on it. That question is the framework's next move, and the subject of the next article in this series.

What this introduction has tried to give you is the lens underneath everything else the framework does: design read as a live system of relationships, starting from people, judged against ethics first, and against sustainability, social responsibility, and economics after it.

If this way of seeing a project is useful to you, the newsletter is where we go deeper: one piece of the framework at a time, plus notes from real projects. And when you are ready to work through the whole framework hands-on, that is what the Academy is for.