>
Fighting with the code...
>
Fighting with the code...
UX Research Playbook
My archive workflow from planning to actionable insights
This is how I currently approach UI/UX work. It’s loosely influenced by Design Thinking, but I don’t treat it as a fixed process. It’s more something I return to and adjust depending on the context.
1
Most of the time,
A project doesn’t begin with a clear solution.
It usually starts with a bit of uncertainty.
UXResearch
.Playbook
Empathise
I try to sit with that for a while, and begin by understanding the people I’m designing for. This part is quiet. I have conversations, run small tests, or read through responses, to hear how people describe things in their own words. To make sense of it, I sometimes put together simple empathy maps or light personas. Nothing too polished, just enough to keep their perspective present. From there, I write small user stories or sketch out a journey to see where things feel awkward, slow, or frustrating.
UXResearch
.Playbook
2
After a while,
Patterns begin to show.
That’s when I try to step back and ask what the problem actually is.
UXResearch
.Playbook
Define
Not everything needs solving, so I focus on what feels meaningful. I write a simple problem statement, mostly for myself, and try to imagine what a better outcome might look like. Something clearer, or lighter, or just easier to use. This part is still a bit uncertain, but it gives me a direction to move towards.
UXResearch
.Playbook
3
When things feel clear enough,
I start exploring ideas.
This stage is usually quite loose.
UXResearch
.Playbook
Ideate
I look at similar products to understand what already exists, then jot down thoughts as they come. Sometimes I use small prompts like “How might we” to reframe the problem, or I sketch quickly without worrying too much about how it looks. It’s more about getting ideas out than getting them right. I also map simple user flows, just to make sure things connect in a way that makes sense.
UXResearch
.Playbook
4
Gradually,
Those rough ideas start to take shape.
I move into wireframes, starting from quick sketches and then building them out digitally.
UXResearch
.Playbook
Design & Prototype
I try to keep things simple and low fidelity so it’s easy to change. At this point, I’m mostly thinking about structure and clarity rather than visual detail. Once there’s enough to interact with, I link the screens into a basic prototype.
UXResearch
.Playbook
5
Then I let people use it.
This part is always a bit humbling.
Watching someone else interact with the work often reveals things I didn’t notice.
UXResearch
.Playbook
Test & Synthesis
I usually set a few small goals for what I want to learn, then observe where people hesitate, get confused, or take unexpected paths. Afterwards, I group the feedback into themes and try to understand what’s actually going on beneath the surface. Some issues are more urgent than others, so I decide what needs attention first.
UXResearch
.Playbook
6
From there,
I go back and adjust things.
I update the wireframes, reconnect the flow, and test again if needed.
UXResearch
.Playbook
Iterate
It’s a slow back and forth. Each round feels a bit clearer than the last. This way of working is loosely shaped by Design Thinking, but in practice it feels less like a strict process and more like a rhythm. I’m still refining it as I go, and I expect that to keep evolving over time.
UXResearch
.Playbook
1
Most of the time,
A project doesn’t begin with a clear solution.
It usually starts with a bit of uncertainty.
UXResearch
.Playbook
Empathise
I try to sit with that for a while, and begin by understanding the people I’m designing for. This part is quiet. I have conversations, run small tests, or read through responses, to hear how people describe things in their own words. To make sense of it, I sometimes put together simple empathy maps or light personas. Nothing too polished, just enough to keep their perspective present. From there, I write small user stories or sketch out a journey to see where things feel awkward, slow, or frustrating.
UXResearch
.Playbook
2
After a while,
Patterns begin to show.
That’s when I try to step back and ask what the problem actually is.
UXResearch
.Playbook
Define
Not everything needs solving, so I focus on what feels meaningful. I write a simple problem statement, mostly for myself, and try to imagine what a better outcome might look like. Something clearer, or lighter, or just easier to use. This part is still a bit uncertain, but it gives me a direction to move towards.
UXResearch
.Playbook
3
When things feel clear enough,
I start exploring ideas.
This stage is usually quite loose.
UXResearch
.Playbook
Ideate
I look at similar products to understand what already exists, then jot down thoughts as they come. Sometimes I use small prompts like “How might we” to reframe the problem, or I sketch quickly without worrying too much about how it looks. It’s more about getting ideas out than getting them right. I also map simple user flows, just to make sure things connect in a way that makes sense.
UXResearch
.Playbook
4
Gradually,
Those rough ideas start to take shape.
I move into wireframes, starting from quick sketches and then building them out digitally.
UXResearch
.Playbook
Design & Prototype
I try to keep things simple and low fidelity so it’s easy to change. At this point, I’m mostly thinking about structure and clarity rather than visual detail. Once there’s enough to interact with, I link the screens into a basic prototype.
UXResearch
.Playbook
5
Then I let people use it.
This part is always a bit humbling.
Watching someone else interact with the work often reveals things I didn’t notice.
UXResearch
.Playbook
Test & Synthesis
I usually set a few small goals for what I want to learn, then observe where people hesitate, get confused, or take unexpected paths. Afterwards, I group the feedback into themes and try to understand what’s actually going on beneath the surface. Some issues are more urgent than others, so I decide what needs attention first.
UXResearch
.Playbook
6
From there,
I go back and adjust things.
I update the wireframes, reconnect the flow, and test again if needed.
UXResearch
.Playbook
Iterate
It’s a slow back and forth. Each round feels a bit clearer than the last. This way of working is loosely shaped by Design Thinking, but in practice it feels less like a strict process and more like a rhythm. I’m still refining it as I go, and I expect that to keep evolving over time.
UXResearch
.Playbook
Tap to flip
Drag to swap
Practical
Work(s)