Research ops, short for research operations and often written ReOps, is the work that keeps a UX research team running: finding and scheduling participants, handling consent and incentives, managing the tools and keeping a library of past findings. Researchers plan and run the studies, and research ops makes it possible for them to run more of them.
The job is a role of its own at companies with large research teams, and it is also a common first step into UX research. If you are weighing the research role itself, how to become a UX researcher covers that path.
Research ops handles the people, paperwork and tools around each study
A ReOps person makes sure the right participants show up, sign the right forms, get paid and hear from the company only as often as they agreed to. Around that sits the work of keeping the team’s tools and knowledge in order.
Participant recruiting
Research ops finds people for studies, through a panel of customers who agreed to take part, a recruiting service or ads. They write screener surveys with the researcher, schedule sessions, send reminders and replace no-shows. Recruiting is the biggest single part of most ReOps jobs, and the one researchers are happiest to hand off.
Consent and incentives
Each participant signs a consent form that says what is recorded, who sees it and how long it is kept. Research ops writes or maintains those forms with the legal and privacy teams. Recordings have to be stored and deleted as the form promised, and research ops is usually the person who checks that they are. They also pay incentives, such as gift cards or payments, and track them for tax and budget purposes.
The research repository
A repository is a searchable library of past studies, findings and clips, so a team can check what is already known before running a new study. A repository only works if someone keeps it tidy, tags new studies and shows the team how to search it, and that someone is usually research ops.
Tools and governance
Research ops picks and runs the team’s tools, from scheduling and testing platforms to the repository, and manages the licenses and budget. Governance means the rules: who may run research, how participant data is protected, how often a customer may be contacted, and which studies need a privacy review. At companies where designers and product managers run their own studies, research ops often trains them and checks their plans.
Teams add research ops when logistics crowd out research
Most research teams start with a few researchers doing their own recruiting and scheduling. When researchers spend more time on logistics than on studies, the team adds research ops. That often happens once a team has several researchers, or earlier when it recruits hard-to-reach participants, such as doctors or business customers.
The first ReOps hire usually covers all of these jobs alone. As the team grows, the work splits into specialist roles: a participant recruiter, a repository or knowledge manager, a tools and program lead, and a head of research operations who sets the plan. Some companies put research ops inside a wider operations team with DesignOps.
Good research ops shows in how fast a study can start
Research ops is judged on what researchers can do because of it. The clearest sign of a working ReOps setup is the time from “we need eight participants” to the first session, and teams that track anything usually track that first.
Other measures follow from the same idea. A low no-show rate means screeners and reminders work. A participant panel that keeps growing without contacting the same people over and over means recruiting is healthy. Designers and product managers who search the repository before asking for a new study mean the library is useful, which is harder to achieve than filling it.
The work changes with the company. At a startup, research ops might be one person with a spreadsheet of customers who agreed to talk, a shared calendar and a folder of recordings. At a large company it is a team with a panel of thousands, a privacy review for each study and a budget for incentives in several countries, where local tax and data rules differ. The skills carry from one to the other, and people who set up the spreadsheet version well are often the ones hired to build the larger one.
Coordinators, recruiters and researchers move into ReOps most often
Research ops has no single route in, and the job titles vary: research operations coordinator, research operations specialist, research program manager, participant recruiter and research operations manager.
The backgrounds that lead into it most often:
- Research coordinators from universities and hospitals already run consent, scheduling and participant payments under strict rules.
- Recruiters and recruiting coordinators know how to find people, screen them and keep a pipeline moving.
- Project and program managers bring the process and budget side of the job.
- Market research and panel operations staff have run participant panels and incentives at scale.
- UX researchers who enjoy setting up systems move across, especially those who already built their team’s repository or screener templates.
Hiring managers look for organization, care with personal data and the ability to get a busy team to follow a process. A portfolio is less central than in research, but a short write-up of a process you set up, such as a recruiting workflow or a repository you organized, helps your application.
ReOps is also a way into UX research
Entry-level research jobs are scarce, and a ReOps role puts you inside a research team, watching how studies are planned and run. Many coordinators help with screeners, sit in on sessions and take notes, and some run small studies of their own once the team trusts them.
If research is your goal, say so early and ask to help on studies when there is room. Keep notes on what you contributed, since that becomes your first research case study. The UX research portfolio guide shows how to write one up.
Research ops jobs usually appear under UX research jobs, and some sit with UX and product design jobs when they belong to a wider operations team.
