Desirability, Feasibility, Viability: The Validation Triangle

Desirability, feasibility, and viability are the three lenses every strong idea must survive: desirability asks whether people actually want it, feasibility asks whether you can build and deliver it, and viability asks whether it can sustain a business. An idea earns the right to exist only where all three overlap — wanted, buildable, and profitable at the same time.

Quick Answer: Validate in risk order, not fixed order. Map your assumptions, find the lens most likely to kill the idea, and test that one first — usually desirability, but not always. Spend real money on feasibility and viability only after demand looks real.

Why All Three Lenses Must Pass Before You Commit

An idea has to clear all three lenses because each one guards against a different way ventures die. Desirability guards against building something nobody wants. Feasibility guards against promising something you can't reliably deliver. Viability guards against selling something that loses money on every unit. Pass two and fail one, and the idea still collapses — just later, and far more expensively.

The framework comes from design thinking, where innovation is described as living at the intersection of what people desire, what is technically feasible, and what is commercially viable. Tim Brown of the design firm IDEO popularized this framing in his book Change by Design. The point of the three-circle picture is not that each circle matters in isolation — it's that the only interesting place is the small overlap in the middle.

That overlap is deceptively small. Most ideas are strong on one or two lenses and quietly fatal on the third. A feature your engineers love to build (feasible) and that would print money if anyone used it (viable) is still dead if customers shrug (not desirable). This is why intrapreneurs inside larger companies burn budgets so predictably — internal ideas tend to be over-tested for feasibility and under-tested for desirability.

There is also a compounding cost to catching a failed lens late. A desirability problem you spot in a week of interviews costs a week; the same problem discovered after a full build, a launch, and a quarter of flat adoption costs the build, the launch, the quarter, and the credibility you spend explaining it. The lenses don't just tell you whether an idea works — tested in the right order, they tell you as early and as cheaply as the evidence allows.

The discipline the triangle imposes is sequencing. You don't test all three at once with equal effort; you find the lens most likely to be false and attack it first. That order-of-operations mindset sits at the heart of any structured startup idea validation workflow, and it's what turns a vague "let's do some research" into a series of cheap, decisive experiments.

Desirability, Feasibility, and Viability Defined: What Each Lens Tests and the Risk It Hides

Each lens answers one core question and hides one specific failure mode you won't see until it's expensive. The table below maps all three side by side so you can name the exact risk you're carrying on any given idea.

The takeaway: desirability and viability are about the outside world — do people want it, and will the economics work — while feasibility is largely about the inside — can your team pull it off. Founders and intrapreneurs consistently over-weight the internal question because it's the one they can answer without leaving the building. The two external lenses are where most real risk hides, and they're the ones you can't answer from your desk.

The Desirability Lens: Proving People Actually Want It

Desirability tests whether real customers want your solution enough to act, not just to nod politely in an interview. It is almost always the riskiest lens, because it depends on other people's behavior — the one thing you cannot will into existence. A "yes, I'd totally use that" is not desirability evidence; a signup, a deposit, or a returned-to-the-product usage pattern is.

The trap is that desirability feels like the easy lens to check. You talk to a few prospective customers, they're encouraging, and you move on. But stated preference and revealed preference diverge constantly — people are polite, and they imagine idealized versions of themselves. The whole point of tools like the Value Proposition Canvas, laid out in Osterwalder and colleagues' Value Proposition Design, is to force specificity: which exact customer job, pain, or gain does this address, and how do we know it matters?

To test desirability without building the full product, lean on experiments that demand a costly signal from the customer:

• Landing-page or "fake door" tests that ask people to sign up, join a waitlist, or click "buy" before the thing exists.
• Concierge and Wizard-of-Oz tests where you deliver the value manually behind the scenes to see if anyone actually wants it delivered.
• Pre-sales or letters of intent, especially for B2B and internal ideas, where a signature or a small deposit is worth a hundred nods.
• Interviews focused on past behavior, asking what people already do and have already paid for, not what they say they might do.

The evidence that counts is behavioral and, ideally, costly to fake. When someone gives up money, time, reputation, or contact details, they're telling you something an opinion never could. Weak desirability signals are the single most common reason a technically excellent build never finds a market.

