To identify product opportunities worth pursuing, you need more than an interesting idea or a collection of customer complaints. You need credible evidence that a meaningful problem exists, that solving it could create sufficient value and that there is a realistic path towards developing a commercially viable product.
Finding possible opportunities is rarely the difficult part. Spend enough time speaking with customers, observing people at work or reviewing an existing product, and you will uncover plenty of frustrations, inefficiencies and unmet needs.
The harder question is whether any of those problems justify a genuine commitment of time and dollars.
Developing a product can require research, industrial design, engineering, prototypes, intellectual property advice, compliance work, tooling, manufacturing setup and stock before the first meaningful return appears. An interesting problem is therefore not enough. It needs to matter to the user, offer credible commercial potential and be realistic to solve.
The purpose of early opportunity assessment is not to prove that a product will succeed. It is to decide whether the evidence is strong enough to justify the next stage of investigation.
What is a product opportunity?
A product opportunity is a clearly defined problem or unmet need that could potentially be addressed by a new or improved product.
It is not yet a finished product idea. It is the space between a genuine user problem and the range of possible solutions that may address it.
This distinction matters because teams often become attached to a solution before establishing whether the underlying problem deserves investment. They begin discussing features, materials, electronics or appearance while the evidence supporting the opportunity itself remains weak.
A stronger sequence is:
- Observe a problem or unmet need.
- Gather evidence about who experiences it and under what conditions.
- Define the underlying problem.
- Assess whether the opportunity is worth pursuing.
- Only then begin exploring possible solutions.
This reflects the early Discover and Define stages of the Design Council’s Double Diamond. The first step is to understand the problem rather than assume what it is, before using the resulting insight to define the challenge more clearly.
Identify Product Opportunities Using Evidence, Not Assumptions
Product opportunities can emerge from many places. Customers may describe a recurring frustration. Operators may develop an awkward workaround. Service teams may encounter the same failure repeatedly. Sales teams may hear regular requests for something the current product range does not provide.
Useful evidence can include:
- Direct observation of users completing a task
- Interviews about recent, real experiences
- Recurring complaints, returns or support requests
- Unsafe, tiring or inefficient work practices
- Improvised tools and user-created modifications
- Tasks requiring unnecessary time, training or physical effort
- Products being used in ways their designers did not anticipate
- Existing solutions that perform poorly in particular environments
- Changes in technology, regulation or manufacturing capability
A complaint alone is not proof of a commercially worthwhile opportunity. However, recurring behaviours and workarounds can reveal that users already invest effort, time or money in managing a problem.
Whistle’s article on why user feedback is crucial in industrial design explains how real-world input can reveal pain points, unexpected uses, ergonomic issues and unmet needs. The next step is to determine what those observations actually mean and whether they point towards an opportunity worth further investigation.
Separate the Observation from the Interpretation
An observation records what happened. An interpretation proposes why it happened.
For example:
- Observation: Operators regularly place tape over a particular control.
- Weak interpretation: The control needs a cover.
- Questions worth investigating: Is the control being activated accidentally? Is its function unclear? Is it positioned poorly? Is it unnecessary during normal use? Does the product provide insufficient feedback?
The weak interpretation jumps immediately to a design feature. The questions keep the investigation open long enough to find the underlying problem.
This is important because a visible frustration may be only a symptom. A difficult latch might appear to need a larger handle, but the true problem could be contamination, misalignment, excessive closing force, poor feedback or a task requiring the user to wear gloves.
If the team responds to the first symptom it sees, it may create a better version of the wrong solution.
Identify Product Opportunities by Looking for Patterns
A single observation may be useful, but patterns provide stronger evidence. To reliably identify product opportunities, review the evidence across different users, environments and stages of the task.
Look for:
- The same problem affecting multiple users
- The same user experiencing the problem repeatedly
- Different complaints with a common underlying cause
- Problems that become worse under time pressure, fatigue or environmental exposure
- Workarounds that have become accepted as normal
- Consequences extending beyond inconvenience into safety, quality, waste, delay or cost
Be careful not to reduce the evidence to a simple popularity contest. A problem can be infrequent but still important if the consequence is serious. Conversely, a frequent irritation may have little commercial value if users can resolve it easily and cheaply.
The objective is to understand the combination of frequency, severity and consequence.
Define the Problem Without Embedding a Solution
A well-framed opportunity should describe the user, the situation, the problem and the desired outcome. It should not quietly prescribe the product the team already wants to build.
A useful structure is:
[User] needs a better way to [complete a task or achieve an outcome] when [relevant situation or constraint], because [evidence-backed problem or consequence].
For example:
Maintenance technicians need a more reliable way to organise and access frequently used components while working in exposed outdoor locations, because current storage methods allow contamination and make it difficult to find parts while wearing gloves.
This is more useful than:
Maintenance technicians need a waterproof component organiser with oversized latches.
The first statement defines an opportunity. The second has already selected a solution, material characteristic and feature before alternative approaches have been explored.
The opportunity statement should be specific enough to direct further work while remaining open enough to support multiple design concepts.
Assess Whether the User Problem Matters Enough
A problem becomes more compelling when users experience a meaningful consequence and have a reason to change their current behaviour.
Ask:
- Who experiences the problem?
- How frequently does it occur?
- How severe is the effect?
- What happens if nothing changes?
- Does it cause lost time, waste, fatigue, risk, rework or poor performance?
- Are users actively trying to solve it?
- What do current workarounds cost?
- Who controls the purchasing decision?
- Would solving the problem create enough value to motivate change?
Pay particular attention to the difference between the user and the buyer. In commercial and industrial products, the person operating the equipment may experience the problem, while a manager, procurement team or business owner decides whether to pay for a solution.
A strong opportunity needs a persuasive value case for both the people who use the product and the people who approve the investment.
Examine Existing Products, Substitutes and Workarounds
A lack of direct competitors does not automatically mean you have found an open market. It may mean the problem is served by substitutes, managed through a manual process or not considered important enough to justify a dedicated product.
Review:
- Directly competing products
- Products adapted from another category
- Manual processes and improvised solutions
- The option of tolerating the problem
- Previous products that entered and left the market
- The reasons users retain their current approach
Ask what an alternative already does well, not only where it fails. Familiarity, low cost, availability and compatibility can make an imperfect solution difficult to replace.
The purpose of this review is not to prove that every existing option is poor. It is to understand whether there is room for a meaningfully better outcome.
Identify Product Opportunities with Commercial Potential
To identify product opportunities with genuine commercial potential, look beyond whether users like the idea. Determine whether solving the problem could create sufficient value to support a viable product and business case.
Consider:
- Who is likely to buy the product?
- Is the buyer also the user?
- What financial or operational value could the solution create?
- How much does the current problem cost in time, labour, waste, risk or lost output?
- How large and accessible is the potential market?
- How frequently would customers purchase, replace or upgrade the product?
- Which sales and distribution channels would be required?
- What price might the created value support?
- Could the likely selling price support development, manufacturing, distribution and support costs?
Expressions of interest are useful, but they are not the same as a commitment to purchase. People may agree that a problem is frustrating while remaining unwilling to pay enough to support a viable physical product.
The stronger evidence comes from existing expenditure, costly workarounds, active attempts to solve the problem, purchasing requests or a measurable financial consequence for the buyer.
Check Strategic Fit
A real user problem with commercial potential does not automatically make a suitable opportunity for your organisation.
Consider whether the opportunity aligns with:
- Your business strategy and intended market position
- Your brand and customer relationships
- Your technical knowledge and access to expertise
- Your manufacturing and supplier capabilities
- Your sales, distribution and support channels
- Your available capital and tolerance for risk
- Your broader product range and future roadmap
An opportunity may be attractive in isolation but unsuitable if it requires a completely unfamiliar route to market, unrealistic certification work or support capabilities the business does not possess.
Strategic fit should not be used to reject every unfamiliar opportunity. Instead, it should reveal which new capabilities, partnerships and investments would be required.
Consider Feasibility Before Committing to a Concept
Early feasibility is not detailed engineering. It is a structured attempt to identify obvious barriers, critical uncertainties and likely development demands before substantial money is committed.
For a physical product, preliminary questions may include:
- Can the required function be achieved with available technology?
- Are there significant size, weight, power or strength constraints?
- What materials and manufacturing processes may be suitable?
- Are critical components readily available?
- Could likely production volumes support the required processes?
- What standards, approvals or certifications may apply?
- Does existing intellectual property restrict the design space?
- Can the likely product cost support an acceptable selling price?
- Will the product be practical to assemble, service, package and distribute?
The goal is not to produce final answers. It is to expose assumptions that could overturn the opportunity.
If success depends on an unproven mechanism, aggressive cost target or difficult regulatory pathway, record that uncertainty clearly. The opportunity can still proceed, but the next stage should be designed to test the most important assumption first.
Account for the Full Investment Required
Product-development investment extends well beyond the cost of creating a few concept sketches or CAD models.
Depending on the product, the required commitment may include:
- User, market and competitor research
- Industrial design and product engineering
- Electronic, firmware or software development
- Proof-of-concept and functional prototypes
- Testing, validation and iterative redesign
- Standards research and compliance testing
- Patent, design registration or other intellectual property work
- Tooling and manufacturing setup
- Pilot production and quality assurance
- Packaging, freight and inventory
- Sales, marketing, distribution and after-sales support
A product opportunity may solve a real problem and still be unsuitable if the expected return cannot justify this complete investment.
Early estimates will contain uncertainty, but even an approximate view of the development pathway can reveal whether the prospective scale of the opportunity is proportionate to what will be required.
Compare Product Opportunities Using Consistent Criteria
When several opportunities appear promising, compare them using the same questions rather than supporting whichever idea has the most enthusiastic advocate.
Using consistent criteria makes it easier to identify product opportunities that combine meaningful user value with commercial potential, feasible development and an acceptable level of risk.
A practical opportunity assessment can consider:
- User significance: How important is the problem to the people experiencing it?
- Evidence strength: Is the opportunity based on repeated behaviour and credible evidence?
- Commercial potential: Is there a plausible customer, buyer and route to revenue?
- Competitive position: Can the outcome be meaningfully better than current alternatives?
- Strategic fit: Does the opportunity support the organisation’s direction and strengths?
- Technical feasibility: Is there a credible path towards a functional and reliable product?
- Manufacturing feasibility: Can the product be made at the expected volume, quality and cost?
- Investment requirement: What is likely to be required before the opportunity can generate a return?
- Risk and uncertainty: Which assumptions could make the opportunity fail?
- Learning value: Can the most important unknowns be tested without committing to the full program?
A score can help organise discussion, but it should not create false precision. A slightly higher total should not automatically determine the outcome when both assessments depend on uncertain assumptions.
Record the reasoning, evidence and confidence behind each assessment. A structured comparison is valuable because it exposes differences in assumptions and helps decision-makers understand where further investigation is needed.
Know the Warning Signs of a Weak Product Opportunity
Pause before committing when:
- The opportunity is built around a preferred solution rather than a verified problem.
- Evidence comes mainly from friends, colleagues or internal opinions.
- People describe the problem but show no motivation to change.
- The proposed benefit is a minor improvement over a cheap and familiar alternative.
- The buyer, budget or route to market is unclear.
- The required selling price is disconnected from the value created.
- Technical feasibility depends on several untested assumptions.
- Compliance, intellectual property or manufacturing constraints could fundamentally change the proposition.
- The opportunity does not fit the organisation’s capabilities or strategy.
- The team is using enthusiasm as a substitute for evidence.
A decision not to proceed is not a failure. Avoiding a weak opportunity before significant development begins can be one of the most valuable outcomes of discovery.
How to Identify Product Opportunities Worth Pursuing
When deciding whether to proceed, bring the evidence together and ask four final questions:
- Does a meaningful problem exist?
The problem should be supported by observed behaviour, recurring evidence or a measurable consequence, not simply an internal assumption. - Would solving the problem create sufficient value?
Users and buyers should have a credible reason to change from their current product, process or workaround. - Is there a realistic path to a viable product?
The technical, manufacturing, compliance and commercial challenges should appear manageable or capable of being investigated progressively. - Is the next investment justified by what can be learned?
The next stage should answer a critical question or reduce a material uncertainty without prematurely committing the entire development budget.
A product opportunity is worth pursuing when credible evidence supports a meaningful user problem, there is a plausible buyer and commercial case, a realistic technical and manufacturing pathway exists, and there is a strategic reason for your organisation to act.
The opportunity does not need to be free of risk. New product development always contains uncertainty. The question is whether the opportunity is strong enough, and the unknowns manageable enough, to justify the next investment decision.
That decision might be to conduct more user research, review relevant standards, investigate intellectual property, test a technical principle or develop several early concepts. It should not automatically be a commitment to complete product development.
Turn the Selected Opportunity into a Clear Product Brief
Once an opportunity has earned further investigation, document:
- The user and relevant use environment
- The problem and supporting evidence
- The consequence of leaving the problem unresolved
- Current alternatives and workarounds
- The intended user and commercial outcomes
- Known constraints
- Critical assumptions
- Questions that remain unanswered
- The evidence required for the next decision
This information provides a strong foundation for a product brief without locking the design team into a premature solution. Our guide to what makes a great product brief explains how purpose, context, user understanding, objectives, constraints and success measures can align the team before development progresses.
After concepts have been generated, the work changes. You are no longer assessing only whether the opportunity deserves attention. You are testing whether a proposed solution meets the need, is desirable to users and deserves further investment. Our guide on how to validate your product concept before investing big covers that next stage.
Choose the Problem Before Committing to the Product
Good product opportunities are rarely discovered through one flash of inspiration. They emerge through observation, careful questioning, evidence synthesis and disciplined comparison.
The most important early decision is not what the product should look like. It is whether the problem matters enough, creates enough value and offers a credible enough path forward to justify the time and money required to solve it.
Whistle Design Group helps founders and established product teams identify product opportunities, clarify requirements and build a practical path from discovery through design, engineering, validation and manufacture. If you need to determine whether an opportunity is ready for development, contact Whistle Design Group to discuss the problem, the evidence and the decisions that need to come next.