Design a centralized participant management system to prevent over-contacting
Tests ResearchOps governance at scale. Strong answers define unified data tracking contact history, consent, and segments; enforce hard frequency caps and cooling-off windows; and build automated guardrails. Red flag: siloed spreadsheets or soft guidelines.
What's really being asked
ResearchOps systems design and governance at enterprise scale. The interviewer wants to see if you can move beyond ad-hoc recruiting to build infrastructure that preserves participant trust, prevents survey fatigue, and maintains data quality across dozens of product teams. They are looking for awareness of the tension between research velocity and panel health, plus the ability to translate policy into enforceable system rules.
The full answer
First, a unified data model. The system must store contact history with timestamps and channel, study participation outcomes such as completed, no-show, or screened out, consent and communication preferences, demographic and segment tags, and a computed fatigue or recency score. Second, hard governance rules rather than best-effort guidelines. Examples include a maximum of one outreach per 30 days, a 90-day cooling-off period after any completed study, and an automatic block on anyone who has opted out or hit their annual participation cap. Third, system architecture for cross-team visibility. A centralized registry should expose a shared queue or API so teams can see pending and past studies for any participant before initiating contact. Fourth, bias mitigation. The answer should address capping power-user or brand-loyal participants at roughly 20 percent of total studies, tracking new-user versus existing-user ratios, and supplementing the internal panel with external recruiting to avoid echo chambers. Fifth, privacy and compliance. The design must include GDPR or CCPA deletion workflows, explicit consent records, and role-based access controls.
The mistakes people make
Proposing that each team maintains its own spreadsheet and simply checks a shared calendar. Suggesting soft rules like please do not email too often without system enforcement. Tracking only email sends rather than actual study participation, which leads to undercounting real burden on participants. Ignoring opt-out mechanics or assuming marketing unsubscribe lists are sufficient. Failing to account for sampling bias, which NN Group notes is a major risk of internal panels because participants develop brand loyalty and may provide artificially positive feedback.
What usually comes next
How would you handle a high-priority study that needs to reach the exact segment currently in a cooling-off period? How do you balance the cost of building this system versus continuing to pay external recruiters? What metrics would you use to prove the panel is healthy and not burned out? How would you integrate this with existing CRM or data warehouses?
A concrete example
Imagine a SaaS company with 15 product teams. A researcher wants to recruit enterprise admins who have not been contacted in 60 days. The system returns a pool of 40 eligible admins but flags that 12 are already scheduled for other studies next week. The researcher submits a request that enters a shared queue. The system auto-enforces the 30-day contact rule and the 90-day post-study cooling-off. It also flags that enterprise admins have already represented 40 percent of this quarter's studies, triggering a bias alert that prompts the team to source external participants to balance the sample.
Interview question
An enterprise panel shows consistently higher satisfaction scores among internal recruits than external ones. Which guardrail directly targets this specific bias?
- a.Require explicit consent records and role-based access controls
- b.Enforce a 90-day cooling-off period after any completed study
- c.Track contact history with timestamps across all channels in a unified registry
- d.Cap internal power users and brand-loyal participants at roughly 20 percent of total studiesCorrect
Why? this is the answer
The card identifies brand loyalty as a source of sampling bias where frequent internal participants provide artificially positive feedback, which is directly mitigated by capping their participation rate. Option B addresses panel fatigue rather than loyalty bias, since cooling-off periods manage burden but do not reduce the proportion of biased respondents in the sample.
Just read this? Test yourself on what you have been reading.
Read the original → nngroup.com
- #ux research
- #researchops
- #system design
- #governance
- #participant panels
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux research — each one lists the topics its interview covers.
See open roles