Rasp logo

Rasp

Five User Research Methods You Can Do This Week With Zero Budget

•By Rasp Team

Every PM knows they should do user research.

Then reality hits:

  • No budget for research tools
  • No dedicated researcher on the team
  • No time to run a formal study
  • No idea where to start

So they skip it. Build based on gut feel. Hope for the best.

Here's the truth: The best user research doesn't require UserTesting subscriptions, fancy tools, or weeks of planning.

It requires curiosity, hustle, and willingness to talk to actual humans.

These five methods cost nothing, take minimal time, and will give you better insights than most expensive research studies.

You can start any of them this week.

Method 1: Support Ticket Deep Dive

What it is: Systematically reading and analyzing support tickets to find patterns

Time required: 2-4 hours

What you need: Access to support ticket system (Zendesk, Intercom, etc.)

How to Do It

Step 1: Pick a Time Period

Start with the last 30 days. This gives recency without overwhelming volume.

Step 2: Categorize Tickets

Create buckets:

  • Bug reports
  • Feature requests
  • "How do I..." questions
  • Complaints
  • Confusion about existing features

Step 3: Look for Patterns

Ask:

  • Which questions get asked repeatedly?
  • What do users struggle to figure out?
  • Which features generate the most confusion?
  • What workflows break down?

Step 4: Note the Language

Pay attention to how users describe their problems. They'll use different words than you do.

Example:

You call it "dashboard filters." Users call it "narrowing down results."

Use their language in your product.

Step 5: Follow Up

Pick 3-5 interesting tickets. Email those users:

"Hey [Name], I saw your ticket about [issue]. I'm the PM for this area. Can I ask you a few quick questions to understand this better?"

Response rate: 30-50% will respond. People love when PMs actually care.

What You'll Learn

  • Which parts of your product are confusing
  • Language users actually use
  • Problems you didn't know existed
  • Workarounds users have created

Real example: A PM analyzed support tickets and found 40% of questions were about one specific workflow. The feature worked fine — the UI just made it hard to discover. They added one tooltip and reduced support volume by 35%.

Method 2: Customer Interview Lightning Rounds

What it is: 15-minute calls with existing customers

Time required: 3-5 hours total (including prep and follow-up)

What you need: Email access and a calendar

How to Do It

Step 1: Identify Targets

Pick 10 users who:

  • Recently signed up (< 30 days) — fresh perspective
  • Are power users — deep product knowledge
  • Recently churned — honest about what failed
  • Upgraded recently — know what drove value

Step 2: Send Simple Outreach

Subject: Quick question about [Product]

Hi [Name],

I'm the PM for [Product]. I noticed you [recently signed up / are a power user / recently upgraded].

Would you have 15 minutes this week for a quick call? I'd love to understand:
- How you're using [Product]
- What's working well
- What could be better

No pitch, no sales — just want to learn.

[Calendar link]

Thanks,
[Your name]

Response rate: 20-40% will book. You only need 5 good conversations.

Step 3: Structure the Interview

Minutes 0-2: Build rapport

"Thanks for making time. Tell me a bit about your role and what you're working on."

Minutes 2-7: Understand their context

  • "Walk me through the last time you used [Product]."
  • "What were you trying to accomplish?"
  • "How does this fit into your broader workflow?"

Minutes 7-12: Dig into specifics

  • "What's frustrating about [Product]?"
  • "If you could wave a magic wand and change one thing, what would it be?"
  • "What almost stopped you from signing up / upgrading?"

Minutes 12-15: Wrap up

  • "What did I not ask that I should have?"
  • "Can I follow up if I have more questions?"

Step 4: Take Notes

Don't record (requires consent, feels formal). Just take notes.

Focus on:

  • Exact phrases they use
  • Problems they mention
  • Workarounds they've created
  • Things that surprised you

Step 5: Synthesize

After 5 interviews, look for patterns:

  • What did 3+ people mention?
  • What surprised you?
  • What contradicts your assumptions?

What You'll Learn

  • How people actually use your product (vs. how you think they do)
  • Jobs they're trying to accomplish
  • Features they don't even know exist
  • Competitors they considered

Real example: A PM assumed users wanted more automation features. After 5 interviews, learned users actually wanted better manual controls — they didn't trust automation. Complete opposite of what roadmap planned.

Method 3: Session Replay Analysis

What it is: Watching real users navigate your product

Time required: 2-3 hours

What you need: Session replay tool (many have free tiers: Hotjar, FullStory, LogRocket)

How to Do It

Step 1: Filter for Interesting Sessions

Look for:

  • Rage clicks — users clicking same thing repeatedly (sign of frustration)
  • Long sessions with no conversion — users trying but failing
  • Dropoffs — users leaving at specific points
  • Error encounters — users hitting errors

