Customers can describe current frustrations and still struggle to specify a solution they have never experienced. Innovation teams can also misinterpret a request because they understand the product better than the customer’s work.
Customer discovery investigates the situation in which value could be created. It combines observation, evidence and interpretation before committing to a solution.
Define whose problem matters
Separate users, buyers, decision-makers and people who influence adoption. Their objectives and constraints may differ.
A production manager may value uptime, procurement may focus on contractual exposure and technicians may need a maintainable system. An offer that appeals to one group can fail because another cannot accept it.
Choose a segment and context. “Industrial customers” is too broad to reveal consistent needs.
Identify the event or task where the problem appears, its frequency and its consequence.
Observe behavior and workarounds
Ask customers to reconstruct recent examples:
- What were they trying to accomplish?
- What happened?
- What did the interruption cost?
- How did they respond?
Where possible, observe the work and examine artifacts such as logs, spreadsheets, handovers and service records.
Workarounds can reveal needs that customers no longer mention because they have become normal. They can also indicate that the problem is tolerable and receives little priority.
Avoid treating every inconvenience as a commercially attractive opportunity.
Test the strength of the problem
Assess frequency, severity and the customer’s ability to act. A problem can be expensive while remaining difficult to solve because budget ownership is fragmented.
Ask what customers have already tried, what they currently pay and what would need to change for a new approach.
Distinguish stated preference from demonstrated behavior. A favorable interview response is weaker evidence than a customer committing time, access or money under realistic conditions.
The appropriate evidence depends on the stage and consequence of the decision.
Explore expectations without making them the only boundary
Customers evaluate performance partly through expectations. Meeting a basic requirement may prevent dissatisfaction without creating preference.
Unexpected features can attract attention, yet their value must be tested. An impressive capability may add complexity or shift work onto the user.
Technology exploration can reveal possibilities customers could not formulate. Bring those possibilities back into discovery through prototypes and concrete scenarios.
Market pull and technology push can inform one another. Neither removes the need to validate the resulting proposition.
Guard against biased interpretation
Interview across relevant cases, including non-users, lost customers and people who rejected the current offer.
Separate observation from inference. “Three customers maintain their own diagnostic spreadsheet” is evidence. “They will buy our analytics service” is a hypothesis.
Document contradictory findings and differences between segments. Averages can conceal a small group with a strong need or a broad group with little willingness to change.
Avoid leading questions that ask participants to endorse the team’s preferred idea.
Turn discovery into a decision
Produce a concise account of the customer context, the unmet outcome, existing alternatives, buying constraints and remaining uncertainties.
For a hypothetical equipment supplier, discovery might show that maintenance teams need a verified response procedure more urgently than additional condition data. That finding should influence the concept and next test.
Define what evidence would support proceeding and what would challenge the opportunity.
Customer discovery improves the quality of the problem being solved. It gives innovation teams a more credible basis for deciding which needs deserve a solution and which apparent opportunities remain unproven.