Product Discovery Workshop: Agenda, Deliverables and Costs

Most failed hardware products were engineered flawlessly - they simply answered a question nobody was asking. The product discovery process exists to find that out in weeks and for thousands of dollars, instead of in a year and for hundreds of thousands. It ends with a concept you can cost, build and sell, plus written evidence of why it is the right one.

Discovery starts with people, not CAD. Fifteen to twenty structured interviews with the actual buyer and the actual user surface the workarounds they already use, what they pay today, and which frustrations they will not tolerate.

When a musician told us their gear failed on the third night of a tour, that single detail reframed the whole product from a feature question into a durability question. Pair interviews with observation - what people do rarely matches what they say.

Research output becomes a written problem statement: who has the problem, how often, what it costs them, and what a good outcome looks like in measurable terms. This is also where you set the constraints that will govern every later decision - target price, size envelope, regulatory environment, distribution channel.

A frame that says touring musicians need a mic mount that survives 200 setups a year and retails under $80 is engineerable. A better mic mount is not.

The last phase makes the surviving concept accountable to arithmetic: a preliminary bill of materials, a manufacturing route with realistic tooling costs, a landed cost estimate, a retail price with channel margin, and a break-even quantity. If those numbers do not close, the time to know is now - either the concept changes, the price changes, or the program stops before the expensive part begins.

Related reading: our product discovery service and how to size a market with TAM, SAM and SOM.

Product discovery is the structured phase before engineering in which a team researches customers, frames the problem, generates and screens concepts, and validates feasibility and business viability - producing a selected concept with a preliminary cost model.

A focused hardware discovery engagement runs six to ten weeks. Simple accessories can compress to three or four weeks; regulated or multi-stakeholder products often need twelve.

Most discovery engagements fall between $25,000 and $70,000 depending on research depth and the number of concepts carried into feasibility - typically 5 to 10 percent of the total development budget.

Discovery fails quietly when interviews collect enthusiasm instead of behaviour. People are generous about hypothetical products and unreliable about hypothetical purchases. Structure the conversation around what the person did last time they faced the problem — what they bought, what it cost, what they improvised — and the answers become usable evidence.

Fifteen to twenty interviews with the actual buyer and the actual user — often different people — is usually enough to reach saturation, the point where new conversations stop producing new problem statements. If interview twenty is still surprising you, the segment is too broad.

Top-down market numbers pulled from industry reports are almost never decision-grade. Build the estimate from the bottom: a countable number of buyers, a defensible attach rate, a price you have evidence for, and a replacement cycle. Then state the assumption that, if wrong, breaks the case — because that is the assumption discovery should test next.

Concept screening degenerates into advocacy unless the criteria and their weights are fixed before scoring. Score against the reference — usually the current workaround — and require the winning concept to beat it decisively on the two criteria you weighted highest, not to win narrowly on the average.

The purpose of discovery is not to approve the product; it is to make the decision cheap. Define the kill criteria in writing at kickoff, when nobody is emotionally invested, and hold to them. A discovery that never kills anything is a formality, and the organisation learns to treat it as one.

The most expensive discovery failure is a good report that changes nothing because the decision had already been made. The second most expensive is research done by the people who will build the product, since it is difficult to disprove a concept you have already begun designing. Separate the roles, or at least separate the sessions.

Partially. Feasibility spikes and long-lead technical de-risking can run alongside customer research, and often should. What cannot run in parallel is detailed design, because it converts open questions into sunk cost before the evidence arrives.

When two or three consecutive interviews produce no new problem statements, no new workarounds and no new purchase criteria. That saturation point usually arrives between interview twelve and twenty for a well-defined segment.

Access difficulty is itself a finding — it usually predicts an equally difficult sales motion. Route around it with distributors, trade groups, service technicians and recruitment panels, but treat a segment you cannot reach for research as a segment you cannot reach for revenue.

Yes, and it is often cheaper and more accurate, because you can interview real customers about real behaviour and validate against sales and warranty data instead of estimates.

Work with LA NPDT: if you are moving from here to execution, start with our our product development process or talk to us about end-to-end product development.