How to Pressure-Test a Product Concept With People Who Aren't Your Target Users Yet

Most product concepts get tested with the wrong people at the wrong time. Teams recruit participants who already use similar tools, already understand the problem space, already speak the language of the category. The feedback comes back reasonably positive, the concept moves forward, and then the product lands in market and meets a wall of indifference from people who were never part of the conversation.

The people you most need to understand at concept stage are the ones who haven't yet decided your product is for them. They are sitting somewhere adjacent to your target audience, living with a version of the problem you're trying to solve, and they haven't found anything that feels right. Testing with them is harder than testing with enthusiasts, and the signals are messier. But those signals are far more honest about what your product actually needs to do to earn its place in someone's life.

This article is about how to design and run that kind of testing well. We'll look at who to recruit, how to frame sessions so you surface emotional responses rather than polished opinions, and how to read what people are telling you without filtering it through what you already believe about your product.

Why Adjacent Audiences Are Your Best Early Signal

Your target user, at the moment you're testing a concept, doesn't exist yet. They're a person you're imagining based on research, intuition, and sometimes wishful thinking. Recruiting people who already fit that profile perfectly sounds logical, but it introduces a problem: those people bring their own fluency with the category, and that fluency masks the friction your concept actually creates.

Adjacent audiences sit close enough to your target segment to have lived experience of the underlying problem, but they haven't yet committed to any solution. A person who tracks their food intake in a notebook is adjacent to the target user for a nutrition app. A parent who manages their child's football schedule in a group chat is adjacent to the audience for a grassroots sports coordination tool. They feel the same frustration, but they haven't been shaped by any product's existing conventions.

This distance is what makes their responses useful. They react to your concept from a position of genuine need, without the filter of what they're used to seeing in the category. When something confuses them, it's genuinely confusing. When something resonates, it's because the concept touched a real feeling rather than confirming a familiar pattern.

The goal at concept stage is to find out whether the emotional problem you think you're solving actually matches the emotional problem people are experiencing. Adjacent audiences give you that signal cleanly, because they haven't already decided how they feel about products like yours.

Mapping Emotional Proximity to Your Target Segment

Before you recruit anyone, it helps to map out the emotional territory around your product. Start by listing every situation that could lead someone to your concept. A product for managing a rented flat, for example, draws in first-time renters who feel overwhelmed by adult responsibility, people going through relationship breakdowns who are suddenly living alone, and people who've just moved to a new city and are finding their footing. Each of those situations carries a different emotional weight, and the concept needs to work across all of them.

Once you've mapped the situations, you can identify which adjacent audiences share the core emotional experience without fitting the exact demographic profile. You're looking for emotional proximity, not demographic match. Someone who recently went through a significant life change and is reconfiguring their daily routines is emotionally close to your target user even if their specific context differs.

Ranking Proximity

Rank your adjacent audiences by how close their emotional experience is to the core problem. The closer the emotion, the more transferable their responses will be. A person who finds admin tasks stressful and unmanageable is closer to your target than a person who is simply unfamiliar with digital tools.

Checking for Blind Spots

Also look at who is conspicuously absent from your mapping. If every scenario you've listed assumes a certain level of digital comfort, or a certain type of living arrangement, you may be designing for a narrower emotional range than you realise. The mapping exercise surfaces those gaps before you start spending money on sessions.

Designing Tests That Surface Feeling, Not Just Opinion

Most concept testing produces opinion data. Participants tell you what they think about the product, what features they'd want, what they'd change. That data has its uses, but it rarely tells you how the product makes people feel, and feeling is what determines whether someone comes back after day one.

The design of your test needs to actively create space for emotional response. That means asking open questions with no right or wrong answer and then letting the conversation find its own shape. If you ask someone whether they would use a product, you get a rational answer. If you ask them to describe how they currently handle a particular situation and then invite them to react to the concept, you get something closer to a felt response.

The questions that matter most are about how someone feels during a process, not what they think they would do differently.

Keep the early questions broad and personal. Ask about the current experience before you show them anything. Ask what's frustrating, what's fine, what they've tried before. By the time they see the concept, they've already articulated the emotional problem in their own words, and you can watch whether the concept lands against that articulation or misses it entirely.

Write your discussion guide in plain language, then read it aloud to someone outside your team. If any question sounds like it's fishing for a particular answer, rewrite it until it doesn't.

Avoid binary questions and scales wherever possible. Asking someone to rate their satisfaction out of ten produces a number, not a story. The stories are where the useful signals live. Build in plenty of time for participants to wander conversationally, and resist the urge to redirect them too quickly when they go off script. The off-script moments are often the most revealing.

Running the Sessions: A Fitness Product Walkthrough

To make this concrete, consider how these principles apply to a fitness product aimed at people who want to build more consistent exercise habits. The target user is someone who exercises irregularly and wants to do better. Adjacent audiences include people who've recently joined a gym but haven't been back in weeks, people who bought home workout equipment that's now gathering dust, and people who walk regularly but feel that doesn't quite count.

