User research when your real users are out of reach, and what to study instead

UX research without access to users: study their work (records, workarounds, helpers, support queries) and name what each source can't tell you.

  • UX Research & Testing
  • B2B SaaS and workflow software
  • B2B SaaS & Workflow Software
Insights

UX research without access to users: study their work (records, workarounds, helpers, support queries) and name what each source can't tell you.

When you have to do UX research without access to users, because the people who use your product can't or won't take part, study their work rather than settling for whoever is available. Their records and workarounds, the place where the work happens, the people who support them and the questions they ask are all evidence. Each of those sources has a known blind spot, so name it, and before any release where a mistake would be costly, find a way to put the product in front of real users anyway.

Two weak defaults, and a better one

When the intended users are out of reach, there are two easy fallbacks. Teams interview whoever they can recruit and treat those people as the user, or they skip research and design from what stakeholders believe. The first gives confident answers from the wrong people. The second gives the team's assumptions with nothing to test them against.

The better path treats the inaccessible user's work as the evidence, rather than their opinions. The idea is older than most product teams. In 1995 Hugh Beyer and Karen Holtzblatt wrote in Communications of the ACM that traditional interviewing and surveying techniques were not adequate for designing the applications of the day, and that a design team comes to understand the whole work problem by understanding each person in the context of that person's work. Clayton Christensen and his co-authors made a related point in Harvard Business Review in 2016: you can learn as much from people who use no product for a job as from those who do, and people who cobble together workarounds are probably unhappy with the solutions available to them. A paper timesheet, a shared spreadsheet or a note stuck to a monitor is a record of what the work needs, made by the people you can't interview.

We met exactly this on Scissors, Auckland-based software for temporary staffing agencies, whose users run from recruiters and the agencies' client contacts to the candidates who work the shifts. Self-onboarding was not usual in temporary recruiting, so the Scissors team onboarded and trained every user by hand, over a couple of weeks. In discovery, the users we had recruited turned out not to be the ideal ones: they were not tech-savvy and hardly used the product, and the ideal users could not be recruited. Meanwhile recruiters kept timesheets and other records on paper, and candidates' shifts went on paper first, at the job location.

We read those paper records as findings: they showed where the product had not yet earned a place in the work. Alongside a heuristic evaluation and design audit, stakeholder conversations, a competitor analysis and the interviews we could get, we mapped the system's objects and their relationships from three angles (the business's view of its problems, the market seen through the competitor study, and users' experience from interviews, feedback and queries) and used all three to take the problem areas apart. The brief moved from onboarding alone to making the core functions easier to operate and understand, so that people would keep using the system after they were onboarded; the redesign covered onboarding, candidate shortlisting, talent pools and job creation. Our UX Research on operational products starts from the same place: sessions with users are one source, next to the records, workarounds, handoffs, policies, product data and surroundings of the work itself.


Which kind of "can't take part" are you facing?

The right substitute depends on why the users are out of reach. In business and operational software, five situations are worth telling apart.

Why users can't take partEvidence to use insteadWhat it can't tell you
They don't use the product yet: the work still happens on paper, in spreadsheets or in another toolTheir current records and workarounds; observation where the work happensWhether they will adopt the new product, or how they will cope with its interface
They are unfamiliar with technology, or a research session feels like a testShort sessions in their own workplace; the people who onboard, train or support themHow the users themselves experience the product, as distinct from what their helpers see
They sit behind your customer, who controls accessThe customer's forms, exports, procedures and support history; the supervisors who check the workThe users' own priorities wherever they differ from the buyer's
They are too busy or too senior to give an hourTheir output: approvals, comments, edits and how long each takes; brief questions at the point of workThe reasoning behind their decisions
Regulation or confidentiality limits contactRecords the customer approves for review; policies and procedures; scenarios tested with people from the same occupationHow the actual users perform; in safety-critical work, nothing here replaces testing with them

A product can face several of these at once. Name the ones that apply before choosing methods, because each points to different evidence.


What each substitute can and can't tell you

Records and workarounds. Timesheets, forms, exports, spreadsheets and handover notes show what information the work needs, in what order, and where the official system is bypassed. They don't show why a step exists or what the person was thinking when they took it.

Observation where the work happens. The UK government's service manual, in its guidance on users who do not use digital services, tells teams to hold research in places where users use the service, and to have an expert researcher judge people's digital skills rather than ask them, because people often misjudge their own. Seeing the work where it happens shows the conditions people work under. It can't tell you how often what you saw occurs.

