PM Gym

The 5-Step User Research Process

A repeatable recipe for learning from users — without a research degree

Good research isn't about fancy labs; it's about asking a sharp question, putting it in front of the right people the right way, and turning what you hear into decisions. Five steps, every time.

Step-by-step lessons

The Five Steps

One lesson per step. The order matters: each step depends on the one before it.

1

Define the Objective

Every good study starts with one sharp question plus the decision that hangs on the answer. "Let's learn about our users" is a wish, not an objective.

Everyday example — texting a friend for advice

When a friend texts "help me decide," the useful first question is: "what will you actually do differently depending on my answer?" If they've already booked the flights, your opinion on the destination is just chit-chat. Research is the same: before you spend anyone's time, know the real decision waiting on the other end. "Understand our users" leads to a nice chat and no change. "Find out why trials die in week one, so we know whether to fix onboarding or the price" has a decision attached — so every finding will actually land somewhere.

The litmus test

Ask: "What will we decide differently depending on the answer?" If nothing changes either way, the research is entertainment.

Weak: "Understand our dashboard users." Strong: "Find out why weekly dashboard usage is flat, to decide between a redesign and better onboarding."

Quick check

Which of these is a strong research objective?

2

Choose the Method

The method follows from the type of question you're asking. Four common question types, four families of methods:

Everyday example — the right tool for the job

You wouldn't use a hammer to tighten a screw. Research methods are the same — each fits a different kind of question. Want to know how many people prefer tea over coffee? Poll a big crowd (a survey). Want to know why your friend quit coffee? Sit down and talk (an interview). Want to know if someone can actually assemble your flat-pack chair? Hand them the box and watch (a usability test). Want to know which of two menus sells more? Try both and compare sales (an A/B test). Pick the tool that matches the question, not the one you're most comfortable holding.

Why? How?

Interviews & field studies

Understand motivations, workflows, and context. Small numbers, deep answers.

Can they use it?

Usability tests

Watch real people attempt real tasks. About five users finds most issues.

How many?

Surveys & analytics

Measure scale and frequency across the whole audience.

Which is better?

A/B & fake-door tests

Compare options with behavioral evidence, not opinions.

Quick check

Your question: "Why do restaurant owners still manage bookings on paper instead of using apps like ours?" Best method?

3

Recruit the Right People

Five people from the right segment beat fifty from the wrong one. Recruiting is where studies quietly go wrong — because the easiest people to reach are rarely the ones you need.

Everyday example — taste-testing kids' cereal

If you're designing a breakfast cereal for children, you test it on kids, not on their parents — a parent guessing what a 7-year-old likes is worthless data. Same logic everywhere: to learn why people quit your gym, talk to ex-members, not the regulars still showing up happily. The easiest people to grab (your friends, your teammates, your biggest fans) are almost never the right ones — and their politeness and insider knowledge quietly poison the answers. Fish where the fish are: recruit the exact people who did the thing you're studying.

1

Screen by behavior, not just demographics

Studying churn? Recruit people who actually canceled. Studying invoicing? Recruit people who send invoices — not people who say they might.

2

Beware convenience samples

Teammates, friends, and your biggest fans are the easiest to book and the least representative. Their answers are polluted by politeness and expertise.

3

Small incentives work

A modest gift card recruits honest strangers. It costs less than one wrong feature.

Quick check

You're researching why users cancel subscriptions. Who do you recruit?

4

Conduct Without Contaminating

The way you ask determines what you get. Three rules keep the data clean:

Everyday example — good reporter vs. bad reporter

A bad reporter asks, "You must have been furious about that, right?" — and gets back whatever they suggested. A good reporter asks, "What happened next?" and then goes quiet, letting the person fill the silence with the real story. In research you want to be the good reporter: ask about what actually happened ("tell me about the last time you…"), keep questions open, and resist the urge to jump in. The moment you hint at the answer you're hoping for, polite people hand it right back to you — and your data is worthless.

1

Past behavior over future intent

"Walk me through the last time you…" beats "would you ever…?" People are historians of their own lives and terrible fortune-tellers.

2

Open questions, then silence

"What happened next?" — then wait. Silence is uncomfortable; users fill it with the good stuff.

3

Never pitch, never lead

"Don't you think this is easier?" teaches participants the answer you want. In usability tests: give the task, then stay quiet while they struggle.

Quick check

Which interview question will produce the most trustworthy answer?

5

Synthesize and Share

Research that stays in a folder changed nothing. The last step converts raw sessions into decisions:

Everyday example — the chef, not the grocery bag