A session with these participants would begin well before the product is introduced. You'd ask them to describe what exercise looks like in their week right now, without judgement and without prompting them towards any particular answer. You're listening for the emotional texture of how they talk about it: whether they feel guilt, resignation, ambivalence, or something more complex.

Introducing the Concept

When you introduce the concept, you do so without a sales pitch. Show it as a sketch or a rough prototype, and frame it simply as something you're working on that might be relevant to what they've just described. Ask how it makes them feel, not whether they'd use it. Watch their physical reactions as much as you listen to their words. A small hesitation, a frown at a particular element, a moment of leaning forward rather than back: these are all data.

What to Listen For

With a fitness product particularly, you're listening for whether the concept feels permissive or demanding. Research in this space consistently shows that people who have struggled with consistency respond to products that celebrate showing up at all, doing two minutes rather than zero, being slightly better than yesterday. If participants start describing the concept in terms of pressure or performance, the emotional framing needs work, regardless of the features on offer.

Run at least one session with someone who has tried and abandoned a similar product before. Their reasons for stopping are often more instructive than a current user's reasons for staying.

Reading Responses Without Projecting Insider Bias

The hardest part of concept testing is reading the responses accurately when you're already close to the idea. Everyone who has spent months developing a concept carries an invisible set of assumptions about what users will understand, what they'll find appealing, and what objections they'll have. Those assumptions shape what you notice in a session and what you explain away.

Insider bias shows up in specific ways. You hear a participant express confusion about a concept and you mentally note that it's because the prototype is incomplete, not because the concept itself is unclear. You hear someone say the product feels overwhelming and you file it under "not the target user" rather than asking whether the concept is genuinely too complex. You hear enthusiasm about a feature you didn't expect and you downplay it because it wasn't part of your original vision.

• Separate observation from interpretation during sessions. Write down exactly what participants say and do before you add any layer of meaning to it.
• Include at least one person in the analysis who wasn't in the sessions. Their reading of the notes will surface assumptions you didn't know you were making.
• Look for patterns across participants rather than anchoring on individual responses. One person's confusion is noise. Four people's confusion about the same element is a signal.
• Pay attention to what people don't say as much as what they do. If nobody mentions a feature you expected to be central, that silence is worth examining.

Removing insider bias doesn't mean dismissing your team's knowledge of the product. It means creating a structured process for interpreting feedback that gives outside perspectives equal weight alongside internal ones. People who already understand the science or the technology behind a product will always find it harder to see it through a newcomer's eyes, and that difficulty is worth designing around.

Translating Emotional Signals Into Concept Decisions

After testing, you'll have a body of qualitative material: notes, observations, recordings, and probably a set of competing interpretations from different members of your team. The challenge is translating that material into decisions about the concept without losing the emotional nuance in the process.

Start by grouping responses around emotional themes rather than features. If multiple participants described feeling reassured by a particular element, that's a signal worth protecting. If several described feeling uncertain or pressured at a certain point in the experience, that's a signal worth addressing, regardless of how logically sound that part of the concept is. Emotional responses to a concept are often more predictive of behaviour than feature preferences, because they reflect how the product will actually feel to use day after day.

Weighting the Signals

Not all signals carry equal weight. A response that was consistent across adjacent audiences who differ in other ways is a stronger signal than one that came from a single participant. A response that echoes something participants said about their current behaviour is stronger than one that only appeared when they were reacting to the concept directly.

Map emotional responses back to the specific moments in the concept that prompted them. This turns abstract feedback into design decisions with a clear reference point.

Knowing What to Hold

Some elements of a concept will survive testing intact, some will need rethinking, and some will turn out to be solving a problem that participants don't actually experience as a problem. The discipline is in being honest about which is which, and in making those distinctions based on what you heard rather than what you hoped to hear. Concept decisions made on honest emotional signal tend to produce products that earn their place in people's lives faster than those built on validated assumptions.

Conclusion

Testing a product concept with people who aren't your target users yet is one of the most honest things you can do for an idea you believe in. It replaces the comfort of confirmation with something more useful: early, clear, unfiltered signal about whether the emotional problem you're solving actually matches the emotional experience people are having.

The process we've described here is not about finding reasons to abandon a concept. It's about giving the concept a fair test before it meets a market that won't give it a second chance. Adjacent audiences, open-ended questions, careful observation, and honest interpretation of what you hear: these are the tools that separate product decisions grounded in real human feeling from those grounded in internal conviction.

The competitive market analysis, the feature mapping, the business case. All of that work retains its value. Testing with adjacent audiences adds the missing dimension that gives it a different edge, because it tells you whether real people, sitting with real versions of the problem, feel something when they encounter what you've built.

If you're working through early concept decisions and want a clearer read on the emotional signal your product is giving off, we'd be glad to think through it with you. You can find us at weareaffective.com.

This article is part of our guide to App User Research.

Frequently Asked Questions