Learn how observing people use a product and hearing their thoughts as they work can reveal confusion, hesitation, and unmet expectations. These simple methods give designers clear clues for improving a product’s usability before production, while keeping real user needs at the heart of each change.

Multiple Choice

Name two methods to test a product's usability during development.

Testing usability with real users during development focuses on how easily and effectively people can use the product. Two practical methods are observing users as they interact with the product and asking them to think aloud while they perform tasks. Observing shows real behavior—where users hesitate, what causes confusion, and where they get stuck—so you can spot design issues that slow or frustrate use. The think-aloud approach adds insight into why those issues occur by capturing the user’s thoughts in the moment, revealing mismatches between the design and the user’s expectations or mental model. Together, they provide direct, actionable feedback to improve usability before final production. The other options address durability, cost, appearance, or engineering performance rather than how a product is used, so they don’t assess usability.

A product can look polished on a desk and still be frustrating to use. A handle may feel awkward, a control may be hard to find, or a simple task may take longer than expected. That’s why usability matters in design technology: it reveals how well a product works for the people it is meant to serve, not just how it looks on a drawing or computer screen.

During development, two useful ways to assess usability are user observation and think-aloud usability testing. Both involve people using a product or prototype, but each offers a different kind of insight. Observation shows what users do; thinking aloud helps explain what is going through their minds.

Usability is about the whole experience

Usability describes how easily and effectively someone can use a product to achieve a goal. The goal might be opening a food container, adjusting a lamp, or entering information on a screen. A product with good usability feels understandable and manageable. It doesn’t make people stop to guess what a button does or wrestle with a part that should move smoothly.

That doesn’t mean every product must be effortless for every person. A piece of specialist equipment may require training, while a children’s toy should be clear and safe for its intended age group. Designers need to consider who will use the product, where they’ll use it, and what they need to do. These details shape the criteria for evaluating its usability.

Appearance, strength, cost, and performance all matter in design. But they answer different questions. A material strength test can show whether a component withstands a load; it won’t reveal whether the component is confusing to operate. A product may be sturdy and affordable, yet still be awkward in the hand. Usability testing focuses on the interaction between people and the design.

First, watch what users actually do

User observation is a straightforward method: give someone a product or prototype and watch them use it. The designer can set a realistic task, such as “adjust the strap” or “open the lid,” then pay close attention without immediately offering help.

The most useful evidence often appears in small moments. Does the user pause before pressing a control? Do they try to pull a part that needs to twist? Do they hold the product in an unexpected way? A raised eyebrow or a repeated attempt may signal a problem, even if the user doesn’t say anything. These details can point to unclear instructions, poor placement, uncomfortable shapes, or a mismatch between the design and the way people naturally behave.

A simple observation record makes findings easier to use. Designers can note the task, the point where a user hesitated, any errors, and how long the task took. They might also record whether the person completed it without help. Video can be useful, too, provided users know they’re being recorded and agree to it. A short clip can show a hand movement or moment of confusion that’s easy to miss in real time.

The observer should try not to lead the user. If they say, “Press the blue button,” they’ve given away information the design may need to communicate on its own. Better prompts are neutral: “Please set the timer,” for instance. Then the designer can see whether the layout and labels make sense without a running commentary.

Then let users think aloud

Think-aloud usability testing asks users to describe what they’re thinking as they work through a task. They might say, “I thought this symbol meant power,” or “I’m not sure whether I should push or turn this.” Those comments offer a glimpse into how the person interprets the design.

This method helps reveal the reason behind a visible action. If someone hovers over a control, observation shows the hesitation. A think-aloud comment may explain it: perhaps the symbol looks like a warning, or the user expects the control to be somewhere else. That difference matters. A designer can’t fix the right problem without understanding what caused the trouble.

The user’s comments don’t need to be polished. In fact, they’re most useful when they’re immediate and candid. A facilitator might remind the person to keep talking if they fall silent, but should avoid explaining the product or suggesting what to say. The aim is to hear the user’s own interpretation, not the answer the designer hopes to hear.

There is one wrinkle: speaking while doing a task can change how someone behaves. A person might slow down or focus on details they’d normally ignore. Think-aloud feedback is valuable, but it shouldn’t be treated as a perfect copy of everyday use. Pairing it with observation helps balance that limitation.

Two methods, one clearer picture

Used together, observation and think-aloud testing provide complementary evidence. Imagine a user trying to refill a reusable bottle. The observer notices that they turn the lid several times before it comes free. The user says, “I thought this section was fixed.” Now the design team has both the action and a likely explanation: the lid’s shape may not make its function clear.

This combination can guide a specific change. The team might add a textured grip, revise the shape, or make the opening direction easier to understand. They can then show the updated prototype to users and see whether the change helps. That’s the point of testing during development: problems are often simpler to address while the design is still being refined than after production has begun.

Feedback should lead to decisions, not just a pile of notes. Designers can look for repeated patterns across several users. One person’s unusual mistake may be a one-off; if several people make the same error, the design may be sending the wrong signal. Even a small group can uncover useful issues, especially when the task is clear and the users reflect the intended audience.

Choose the method to suit the product

The way a product is tested should fit its purpose. A handheld tool may need close attention to grip, reach, and force. A website may call for tasks such as locating a setting or completing a form. A public information display should be checked in the setting where people will encounter it, since lighting, noise, and time pressure can affect how easily it can be used.

It also helps to include people with a range of needs and abilities. Hand size, vision, mobility, age, and familiarity with technology can all shape a user’s experience. A design that feels obvious to its creator may be unfamiliar to someone seeing it for the first time. That’s not a failure of the user; it’s valuable information about how the product communicates.

Other forms of testing still have an important role. Strength tests assess durability. Cost analysis helps estimate whether a design can be made within a budget. Visual checks can assess appearance and finish, while engineering analysis can predict how a component may behave under particular conditions. These methods answer important questions, but they don’t replace watching people use a product.

Better products begin with better questions

Usability testing works best when designers start with a clear question: Can users complete this task? Can they identify the right control? Can they hold the product comfortably? A focused task makes feedback easier to interpret and gives the team something concrete to improve.

User observation shows where people pause, struggle, or take an unexpected route. Think-aloud testing sheds light on the expectations and misunderstandings behind those actions. Together, they turn real interactions into useful design evidence.

A product doesn’t need to be perfect in its first form. It does need to teach its designers something. When people can use a prototype in a natural setting and share what they’re thinking, small design flaws become easier to spot—and good ideas have a better chance of becoming products that feel clear, comfortable, and genuinely useful.