Building and Leading the Research Function Questions

Position (thesis)
I support a 30/70 split for a company moving from MVP to growth. It balances near-term product optimization with continued discovery that prevents blind spots and enables new growth levers.

Why (trade-offs & reasoning)

• 70% evaluative: during growth you must reduce churn, improve conversion, and validate scaling assumptions quickly; evaluative studies (usability tests, A/B UX research, funnel analysis) produce actionable changes with fast ROI.
• 30% exploratory: sustaining upstream discovery (contextual interviews, ethnography, concept testing) prevents feature bloat, uncovers new segments, and seeds longer-term strategic bets. Cutting exploration risks optimizing the wrong thing.

Governance model to enforce the split

• Quarterly research planning cycle owned by Research Lead + PM guild:
  • Capacity ledger: track researcher FTE-weeks allocated to Exploratory vs Evaluative.
  • Research intake board: all requests must be categorized (exploratory/evaluative), prioritized with RICE, and approved against the ledger.
  • Monthly audit: ops dashboard shows real-time % usage; deviation >±5% triggers review.
  • KPIs: lead time for evaluative studies, number of exploratory insights adopted, and ROI signal (metric lifts attributable to research).

Rapid reallocation mechanisms

• Emergency buffer: keep 10% of total capacity uncommitted each quarter to absorb urgent work.
• Fast-triage protocol: PMs submit emergency request; Research Lead and stakeholder triage within 24 hours; if approved, pull from buffer and deprioritize lowest-impact evaluative item (documented swap).
• Cross-training & playbooks: maintain templated study plans and trained product/design partners who can run lightweight evaluative research (5–10 day studies) to reduce ramp time.
• Sunset criteria: short-lived experiments in pipeline with clear kill criteria to free capacity quickly.

Outcome & governance discipline
This approach preserves speed for growth while safeguarding long-term discovery. The ledger + buffer + triage process makes the split enforceable and flexible under urgent business needs.

Overview — goal
I’d ensure research is both culturally valid within each country and comparable across markets by balancing localized practice with standardized design and analysis.

Recruitment

• Partner with local recruiters who understand socio-cultural segments and appropriate incentives.
• Localize screeners with back-translation and cognitive testing to preserve meaning (not literal wording).
• Adjust quotas for local digital literacy, urban/rural split, age norms, and family roles so samples map to product personas.

Study design

• Define core comparable measures (same tasks, success criteria, metrics) and a localized layer (examples, task wording, scenario context).
• Pilot in each market to surface cultural misinterpretations and refine prompts.
• Choose modalities appropriate per market (remote, in-person, moderated) while keeping core task equivalence.

Moderation

• Use local moderators for cultural rapport; train them on common probes and standardized scoring rubrics.
• Provide detailed moderator guide, example probes, and translated scripts; run calibration sessions and shadow moderations.

Analysis

• Transcribe and translate data with notes on untranslatable concepts; use bilingual analysts or cultural consultants.
• Build a shared codebook with core themes + market-specific codes; run intercoder reliability checks.
• Normalize behavioral metrics and contextualize qualitative patterns—highlight both universal themes and culturally specific insights, and recommend market-tailored product decisions.

This approach preserves comparability while honoring local nuance, producing actionable, culturally grounded insights.

RICE

• Inputs: Reach (users affected in a time period), Impact (degree of change on a scale), Confidence (certainty in estimates), Effort (person-months or days).
• How scoring works: RICE score = (Reach × Impact × Confidence) / Effort. Higher score = higher priority. Example: a 1-week guerrilla usability test might be Reach=200, Impact=2 (medium), Confidence=0.9, Effort=0.1 → high score.
• Advantage: Quantitative and comparable across disparate studies; forces you to make and surface assumptions (e.g., expected reach).
• Limitation: Inputs can be noisy for qualitative research (estimating Reach or Impact for exploratory studies is hard), and it can bias toward low-effort, high-reach quick studies.

Effort–Impact Matrix

• Inputs: Estimated Effort (low→high) and Expected Impact (low→high) — typically plotted as four quadrants.
• How scoring works: Place each study in one of four quadrants: Quick Wins (low effort, high impact), Major Projects (high effort, high impact), Fill-Ins (low effort, low impact), Time-Sinks (high effort, low impact). Prioritize Quick Wins first, then Major Projects as capacity allows.
• Advantage: Simple, visual, and great for stakeholder alignment and quick decisions.
• Limitation: Binary/qualitative placement can hide nuance (two “Major Projects” may be very different) and it lacks a numeric way to trade off confidence or opportunity cost.