Step 2: Watch 10-15 Sessions

Don't just skim. Actually watch what users do.

Watch for:

  • Where they pause or hesitate
  • Where they backtrack
  • What they ignore
  • What they click that doesn't do anything
  • Forms they abandon

Step 3: Note Patterns

After 10 sessions, you'll see patterns:

  • "Users keep trying to click [thing that's not clickable]"
  • "People miss the [button] because it's below the fold"
  • "Everyone hovers over [element] looking for explanation"

Step 4: Test Your Hypotheses

Spotted a pattern? Test it yourself:

  • Can you replicate the confusion?
  • What would make it clearer?
  • Is this a quick fix or bigger problem?

What You'll Learn

  • Where your UX fails
  • What users expect vs. what happens
  • Features users don't discover
  • Copy that confuses people

Real example: A PM watched users repeatedly try to click a decorative element that looked like a button. Quick CSS change to make it not look clickable reduced confusion by 60%.

Method 4: "Five Whys" on Churn

What it is: Deep investigation into why customers leave

Time required: 3-4 hours

What you need: Access to churned customer list and email

How to Do It

Step 1: Identify Recent Churns

Last 30 days. Pick 10-15 customers who cancelled.

Step 2: Send Personal Email

Subject: Can I ask why you left?

Hi [Name],

I noticed you recently cancelled [Product]. I'm the PM and I'd love to understand what didn't work for you.

Would you have 10 minutes for a call? Or if that's too much, even just a quick reply would help.

I'm not trying to win you back (though if we can fix your issue, that'd be great). I genuinely want to make the product better.

Thanks,
[Your name]

Why this works: Honesty. You're not sales. You're not promising anything. You just want to learn.

Step 3: Do the "Five Whys"

When they tell you why they left, keep asking "why":

Example conversation:

  • User: "It was too expensive."
  • You: "What made it feel too expensive?"
  • User: "We weren't using it enough to justify the cost."
  • You: "Why weren't you using it?"
  • User: "It didn't integrate with our CRM."
  • You: "Why was CRM integration important?"
  • User: "We needed data in one place. Manual export/import was too much work."

Root cause: Not price. Missing integration that blocked workflow.

Step 4: Categorize Churn Reasons

