Every idea rests on assumptions
An idea can sound persuasive because its pieces fit together: a group of people has a problem, a proposed solution seems helpful, and there is a way to deliver it. Each piece, though, may contain an untested belief. People might not experience the problem as often as expected. They might prefer their current workaround. The solution might help but be too difficult to use or sustain.
The goal is not to eliminate all uncertainty before starting. It is to find the assumption that matters most to the next decision. Testing a minor detail can create a comforting sense of progress while leaving the idea’s central weakness untouched. A useful test asks a more demanding question: What would we need to learn to decide whether to continue, change direction, or stop?
Find the belief that could change your plans
Write the idea as a short chain of claims. For a proposed neighborhood tool-sharing service, the chain might be: residents sometimes need tools they do not own; they are willing to borrow from nearby people; lenders are comfortable making tools available; and the service can coordinate exchanges without excessive effort. This exercise turns a broad concept into assumptions that can be examined separately.
Next, consider each claim on two dimensions: how uncertain is it, and how much would it matter if it were false? The riskiest assumption is often one with both high uncertainty and high consequences. A question about the color of the service’s logo may be uncertain, but its answer probably would not determine whether the service should exist. Willingness to lend tools could be decisive if the entire model depends on neighbors supplying them.
Be careful not to confuse what is easiest to test with what is most important to know. Also distinguish evidence from confidence. A team may feel certain that people want an idea because friends responded enthusiastically. That reaction is worth noting, but it may not tell the team whether people will make room for the idea in their routines.
Turn the assumption into a testable question
A vague assumption such as “people will use this” is difficult to test. Make it specific about who, what they would do, and under what conditions. For example: “Residents who occasionally need household tools will request a loan when offered a simple way to see what is available nearby.” The wording should point toward observable behavior rather than approval of the concept.
Before collecting responses, decide what result would support the assumption, what would weaken it, and what remains ambiguous. You do not need a universal numerical threshold; the appropriate standard depends on the size of the decision and the cost of being wrong. But setting a standard in advance makes it harder to reinterpret any outcome as success. Write down the decision the test is meant to inform, such as whether to try a small pilot or revise the intended audience.
Run the smallest test that can teach you something useful
Choose a test that resembles the behavior you care about without building the whole idea. To explore demand for tool sharing, you might invite a small group of relevant residents to request a tool from a real, limited list. To explore supply, you could separately ask potential lenders to list one tool they would actually make available under clearly stated conditions. These tests reveal different things; interest from borrowers does not prove that lenders will participate.
Interviews can help explain why people act as they do, especially when questions ask about past situations rather than hypothetical enthusiasm. A prototype can reveal whether people understand how an idea works. An invitation to take a concrete step can show more commitment than a general expression of approval. Match the method to the assumption, and avoid treating one type of evidence as proof of every part of the idea.
Keep the test honest and proportionate. Tell participants what is being offered and avoid implying that an unfinished service is fully available. If the test involves personal information, collect only what is needed and handle it with care. A small test is most valuable when it creates a realistic opportunity to act, not when it pressures people into saying yes.
Use the result to decide what comes next
After the test, compare what happened with the standard you set beforehand. Look beyond a simple yes-or-no verdict. Did people understand the offer? Did the intended participants respond, or only people outside the target group? Did they take the relevant action, or merely say that the idea sounded good? A disappointing result might challenge the core assumption, but it might also expose a confusing invitation or an inconvenient test setting.
Decide whether the evidence supports another step, a revision, or a pause. Record what you expected, what you observed, and what you still do not know. Then identify the next riskiest assumption. This process is not about proving that the original idea was right. It is about making the next investment of time, attention, or resources with a clearer view of what the idea requires.