The Feasibility Lens: Proving You Can Build and Deliver It

Feasibility tests whether you can actually build, deliver, and operate the solution with the capabilities, technology, and partners available to you. It's the lens teams are most comfortable with, because it lives inside the organization — you can investigate it without a single customer. That comfort is exactly why feasibility is easy to over-test and mistime.

Feasibility is not one question but a stack of them. There's technical feasibility (can the core technology do this?), operational feasibility (can we run it day to day at quality?), and organizational feasibility (do we have the skills, and will the company actually let us?). For intrapreneurs, that last one is often the real blocker: the technology works fine, but the compliance, procurement, or platform team makes delivery impractical. Name which layer you're actually worried about before you start testing.

The right feasibility experiments are narrow and fast, aimed only at the parts you genuinely doubt:

• Technical spikes — a throwaway build of the single riskiest technical component, not the whole system.
• Prototypes and proofs of concept that answer "can this even work?" before "is this polished?"
• Vendor and dependency checks confirming that the API, dataset, supplier, or integration you're counting on actually exists and performs.
• Operational dry-runs that walk one real transaction end to end to expose the hand-offs that break at scale.

The key discipline is not to fully solve feasibility before you've confirmed desirability. Building the hard thing is satisfying, and it feels like progress, but a beautifully engineered solution to a problem no one has is the most expensive kind of failure. Test just enough feasibility to know the idea isn't impossible — then get back to demand.

The Viability Lens: Proving It Can Sustain a Business

Viability tests whether the idea can support itself financially over time — whether the money coming in reliably exceeds the money going out, at a scale that's worth the effort. It's the lens that separates a beloved product from a durable business. Plenty of things people want and you can build still shouldn't be built, because the economics never close.

Viability lives in the relationship between what customers will pay and what it costs you to serve them, repeatedly. That means testing price as seriously as you test the product: what people say they'd pay is notoriously unreliable, so you look for real pricing signals — actual purchases, plan choices, renewal behavior. A structured viability test built for founders walks through pricing experiments, cost structure, and the margin questions that decide whether an idea can stand on its own.

For a corporate intrapreneur, viability carries an extra dimension: strategic fit. An idea can be independently profitable and still fail the internal viability test if it cannibalizes a bigger line of business, can't reach the scale your leadership cares about, or doesn't align with where the company is heading. "Would this be a good standalone business?" and "Is this a good use of our company's resources?" are different questions, and both have to pass.

Useful viability experiments stay lightweight until the other lenses hold:

• Price sensitivity and packaging tests that expose real prices to real prospects and watch what they choose.
• Cost modeling of the delivery path, so you know your rough cost to serve before you scale, not after.
• Channel and acquisition tests to check whether you can reach customers at a cost the economics can bear.
• Repeatability checks — evidence that the first sale wasn't a fluke and the second, third, and tenth look similar.

Viability is usually the last lens you invest heavily in, because pricing and cost structure only matter once you've confirmed people want the thing and you can build it. But "last" is not "optional" — an idea that skips viability grows into a business that loses money faster the more it succeeds.

Which Lens to Validate First, by Idea Type

The lens you validate first should be the one most likely to be false for your specific idea — not a fixed sequence you apply to everything. Desirability is the default starting point because demand risk is so common, but idea type shifts the answer. The table below shows where the riskiest assumption usually sits for four common patterns.

The takeaway: sequence follows risk, not habit. The reliable way to find your starting lens is assumption mapping that surfaces the riskiest assumption first — list everything that must be true for the idea to work, then sort by how uncertain and how fatal each assumption is. Whatever lands in the "most uncertain, most fatal" corner is where you point your first experiment, regardless of which lens it belongs to. Alexander Osterwalder and David Bland's Testing Business Ideas organizes an entire experiment library around exactly this desirability-feasibility-viability structure.

Common Mistakes: Building Before You've Tested Desirability

The most common and most expensive mistake is inverting the order — investing heavily in feasibility (building the thing) before confirming desirability (that anyone wants it). Teams do this because building is concrete and testing demand feels squishy, but it means the largest costs get committed against the least-validated assumption. By the time the polished product ships to silence, the money is already spent.

