15 MCP Prompts for Research Architects

The research operations role is changing faster than almost any other function in a product organization. AI is handling more of the execution layer - drafting screeners, summarizing transcripts, scheduling sessions - which means the value of a skilled ReOps leader is shifting. Less time on coordination, and more time on tasks that require your expertise: building the infrastructure that makes research trustworthy, scalable, and defensible across an entire organization.

This is a working list of prompts scoped specifically to that infrastructure layer, organized by workflow. Copy, paste, adapt to your program!

Panel Governance: Keep Your Most Valuable Asset Healthy

Your participant panel is the foundation everything else runs on. These prompts help you monitor it, protect it, and make the case for why it matters.

1. "Give me a full panel health report. I want show rates, no-show rates, how many participants are in cooldown, how many are on the blocklist, and how many haven't been contacted in over six months. Flag anything trending in the wrong direction and tell me what's at risk if we don't address it."

2. "Which participants have been contacted the most across all studies in the last 90 days? I want to identify anyone we're over-relying on and flag them before they start opting out."

3. "Show me opt-out trends over the last [X months]. Are opt-out rates increasing? Which studies or teams are associated with the highest opt-out rates? I want to understand if we have a participant fatigue problem developing before it becomes one."

4. "How diverse is our panel by [segment, role, company size, or other property]? Where are the gaps between the participants we have and the participants we actually need for the research our teams are running?"

5. "Which populations or segments are most depleted right now - meaning we have very few free-to-contact participants left? I want to prioritize panel building efforts for next quarter."

Program Visibility: Know What's Running Across Your Org

One of the hardest parts of ReOps at scale is maintaining visibility into everything happening across multiple teams simultaneously. These prompts give you that view without having to chase anyone down.

6. "Give me a full snapshot of all active studies running right now across the workspace. Who owns each one, what stage is it at, how many sessions are scheduled versus completed, and are there any that look stalled?"

7. "Are any teams currently recruiting from the same participant segment at the same time? I want to catch any overlap before it creates contact frequency issues."

8. "Which studies have been in draft status for more than [X weeks] without launching? I want to follow up with the owners and find out if they need support or if we can close them out."

9. "Which researchers or teams are running the most research right now? And which teams haven't run a study in the last 90 days? I want to understand where research activity is concentrated and where adoption is lagging."

Program Reporting: Make The Case For Research At The Org Level

10. "Generate a quarterly research program report for [Q and year]. Look across all studies in the workspace - active, closed, draft, and paused - and tell me how many studies ran, what types they were, who owned them, which researchers were most active, and what the headline findings were. Format it as a report I can share with senior leadership."

11. "How has research volume changed quarter over quarter over the last year? I want to show the growth of our research program and connect it to headcount or tooling investments we've made."

12. "A product leader has asked me to justify our participant panel investment. Pull together the data I need: panel size, studies run from the panel, average time to recruit, and participant re-use rate. Frame it as a cost and speed argument."

Scaling Research Across Teams: Governance Without Gatekeeping

This is the core ReOps challenge as research democratizes: how do you let more people run research without losing quality, burning your panel, or creating compliance risk? These prompts help you monitor and maintain the standards you've built.

13. "Which studies run in the last quarter did not have a consent form attached? I want to identify any compliance gaps and follow up with the study owners."

14. "Show me all studies that were run by non-researchers - PMs, designers, or engineers - in the last quarter. What methods did they use, how many sessions did they run, and were there any issues flagged?"

15. "Generate a research calendar for next quarter based on what's planned. Here are the studies in progress or planned: [list]. Flag any recruiting conflicts - studies targeting the same segment in overlapping timeframes - and suggest a sequencing that protects participant experience."

A note on what these prompts are doing behind the scenes

Every prompt in this list requires Rally's infrastructure to work - not just a language model generating text, but a system that knows your participant panels, your study history, your governance rules, and your org's accumulated research knowledge.

The panel health prompts work because Rally tracks every participant touchpoint across the entire workspace, not just per team or researcher. The program reporting prompts work because Rally stores structured study data that can be queried and summarized across time. The governance prompts work because consent, contact frequency, and compliance rules are enforced at the platform level - which means the data they surface reflects what's actually happening, not what people remember to report.

For a ReOps leader, the infrastructure is the job. The MCP is how you interact with it at scale - surfacing what's working, catching what isn't, and communicating the value of a well-run research program to the people who need to understand it.

The teams getting the most out of Rally's MCP aren't the ones using it to move faster on individual tasks. They're the ones using it to operate a research program that's bigger, more consistent, and more defensible than anything they could have managed manually. 

Ready to connect Rally MCP to your research program? Talk to your CSM about enabling access, or book a demo to get started.