👋 Hey, I’m Nikki. Each week I write about UX research strategy, communicating impact, and using AI to do your best work.
Scaling Research Without Sacrificing Rigor
Research democratization is not a one-size-fits-all solution. What works for one company might fail in another due to differences in team size, research maturity, leadership buy-in, and decision-making culture. Instead of adopting a democratization model blindly, your first step should be research on your own organization.
This chapter has outlined multiple approaches to research democratization, from fully decentralized models to research-led approaches with controlled access. But choosing the right approach requires an honest evaluation of your company’s unique needs, challenges, and research maturity.
This is where your own research skills come into play. Before deciding how to scale research within your organization, take time to assess your current environment, define your goals, and determine the level of structure and oversight required to ensure success.
Assess the Current State of Research in Your Organization
To scale research without sacrificing rigor, you first need a comprehensive understanding of how research currently functions within your organization. Without a clear baseline, democratization efforts risk becoming chaotic, misaligned, or ineffective. Don’t skip this step! We do this:
To identify exactly who is conducting research.
To understand the types of research being performed.
To find bottlenecks preventing effective research.
To gauge how leadership values research.
To document how research insights are shared and consumed.
Let’s dive into how to assess the current state.
1. Map Out Current Research Roles and Responsibilities
Objective: Clarify exactly who is conducting research, formally or informally.
Steps:
List all individuals conducting research regularly, including:
Trained researchers (User Researchers, UX Researchers, etc.)
Designers
Product Managers
Marketers
Engineers
Customer Support or Success Teams
Determine the frequency with which each role performs research:
Is research part of their job description, or are they doing it informally?
How frequently do non-researchers independently initiate studies?
2. Inventory Types of Research Currently Conducted
Objective: Understand what research methods are being used and by whom.
Steps:
Catalog recent research projects over the last 3-6 months.
Categorize these by research type:
Usability testing (quick tests, prototype evaluations)
Surveys (customer satisfaction, feedback)
Interviews (generative or evaluative)
Analytics reviews (product usage analysis)
Generative or strategic studies (exploratory, opportunity-focused research)
Highlight gaps between desired and actual types of research performed.
3. Identify Research Bottlenecks and Pain Points
Objective: Determine the obstacles preventing effective and timely research.
Steps:
Conduct stakeholder interviews or surveys asking:
“How often are you delayed by waiting for research results?”
“Have you ever skipped research due to lack of availability?”
“How often do you have to conduct research on your own without support?”
Quantify these pain points if possible (“70% of Product Managers skip research due to long wait times”).
Example survey question (with rating scale):
“On a scale of 1-5, how often do you find research availability a blocker for timely decisions?”
(1 = Never, 5 = Always)
Example finding:
“80% of Product Managers rated research availability as 4 or higher, indicating significant delays.”
4. Evaluate Leadership’s Attitude Toward Research
Objective: Assess how research is valued by leaders and decision-makers.
Steps:
Conduct targeted leadership interviews or distribute a leadership-focused survey. Ask clear, pointed questions such as:
“Do you consider research essential, helpful, or optional for decision-making?”
“Can you provide examples of recent decisions influenced by research?”
“How much are you willing to invest in research resources and training?”
Analyze responses to determine if leadership views research as:
A critical component
An occasional input
A luxury or nice-to-have
Example question:
“Describe a recent instance where research directly impacted your decision-making.”
Example finding:
“We delayed launching the new pricing model until the UX team conducted surveys—research is crucial for big decisions like pricing.”
5. Assess How Research Insights Are Currently Shared and Stored
Objective: Understand how research insights are documented and made accessible.
Steps:
Identify all locations where research insights currently live:
Centralized (Dovetail, Airtable, Confluence)
Decentralized (Google Drive folders, Slack, emails)
Check how consistently insights are documented:
Do insights consistently include the research question, methods, results, and actionable recommendations?
Evaluate accessibility and discoverability:
Are insights easy to find by people across the organization?
How often do stakeholders complain about not finding past research?
6. Summarize Your Findings Into a Clear Research Landscape Report
Objective: Create a succinct, actionable summary highlighting gaps, strengths, and weaknesses.
Suggested structure:
Current research roles:
Who’s conducting research (trained vs. informal)?
Research types in use:
Methods commonly and rarely used.
Identified bottlenecks:
Delays in conducting or accessing research.
Leadership alignment:
How critical is research viewed by leadership?
Research documentation & sharing:
Current status of knowledge management and accessibility.
Example:
“Research is primarily done by one full-time UX researcher, supported informally by designers and PMs. Usability testing is frequent, but generative research is nonexistent. Teams often skip research due to delays, and leadership sees it as important but secondary. Documentation is decentralized, causing frequent duplication and wasted efforts.”
Define Your Organization’s Research Needs and Risks
Not all organizations require the same level of research rigor, nor can they accept the same level of risk. Clearly understanding your organization’s specific needs and risk tolerance is essential to creating a democratization model that is both effective and safe. This step is necessary to:
Ensure the democratization model aligns with your organization’s specific risk and rigor requirements.
Prevent costly errors resulting from inappropriate levels of oversight.
Leverage existing skills within your organization efficiently.
1. Determine the Level of Research Rigor Required
Research rigor refers to the quality standards and methodological thoroughness expected within your organization.
Steps:
Classify decision types and their consequences. List recent or upcoming decisions influenced by research. Categorize these by the impact and risks involved.
Categorize the decisions into tiers of required rigor:
High-Rigor: Decisions have significant financial, legal, or safety implications.
Medium-Rigor: Decisions impact user satisfaction, retention, or moderate financial outcomes.
Low-Rigor: Decisions are incremental, reversible, or experimental.
Prompting questions:
What kinds of decisions does your organization regularly face?
What is the worst-case scenario if research for these decisions is inaccurate or incomplete?
Can you group your decisions into categories based on the potential risk or consequence?
2. Clarify Your Organization’s Risk Tolerance
Risk tolerance defines how much uncertainty or potential harm your organization is willing to accept as it expands research responsibilities.
Steps:
Conduct internal interviews or workshops to gauge comfort with risk:
Ask stakeholders to rate their tolerance for potential research errors (low, medium, high).
Discuss potential consequences openly and document responses.
Create a risk assessment matrix to visualize tolerance clearly.
Prompting questions:
How comfortable is leadership with research findings from non-researchers driving key decisions?
What types of errors or biases can your organization afford, and what is completely unacceptable?
Which areas (finance, regulatory, health) require the strictest oversight, and which can afford some flexibility?
3. Evaluate Existing Research Skills in Your Organization
Understanding the research skills and experience within your organization is essential for deciding how much oversight or training you’ll need to implement.
Steps:
Create an inventory of current research skills among non-research stakeholders.
Use surveys or interviews to capture their research experience.
Categorize teams by experience (High, Medium, Low).
Assess the gap between current skills and desired research rigor levels.
Prompting questions:
Do your product or design teams have formal research training?
Are there team members regularly conducting interviews, usability tests, or surveys without oversight?
Which teams consistently produce reliable insights, and which require significant researcher intervention?
Identify the Right Democratization Model for Your Context
Selecting the appropriate democratization model is critical. The right model enables your organization to effectively scale research without sacrificing quality, credibility, or reliability. Using insights gathered from assessing your current state (Step 1) and defining your organization’s research needs and risks (Step 2), follow the guide below to pinpoint exactly which model aligns best with your organization’s unique circumstances.
If your organization has a small research team supporting many product teams:
You may need a Hybrid model
This approach empowers non-researchers to run tactical studies like usability tests and surveys, provided there’s clear oversight and structured guidelines.
Define which types of research non-researchers can conduct (usability tests, surveys).
Develop standardized templates and checklists for non-researchers.
Create a structured review process where trained researchers review study plans and synthesis regularly.
Example:
At Shopify, designers and product managers regularly run usability tests independently. However, all tests follow standardized scripts and must pass researcher approval before sharing insights broadly. Researchers remain responsible for generative or strategic research.
If your organization has fast-moving teams who need quick access to user insights:
You may need a Decentralized model (with required training and quality controls)
Non-researchers gain autonomy to quickly validate smaller decisions while maintaining quality through mandatory training and periodic audits.
Conduct mandatory, regular training for everyone who will run research.
Clearly document acceptable research types (low-risk studies like usability tests, rapid surveys).
Implement quarterly quality audits to ensure ongoing rigor and minimize bias or misuse.
Example:
Atlassian encourages a decentralized approach where product teams rapidly conduct small usability tests and user validation. However, every team member must complete basic user research training, and research outputs are periodically reviewed for quality by dedicated UXRs.
If your organization requires high levels of rigor and compliance (finance, healthcare, government):
You may need a Research-led model
All research remains under the control of trained researchers due to the significant risks associated with regulatory and legal compliance.
Clearly define policies stating only trained researchers conduct all research.
Establish clear processes for non-researchers to submit research requests formally.
Researchers regularly share insights proactively to ensure teams have necessary data without conducting research independently.
Example:
Fidelity Investments uses a research-led model. Due to regulatory compliance, financial risk, and ethical considerations, only professional UX researchers conduct studies. Stakeholders access insights via a controlled central repository and structured insight-sharing sessions.
If your organization lacks a structured way to store and share insights:
You may need a Centralized repository model
Establish a single, accessible, and organized repository for research documentation and insights, ensuring consistent storage and preventing duplication of work.
Choose and implement a dedicated research repository tool (I love and use Condens).
Establish standards for documentation, tagging, and summarizing insights.
Train stakeholders to use, contribute to, and search within the repository.
Example:
At HubSpot, a centralized research repository allows stakeholders company-wide to search, discover, and use insights, significantly reducing duplicated studies and enabling faster decision-making.
If your organization already has non-researchers conducting research informally:
You may need a Hybrid model with governance to standardize and improve quality
Leverage existing informal research practices, but introduce standardized methods and clear governance to ensure consistency, reliability, and ethical standards.
Document current informal practices across teams.
Introduce clear governance (templates, research plans, mandatory review points).
Provide training to standardize methodologies and ensure consistent research quality.
Regularly audit informal research practices to identify and close quality gaps.
Example:
Airbnb initially found many teams informally conducting user research. They established clear, standardized research frameworks and mandatory review checkpoints. Now, informal research follows consistent standards, significantly enhancing overall research quality and reliability.
Questions to help you choose
Use these guiding questions to clarify your context, highlight the strengths and challenges of your current setup, and confidently choose the right democratization approach.
Understanding your organization’s research environment
How many dedicated researchers do you currently have?
Could you list their primary responsibilities?
Are these researchers overloaded or struggling to keep up?
How frequently do teams request research support?
Do you find your team turning away important research requests?
Are stakeholders conducting their own informal studies without oversight?
Clarifying the importance of research rigor in your context
What is the consequence of a research mistake in your industry?
Could it lead to financial loss, regulatory fines, legal action, or reputational damage?
Or would the consequences be minor and quickly reversible (quick product fixes)?
What level of evidence or rigor do executives or leadership expect from research insights?
Do executives require detailed, formal research reports?
Are informal, rapid insights acceptable for decision-making?
Evaluating stakeholder skills and experience
Do stakeholders already conduct informal research?
What kinds of research do they currently run (surveys, usability testing, informal interviews)?
Have you reviewed the quality of their work? What have you found?
Have stakeholders received formal training or support previously?
If yes, was it effective or insufficient?
If not, how confident are you in their ability to learn quickly?
Examining your organization’s pace and decision-making culture
How quickly does your organization move?
Do product and design teams regularly release new features or products weekly, monthly, quarterly, or annually?
Is research a bottleneck or a helpful part of the process?
Do teams often bypass research due to speed pressures?
If yes, what kinds of research do they skip most often (generative research, usability tests)?
Considering your organization’s documentation and sharing practices
How are research insights currently documented and shared?
Are insights scattered across different teams, Slack channels, or Notion pages?
Or is there a reliable, centralized source of truth accessible to all?
Do teams often duplicate research because insights are not easily discoverable?
Can you provide examples of recent duplicated studies or lost insights?
Reflecting on your desired future state
What would successful democratization look like in your ideal scenario?
Would it involve more teams confidently running their own studies?
Or would it mean researchers have more bandwidth to focus on strategic research, with stakeholders handling only tactical tests?
How will you know democratization is successful in your organization?
What metrics or signs would indicate successful scaling of research?
What signs would indicate that democratization isn’t working?
Considering the trade-offs
What risks are you most concerned about with democratizing research?
Poor research quality?
Ethical concerns or privacy risks?
Losing research credibility internally?
What benefits do you think democratization could bring your organization?
Increased speed of decision-making?
More teams using research to inform decisions?
Better stakeholder empathy with customers?
Organizational readiness
Do you have leadership buy-in for increased democratization?
If no, what would you need to demonstrate to build leadership support?
Are you prepared to allocate resources (time, people, budget) toward training and oversight?
If resources are limited, can you realistically implement a robust oversight or training program?
Future scalability and evolution
As your organization grows, how sustainable will each democratization model be?
Can your chosen model scale effectively if your teams double or triple in size?
Will more centralized oversight become impossible if research requests grow significantly?
Based on your reflections:
Which model seems most aligned with your current resources, goals, and constraints?
If you’re still uncertain, what’s one small step or experiment you could run to test this model before fully committing?
Document Your Chosen Democratization Model Clearly
Clear documentation ensures everyone understands exactly what your democratization model involves, how it functions, and the responsibilities of all stakeholders.
Your documentation should clearly outline:
What: Explicitly state the chosen democratization model (e.g., Hybrid, Decentralized with oversight).
Why: Explain your rationale and how it aligns with organizational goals.
Who: Define clearly who can and can’t conduct research, including oversight roles.
How: Describe precisely how research should be conducted within this model (protocols, approvals, roles).
Steps:
Summarize Your Model
“We’ve chosen a Hybrid Democratization Model, allowing non-researchers to conduct usability tests and small surveys after receiving standardized training and templates, with oversight from trained researchers.”
Create clear role descriptions
Non-researchers: Who qualifies, what they can do (ex: usability tests).
Researchers: Their oversight responsibilities (reviewing research plans and findings).
Define limits and boundaries
Clearly state what research methods (generative studies, complex behavioral analyses) are exclusively reserved for trained researchers.
Document governance structure
The governance structure clarifies who approves, reviews, and ensures the quality of democratized research. This prevents confusion, maintains rigor, and safeguards research integrity. Your documentation should explicitly define three things:
Approval workflows – Clearly defined steps for research approval.
Quality checkpoints – Specific points when research quality is assessed.
Escalation paths – Clear instructions on when and how to escalate research concerns.
Approval workflows
Purpose: Ensures all research conducted by non-researchers adheres to your organization’s standards.
Steps:
Identify who must approve each type of study:
Who reviews usability tests, surveys, interviews?
Differentiate between trained researchers and peer reviewers (trained non-researchers).
Define the exact approval steps clearly:
Initial submission:
What documents or plans must stakeholders submit?
Where do they submit these documents (ex: centralized Notion, Google form)?
Who receives submissions?
Review and feedback:
Who is responsible for initial reviews (a researcher, senior stakeholder)?
What criteria are used to review (methodology, ethics, clarity)?
How quickly will reviews be conducted (ex: 1–2 business days)?
Approval or revision:
Clearly state how approvals or requested revisions are communicated back (ex: via Slack, email, Notion comments).
What happens if research is not initially approved (guidance for revision)?
Quality checkpoints
Purpose: Ensure research quality remains high throughout the process.
Define exactly when research quality is evaluated:
Before launch:
Has the researcher approved the study plan?
Are participant recruitment criteria met?
Mid-research (optional but valuable for complex studies):
Is the method working as planned?
Are participants responding well (no unforeseen issues)?
Post-research (before insights are shared):
Are insights accurate, actionable, and unbiased?
Did stakeholders correctly interpret participant feedback?
Escalation paths
Purpose: Provides clarity on how to handle problems and issues efficiently.
Clearly define scenarios that require escalation:
When stakeholders disagree with reviewer feedback.
When ethical or compliance concerns arise (privacy/data issues).
When research methodology requires significant changes.
When timelines are consistently not met or quality repeatedly falls below standards.
Sample governance structure document
Below is an example format you can use directly or adapt:
Governance structure for democratized research
Approval workflows:
Simple studies (usability tests, small surveys): Submit research plan via [Notion link]. Approval within 2 business days by designated researcher or peer reviewer.
Complex studies (interviews, behavioral studies): Submit via [Research Intake Form], expect review within 3–5 business days by Senior Researcher.
Quality checkpoints:
Pre-launch: Approval required (check methodology, recruitment plan, ethics).
Mid-study check (optional): Scheduled for longer or complex studies.
Post-study review: Mandatory before insights are shared broadly.
Escalation paths:
Stakeholders should escalate directly via Slack or email clearly stating the issue, research type, and reason for escalation.
First point of contact: Assigned researcher
Second escalation: Senior Researcher
Final escalation: Head of Research
Communicate Your Choice Broadly Across the Organization
Communication ensures alignment, buy-in, and clarity. Everyone should understand the democratization model you’ve chosen, how it benefits them, and their specific roles.
Your communication should include:
The reason for democratizing research.
How it impacts stakeholders (clarifying roles, responsibilities, and benefits).
Clear guidelines for getting involved or escalating research needs.
Opportunities for training, questions, and clarification.
Steps:
Craft a clear announcement. Write a concise, compelling explanation of why this model is beneficial.
Host a kick-off meeting or town hall. Present the model, answer questions, and provide clarity.
Provide continuous updates. Use newsletters, Slack channels, or monthly updates to reinforce the democratization model and any adjustments.
Example:
Slack announcement example:
Launching our new research democratization model!
To scale our research impact, we’re adopting a Hybrid model. Product Managers and UX Designers can now conduct usability tests and small surveys independently, provided they complete mandatory training and follow clear templates.
Benefits for you: Faster insights, more direct user feedback, increased ownership over your research questions.
Next Steps: Join our kick-off session this Thursday at 3 pm for detailed Q&A and access training links here [link].”
Creating a Detailed Implementation Plan
An implementation plan translates your democratization model into tangible, structured steps your teams can follow. This prevents ambiguity, ensures alignment, and increases adoption.
Below is a step-by-step approach, complete with concrete examples, prompts, and checkpoints:
Step 1: Define Clear Objectives & Success Criteria
Clarify what success looks like so you can measure progress and effectiveness later.
Prompts:
What are the top three goals of democratizing research at your organization?
Example: Improve decision-making speed, reduce researcher bottleneck, increase user-centered decisions.
How will you measure success? Define metrics such as:
Research turnaround time reduction
Number of teams using research insights regularly
Stakeholder satisfaction (surveys)
Reduction of research bottlenecks
Step 2: Assign Roles & Responsibilities
Clearly define who is accountable for each component of the implementation.
Prompts:
Who will lead and oversee the democratization initiative?
Who is responsible for developing and maintaining documentation?
Who will deliver training and ongoing support?
Who manages the centralized research repository?
Step 3: Create and Organize Core Documentation
Ensure everyone has easy access to standardized information.
Essential documentation:
Governance & approval workflows (approval process, checkpoints, escalation paths)
Research protocols & templates (usability scripts, survey templates, interview guides)
Ethics and compliance guidelines (consent forms, data handling procedures)
Training materials (slides, video recordings, FAQs)
Step 4: Develop and Schedule Training Programs
Equip non-researchers with skills necessary to conduct quality research.
Training levels:
Awareness training (Level 1): Bias awareness, when to escalate, ethics overview
Basic research training (Level 2): Usability testing, basic surveys, interviewing techniques
Advanced training (Level 3): Advanced interviewing, complex study designs, advanced analysis
Step 5: Launch and Communicate Broadly
Ensure organization-wide awareness and adoption.
Launch & communication steps:
Schedule organization-wide launch event (virtual webinar or town hall)
Announce via internal communication channels (Slack, Teams, newsletters)
Provide simple, one-page “quick-start guides” tailored to stakeholders (product managers, designers, marketers)
Hold dedicated Q&A sessions post-launch to address concerns, clarify processes
Setting Checkpoints to Periodically Review and Adjust
Regular checkpoints are critical to ensure your democratization framework remains effective, responsive, and aligned with your organization’s evolving needs. Without structured reviews, research quality and effectiveness can degrade over time.
Step 1: Define Clear Objectives for Checkpoints
To maintain clear focus and ensure each review meaningfully assesses key areas of your democratization model.
For checkpoints:
Evaluate adherence to established protocols and governance.
Assess overall quality of research conducted by non-researchers.
Monitor the impact and effectiveness of research democratization on decision-making.
Identify any new or emerging issues related to democratization (skills gaps, misalignment, repository challenges, etc.).
Review and revise your training and support strategies.
Prompts:
“What specific outcomes do we hope to achieve at each review?”
“What would trigger us to change or update our current model?”
Step 2: Schedule Regular Review Cadence
Establish a consistent schedule so teams can prepare, and adjustments become part of your organization’s operating rhythm.
Recommended review cadence:
Examples:
Monthly check-in: Brief meetings (~30 minutes) to discuss ongoing democratization progress, surface emerging issues, and address quick concerns.
Quarterly audits: Structured audits reviewing samples of research projects, assessing research quality, documentation compliance, and repository use.
Bi-annual stakeholder surveys: Send out surveys to assess stakeholder satisfaction, ease of access, perceived quality of democratized research, and additional support needs.
Annual strategic review: Dedicated strategic session to review long-term impact, align on adjustments to the democratization approach, and reset objectives for the following year.
Step 3: Design a Standardized Review Template
Streamline the review process and ensure consistency each time you conduct a checkpoint.
Template for quarterly audits:
Review period: [Q1 YYYY]
Conducted by: [Name/Title]
Date of audit: [Date]
Overall findings:
[Summary of key strengths]
[Summary of areas for improvement]
[Recommendations for actions to take before next audit]
Step 4: Communicate Results and Action Items
Ensure transparency and accountability by communicating results to stakeholders clearly, and ensure action items are addressed promptly.
Steps:
Host a brief stakeholder meeting or webinar after each formal review to present findings and outline next steps.
Distribute a concise summary of audit results via internal channels (e.g., Slack, Teams, email newsletters).
Clearly assign responsibilities for each action item, with specific due dates.
Example:
“Our quarterly review highlighted strong adherence to protocols (96%) and high-quality insights (92%). However, we’ve identified gaps in repository documentation. The UX Research Ops team will lead an improvement plan and provide additional training by the next audit (date). We’ll share an update on progress monthly.”
Step 5: Take Action and Adjust the Model Accordingly
Use your review findings to make targeted, informed adjustments to your democratization model.
Prompts
“Are there recurring issues that suggest we need to revise our training program?”
“Are stakeholders consistently facing the same challenges, suggesting a need for new resources or support?”
“Is our current repository setup working effectively, or do we need adjustments in how research is documented or accessed?”
Start Small, Test, and Iterate
Once you have identified a starting model, don’t roll it out across the entire company at once. Instead, start small and iterate, just as you would with a research-driven product change.
Test Your Democratization Approach in a Low-Risk Way
Start with a pilot team.
Choose one product or design team to test research democratization.
Provide training, mentorship, and oversight to guide their first few studies.
Measure the impact.
Track whether the team’s research efforts led to better, faster decisions.
Assess whether research quality remained high or if biases/errors crept in.
Identify areas for improvement.
Were non-researchers able to apply their training effectively?
Did studies get logged in a centralized repository, or were insights lost?
Refine the process before scaling.
Based on feedback, adjust training, review processes, and access levels.
Slowly expand the model to additional teams, ensuring quality control at each step.
By treating democratization as an iterative process, you reduce risk while ensuring that your model is optimized for your organization’s needs.
Maintain Research Integrity Over Time
Democratization requires continuous refinement to ensure research remains high-quality and impactful. To maintain integrity:
Conduct regular research audits.
Review a sample of studies every quarter to ensure they meet research standards.
Identify gaps in training or oversight and adjust accordingly.
Keep the training program updated.
As the organization evolves, new research needs will emerge; ensure training materials stay relevant.
Ensure that research findings continue to drive decisions.
If democratized research is not being used effectively, investigate whether the issue is quality, visibility, or stakeholder engagement.
By continuously evaluating and improving the democratization model, organizations can ensure that research remains an embedded, high-value function rather than becoming a diluted or ineffective process.
Done right, democratization strengthens the research function, rather than diluting it. It allows organizations to move faster while still making decisions grounded in strong, reliable user insights.
The future of research is about scaling insights responsibly. By balancing access, training, and governance, your organization can create a research culture that is not just functional, but foundationa