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.
Tests senior ResearchOps architecture balancing speed, trust, and data quality. A strong answer specifies a centralized registry tracking contact history, outcomes, consent, segments, and fatigue scores. It mandates hard rules like one contact per 30 days, a 90-day post-study cooling-off, and auto-suppression of opt-outs. It covers cross-team visibility via a shared queue, bias mitigation capping power users at 20 percent of studies, and privacy compliance. Red flag: manual checks or ignoring bias from over-relying on a captive internal panel.
Read the original → nngroup.com
- #ux research
- #researchops
- #system design
- #governance
- #participant panels
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.