The people who onboard, train or support users. The same guidance asks teams to research with the third parties who help users, from contact centres to friends, family and colleagues. These people have watched users struggle, and they are easier to reach than the users. They are also proxies, and proxies distort. Health research has measured how much: a 2022 systematic review and meta-analysis by Khanna and colleagues, covering 30 studies that compared children's own reports of their health-related quality of life with reports from parents and health professionals, found poor overall agreement (a pooled intraclass correlation of 0.49). Agreement was low on domains such as emotion, cognition, worry and pain, in contrast to more observable physical health and functioning. That is a neighbouring field, not software, but it suggests a working rule: trust a proxy on what they could see, and doubt them on what the user felt or understood. Bear in mind, too, that support and training staff see the cases that reach them, which may not be typical ones.

Support queries and feedback. What users ask for help with shows where the product stops making sense to them. It covers only the people confident enough to ask, and only the problems they could put into words.

Public reviews. For consumer-facing products, reviews are plentiful. Dennis Pagano and Walid Maalej analysed more than a million App Store reviews in a 2013 study and found praise in over 75% of a coded sample, while negative feedback typically lacked context and detail about the user's experience. Reviews are good for the language people use and the complaints that recur. They are poor at explaining why.

A competitor study. Other products show what users of the category have learned to expect. They show nothing about whether those expectations fit your users' work.

An expert review of the product. A heuristic evaluation finds where an interface breaks well-established usability principles. That is a different question from what the work requires: it is a useful stand-in for the first and no help with the second.


When substitute evidence is not enough

Substitute evidence helps you decide what to design. It is much weaker at telling you whether the design works for the people who will use it. Stop and insist on reaching real users when:

  • the release carries real consequence. If an error could cost someone money, their job, their legal standing or their safety, test with representative users first. Medical devices make the principle explicit: the US Food and Drug Administration's human factors guidance, revised in August 2026, says in section 8.1.1 that the most important consideration for participants in human factors validation testing is that they represent the population of intended users, and names literacy level and occupational specialty among the user characteristics that could particularly influence how people interact with a device's user interface.
  • the question is about understanding, trust or motivation. These are inner states, and in the proxy research above agreement was lowest on inner states such as emotion and worry.
  • your sources disagree. When the support team, the records and the customer's managers tell different stories, only the users can settle it.
  • everything you have came from the people who were easiest to reach. Ease of access is itself a bias.

When you do reach them, watch for a second distortion. In a 2012 study of 450 interviews in Bangalore, Nicola Dell of the University of Washington and colleagues from San Jose State University and Microsoft Research India found that respondents were about 2.5 times more likely to prefer a technology they believed the interviewer had made, even when the alternative was identical; when the interviewer was a foreign researcher who needed a translator, the bias rose to five times. The authors drew the lesson for research with underprivileged populations; applying it to anyone who may feel a session is a test, or who depends on the person asking, is our inference, and such people may not tell you a design is poor. Show alternatives without saying which one is yours, and give more weight to what people do with the product than to what they say about it.

About the authors

  • Rushali Bhatt

    Product Designer

    Rushali Bhatt is a Product Designer at Tcules. Rushali's articles start from the people inside complex software: clinicians and patients in healthcare products, users who cannot take part in research sessions, and the reviewers who check an AI feature's output before anyone acts on it. Topics include usability studies for enterprise software, human-in-the-loop patterns, a readiness checklist for AI product UX, what to fix first when adding AI to a live SaaS product, and what a heuristic evaluation should deliver. Useful reading for product teams whose software people rely on to make decisions.

    More from Rushali
  • Yash Gidwani

    Product Designer

    Yash Gidwani is a Product Designer at Tcules who writes about getting people into a SaaS product and keeping them there. Yash's guides cover SaaS onboarding strategies, onboarding and engagement software, and redesigning a live product without upsetting the people who use it. Other articles go into specific workflows: lending and loan origination apps, insurance quoting and claims, staffing and recruitment software, and a search-first create flow that stops duplicate records. Yash has also co-written the SaaS UX audit checklist and a 20-question checklist for legacy modernisation readiness.

    More from Yash

Research the product when its users are hard to reach

Explain who your users are and what keeps them out of research.