When Users Are Off-Limits: Practical UX Research Workarounds

Every UX practitioner eventually hits the same wall: stakeholders need design decisions backed by evidence, yet no one will give you time with actual users. Strict NDAs, privacy regulations, hard-to-recruit groups like lawyers or doctors, or simply business relationships too delicate to disturb can all close that door. The uncomfortable truth is that substitutes — assumptions, bias, guesstimates, even synthetic users — do not add up to research.

You can still gather meaningful signals. The techniques below won't produce a full usability study, but they will surface real pain points and give your work a defensible foundation when direct access is impossible. Just be careful: never draw sweeping conclusions from a thin evidence base. Multiple sources are required to dilute assumptions and bias, and at minimum you need five users to start seeing patterns.

Mine Your Organization's Front Lines

Your closest proxy for real users may already be on the payroll. Sales, customer success, support, and QA teams talk to customers constantly. Befriend them and learn how they gather intelligence about customer needs.

This overlap between design and sales is not a coincidence. As Paul Adams has pointed out, subscription-based products force sales teams to nurture long-term relationships, which in turn demands a deep understanding of user needs. Retention and loyalty depend on meeting those needs consistently. It is not unusual to find UX researchers embedded in marketing or customer success teams under a different job title.

Circle diagram with leadership in the middle and different functions around it, such as support, research, design, and so on
Every company circles around leadership. And every department is interconnected. This is especially true for design, engineering, research, sales, and marketing. Image by Paul Adams. (Large preview)

Rather than recruiting your own participants, you can funnel questions through these colleagues. They can relay customer feedback, flag recurring frustrations, and give you a channel to the people you cannot reach directly.

A question 'what do we build?' in the center, and various answers on UX from different departments
Everybody on the team shapes UX. And all departments have insights that can guide and inform design decisions. Image by Paul Adams. (Large preview)

Go Where the Evidence Lives

If users will not come to you, go to them — or at least go to the traces they leave behind. Ask permission to observe or shadow customers at their workplace. Sit in on customer calls or interview call center staff about the issues they hear every day.

Passive data sources are just as valuable. Analytics platforms, CRM reports, and call center logs will show you behavioral patterns without a single recruitment email. Google Trends can reveal product-related searches you did not anticipate. Inside your own organization, search logs, Jira backlogs, and support tickets are a running record of user frustration.

Graph with the words 'the truth' in the center and Desk research, Real world, Proxies, and Data on the corners
You might not have all the data, but if you keep exploring various sources, the truth will eventually come to light. Image by H Locke. (Large preview)

External channels work too. Study reviews, discussions, and comments about your product and your competitors'. TrustPilot and app store listings are rich sources for mapping key themes and overall sentiment. If you are determined to speak with real people, recruitment tools like UserTesting, Maze, or UserInterviews can help you find participants who are willing to talk.

UX activities in the product and service design cycle
Susan Farrell from the Nielsen Norman Group summarized a wide range of UX activities, useful when you do have access to users, but we can convey them to users or run them even with very limited access to users. (Large preview)

Negotiating for Real Access

It is a familiar irony: the stakeholders who refuse you time or resources to talk to users are often the first to demand evidence behind your design work. Use that tension productively. Explain what you need and how little it actually costs. Research does not require a major budget or a lengthy timeline — a small but steady commitment can be enough. Five users at 30 minutes each, once a month, may already produce meaningful change.

Often the reluctance is rooted in a lack of trust. Customer success teams carefully manage relationships with major clients and may fear that a research session will disturb them. In B2B and enterprise settings, NDAs and privacy rules can make access legally complicated. Whatever the stated reason, signal that you understand and respect those constraints. Show that you care about the relationship as much as they do, and demonstrate the concrete value your work delivers.

When that value becomes visible — when your design decisions withstand scrutiny because they are grounded in actual evidence — the door that seemed locked will start to open.

Checklist for No-User Research

  • Push back: ask stakeholders why users are off-limits. Sometimes there is no good reason.
  • Locate colleagues closest to customers and make them allies.
  • Cultivate relationships with sales, customer success, support, and QA.
  • Route your research questions through those colleagues.
  • If users cannot come to you, find a way to observe them where they work.
  • Sit in on customer calls; interview call center staff about pain points.
  • Dig through search logs, Jira backlogs, and support tickets.
  • Map themes and sentiment across TrustPilot, app stores, reviews, and competitor discussions.
  • Recruit willing participants through UserTesting, Maze, UserInterviews, or similar tools.
  • Request a modest recurring commitment: 5 users × 30 minutes, once a month.
  • Build regular check-ins and timelines instead of one-off ad hoc sessions.