After talking to 5-10 churned customers, categorize:

  • Product gaps (missing features)
  • Onboarding failures (never activated)
  • Performance issues (too slow, buggy)
  • Price sensitivity (actual pricing issue)
  • Wrong fit (shouldn't have bought in first place)

What You'll Learn

  • Real reasons people leave (not what they say in cancellation survey)
  • Features that block adoption
  • Competitive weaknesses
  • Onboarding gaps

Real example: SaaS company thought churn was about price. Churn interviews revealed 70% of cancellations happened because users couldn't import their existing data. Built import tool. Churn dropped 40%.

Method 5: Competitor User Interview

What it is: Talking to people who use competitor products

Time required: 4-5 hours

What you need: LinkedIn, Twitter, or relevant communities

How to Do It

Step 1: Find Competitor Users

Where to look:

  • LinkedIn: Search "[Competitor] user" or job titles
  • Twitter: Search mentions of competitor
  • Reddit/communities: Product-specific subreddits
  • G2/Capterra reviews: People who reviewed competitor

Step 2: Reach Out

Hi [Name],

I saw you use [Competitor]. I'm researching [category] tools and would love to understand what you like/dislike about it.

Not pitching anything — just doing research. Would you have 15 min for a quick call?

Happy to send you a $25 Amazon gift card as thanks.

[Your name]

Note: $25 gift card is optional but dramatically increases response rate. If you can't expense it, skip it. You'll still get some responses.

Step 3: Interview Script

Ask:

  • "How did you choose [Competitor]?"
  • "What other tools did you evaluate?"
  • "What does [Competitor] do really well?"
  • "What's frustrating about it?"
  • "What's missing that you wish it had?"
  • "If you were starting over, would you choose it again?"

Step 4: Compare to Your Product

Look for:

  • Features they love that you don't have
  • Features they hate that you also have (don't copy blindly!)
  • Unmet needs neither product solves
  • Positioning opportunities

What You'll Learn

  • Why users choose competitors
  • Competitive strengths and weaknesses
  • Features that actually matter (vs. marketing claims)
  • Opportunities to differentiate

Real example: PM interviewed 8 competitor users. Expected to hear about feature gaps. Instead, everyone complained about terrible support. Realized differentiator wasn't features — it was being responsive. Doubled down on support quality.

Bonus Method: Hallway Testing

What it is: Showing prototypes/designs to anyone nearby

Time required: 30 minutes

What you need: A prototype or even just a sketch

How to Do It

Step 1: Create Something to Test

  • Wireframe
  • Figma prototype
  • Even just a sketch

Step 2: Grab Anyone

  • Coworkers (non-product team)
  • Friends
  • Coffee shop strangers (buy them coffee)
  • Family members

Step 3: Give Them a Task

"Pretend you're trying to [accomplish goal]. Walk me through what you'd do."

Don't help them. Just watch.

Step 4: Note What Breaks

  • Where do they get stuck?
  • What do they try that doesn't work?
  • What do they expect vs. what happens?

What You'll Learn

  • UX that seems obvious to you but isn't
  • Copy that confuses people
  • Workflows that don't make sense

Important: These aren't real users, so don't treat this as validation. Use it to find obvious UX problems before building.

How to Synthesize Research Findings

After doing 2-3 of these methods, you'll have notes. Now what?

Step 1: Pull Out Themes

Read through all your notes. Look for:

  • Things mentioned by 3+ people
  • Surprising insights
  • Contradictions to your assumptions

Step 2: Create a Simple Doc

# Research Findings — [Date]

## Methods Used
- [List methods]
- [Total people talked to]

## Key Themes

### Theme 1: [Name]
- Evidence: [Quotes, data points]
- Impact: [How many users affected]
- Recommendation: [What to do about it]

### Theme 2: [Name]
[Same format]

## Surprises
[Things that contradicted assumptions]

## Quick Wins
[Problems that are easy to fix]

## Longer-Term Opportunities
[Strategic insights for roadmap]

Step 3: Share Widely

Don't hide research in a doc. Share with:

  • Engineering team
  • Design team
  • Leadership
  • Sales/support

Why: Research builds empathy. When team hears actual user voices, priorities shift.

Common Mistakes to Avoid

Mistake 1: Only Talking to Happy Customers

Problem: Survivorship bias. You only learn why people stay, not why they leave.

Fix: Balance happy customers with churned ones.

Mistake 2: Leading Questions

Bad: "You'd love it if we added [feature], right?"

Good: "What's the biggest challenge you face with [workflow]?"

Fix: Ask open-ended questions. Let them tell you problems, not confirm your solutions.

Mistake 3: Ignoring Negative Feedback

Problem: Dismissing criticism as "they just don't get it."

Fix: If 3+ people say the same thing, take it seriously.

Mistake 4: Doing Research But Not Acting

Problem: Research becomes performative if you don't change anything.

Fix: Every research effort should have action items.

Mistake 5: Waiting for Perfect

Problem: "I need 50 interviews to be statistically significant."

Fix: 5 interviews reveal 80% of insights. Start small. Iterate.

Your Week-Long Research Plan

Monday (2 hours):

  • Morning: Support ticket analysis
  • Afternoon: Email 10 customers for interviews

Tuesday (1 hour):

  • Watch 10 session replays

Wednesday (3 hours):

  • Conduct 3 customer interviews (scheduled from Monday's emails)

Thursday (2 hours):

  • Email 5 churned customers
  • Start competitive user outreach

Friday (2 hours):

  • Synthesize findings
  • Share with team
  • Identify top 3 action items

Total time: 10 hours

Total cost: $0 (or $50 if you do gift cards)

Output: More user insight than most PMs get in a quarter

Tools That Actually Help (All Free Tiers)

Session replay:

  • Hotjar (free up to 35 sessions/day)
  • Microsoft Clarity (unlimited, free)
  • LogRocket (free tier available)

Scheduling:

  • Calendly (free tier)
  • Cal.com (open source, free)

Note-taking:

  • Notion (free for personal)
  • Google Docs (free)
  • Obsidian (free)

Finding users:

  • LinkedIn (free search)
  • Twitter (free)
  • Reddit (free)

Making Research a Habit

Don't treat this as one-time exercise.

Weekly ritual:

  • Read 10 support tickets
  • Watch 5 session replays
  • Talk to 1 customer

Monthly ritual:

  • Interview 5 customers
  • Interview 2 churned customers
  • Check competitor reviews

Time commitment: 2-3 hours per week

Impact: Constant stream of user insights feeding roadmap

What to Do With Research Insights

Short-term (This Sprint)

  • UX quick fixes
  • Copy improvements
  • Bug priorities

Medium-term (Next Quarter)

  • Feature enhancements
  • Onboarding improvements
  • Documentation gaps

Long-term (Strategic)

  • New features
  • Product positioning
  • Market opportunities

Final Thought

You don't need a research team to do research.

You don't need expensive tools to talk to users.

You don't need months of planning to learn what's broken.

You need curiosity and hustle.

Pick one method from this list.

Do it this week.

You'll learn more than you expect.

And it won't cost you a dollar.