A chef doesn't dump a bag of raw ingredients on your table — they cook and plate a dish you can actually enjoy. Handing stakeholders raw transcripts is dumping the grocery bag: you're making them do the cooking (and they won't). Your job is to synthesize the messy sessions into a few clear, well-plated insights, and to show the evidence — a 30-second clip of a real user getting stuck beats a 30-page report every time. Bring the dish, cooked and served, into the room where the decision gets made.

1

Cluster into themes

Affinity-map the observations and let patterns emerge (the full technique lives in Driving User Insights).

2

Write insight statements

[Observation], because [reason], which means [implication] — each tied back to the original research objective.

3

Share with evidence attached

A 30-second clip of a real user failing beats a 30-page report. Bring quotes and clips into the room where the decision happens.

Quick check

You finished eight interviews and the findings challenge the roadmap. What's the most effective way to share them?

Review the concepts

User Research Flashcards

Six cards — the process plus one per step. Click to flip.

Process Card 1 of 6

The 5 Steps

Click to flip

Tip: say the answer out loud before flipping.

Explanation

In practice

1 / 6
Apply what you learned

Practice Scenarios

15 research situations with realistic constraints — sharpening objectives, choosing methods, recruiting well, asking clean questions, and sharing findings. Pick the move a disciplined researcher makes, then read why the others miss.

Scenario 1

Your manager says: 'Go do some user research on our new dashboard.' Nothing more specific.

What's your first move?

Scenario 2

You have one week and almost no budget to find out whether people can complete checkout in your new app.

What do you do?

Scenario 3

A teammate proposes validating a new feature idea by surveying your most engaged power users: 'They know the product best.'

What's the problem?

Scenario 4

Your question is "How many of our users would use a dark mode, and how strongly do they want it?" A researcher plans five in-depth interviews.

Is the method a good fit?

Scenario 5

A usability test is scheduled with 50 participants to "be statistically valid," which will take a month to run and analyze.

What's the more efficient approach?

Scenario 6

To study why users churn, a PM recruits from the list of users who are still actively subscribed, because "they're the easiest to contact through the app."

What's the recruiting error?

Scenario 7

In a usability test, the moderator says before each task: "This next part is really easy and intuitive, you'll love it."

Why does this ruin the test?

Scenario 8

A stakeholder wants to run research to "prove that users want the feature we've already decided to build."

What's wrong with this framing?

Scenario 9

During an interview, a user goes quiet for eight seconds after you ask about their last frustrating experience. The interviewer feels awkward and jumps in with "was it the loading speed?"

What did the interviewer do wrong?

Scenario 10

You need to decide between two onboarding designs. You have live traffic and can measure which one leads to more completed setups.

Which method best answers 'which is better?'

Scenario 11

Leadership wants "big, statistically-significant research" before any decision, but you have a small user base and a one-week deadline for a design choice.

What's the pragmatic, honest approach?

Scenario 12

A researcher recruits participants for a study on a professional accounting tool by posting in a general "make money online" forum, because it was quick and free.

What's the risk?

Scenario 13

After great interviews, a PM emails stakeholders a 40-page report with every transcript. Two weeks later, the roadmap decision ignored all of it.

What's the synthesis-and-share failure?

Scenario 14

You want to understand the real workflow of warehouse pickers, but you plan to interview them over video calls during their lunch break.

What might a better method capture that interviews miss?

Scenario 15

A PM insists that talking to just five users can never be trusted and that no research is worth doing unless hundreds participate.

What's the balanced, correct view?

Lock it in

Guess the Term

Read the clues and name the concept. The fewer clues you need, the more points you score.

Round 1 Score 0
Keep it handy

User Research Quick Reference

The five steps and the golden rules on one screen.

The 5 Steps

1

Define the objective

One sharp question + the decision that hangs on it.

2

Choose the method

Why → interviews. Can they → usability tests. How many → surveys/analytics. Which → A/B tests.

3

Recruit

Screen by behavior; five right people beat fifty wrong ones.

4

Conduct

Past behavior, open questions, silence. Never pitch.

5

Synthesize & share

Themes → insight statements → clips in the decision room.

Golden Rules

Behavior over intent

"Tell me about the last time…" beats "would you…?" every time.

No convenience samples

Teammates, friends, and superfans are biased by definition.

Five users find most usability issues

Small, fast rounds with fixes in between beat one giant study.

No decision, no research

If no choice depends on the answer, save everyone the time.

Which Method?

Match the tool to the question you're asking.

Why? How?

Interviews — deep motivations and context, small numbers.

In their real setting?

Field study / contextual inquiry — watch the work where it happens.

Can they use it?

Usability test — ~5 users on a real task find most issues.

How many? How often?

Survey or analytics — measure scale across the base.

Which is better?

A/B or fake-door test — behavioral proof, not opinions.

Common Pitfalls

Where studies quietly go wrong.

Research to "prove" a decision

Confirmation bias baked in. Ask an open, falsifiable question.

Leading / reassuring

"This is easy, right?" plants the answer. Stay neutral and quiet.

Wrong sample size

~5 for usability, large for quantitative. Match size to the question.

The unread report

Distill to insights + clips; present in the decision room, don't email a PDF.

Notification