
If you’ve spent any time looking into UX/UI design, you’ve probably come across the term “design thinking.” It gets used a lot — sometimes as a buzzword, sometimes as a genuine methodology — and it’s easy to assume it’s something only designers need to understand. In reality, design thinking is a way of solving problems that puts people first, and it’s used everywhere from product teams and start-ups to healthcare, education and government.
For anyone starting out in UX/UI design, understanding design thinking is one of the most useful foundations you can build. Here’s what it actually means, why it matters, and how the five-stage process works in practice.
At its heart, design thinking is a human-centered approach to solving problems. Instead of starting with a solution and hoping people will use it, you start with the people themselves — what they need, what frustrates them, and what they’re trying to achieve — and you let those insights guide everything that follows.
The approach was popularised by the Hasso Plattner Institute of Design at Stanford (often called the d.school), and it’s since been adopted by organisations of every size around the world. What makes it powerful isn’t complexity; it’s the discipline of staying curious about the problem before rushing to fix it.
Most versions of the framework break the process into five stages: Empathise, Define, Ideate, Prototype and Test. They’re usually drawn in order, but as you’ll see, the real process is far messier — and that’s a feature, not a flaw.
Everything begins with understanding the people you’re designing for. In the empathise stage, you set your own assumptions aside and try to see the world through your users’ eyes.
In practice, this means research: interviewing people, observing how they behave, and paying attention to the gap between what they say and what they actually do. A designer might sit with someone as they use an app, noticing where they hesitate or grow frustrated. The goal is to build a genuine, emotional understanding of your users’ experiences rather than guessing at them from a distance.
This stage is the foundation of the entire process. Skip it, and you risk solving a problem nobody actually has.
Once you’ve gathered your insights, you need to make sense of them. The define stage is where you sift through everything you’ve learned and pin down the real problem you’re trying to solve.
The output here is usually a clear problem statement — a concise sentence that frames the challenge from the user’s perspective. Rather than “we need a better checkout page,” a well-defined problem might read: “busy parents need a faster way to reorder groceries because they don’t have time to browse a full catalogue every week.”
A sharp problem statement keeps the whole team focused and stops good ideas from wandering off in every direction.
With a clear problem in front of you, it’s time to generate ideas — lots of them. The ideate stage is about quantity over quality, at least to begin with. You want as many possible solutions on the table as you can manage, without judging them too early.
Techniques like brainstorming, sketching and mind-mapping all come into play here. The point is to think broadly and creatively, encouraging even the odd or unrealistic ideas, because a “wrong” idea often sparks a brilliant one. Only once you’ve generated plenty of options do you start narrowing down to the concepts worth exploring further.
Ideas are cheap until you can see them. In the prototype stage, you turn your strongest concepts into something tangible — a rough, scaled-down version of the product or feature that people can actually look at and interact with.
Prototypes are deliberately quick and inexpensive to make. They might be paper sketches, simple wireframes, or clickable mock-ups built in a tool like Figma. The idea isn’t to build the finished product; it’s to make your thinking real enough to get feedback on. The cheaper and faster the prototype, the more freely you can experiment and discard what doesn’t work.
Finally, you put your prototype in front of real users and watch what happens. The test stage is where you learn whether your solution actually works — and, just as importantly, where it falls short.
Watching someone use your prototype almost always reveals something you didn’t expect. Maybe a button they can’t find, a step that confuses them, or a need you hadn’t accounted for. Those discoveries are gold. They tell you exactly what to refine, and they often send you back to an earlier stage with fresh understanding.
Although the five stages are usually listed in order, design thinking is iterative rather than linear. Testing might reveal that you misunderstood the problem, sending you back to empathise. A prototype might spark a completely new idea, pulling you back to ideate. Teams loop through the stages repeatedly, refining their understanding a little more each time.
This willingness to revisit, rethink and improve is what separates design thinking from a rigid, one-and-done process. It builds in the expectation that your first attempt won’t be perfect — and gives you a structured way to make it better.
Design thinking is a core skill for UX/UI designers, but its value reaches well beyond design. Product managers, marketers, engineers and business leaders all use the same mindset to tackle problems more creatively and keep users at the centre of their decisions. Employers increasingly look for people who can think this way, because it leads to products and services that people genuinely want to use.
If you’re considering a career in UX/UI design, learning to apply the design thinking process is one of the best places to start. It teaches you to ask better questions, to test your assumptions, and to build solutions grounded in real human needs — skills that stay valuable no matter how the tools and trends around them change.
Want to put design thinking into practice? Our UX/UI Design course guides you through the full process, from user research to polished prototypes, and helps you build a portfolio ready for Ireland’s growing tech sector. Check out the details in the Courses Page.