Chapter 2

Design Thinking & User-Centered Design

Design thinking is a major approach used in UX/UI design that helps turn difficult problems into user-focused and creative solutions through an organized, flexible process. Instead of jumping straight into building a solution, it begins by pushing designers to focus on real people first and understand what they actually need. This mindset fits smoothly with tools like Figma, where ideas can move quickly from early research notes and rough sketches into multiple design versions that can be improved step by step.

In simple terms, design thinking is a problem-solving method that repeats in cycles and blends empathy, creativity, and reasoning to deal with challenging situations. Rather than rushing forward with an answer based on guesswork or what has been done before, it encourages designers to first study the situation and learn what users are dealing with in real life. By doing this, the final result is more likely to feel useful, clear, and genuinely relevant to the people who will use it.

Design thinking is often described as a five-step process: Empathize, Define, Ideate, Prototype, and Test. Even though these stages are presented as steps, the process rarely moves in a straight line. Designers often return to earlier stages as they learn new things during testing or discover better directions while building and refining their ideas.

The first phase is Empathize, and this is where the base of the entire design thinking process is built. During this stage, designers carry out qualitative research so they can step into the user's world and see things from their point of view. That often means watching how people behave, listening carefully to what they say, and paying attention to what frustrates them or slows them down. Designers may create surveys, hold interviews, or observe real situations to collect clear information about what users feel, think, and do. The goal is not to confirm a personal opinion or defend a guess, but to understand the user's reality as it is. Empathy helps designers move past their own preferences and focus on the real experiences of others.

Once enough research has been gathered, the process moves into the Define phase. Here, designers sort through what they found and shape it into a clear problem description. A broad topic becomes a focused problem statement that centers on what people need, rather than jumping straight into what the solution should look like. Tools such as user personas and journey maps help designers understand goals, expectations, and where users struggle with current options. This stage keeps the work on the right track by making sure the team is solving the right problem before spending time building anything.

With the problem clearly framed, designers enter the Ideate stage. This part of the process is about generating a wide range of ideas without worrying too much about polishing them right away. The focus shifts from careful detail to open thinking, where creativity has space to grow. Brainstorming sessions help teams produce many possible directions, even if some ideas feel unfinished or even strange at first. Methods such as mind mapping, sketching, and whiteboarding can push designers past their usual thought patterns and help them find new paths they may not have considered.

Prototyping is where ideas take shape in a form that people can interact with. Prototypes can be as simple as paper sketches showing a rough layout, or as detailed as digital versions that mimic real screen flows. Figma works especially well during this stage because it allows designers to build clickable prototypes that can be shared easily and tested by others. The purpose of prototyping is not to create a final product, but to make the idea real enough to try, question, and improve.

The last stage is Test, and this is where designers check whether their ideas actually work for real users. Testing is not meant to happen once and then end. Instead, it becomes a repeated conversation between designers and the people using the design. Through usability testing, teams notice where users hesitate, what feels unclear, what causes mistakes, and what needs to be adjusted. Based on what happens during testing, designers often return to earlier stages, improving the problem definition, revising ideas, and rebuilding prototypes until the experience feels more natural.

Taken together, these stages create both a way of thinking and a way of working in UX/UI design. The process begins with strong empathy, moves into clear problem framing, opens up space for idea generation, turns concepts into testable prototypes, and then relies on real user reactions to guide improvements. For anyone designing in Figma or using any other design tool, practicing design thinking keeps the focus on what users actually need, rather than what a designer personally prefers.

Empathy & Problem Definition

Design Thinking and user-centered design are two guiding ideas in modern UX/UI work, even when using tools like Figma to present and communicate designs. At their core, these approaches push back against designing from guesswork by putting real people at the center of every decision. If the goal is to create something that truly works for users, two steps matter most in the early process: building empathy and defining the problem clearly.

Empathy in design thinking is not a temporary trend. It is the starting point of creating solutions that serve real human needs. Empathy asks designers to step outside their own viewpoint and pay close attention to how users actually live, think, and move through their day. It is not about feeling sorry for someone, but about understanding their situation from the inside. That means noticing what users feel, what they do, what motivates them, and what holds them back. Designers build empathy by listening closely, watching users in real settings, and paying attention to what matters most to them.

As empathy becomes part of the process, designers begin to uncover user needs that don't always show up in quick or surface-level research. Instead of assuming how users "should" behave, designers observe the real struggles people face, including problems users may not even be able to explain clearly. For example, during interviews or field research, someone might say they want "something faster." But when you look more closely, the real issue may not be speed at all. It could be that the navigation feels unclear, or that the user is nervous about making a wrong choice, which makes the experience feel slow even if the system is working fine.

Empathy shapes user experience in a way that feels natural and considerate. When designers care about the user beyond basic function and also consider how the product feels to use, the result is an experience that feels easier to trust and more comfortable to return to. It can make interactions feel smooth and familiar, rather than cold or confusing, because the design reflects real people instead of only technical features.

Once empathy has been built through research and observation, the design thinking process moves into Problem Definition. This is where scattered research results are narrowed down into one clear problem that needs to be solved. Without this step, it's easy to create solutions that are too broad or not connected to what users truly need. Problem Definition is the moment where the team stops collecting information and starts shaping a focused direction.

To define the problem well, designers take a messy mix of user findings and turn it into a clear problem statement. This means making sense of who is affected, what they are trying to do, and what is getting in their way. A strong problem statement also frames the issue from the user's viewpoint, not the team's internal preferences. Instead of saying, "we want a quicker onboarding screen," the statement shifts to something like, "new users feel confused because there are too many steps and no clear starting point." This keeps the work grounded in the user's real experience rather than a design wish list.

This stage is not about jumping into solutions. It is about sharpening focus so the team knows exactly what they are trying to fix. It also helps prevent a common mistake in design, where people treat the surface problem while ignoring what is actually causing it. When the problem is clearly stated, it becomes a guide that keeps the design process steady and helps teams build something that solves a real need instead of a made-up one.

Empathy and Problem Definition are closely connected. Empathy uncovers what matters most in real human behavior, and Problem Definition turns that understanding into a clear direction that can be worked on through design. When designers build interfaces and user journeys in tools like Figma, these two steps give them a strong starting point based on real user reality. The result is a user experience that feels more purposeful, easier to trust, and more satisfying to use.

Ideation Techniques

Ideation is often seen as the heart of design thinking and user-centered design because it is the stage where research and a clear problem statement start turning into possible answers. In the design thinking flow, ideation comes after the team has built empathy and framed the problem, and it happens before any serious prototyping begins. This stage is meant to make space for creativity before anyone becomes too attached to one direction. If a team locks onto a single answer too early, personal bias and narrow thinking can limit what gets created, which is why ideation plays such a major role in UX/UI work.

At its simplest, ideation is the process of producing many ideas, options, or possible ways...