All outcomes
Teams

Conduct 50 User Research Interviews

16 weeks · 0 milestones

Plan, run, and synthesize insights from 50 structured user research interviews with documented themes and decisions made.

Milestone map

Milestone map

3 milestones

Define a user research question for a real product, service, or internal tool: what behaviour, need, or pain point do you want to understand? Write a research protocol covering: the research question, participant criteria (role, experience level, relationship to the product), recruitment method, interview format (semi-structured with open questions), and the ≥10 core interview questions. Pilot the protocol with ≥1 internal colleague before external recruitment — a pilot surfaces ambiguous questions, timing issues, and question ordering problems before they affect real participant data. A research protocol without a pilot run is a protocol that was never tested.

Proof required

Submit your research protocol (research question, participant criteria, ≥10 interview questions with rationale for each), and your pilot run notes: who the pilot was with, what changed after the pilot, and the final revised question list.

What gets checked

  • Research question is specific and investigable — 'understand user behaviour' is not a research question; 'understand why registered users do not complete the onboarding flow after day 1' is
  • ≥10 interview questions are listed with a brief rationale for each — not just the question list
  • Pilot run notes document at least one change made after the pilot — a protocol that changed nothing after piloting was not piloted critically

We use analytics to improve Powstik. No ads, ever.