What Complex Systems have taught me about User Research
What Complex Systems have taught me about User Research
After a little over a year of doing user research in the UK public sector, I have started to think differently about what it means to understand a “user”.
Working across workshops, interviews, usability sessions, online research and site visits has taught me that, in complex systems, the person in front of you is rarely the whole story.
Here are three things that have changed how I approach research :
1. User research goes beyond the user
Complex systems are webs of information, data, decisions, processes and stakeholders, with people positioned somewhere within them.
The people (our users) we speak to are often just one node in something much bigger.
A decision made somewhere else, by someone else, months or even years earlier, can shape what that person does today. For instance, a policy decision can create a constraint, an organisational process can create a workaround and a technology decision can introduce friction that someone on the frontline quietly struggles.
This has made me increasingly interested in the ecosystem around a user, not just the user's interaction with a service.
My learning is that the user is not separate from the system, they are a part of it.
2. Observation on the ground makes the system visible
What people do in a set-up environment — a workshop, usability test or interview — can be very different from what they actually do in their own space.
The true scale of a system rarely hits you on a polished Miro board. It hits you when you visit a site and stand in the operational environment.
On paper, a service blueprint might show a clean, single-step interaction. On site, that same step can shatter into a long chain of micro-moments: nervous waiting, manual handoffs, tedious double-checking, repeated data entry, and people relying on informal workarounds to bridge gaps left by digital tools.
Systemic complexity doesn't always live inside the boxes we draw. It lives in the messy white space between them, in the unwritten rules, shadow processes, workarounds and small acts of adaptation that rarely make it onto the page.
Observation has therefore become more than a way of validating what people tell us. It is a way of making the invisible parts of a system visible.
3. Data informs. Stories move...
You can gather hundreds of survey responses and moderate interviews, but raw insights don't necessarily create momentum.
The challenge isn't only uncovering an insight. It is translating that insight for people who may be several steps removed from the day-to-day reality of the service and the on ground system.
I have come to see storytelling as an orchestration of data, communication and context.
A survey statistic can tell us how often something happens. An interview can help us understand why. An observation can show us what it looks like in practice. But bringing these things together can help someone who doesn't experience the system every day understand what is actually at stake. A good research story doesn't replace the evidence. It gives the evidence somewhere to land.
It turns static metrics, interview findings and scattered quotes into a narrative that makes system more visible.
How have these learnings shaped my practice
These experiences have shifted my understanding of what good user research looks like in complex environments. I am curious about the context and into the environment where the work actually happens.
I am thinking more deliberately about how research findings travel - from the person who shared their experience, to the people who need to understand it, to the people who have the power to change something.
Perhaps the biggest lesson has been that researching a complex system isn't about making the system look simpler. It is about making its complexity visible enough for people to understand it, question it, and ultimately change it.