Both frameworks work well together: use Effort–Impact for initial triage and RICE to break ties or compare within a quadrant, especially when justifying choices to PMs and designers.

Situation & objective
Two senior stakeholders disagree: one cites my research recommending a product direction; the other argues a strategic partner requirement forces a different path. My role is to mediate, present evidence impartially, propose further data if needed, and protect relationships.

Approach — neutral mediation

• Convene a short, structured meeting with both stakeholders and any required SMEs.
• Set goals up front: clarify the user problem, business constraints, partner obligations, and decision criteria (user impact, revenue, technical feasibility, timeline).

Presenting evidence impartially

• Share original research artifacts (synthesis, personas, key quotes, metrics) and explain methods, sample sizes, confidence, and limitations.
• Contrast hypotheses: what outcomes each option predicts for users and business.
• Use visual comparisons (expected user journeys, impact vs. risk matrix) to make trade-offs explicit.

Propose additional data

• If gaps exist, recommend targeted, fast studies: a 1-week prototype usability test with n=8–12 users, or partner-scope interviews and a quantitative funnel analysis to estimate lift vs. cost.
• Define success metrics and timeline so additional work won’t drag decision-making.

Preserve relationships

• Frame recommendations as trade-offs, not “right/wrong.”
• Acknowledge partner constraints and propose compromises (MVP that satisfies core partner requirement while validating user hypotheses).
• Commit to shared milestones and regular check-ins; document decisions and rationale for transparency.

Outcome
This process centers users, reduces perceived bias, equips leaders with clear trade-offs and metrics, and keeps cross-functional trust intact while moving toward a pragmatic decision.

Associate Design Researcher (Entry)

• Core competencies: Research fundamentals, Moderately structured interviews, Basic usability testing, Descriptive analysis, Clear reporting, Collaboration with designers.
• Deliverables/ownership: Moderated/usability sessions, cleaned datasets, participant recruitment, basic research briefs.
• Promotion criteria: Consistently executes studies with guidance, produces clear findings, improves methods, reliable logistics, positive stakeholder feedback.
• Mentorship: Receives regular coaching; documents learnings; pairs with a researcher for study design and analysis.

Researcher

• Core competencies: Mixed methods, Study design, Qual & quant synthesis, Stakeholder communication, Research ops, Ethics & recruitment.
• Deliverables: End-to-end studies, personas, journey maps, prioritized recommendations, A/B research input.
• Promotion criteria: Independently leads medium-complexity projects, influences product decisions, demonstrates rigorous analysis, repeatable processes.
• Mentorship: Mentors Associates on execution; runs brown-bags; solicits feedback on growth areas.

Senior Researcher

• Core competencies: Complex study design, Advanced synthesis, Strategic storytelling, Cross-team influence, Measurement & impact tracking, Coaching skills.
• Deliverables: Research strategy for features, impact metrics, design recommendations tied to KPIs, synthesis across studies.
• Promotion criteria: Repeatedly shapes product direction, measurable impact on metrics, leads cross-functional initiatives, mentors others.
• Mentorship: Regular 1:1s with Researchers, feedback on narratives, delegates study leadership, develops training materials.

Staff Researcher

• Core competencies: Program design, Methodological innovation, Stakeholder partnership, Thought leadership, Prioritization at scale, Organizational advocacy.
• Deliverables: Longitudinal research programs, tooling/standards, executive briefs, scalable recruitment pipelines.
• Promotion criteria: Creates research programs that shift strategy, builds org-level processes, high cross-functional trust.
• Mentorship: Coaches Senior Researchers, runs mentorship circles, shapes career growth plans.

Principal Researcher

• Core competencies: Vision & strategy, Domain expertise, Organizational influence, Research ROI mastery, Policy & ethics leadership, Talent development.
• Deliverables: Company-wide research roadmap, strategic advisories to execs, published frameworks, hires key talent.
• Promotion criteria: Demonstrable, sustained product/market shifts driven by research; recognized internal/external leader.
• Mentorship: Sponsors leaders, builds bench strength, mentors Staff and Senior Researchers; advises on promotions and org design.