Why a promising idea needs three tests
New ideas often begin with an observation: a task takes too long, a service is confusing or an existing product leaves someone out. Spotting a problem matters, but it does not tell you whether a proposed solution will work. A useful way to examine the idea is through three questions: Is it desirable to the people it aims to serve? Is it feasible to deliver? Is it viable to sustain?
These questions are connected, but they are not interchangeable. People might love the idea of a personalized service that would be too difficult to provide reliably. A team might build a clever tool that solves a problem few people consider important. A product could meet a real need and be technically achievable, yet cost more to operate than its supporters can reasonably fund. The three tests help reveal those differences before a team commits heavily to one approach.
Desirability: Does it solve a problem people care about?
Desirability concerns the people affected by an idea. Who encounters the problem, what do they do about it now and what would make a different solution worth trying? The answer is not always a request for a new product. Someone may need a clearer explanation, fewer steps or more confidence that a service will work as expected.
To investigate desirability, talk with potential users about specific experiences rather than asking whether they like a proposed idea. Ask them to describe the last time the problem occurred, how they handled it and what was frustrating about the outcome. Observation can add context: a person may forget a step in an interview but encounter it every time they complete a task. A simple sketch or mock-up can then show whether the proposed approach makes sense to them.
Expressions of interest are useful clues, not proof of demand. It is easy to approve of an idea in conversation without changing a habit to use it. Look for a meaningful next action, such as choosing to try a prototype, making time to learn a new process or explaining what they would give up to adopt it. Include people who may face different constraints; an idea that suits one group may create barriers for another.
Feasibility: Can you deliver it reliably?
Feasibility asks what it would take to turn the idea into a dependable experience. That includes the necessary skills, materials, technology, processes and access to partners. It also includes less visible work: training staff, handling exceptions, maintaining quality and helping people when something goes wrong.
A small prototype can test a specific uncertainty without pretending to be a finished product. For example, a team considering a service that summarizes complex documents might first test whether its proposed workflow produces clear, accurate summaries on a limited set of examples. If a human has to correct every result, that finding does not necessarily end the idea. It may point toward a narrower use case or a service designed with human review from the start.
Define the conditions under which the idea must work. A process that succeeds with a few willing participants may struggle when requests arrive in different formats or demand increases. Write down the assumptions that matter most, then design tests that could show where those assumptions fail. The aim is not to prove that every obstacle has been solved; it is to understand which obstacles are manageable and which require a different approach.
Viability: Can the idea keep delivering value?
Viability looks beyond the first successful trial. What resources will the idea require over time, and where will those resources come from? For a business, this may involve pricing, operating costs and repeat purchases. For a public or community service, it may involve a continuing budget, organizational support or a sustainable volunteer workload. Viability need not mean maximizing profit, but it does mean having a credible way to continue delivering the promised benefit.
Consider incentives alongside costs. The people who use an innovation, pay for it, maintain it and approve it may be different. If one group gains the benefit while another takes on work it cannot sustain, adoption may stall. Map those roles and ask what each group needs to participate. A rough estimate of recurring effort can be more informative at this stage than a detailed forecast built on uncertain assumptions.
Use the tests as a learning loop
Start by stating the idea in one sentence and listing what must be true for it to succeed. Sort those assumptions under desirability, feasibility and viability. Then choose the assumption that is both important and uncertain, and find a modest way to test it. An interview, a paper prototype, a limited trial or a basic cost outline may each answer a different question.
The tests are not three boxes to tick once. Evidence from one can change the others: a simpler version may be easier to deliver but less useful; a more appealing version may require a different funding model. Revisit the idea as you learn, and be willing to narrow it, redesign it or set it aside. A strong innovation is not merely exciting at first glance. It offers value people recognize, can be delivered in practice and has a workable path to keep going.
