B2B User Research with Small Groups of Expert Users

B2B products may have only dozens—or even a handful—of core users, leading teams to conclude that the sample is too small for research. The opposite mistake is interviewing only business leaders and treating management views as the frontline experience.

Small expert populations can still be researched. Teams need precise role selection, observation of real work, and a clear distinction between individual preferences and systemic problems.

01 Map Stakeholders and Roles First

List users, approvers, administrators, buyers, IT, security, and people affected by the data. The buyer and daily user of an enterprise system are often different groups.

Select participants by task, permission, frequency, and proficiency—not job title alone.

02 Prioritize High-Risk, Frequent, and Cross-Role Tasks

Begin with processes that are slow, error-prone, training-intensive, highly regulated, or dependent on departmental handoffs. Limited research resources do not need to cover every module evenly.

Set a focused research question such as “Why is the review rejection rate high?” instead of the broad goal “Understand user needs.”

B2B Research Methods and Uses

03 Ask About the Most Recent Real Event

Do not ask only what features users want. Ask them to reconstruct a recent order, approval, exception, or report and show the files and messages they used.

Real events expose gaps between policy and practice and reduce vague wish lists.

04 Treat Workarounds as Important Evidence

Exporting to Excel, sending group reminders, or writing on paper does not necessarily mean users resist the system. The product may lack batch actions, collaboration, or traceability.

Understand what the workaround solves before deciding to integrate, permit, or prohibit it.

05 Report Patterns and Risks, Not Percentages, in Small Samples

Three of five participants experiencing a problem does not mean “60% of users.” Describe patterns repeated across roles, tasks, and data and explain their impact.

Triangulate interviews with logs, support, business metrics, and testing to improve confidence.

06 Turn Insights into Actionable Design Inputs

Connect each insight to a task, evidence, impact, design opportunity, and assumptions that still need validation.

A research report should go beyond personas and quotations to support decisions about flows, permissions, information architecture, and priorities.

Frequently Asked Questions

How many users does B2B research require?

There is no fixed number. Cover key roles, tasks, and differences until patterns stabilize and can be triangulated.

What if the client does not allow direct user access?

Use proxy interviews, tickets, recordings, accompanied observation, and usability tests to gather evidence progressively, while documenting the limitation.

Can a business expert represent every user?

Not completely. Experts understand rules, while frontline users better understand real operations and workarounds.

Should a problem be fixed when experts say they are used to it?

Review task efficiency, errors, training, and new-user difficulties. Habit can conceal long-term cost.

Will research slow the project?

Focused early research usually reduces later rework. Control scope around high-risk questions.