Expiration Dates for Exploration Phases in Product Development
Updated
Knowledge on this page was mainly distilled from Prioritize Feature Requests Before You Know Your Customer.
The subtlest trap in early-stage product development catches builders who follow every rule of disciplined experimentation. Each shipped probe earns a thank-you, fills another record, costs only a few reversible days. Every probe is defensible on its own. Together, they can become a very disciplined way of never deciding anything.
Why Comfort Becomes the Enemy
The reversibility that makes probes safe also makes them comfortable. Shipping small experiments produces a steady stream of positive feedback and observable data without requiring commitment to a customer segment. Over time, the research phase stops serving its purpose and starts becoming a personality. Builders mistake motion for progress because every individual step looks responsible.
Count Probes, Not Months
The exploration phase needs its own expiration date, not just each feature within it. The article's recommendation is to count it in probes rather than months: pick a number of filled probe records before you start (ten is plenty), and when you hit it, name the segment you believe in most and act as if you are right.
Measuring in probes rather than calendar time has a practical advantage. A month of probing at different speeds produces different amounts of evidence. A fixed number of completed experiments guarantees a minimum evidence base before the decision point arrives.
When the Records Refuse to Converge
Sometimes probes keep surging but the adopters never look alike. No segment clusters around the product. This is not a failure of the method. It is a verdict: no segment is waiting to be discovered, and the customer will have to be chosen rather than found. Choosing is scarier than finding. It is also a decision you can now make with seven lines of evidence per option, which is more than most builders ever get to hold.
After the segment is named, the product gets smaller. Requests from inside the segment point at the core product. Requests from outside it get a polite no, delivered with the confidence that comes from evidence. Then comes the step almost nobody takes: removing the probes that served segments you decided not to pursue. The generosity phase has a purpose, and the purpose is its own ending.
Q&A
Why count probes instead of setting a calendar deadline?
Calendar deadlines reward speed, not learning. A team that ships ten well-documented probes in six weeks has a stronger evidence base than one that ships three in six months. Counting completed probe records guarantees a minimum amount of structured evidence before the commitment decision.
What does 'act as if you are right' mean in practice?
It means stop probing and start prioritizing. Requests from the chosen segment get conventional prioritization treatment (scoring by urgency, retention impact, revenue potential). Requests from outside the segment get declined. Features that served non-chosen segments get reviewed for removal.
Is choosing a customer segment truly irreversible?
Not strictly, but the point is to create a forcing function. You can revisit the decision if strong new evidence appears, but treating the choice as real is what breaks the cycle of comfortable exploration. The probe records you accumulated give you a rational basis for the choice, which most builders never have.