After more than three years as a UX designer, I've often wondered: Which process should I follow? Which framework is the "right" one? How do I know which method to choose?
For a long time, I felt unsure about design thinking and UX frameworks. I asked myself, why do we need to follow them? The answer I've found over time is this: the mindset matters more than the method.
What I've Learned
The goal of UX is simple: understand the user — their actions, their tasks, and the problems they face — and help them complete their work efficiently.
If a user flow is confusing or takes too long, users won't adopt the product — they'll go back to old, traditional methods. People use applications to save time and make life easier. If your design gives them more headaches, they simply won't use it.
This might sound obvious, but it's easy to forget when focusing on frameworks, processes, or even aesthetics.
We also need to consider how users feel when interacting with an application. In sensitive contexts — like apps for HIV patients or stress and mindfulness — emotions, stigma, and comfort are crucial. Choices like colors, UX writing, and interactions can make users feel safe, respected, and supported, not judged or anxious.
I also sometimes wonder how senior UX designers with 12+ years of experience would view my approach. Would they critique me for not following frameworks strictly? Thinking about this helped me realize that what matters most isn't following a "perfect" process — it's staying focused on the user and their tasks.
How I Approach UX Today
Here's how I apply this mindset in real projects. Recently, we wanted to create a unique Kitchen Display System (KDS) for a client:
- Research Existing Systems I explored current KDS tools and AI solutions like ChatGPT and Claudia to see how they really help chefs.
- Understand User Pain Points I read user reviews and observed workflows to identify what frustrates chefs and what features are missing.
- Brainstorm Features With user stories in hand, I generate ideas that could reduce the chef's workload. I also create two additional proto-personas — a server and a manager — to ensure the system supports the entire kitchen workflow, not just the chef's tasks. This helps identify features that improve collaboration, communication, and efficiency across all roles.
- Map User Journeys & Flows If we don't fully understand their work — from starting a shift to closing it — we map it out. Then we try different user flows to ensure tasks are easy and intuitive.
- Design the UI Only after research, user stories, and flow testing do I begin UI design, confident that every element serves a real user need.
Frameworks Are Tools, Not Rules
I don't follow design thinking like a checklist. I adopt the mindset behind it: empathy, iteration, and problem-solving. I choose methods based on what helps me understand the user best — no extra steps, no unnecessary processes.
Final Reflection
UX is ultimately about helping users complete tasks efficiently and reducing friction, not about adhering strictly to a framework. Using modern tools like AI for research, observing real workflows, and iterating thoughtfully all help me stay focused on that goal.
I also realize that my approach or way of thinking might change a few years from now. As I gain more experience and face new challenges, I expect to refine my methods, try different tools, and see things from perspectives I can't yet imagine.
At the end of the day, if the user can finish their work faster, easier, and with less frustration, the design has succeeded.
UX isn't about following a framework. It's about empathy, clarity, iteration, and using the right tools — including AI — to make life easier for the people we design for.