What is User Centric Design?
User-centred design is often described as a process of researching users, interviewing them, mapping their needs, and validating flows. These activities are important, but they can make the “user” feel abstract — someone we study at a distance rather than someone whose experience we can often understand directly through lived interaction with the system.someone we locate through research rather than someone we can immediately understand through lived experience.
My view is simpler: the first user should be you.
Not because you represent every user or because your needs are universal — but because if you can’t inhabit the system you’re building, you’re missing the experiential foundation of design. You can replicate a workflow without ever understanding what it feels like to move through it: stimulating, disorienting, frustrating, empowering, tedious, or reassuring. That feeling — the texture of the experience — is where most of the meaningful insights live.
This comes from an anthropological mindset: participant observation. If you don’t understand the culture around a process — the tacit shortcuts, the points of friction, the rhythms and hesitations — you’re only designing the surface. You might recreate the steps of a task, but you won’t understand the lived experience of the task.
That’s why I use the systems I build. The project-management platform my team provides to thousands of users is the same system I rely on daily. The CMS we maintain is the same one I use to manage content. The WordPress plugins I create are the ones I personally depend on. Even the AI-assisted specification tools and visualisation systems I design are core parts of my own workflow.
Using the tools changes the design. It makes the work grounded.
You feel the natural paths, the unexpected dead-ends, the confusing choices, the moments of clarity. Design becomes wayfinding — moving through the interface like you’d move through a space, noticing where you backtrack, where you hesitate, and where the system pushes back.
And this is the central insight:
If you’re building something meaningful, you should be able to feel its logic and its friction in your own hands.
Start by becoming the user. Live inside the system and let that experience shape your instinct.
Research and testing absolutely matter, but they become more powerful when paired with lived experience. When you know what the work feels like — not just what it looks like in a diagram — your design decisions become sharper, more humane, and more aligned with the real people who will depend on the software.
User-centred design begins long before the interviews or the journey maps.
It begins the moment you step into the system yourself and walk the first steps in the user’s shoes.