I used to think design was about the product. It took me a while to realise it was about what the product makes possible between people.
Every product and service designs relationships. Not just experiences. Relationships. Between people, between organisations, between communities and systems. The product is the visible output. But underneath it, something else is being shaped.
We tend to measure design through familiar lenses. Usability. Efficiency. Adoption. Engagement. These describe what the product does. They say less about what the product changes.
A product changes how people behave. A service creates dependencies. An interface determines what information someone can access and what actions they can take. A platform shapes who participates, who has power, and who gets left out. Those are not product features. They are relationships the product has created around itself.
The Product Is Rarely the End of the Story
In my own work, I design products that sit at the intersection of satellite data and human decisions. A farmer trying to access credit. An insurance company evaluating risk. An infrastructure team monitoring assets across thousands of kilometres. What we are building in each case is not just a dashboard or a data pipeline. We are building the relationship between complex technology and the human being who has to trust it enough to act on it.
That is a different kind of design problem. It asks different questions.
Think about something as ordinary as a digital service that makes a process more efficient. We celebrate reducing the steps from ten to five. But what else changed? Did people become more independent or more dependent on the system? Did they gain more agency or simply have fewer choices? Did the interaction become more connected or more transactional?
These questions do not replace the standard measures of good design. They sit alongside them. And they become more important as the products we build touch more parts of people's lives.
Asking What We Are Creating, Not Just What We Are Building
Many of the problems we are dealing with as designers today are not isolated problems with isolated solutions. Climate adaptation, public health, infrastructure, financial inclusion, and AI all involve multiple people, institutions, technologies, and systems interacting with one another. There is not always a single user. There is not always a single problem. And there is certainly not always a single solution.
So the design question has to expand. Instead of only asking what should we build, we could also ask: what relationships and conditions are we creating by building it?
The product we ship becomes part of someone's routine. Part of an organisation's process. It changes how two groups interact. It creates new expectations. It removes some dependencies and creates others. Those small changes eventually become part of a much larger system, whether we designed for that or not.
Maybe the most important thing we design is not always the thing we put in a portfolio. Sometimes it is what happens between people because that thing exists.
And if that is true, then designing well is not just about making better products. It is about becoming more deliberate about the relationships those products make possible.
This idea of relational infrastructure, that the less visible output of design is the network of behaviours, trust, and participation that develops around a product, comes from the work of Dr. Idrees Chasi. It is one of those ideas that sounds abstract until you start looking at your own work through it. Then it becomes difficult to unsee.