A few years ago, I led a user research team to help a large organization redesign a public-facing service portal. The internal team had spent months building a new interface. It looked clean, the navigation was logical, and the project was on schedule.
Then we sat down with actual users.
Within the first few sessions, we learned that the language across the portal didn’t match how people described the services they needed. Key tasks had been buried three clicks deep because the team assumed people would navigate the way the org chart was structured. And a feature they’d invested heavily in? Most users didn’t notice it was there.
The team was talented and well-intentioned. They simply hadn’t had the opportunity to pressure-test their assumptions against the lived experience of the people they were designing for. That gap between what organizations believe about their users and what is actually true is exactly where user research lives.
What Is User Research and Why Does It Matter for UX
User research is the process of studying real people—their behaviors, needs, motivations, and pain points—to inform the design and improvement of products and services. In large organizations, the stakes are high. When a platform confuses its users, people make poor decisions with real consequences. When an enterprise tool frustrates its workforce, organizations lose time and money in ways that rarely show up on a dashboard. When a public service portal fails, people lose access to services they depend on.
There’s an old rule in product development known as the 1-10-100 rule: it costs $1 to fix a problem in the design phase, $10 during development, and $100 after launch. That ratio holds whether you’re building a digital service for millions of customers or rolling out an internal tool for a department of 5,000. Investing in product research early is how you catch those $100 problems while they’re still $1 problems.
At Design Centered Co., we’ve seen this across sectors—from multinational financial institutions and global technology companies to the Government of Canada and organizations in defence, healthcare, sports technology, and food security. In every context, the research we conducted up front reshaped the project’s direction in ways the teams didn’t anticipate. That’s the whole point.
How UX Research Works in Practice
Most organizations have conducted some form of user research—whether through usability studies, stakeholder interviews, or feedback surveys. But in complex enterprise environments, the user experience research process looks different. Here’s how it typically unfolds when we work with clients.
It begins with alignment. Before recruiting a single participant, we work with stakeholders to define research goals. What decisions does the organization need to make? What assumptions are on the table? Who are the users? This step is critical because research without a clear purpose produces data without direction. We use co-design workshops to bring product owners, leadership, and technical teams together around the same set of questions.
From there, we choose the right methodology. User research broadly falls into two categories: qualitative and quantitative.
Qualitative methods, like in-depth interviews, usability testing, and contextual inquiry, help you understand the why behind user behavior. Whereas quantitative methods, like surveys, analytics reviews, and A/B testing, help you measure the what and how much. The best research programs use both, and the choice depends on where you are in the product lifecycle and what questions you’re trying to answer.
When we partnered with Spotify on a usability study for their reverification flow, we conducted moderated sessions with carefully recruited participant pairs. Each 75-minute session was observed remotely by client stakeholders, with live relay of observer questions. That’s a very different design than a broad satisfaction survey across a large user base. The methodology followed the research question, not the other way around.
Why Recruiting the Right Users Makes or Breaks a Study
One of the most underestimated aspects of UX research is recruitment. You can have the sharpest research questions and the most elegant study design, but if you’re talking to the wrong people, your findings won’t hold.
Proper recruitment means identifying participants who genuinely represent your user population. Depending on the organization, this might mean recruiting across roles, seniority levels, regional offices, language preferences, and levels of digital literacy. Inclusive recruitment reaches people whose experiences are too often invisible in conventional research.
Image
Screening matters just as much. We’ve seen organizations recruit people too familiar with the product, producing overly positive feedback, or who don’t match the user profile, producing insights that don’t translate. Getting this right takes careful planning and experienced practitioners.
Navigating the Practical and Ethical Side of User Experience Research
Research in large organizations comes with practical and ethical considerations that scale with complexity.
On the practical side, large organizations often require formal approvals, privacy impact assessments, and strict data-handling protocols. Research may involve getting buy-in from department heads, coordinating across time zones, and working within security constraints. In public sector environments, these governance layers can be especially rigorous. Planning for these realities early prevents delays later.
Image
Confirmation bias shapes which findings get emphasized. Leading questions nudge participants toward expected answers. Selection bias produces pools that don’t reflect the actual user base. And interpretation bias leads researchers to see patterns that support their narrative while overlooking data that complicates it.
How Bias Undermines Product Research and How to Manage It
Bias is one of the most persistent challenges in user research, and every team is susceptible to it.
Confirmation bias shapes which findings get emphasized. Leading questions nudge participants toward expected answers. Selection bias produces pools that don’t reflect the actual user base. And interpretation bias leads researchers to see patterns that support their narrative while overlooking data that complicates it.
Internal teams are especially vulnerable because they are close to the product—they know the history of design decisions, understand the constraints, and have personal investment in the outcomes. That’s human nature. But it means research conducted entirely in-house risks being shaped by the organization’s existing worldview.
This is one of the strongest arguments for engaging an external research partner. A third-party team approaches the work without the internal assumptions or legacy attachments that can cloud the picture, designing studies to surface what’s true even when the truth is uncomfortable.
We saw this clearly conducting national research for Transport Canada’s supply-chain modernization initiative. The project involved federal and provincial agencies, logistics industry partners, and data science teams—each with their own mandates for shaping public policy. As a third party with no stake in the network, we could ask the important questions without allegiance to any single agenda, uncovering the most urgent user needs and helping the organization prioritize objectively. User research was an important step towards guiding a strategy for shaping Canada’s supply-chain initiative, and the findings gave senior leadership the confidence to fund a dedicated product team—because priorities were grounded in evidence, not politics.
Making User Research a Continuous Practice
The organizations that get the most from user research treat it as continuous practice, not a one-time event. It should inform decisions at every stage: during discovery, through design and development, at launch, and long after.
For leaders in UX, product, and research, this means advocating for research as a line item, not an afterthought. It means building relationships with leadership so findings have a seat at the decision-making table. And it means being honest about where outside expertise would strengthen the work.
At Design Centered Co., our approach is rooted in Impact Centered Design—a methodology that starts from the impact you want to create and maps the research, strategy, and design decisions needed to get there. We don’t start with wireframes or feature lists. We start by asking: what change are we trying to make, and how will we know if we’ve made it? User research drives that process.
Let’s Make Your User Research Practice More Effective
If you’re leading a UX, product, or research function and want to strengthen your approach—or if you’re wondering whether your current practice is giving you the insights you actually need—we’d welcome the conversation.
Design Centered Co. offers a complimentary review of your existing research practice. We’ll look at your current methods, identify gaps, and provide honest recommendations—no sales pitch, just a candid conversation between practitioners.
Contact us to learn more about how we help enterprise and public sector organizations conduct research that moves the needle.
