A row of pencils from a new full-length one to a tiny stub fitted into a paper extender, the middle ones softly out of focus.

8of 13

Extreme users for discovery, not market sizing

Heavy use, inventive workarounds and complete abandonment can expose overlooked problems. Learn from these cases, then test which insights apply to the wider customer group.

Build & Validate
Customer discovery

By the EWOR Team2 min read

A daily user who has developed elaborate workarounds can reveal a product's limitations in unusual detail. Someone who abandoned the same product may expose barriers that satisfied customers no longer notice. Both can offer valuable insights, but neither represents everyone who might become a customer.

Choose initial participants who can help uncover overlooked needs, then recruit others to test how widely those findings apply. Sampling is a deliberate research decision, not simply a way to make interviews more insightful.

Define the extreme through the task

Base your selection criteria on the behaviour or constraint you want to investigate. This might include unusually frequent use, repeated failed attempts, sustained reliance on a workaround or deliberate nonuse despite encountering the task.

For a hypothetical scheduling product, someone who regularly coordinates last-minute changes could reveal limitations that an occasional organiser never encounters. Someone who stopped using scheduling software might expose the burden of setup or coordination. However, nonuse alone does not establish an unmet need. The person may simply prefer an alternative that works well enough.

Avoid recruiting people under vague labels such as "difficult users". A disability or other personal characteristic does not automatically make someone an extreme user. Identify the specific task, barrier or behaviour that makes their experience relevant to your research.

Make participation accessible

Recruit participants through appropriate, permission-based channels and explain the purpose of the research. Offer ways to take part that accommodate their communication, accessibility and scheduling needs. Do not ask for sensitive personal information when a description of the task-related barrier is sufficient.

If someone has developed a workaround, ask permission to explore it without requiring them to demonstrate anything unsafe. Respect their expertise in their own circumstances, and do not generalise their experience to everyone who shares a demographic or disability category.

Turn the case into a question for other users

Record the conditions that make the problem visible. Does the workaround arise from high usage, a particular environment, missing functionality or an access barrier? Distinguish the underlying need from the participant's preferred solution.

Strong enthusiasm may identify a potential early collaborator, but it does not establish adoption, willingness to pay or how many similar customers exist. Equally, a problem does not need an especially vocal user to be worth investigating.

Recruit the comparison next

Investigate the same question with typical users in the intended segment and independently recruited nonusers. Look for both recurring patterns and meaningful differences. A specialist forum can help you find detailed cases, but it may overrepresent people who are especially motivated to discuss the issue.

If the problem appears only under demanding conditions, narrow the target segment or investigate whether the underlying mechanism affects others too. Never treat the proportion found in a small, purposively selected sample as an estimate of the wider population. Use initial interviews to uncover possibilities, then compare experiences to understand where those insights apply and where they do not.

No comments yet.

Be the first to comment on this signal.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter

Continue learning

Related modules