How Designers Use Research to Understand Real People

User research is the systematic study of the people who use a product, service or system, with the goal of understanding their needs, habits, goals and frustrations before and during design work. For designers, it replaces guesswork with evidence gathered directly from users. Research matters because design decisions made without it often reflect the assumptions of the team rather than the realities of the people affected. Designers who want to study the subject in a structured way can look at the course Micro Diploma: User Research for Designers, which covers the methods and reasoning behind this practice.

Most user research rests on a few core principles. The first is that the researcher should observe what people actually do, not only what they say they do, because stated preferences and real behavior often differ. The second is that research should be tied to a specific decision, so that each study answers a question a team needs answered. The third is that findings should be interpreted with care, separating what was observed from what is inferred. Common methods include interviews, usability tests, surveys, diary studies and contextual inquiry, each suited to different questions.

A basic research cycle moves through planning, recruiting participants, collecting data, analyzing patterns and sharing results in a form that teams can act on. Sample size and participant selection matter because a small, unrepresentative group can lead to misleading conclusions. Good practice includes writing a clear research question, selecting participants who reflect the target users, and taking notes that distinguish direct quotes from the researcher's own interpretation.

In a large organization with many teams, user research is often spread across product groups, each with its own priorities and users. A research practice in such a setting may begin with a shared repository where findings from earlier studies are stored, so that a team designing a new internal tool can learn what a related team discovered about the same employees. A central research group might set standards for how studies are run, while embedded designers conduct smaller studies tied to their own projects.

Consider a hypothetical case in which a company with several regional divisions wants to redesign its expense reporting system. Designers could interview employees from different departments, observe how they submit receipts during a typical week and compare the results across divisions. The findings might show that field staff struggle with uploading photos on mobile devices while office staff have few problems. That insight would shape which features get priority and which teams need to be involved in the next round of testing.

User research has real limitations. Studies capture a snapshot of behavior at one point in time, and participants may change how they act when they know they are being observed. Small sample sizes can overrepresent vocal users and miss quieter groups, and research conducted only with people who are easy to reach may leave out those with the greatest need. Some debates in the field concern how much weight to give qualitative findings compared with quantitative data, and how to ensure that research influences decisions rather than being filed away after a project ends.

For organizations, the main takeaway is that research works best as an ongoing practice with clear ownership, shared records and a habit of connecting findings to decisions. As design teams grow, the challenge is less about running individual studies and more about making sure that what one team learns is available to others. Continued attention to method quality, ethics in working with participants and the integration of research into planning will shape how the discipline develops.