THE IDEA
Design that sees the whole
Traditional design starts with a brief: build this product, solve this problem, create this experience. The designer works within the brief, producing something that meets the stated need. It’s a powerful approach - and it has a blind spot the size of the system the brief sits inside.
Systemic design combines systems thinking with design practice. Before designing a solution, it asks: what system does this solution exist within? Who’s affected beyond the intended user? What feedback loops will the design create or disrupt? What will the second-order effects be? How might the system adapt to the intervention?
The shift is from designing an object or service to designing an intervention in a system. A traditional designer creates a product. A systemic designer creates a change in the relationships, flows, and dynamics of the world the product enters. The product is still important. But it’s understood as a perturbation in a system, not an isolated object. This wider view doesn’t make design slower or more complicated. It makes it more likely to work - because solutions that account for the system they enter are less likely to produce unintended consequences, resistance, or failure.
IN PRACTICE
Designing with the system, not just for the user
A city commissions a new public transport route. Traditional design: study ridership data, optimise the route for passenger volume, design comfortable vehicles. Systemic design: map the entire mobility system - how people currently move, what alternatives exist, how land use patterns create demand, what happens to the communities the route connects and the ones it bypasses. The route design changes because the system view reveals that the biggest impact isn’t moving existing riders faster but connecting underserved communities to employment. The technical design is the same. The strategic design is completely different.
A charity designs a new programme to support refugees into employment. Traditional design: create workshops, build a CV template, connect with employers. Systemic design: map the full system of barriers - language, cultural navigation, credential recognition, employer bias, housing instability, childcare, trauma - and design an intervention that addresses the binding constraints, not just the visible ones. The programme looks different because the system view revealed that the bottleneck wasn’t skills or information but the interplay of housing instability and employer scheduling requirements.
A team redesigns its meeting practices. Traditional approach: shorter agendas, better facilitation, clearer action items. Systemic approach: map why the meetings exist in the first place, what information flows they serve, what decisions they’re supposed to support, and what happens between meetings. The redesign might conclude that three of the five regular meetings are compensating for a broken information system, and the real intervention is fixing the information flow rather than improving the meetings.
WORKING WITH THIS
The practice of seeing before solving
The first move in systemic design is always: understand the system before intervening. Map it. Walk it. Talk to the people who live in it. Understand what’s connected to what, what flows where, and what the existing dynamics are. This isn’t a delay to the design work. It IS the design work.
Then design for the intervention, not just the artefact. Ask: how will the system respond to this? Who will be affected beyond the intended users? What feedback loops will this create? What will happen in six months that won’t happen in the first week?
Finally, design for learning. In a complex system, you can’t predict exactly what will happen. Build measurement and feedback into the intervention from the start. Create checkpoints where you assess whether the system is responding as expected and adjust if it isn’t. The design isn’t finished when it launches. It’s finished when the system has settled into a new, better pattern.
THE INSIGHT
The line to remember
Designing a solution without understanding the system is like prescribing medicine without examining the patient. It might work. It might make things worse. You won’t know which until it’s too late.
RECOGNITION
When this is in play
You need systemic design when a well-designed solution keeps failing in practice. When the user loves the product but the system rejects it. When the brief is too narrow to capture what’s really going on. When different stakeholders have different definitions of the problem. When the design team says “we solved it” and six months later the problem is back in a different form.