Marcus Andrey Study
Ler em português Library

UX Research · Step 7 · 6 min read

ResearchOps

ResearchOps is the people, tools and processes that let research happen well, more often, and with impact. What it covers, the ResearchOps Community's eight pillars, NN/g's six components and Kate Towsey's eight functions side by side, and how to start without building a bureaucracy.

Research rarely fails in the interview. It fails in the week before and the month after. Finding participants takes three weeks, the consent form is out of date, the incentive budget is gone, nobody can find last year's study. None of that is research, and all of it decides whether research happens. ResearchOps is the name for doing that work on purpose.

What you'll be able to do after reading:

  • Explain what ResearchOps is, in one sentence
  • Name the areas it covers, using the eight pillars
  • Compare three public models of ResearchOps
  • Pick the first operational problem worth solving in your team

1. What it is

The ResearchOps Community, a global group of practitioners, defines it as "the people, mechanisms, and strategies that set user research in motion": the roles, tools and processes that support researchers and help research scale its impact across an organisation (ResearchOps Community). NN/g calls it "the orchestration and optimization of people, processes, and craft", a specialised part of DesignOps (Kate Kaplan, ResearchOps 101, NN/g, 2020).

Kate Towsey, who wrote the handbook on the subject, puts it more widely: it isn't only support for researchers, it's the system that lets everyone who does, uses or takes part in research exchange knowledge (Kate Moran and Maria Rosala, NN/g, 2025).

In a small team, ResearchOps isn't a person. It's a shared consent template, a participant list, a repository and a budget line. It becomes a role when the volume of research makes those things a job.


2. The eight pillars

1Environment

Why does research happen? Who is engaged?

Sponsors, demand, culture
2Scope

How and when does research happen? With what methods?

Study types, cadence
3Recruitment and admin

How do we manage participants and project admin?

Pool, screeners, incentives, scheduling
4Data and knowledge

What happens to the findings, data and insights?

Repository, tags, retention
5People

Who is responsible for doing research?

Roles, skills, coaching
6Organisational context

What are the internal and external constraints?

Budget, structure, politics
7Governance

What are the legal and ethical considerations?

Consent, privacy, storage
8Tools and infrastructure

What systems and tools do our projects need?

Recording, analysis, panels
The eight pillars of user research, the ResearchOps Community's map of what operations must cover. Each is a question; the line in grey is what an answer usually involves.Pillars and questions: ResearchOps Community, Revisiting the 8 Pillars (2023), after Emma Boulton (2019). Diagram and grey lines: Marcus Andrey, CC BY 4.0.

In 2018 the community asked practitioners around the world "what is ResearchOps?", through a survey with more than 300 responses and 33 workshops. In 2019 Emma Boulton turned that work into eight pillars of user research, with input from Brigette Metzler, Holly Cole and Tomomi Sasaki (Boulton, The Eight Pillars of User Research, 2019; ResearchOps Community, About; Revisiting the 8 pillars, 2023). Each pillar is a question your team either has an answer to, or doesn't.


3. Three models, the same territory

ResearchOps Community, 8 pillars NN/g, 6 components Kate Towsey, 8 functions
Recruitment and admin Participants Participant recruitment
Data and knowledge management Knowledge Knowledge management
Governance Governance Ethics and privacy
Tools and infrastructure Tools Tools and vendors
People Competency People and skills · Onboarding and support
Environment · Organisational context Advocacy Money and metrics · Program management
Scope

Sources: ResearchOps Community, NN/g, 2020, NN/g interview with Towsey, 2025. The rows are this course's matching, not the authors'.

The lists differ in where they draw lines, not in what they cover. Two points they share:

  • Everything connects. NN/g says its components are "interrelated factors", not isolated ones (NN/g, 2020). Towsey says working on any one function eventually pulls in all the others, which is why ResearchOps work is so often underestimated (NN/g, 2025).
  • Strategy first. Towsey warns against "knee-jerk operations": building a research library because someone asked for one, without tying it to what the business needs. Start small, but map the whole journey first: who will use the system, when, and with what resources (NN/g, 2025). Her image for it: "Every city started as a village."

4. Where to start

Pick the problem that costs the most research, not the one that's most interesting to fix. Some common first moves:

  1. A consent and privacy kit: one consent form, one data retention rule, one place to store recordings. It removes risk from every study at once. See Research ethics and consent and Research data and privacy.
  2. A participant pool: people who agreed to be contacted, with how they were recruited and when they last took part, so you don't ask the same five customers every month. See Recruiting participants.
  3. Templates: a plan, a screener, a guide, a report. Cheap to make, and they raise the floor of every study.
  4. A repository with an owner: see Research repositories.
  5. One number you report: studies run, time from request to first session, or how many recommendations were adopted. See Showing the impact of research.

Measure before and after. If recruiting took three weeks and now takes one, that's the case for the next investment.


5. Common mistakes

  • Buying tools before agreeing on the process they support.
  • Building operations for an imagined research volume, ten times the real one.
  • Treating ResearchOps as admin, without a seat in planning.
  • Letting every team keep its own consent form and participant list.
  • Not measuring anything, so nobody can tell if it helped.

6. Vocabulary

Term Meaning
ResearchOps (ReOps) The people, processes and tools that support research at scale
DesignOps The same idea for design work in general; ResearchOps is often part of it
Participant pool A list of people who agreed to be contacted for research
Governance The legal and ethical rules for research: consent, privacy, storage
Incentive What participants receive for their time
Knowledge management How findings are stored, found and reused

7. Try it (no tools needed)

  1. Write the eight pillars on a page.
  2. Next to each, write what your team does today, in one line, or "nothing".
  3. Circle the one that cost you the most time, or the most risk, in the last study.

Reflection questions: Which pillar does nobody own? What would it take to fix the circled one in a month?


8. If you already practise

  • Time your research pipeline: request, recruitment, first session, report. Find the slowest step.
  • Put ResearchOps work on the same roadmap as research, with goals and dates.
  • Share templates with the people who do research outside your team (see Democratising research without losing quality).

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Research repositories · Building a research practice · Recruiting participants · Research data and privacy

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close