How do I know if my product has a market fit problem or a marketing problem?

If rewriting your copy, redesigning your funnel, or improving your onboarding hasn't moved the needle, it's probably not a marketing problem. Most persistent traction problems trace back to untested assumptions about who the customer is and how painful their problem actually is. Talking to churned users and non-buyers is usually the fastest way to find out which one it is.

When should a product team invest in UX research?

The most valuable time to invest in research is before you commit to a direction. But if you've already launched and traction is weaker than expected, structured research with churned users and non-buyers can diagnose the problem faster than any amount of A/B testing or analytics review.

What is customer discovery research and when do you need it?

Customer discovery research is structured qualitative research designed to understand whether a problem is real, how painful it is, and who actually experiences it. You need it when you're about to commit significant resources to a new product or direction, or when an existing product isn't performing as expected and you need to understand why.

How much does it cost to hire a UX research consultant?

It depends on the scope and the specific question you're trying to answer. A focused market validation or discovery research engagement typically runs 3 to 6 weeks. The best starting point is a 20-minute conversation to scope what you actually need: cal.com/mattwallens.

Why Your Product Isn't Getting Traction (And Why It's Probably Not the Product)

You shipped. You have users. The numbers aren’t moving.

Leadership is asking questions, and your team is debating positioning, pricing, the funnel, the feature set. You’re three sprints into building things nobody asked for, wondering if the whole premise was wrong.

Here’s what I’ve seen after 25 years of running research for product teams: a traction problem is almost never a product problem. It’s a research problem, and it usually started 12 to 18 months before you shipped.

The assumption you made before you built

Every product rests on a stack of assumptions: who the customer is, what problem they have, how painful it is, whether they’d pay to solve it and how much, and whether that holds across your whole target segment or was just a quirk of the first few people who said yes.

Most teams test these in the wrong order, or skip them entirely, because what gets validated early is the easiest thing to validate: the concept. A mockup gets a thumbs up, a landing page gets 200 emails, a few interviews with your own network go well. That feels like research. It isn’t.

What doesn’t get tested is whether the problem is real and painful enough to change behavior, whether the people who said they were interested are the people who’ll actually pay, and whether the segment is big enough to build a business on. That takes talking to strangers instead of your network, and asking about past behavior instead of hypothetical future behavior. That’s the work that gets skipped, and it’s what you’re paying for now.

Why it looks like something else

The gap doesn’t show up labeled as a research problem. It shows up disguised as other problems.

It looks like a conversion problem, so you rewrite the copy and test a new CTA. It looks like a churn problem, so you build better onboarding. It looks like a sales problem, so you hire a better closer. Each fix might help a little, but none of them fix a product built on assumptions that were never tested, because the offer itself doesn’t match what people need.

Your existing data won’t tell you this. Analytics show what people did, not why. NPS shows how current customers feel, not why you’re failing to acquire new ones. Exit surveys capture what people say on the way out, and most people don’t give the real reason, they say “too expensive” when they meant “I never got it working.” And interviews with your existing users only cover people who already said yes. The signal you’re missing belongs to the people who said no, and most teams never talk to them.

What to do before you build more

Before another round of features, before a growth agency, before an onboarding redesign: go talk to people who didn’t work out.

Talk to churned users, not to win them back but to understand what happened between what they expected and what they got. Talk to people who tried your trial or free tier and didn’t convert, and ask what made them hesitate. And talk to 8 to 10 people in your target segment who’ve never heard of you, about how they handle the problem today and what it would take to switch. That last group is the hardest to reach and the most valuable. You’ll learn more from those conversations than from six months of analytics.

The pattern that emerges is usually one of three things: the product doesn’t solve the problem the way people need, the problem isn’t as painful as you assumed, or you’re targeting the wrong segment. All three are fixable, but none of them are fixable without knowing which one it is.

When to bring in outside help

You can run this yourself if you have someone who isn’t too close to the product and can protect the time to do it properly. Outside help makes more sense when your team is too invested to ask neutral questions, when research keeps losing to other priorities, when you’ve already run studies but can’t agree what they mean, or when leadership needs an answer in weeks, not quarters. A fractional research lead exists for exactly these situations, work that needs to happen but doesn’t fit inside anyone’s regular sprint.

What good research actually changes

A FinTech client came to me with concept testing results the team didn’t trust enough to bring to leadership. We reran it properly with real people in the target segment and gave them a clear go/no-go they could defend in the room.

That’s what good research does: it gives you something to stand behind when the stakes are high.

If your product isn’t getting the traction you expected, the answer probably isn’t in your roadmap. It’s in conversations you haven’t had yet.

A 20-minute call is enough to figure out whether research is the right next move for your team. Book one here.

Matt Wallens is a fractional research lead based in Atlanta, GA. He founded UX Research Atlanta, a community of UX practitioners, and has led research engagements for Mailchimp, NAPA, Mayo Clinic, HP, and dozens of mid-size product teams.