Liking an idea is not needing the solution

Imagine an app for booking home services. Ten friends say it is a good idea. That shows enthusiasm, but not whether someone can find an available professional, accept the price, and complete a booking. The first test should approach that real decision without requiring the whole product.

Ask how the person solved the problem last time, what took time, and what failed. A concrete account usually offers more useful clues than “Would you use this app?” Also notice who does not face the problem; you do not need to convince everyone to serve a defined group well.

Write an assumption that can be disproved

“People want convenience” is too vague. A testable assumption might be: “In a two-week pilot, five of ten participants with this need will complete a booking through the proposed process.” That number illustrates a decision made in advance, not a universal benchmark. Choose the threshold for your risk and context.

Decide beforehand what would make you continue, change the offer, or stop. If every result confirms the idea, the test is not reducing uncertainty. Record limitations: ten participants do not represent an entire market, and recruiting friends may hide trust or acquisition problems.

The smallest test that answers the question

A simple form and manual follow-up can test booking demand and coordination. A prototype can test whether the interface is understood. These are different experiments: understanding a screen does not prove someone will buy. Choose the instrument based on the question you need answered.

Explain what is experimental, collect only necessary data, and set response expectations. Manual work helps uncover exceptions before automation. Turn what you learn into requirements: who does what, what information is missing, and where people give up.

One page before one line of code

Write down the audience, observed problem, riskiest assumption, test, duration, and decision criteria. Ask an outsider to read that page. If you cannot explain what the result will teach you, simplify the experiment. Your first valuable delivery may be a better decision about what deserves to be built.

Sources & further reading

Sources accessed October 24, 2026. Numerical examples and scenarios are illustrative.

Ready to put this knowledge into practice?

We can work together on your team’s challenge or your next project.

Talk to Calembe ↗