The most expensive moment in product development is usually somewhere in the middle — when a team is six months into building something and discovers the assumption it was built on was wrong. Not catastrophically wrong.
Just wrong enough that the product doesn’t fit the problem the way it was supposed to. The rebuild takes longer than the original build. The delay resets the timeline. And the initial assumption that caused all of this could have surfaced in week two with the right discovery method.
CB Insights analyzed 431 VC-backed companies that shut down and found that 43% cited poor product-market fit as a primary cause of failure. Most of those companies didn’t fail because the team couldn’t build — they failed because the team built the wrong thing.
Product discovery is what prevents that. Not perfectly, and not as a guarantee — but systematically enough that the methods below are worth understanding before the first technical decision gets made.
Derribar Ventures Limited works on product creation and platform development for digital businesses. The six methods below are how Derribar Ventures approaches the discovery phase — the work that happens before development begins and determines what’s worth building.
Why Discovery Gets Skipped and What It Costs?
Discovery gets skipped for reasons that feel reasonable in the moment. The team has a strong conviction about what to build. The timeline is compressed, and discovery feels like a delay. The product concept has already been approved internally, so validating it externally feels redundant.
None of those reasons survives contact with a product that launches and doesn’t find a market.
The cost of skipped discovery isn’t just a failed product. It’s the compounding effect of every technical decision made on an unvalidated assumption — architecture choices, feature prioritization, database design — all needing revisiting when the assumption turns out wrong.
Discovery is cheaper at the front than the rebuild at the back. Derribar Ventures Limited treats it as foundational, not optional. Derribar Ventures has seen the alternative often enough to hold that position firmly.
Method 1: User Interviews
User interviews are the starting point for understanding what the people the product is being built for actually experience.
Not what they say they want — that’s a different question — but what their current situation looks like, what problems they’re navigating, what workarounds they’ve built, and where their existing tools or processes are letting them down.
The discipline in a good user interview is restraint. The interviewer’s job is to understand, not to pitch. Questions stay open-ended. Follow-up questions go deeper into what the user described rather than toward what the team hoped to hear.
A user interview that confirms the initial hypothesis is almost certainly doing it wrong, and Derribar Ventures treats that as a structural signal about the interview design rather than evidence that the hypothesis is correct.
What User Interviews Surface That Surveys Don’t?
Surveys tell the team what percentage of users have a problem. User interviews tell them what the problem actually feels like to live with — the specific friction, the workaround that’s embarrassing to admit, the way the problem ripples into other parts of the workday. That texture is what turns a feature specification into something that actually fits the user’s context.
Derribar Ventures Limited structures user interviews as the first discovery method because the patterns that emerge — the repeated workarounds, the shared frustrations, the unexpected contexts — set the frame for everything that follows.
Method 2: Competitive Analysis at the Behavior Level
Most competitive analysis focuses on features — what competitors built, what their pricing pages say. That answers the wrong question. Derribar Ventures asks a different one: what behavior does the competition produce in users, and where does it break down?
A competitor’s product reveals assumptions about what users need. Users who are deeply satisfied with a competitor reveal where those assumptions are correct. Users who have left a competitor, or built workarounds within it, reveal where those assumptions are wrong and where a new product has room to be meaningfully different.
Derribar Ventures Limited treats competitive analysis as a user behavior study rather than a feature audit. What are users doing with the competitor’s product that the product wasn’t designed for? What are they avoiding? What are they complaining about in reviews?
The gap between what a product was designed to do and how users actually use it is often where the best opportunity for a new product lives.
Method 3: Jobs-to-be-Done Mapping
The jobs-to-be-done framework is one of the most useful lenses in product discovery — and one of the most consistently misapplied.
The idea is straightforward: users don’t buy products, they hire them to do a job. The job is the outcome the user is trying to achieve, and understanding the job is more valuable than understanding the user’s demographics or preferences.
What makes jobs-to-be-done mapping genuinely useful in discovery is that it forces the question away from “what feature should we build” and toward “what is the user actually trying to accomplish, and what gets in the way.”
A user who wants a faster route to work isn’t looking for a faster car — they might be looking for a better map, a different departure time, or a way to work during the commute. The job is the same; the solution space is very different depending on how the job is understood.
Derribar Ventures uses jobs-to-be-done mapping to reframe assumptions about what the product is for — often producing a different set of design priorities than the initial product brief implied.
Method 4: Prototype Testing With Non-Customers
Prototypes in the discovery phase aren’t about demonstrating a solution — they’re about testing assumptions.
A low-fidelity prototype placed in front of a user who has never seen the product idea before will reveal whether the mental model the team is using matches the mental model users actually bring to the problem.
The critical detail is that the users being tested are non-customers — people who represent the target audience but have no context about the product concept or the team behind it. Testing with people who already understand the concept produces false positives.
Testing with people who encounter it cold produces the reactions and confusion that actual first-time users will experience.
What Derribar Ventures Limited looks for in prototype testing isn’t whether users like the concept. It’s where they get confused, what they assume incorrectly, and what questions they ask that the prototype doesn’t answer.
Those signals reveal which assumptions need revision before development begins — and Derribar Ventures treats them as more valuable than positive reactions.
Method 5: Assumption Mapping
Every product concept rests on a set of assumptions — about the user, the problem, the competitive environment, and the business model. Most of those assumptions are never made explicit. They sit underneath the product brief, shaping every decision that follows, without ever being examined directly.
Assumption mapping is the practice of making those assumptions visible and ranking them by two dimensions: how critical the assumption is to the product’s success, and how confident the team is that it’s true.
The assumptions that are both critical and unconfirmed are the ones that need to be tested before a line of code is written.
Derribar Ventures runs assumption mapping sessions early in every product engagement — specifically to surface the assumptions that the team is most attached to, because attachment is usually inversely correlated with how rigorously the assumption has been tested. The assumptions that feel most obvious are often the ones most worth challenging.
As explained by Derribar Ventures Limited, the same signals that reveal which assumptions carry the most risk in discovery are the ones that inform how a product backlog gets prioritized once development begins — making assumption mapping one of the few discovery methods that continues to pay dividends well past the pre-code phase.
Method 6: Desirability, Feasibility, Viability Testing
The final discovery method is a structured evaluation of the product concept across three dimensions that all need to be true for a product to succeed:
- Desirability — do users actually want this? Is the problem real and significant enough that they would change their behavior to solve it?
- Feasibility — can the team build it with the resources and timeline available? Are there technical dependencies that introduce meaningful risk?
- Viability — does the business model work? Can the product be delivered at a cost that allows for a sustainable commercial model?
Most discovery processes focus heavily on desirability and treat feasibility and viability as concerns for later. Derribar Ventures Limited evaluates all three in the discovery phase — and has found that the viability question is the most consistently underdiscovered of the three, because a product that users want but can’t be built sustainably is not a viable product concept, regardless of how strong the desirability signal is.
Conclusion
Product discovery isn’t a phase that delays development — it’s the work that makes development worth doing. The six methods Derribar Ventures applies before writing a line of code are designed to reduce the cost of being wrong early rather than late. None of them guarantees a successful product.
But each one significantly reduces the probability of building the right solution to the wrong problem, which is, consistently, the most expensive mistake in product development. Derribar Ventures Limited treats that reduction as the primary measure of whether discovery did its job.