A cluster of related errors reinforces the same trap:

• Treating opinions as evidence. "People said they loved it" is desirability theater; a waitlist signup or a pre-order is desirability data.
• Over-engineering feasibility early. Solving the hardest technical problem beautifully before you know the market wants it is expensive procrastination dressed as progress.
• Deferring viability until launch. Discovering your cost to serve exceeds your price after you scale is a discovery you can make on a spreadsheet months earlier.
• Testing all three lenses with equal effort. Equal effort ignores that one lens almost always carries most of the risk — flat testing wastes the budget you should have aimed.

For intrapreneurs specifically, watch for the internal-mandate mirage: because leadership approved the budget and engineering confirmed feasibility, the idea feels validated. But approval and buildability say nothing about whether the end users — customers or your own colleagues — will actually adopt it. Sponsorship is not desirability, and the graveyard of internal tools is full of feasible, funded products no one chose to use.

The fix in every case is the same discipline the triangle exists to enforce: identify the lens most likely to be false, test it with the cheapest experiment that would produce real evidence, and only then spend more. Lightweight validation platforms — including Edmired — exist to make that first cheap test faster to run, but the thinking matters more than any tool.

Key Takeaways

• All three lenses gate survival, not just quality. An idea that is desirable and feasible but not viable — or any other two-out-of-three — still fails; the only durable position is the overlap where wanted, buildable, and profitable all hold at once.
• Desirability is usually the riskiest lens. It depends on other people's behavior, which you cannot control, so a costly signal like a signup or deposit beats any amount of polite enthusiasm in an interview.
• Feasibility is the lens teams over-test. Because it lives inside the organization and feels like progress, it tempts you to build before you've confirmed anyone wants the thing — test just enough to know it's possible, then stop.
• Viability is tested last but never skipped. Pricing and cost structure only matter once demand and buildability hold, yet an idea that ignores unit economics grows into a business that loses money faster as it succeeds.
• Sequence follows risk, not habit. Map your assumptions, find the one that is both most uncertain and most fatal, and test whichever lens it belongs to first — often desirability, but feasibility for deep-tech and viability for thin-margin models.
• For intrapreneurs, approval is not validation. A funded, feasible, leadership-backed idea can still fail desirability when the actual end users won't adopt it — sponsorship and buildability say nothing about demand.

Frequently Asked Questions

Which lens matters most: desirability, feasibility, or viability?

No single lens matters most in the abstract — the idea must pass all three to survive. In practice, desirability is usually the riskiest and the one to test first, because demand depends on other people's behavior and is the most common reason ideas fail. But the lens that "matters most" for your idea is whichever one is most likely to be false, which is why you map assumptions before choosing.

Can an idea be desirable but not viable?

Yes, and it's extremely common. People can genuinely want something you're fully able to build, yet the economics never work — the cost to serve each customer exceeds what they'll pay, or you can't acquire customers cheaply enough to profit. Many beloved products are commercial failures for exactly this reason. Desirability confirms demand; only the viability lens confirms that demand can pay for itself.

What's the difference between feasibility and viability?

Feasibility asks whether you can build and deliver the solution — a capability and technology question, mostly internal to your team. Viability asks whether the result can sustain itself financially — a business-model question about pricing, cost, and margin over time. An idea can be perfectly feasible (you can build it) and completely unviable (it loses money on every sale), so the two lenses have to be tested separately.

Who created the desirability, feasibility, viability framework?

The three-lens model is rooted in human-centered design and design thinking, and was popularized by the design firm IDEO — Tim Brown describes innovation as the intersection of desirability, feasibility, and viability in his book Change by Design. It was later adapted for structured business-idea testing in Testing Business Ideas by David Bland and Alexander Osterwalder, which organizes experiments around the same three categories of risk.

How do I test desirability without building the product?

Use experiments that demand a costly signal before the product exists. Landing-page or "fake door" tests measure whether people will sign up or click to buy; concierge and Wizard-of-Oz tests deliver the value manually to see if anyone wants it; pre-sales and letters of intent — especially for B2B — turn interest into commitment. The rule is to look for behavior people pay for with money, time, or reputation, not stated opinions.