• Home
  • Blog
  • Desirability, Feasibility, and Viability

Desirability, Feasibility, and Viability

Alex Mika
Written by Alex Mika
Juri Vasylenko
Reviewed by Juri Vasylenko
null

Strong product ideas need more than excitement. A concept can sound compelling in a workshop and still fail once it meets real users, technical limits, or commercial pressure. Desirability, feasibility, and viability framework — also known as the “Three Lenses of Innovation” — gives teams a practical way to test all three conditions before committing time, money, and attention.

It asks three direct questions.

  1. Do people want this?
  2. Can we build and support it?
  3. Can it create lasting value for the business?

The strongest products sit where those answers overlap, turning an attractive idea into something people will adopt, teams can deliver, and organizations can sustain.

For brand-led businesses, this balance carries particular weight because every product decision shapes what the brand promises and whether customers believe it. A strong concept gives the brand something credible to stand behind, while a weak one can expose a gap between what the company says and what the experience actually delivers.

Desirability, Feasibility, and Viability Explained

Desirability, feasibility, and viability is a decision framework for examining an idea from user, technical, and business perspectives. It gives cross-functional teams a shared language for deciding whether a concept should move forward, change shape, or stop.

Desirability measures whether the idea solves a meaningful problem for a defined group of people. Feasibility tests whether the organization has the technology, skills, time, budget, and operating capacity to deliver it well. Viability asks whether the idea can support revenue, strategic growth, market positioning, or another clear business outcome.

Each dimension answers a different type of risk, and together they reveal whether the concept is balanced. Demand may be strong while delivery is unrealistic, or a technically elegant solution may address no urgent customer need. A commercially attractive concept may also fail because the experience creates too much friction or asks users to change their behavior without enough incentive.

By looking at all three dimensions together, the framework moves discussion away from personal preference and toward evidence. The outcome may be approval, refinement, a narrower scope, or rejection. Each can be a good decision when it happens early enough to protect resources and improve the quality of the final product.

Why the Framework Matters

Product failure often begins with an idea that performs well in one dimension and poorly in the others. The imbalance may stay hidden during early presentations because each specialist sees the concept through a familiar lens.

A design team may champion a beautiful interaction that depends on data the company can’t access. An engineering team may produce an impressive system that customers do not understand or value. A commercial team may push an offer with attractive margins while overlooking the friction it creates for users. In every case, one strong argument masks a larger weakness.

Three examples showing risks when design, engineering or commercial priorities dominate a product decision.

Strong individual arguments can hide weaknesses elsewhere in the product.

Desirability, feasibility, and viability creates productive tension between those viewpoints. It asks teams to treat customer evidence, delivery reality, and business logic as connected parts of the same decision, making assumptions easier to expose before they harden into expensive commitments.

Organizations that develop ideas in stages, gather evidence across desirability, feasibility, and viability (and release further resources only when that evidence supports continued investment) can reduce waste and direct scarce resources toward initiatives with stronger strategic value.

This way of working also protects the brand because customers feel internal decisions through every feature, message, and service moment. When a product overpromises, breaks under pressure, or solves the wrong problem, the brand carries the damage. A balanced process helps the experience live up to the promise.

Desirability: Do Users Want It?

Desirability is evidence that people face a real problem and care enough about solving it to change their behavior. Interest alone is weak proof. Compliments in a research session, clicks on a concept, or enthusiastic stakeholder reactions may show curiosity without showing genuine demand.

The work starts by defining the audience and understanding the context around the problem. Teams need to learn what people are trying to achieve, what blocks them, how they solve it today, and what the current frustration costs them. Good research explores behavior as well as stated preference because people often describe what sounds reasonable while acting according to habit, convenience, or trust.

That makes validation methods like user interviews, field research, prototype testing, search analysis, and competitive analysis especially useful. Interviews uncover language and motivation, observation exposes workarounds, and prototypes show whether people understand the proposed interaction. Used together, these methods help teams move from broad interest to stronger evidence of need.

Product desirability testing methods including interviews, field research, prototypes, search analysis and competitive analysis.

Stronger desirability evidence goes beyond stated interest.

A desirability test should also examine the brand relationship. People might want the solution but reject it from a company they do not trust. A financial tool, health feature, or AI assistant asks users to grant different levels of permission, so the concept must feel credible coming from this particular organization.

Teams often chase imagined demand, spend heavily, and see little adoption. Starting with desirability helps uncover the deeper customer pain points behind surface requests while feasibility and viability remain part of the evaluation.

This emphasis does not mean building everything users request. Customers usually describe needs through the solutions they already know. The team’s job is to identify the underlying job, tension, or unmet expectation, then explore better ways to address it through design, content, and technology.

Feasibility: Can We Build It?

Feasibility tests whether the organization can deliver the idea within real technical, operational, financial, and time constraints. A prototype may prove that an interaction is possible, while production demands a much broader level of readiness.

Teams need to examine system architecture, integrations, data quality, security, accessibility, legal requirements, specialist skills, vendor dependencies, and delivery timelines. They also need to understand the trade-offs. A feature might be possible within six months but impossible within six weeks, or it could work for a pilot audience and fail at national scale.

The same thinking must extend beyond launch. Maintenance, monitoring, customer support, incident response, analytics, and future updates all require ownership. When these needs stay outside the initial estimate, the product can become fragile or expensive soon after release.

Scalability deserves particular attention because a service that works for one hundred users may need a different architecture and support model for one hundred thousand. Teams should test where costs rise, where manual processes become bottlenecks, and where performance could affect the user experience.

Product feasibility checklist covering build, delivery, operations and scalability.

Feasibility includes operating and scaling the product after launch.

Brand and design decisions influence feasibility as well. A distinctive user interface may depend on custom components that take longer to build and maintain. Rich motion, personalization, and complex content can improve the full user experience while adding technical weight. The right balance supports the intended experience without creating a system the organization can’t reliably operate.

Early collaboration reduces late surprises. Designers, engineers, operations specialists, security teams, and commercial leaders should examine the concept together. This holistic approach makes constraints visible while there is still room to reshape the idea, adjust the scope, or simplify the design approach.

Viability: Can It Succeed as a Business?

Viability asks whether the product can create enough value to justify continued investment. Revenue is one measure among several. A product may reduce service costs, improve retention, open a strategic market, strengthen a core offer, or increase the value of an existing ecosystem.

The business logic should connect the user problem to a measurable organizational outcome. If customers save time, the team should understand what that means for adoption, retention, or willingness to pay. If an experience strengthens the brand, the organization should have a clear way to recognize that effect through behavior, perception, or commercial performance.

Teams should study market size, pricing, acquisition costs, operational costs, competitive pressure, channel fit, and expected lifetime value. They should also test the assumptions behind those numbers because a spreadsheet can make weak logic look precise. Evidence from experiments, pre-orders, pilots, and real behavior gives the model more substance.

Product viability checklist covering market, pricing, costs, competition, channels, lifetime value and strategy.

Viability connects customer value to measurable business value.

Viability also includes strategic fit. An idea may produce revenue while distracting the company from its strongest position. It might pull the brand into a category where it lacks authority or require capabilities that offer little value elsewhere. The best opportunities support immediate performance while reinforcing a coherent long-term direction.

Content plays an important role here because customers need to understand the offer before they can value it. Clear product content explains the problem, frames the benefit, and reduces hesitation. It also reveals whether the proposition is genuinely simple. When a team needs pages of explanation to make an idea sound useful, the value may still be unclear.

The Product Sweet Spot

The product sweet spot lives somewhere in-between desirability, feasibility, and viability. Ideas in this space solve a meaningful problem, can be delivered with confidence, and support a sustainable business case.

Product sweet spot diagram showing desirability, feasibility and viability and what to change when one condition is missing.

Missing one lens reveals where an idea needs to change.

Few concepts arrive there fully formed, so most need some degree of adjustment. A desirable and viable service may require a smaller first release to become feasible. A feasible and desirable feature may need a different pricing model or strategic role. A feasible and viable offer could need deeper research because demand remains uncertain.

This is where the framework becomes a creative tool rather than a scorecard. Weakness in one dimension gives the team a direction for improvement. Narrowing the audience, changing the channel, simplifying the feature set, or reframing the promise can move the idea toward balance without abandoning its core value.

For digital products, a holistic design approach helps teams see those relationships. The holistic approach to web design connects business goals, technical systems, content, interaction patterns, and brand expression. That wider view prevents local improvements from creating problems elsewhere.

The same principle applies beyond web design. A holistic approach includes the full customer journey; meaning discovery, onboarding, use, support, and renewal. Each moment can strengthen or weaken the product’s position in the sweet spot, which makes the framework valuable across the entire lifecycle.

How to Use the Framework

Teams can apply it during idea selection, concept validation, feature evaluation, roadmap planning, and design reviews. Its value grows when it becomes a repeated practice rather than a one-time workshop.

Validate ideas early

Start by testing if the problem deserves attention or not. Speak with users, study current behavior, map alternatives, and test a lightweight concept before building a polished solution. Early desirability evidence helps the team avoid spending months answering a question customers never asked.

Once the need looks credible, deepen the feasibility and viability work. Engineers can test risky integrations or architecture choices, commercial teams can model pricing and market potential, and designers can refine the interaction and user interface around what the research has revealed.

The evidence should become stronger as investment grows. A rough interview insight might support a prototype. A prototype could support a pilot. A pilot should produce behavioral and commercial evidence before a large launch. This staged approach gives leaders clear points at which to continue, change direction, or stop.

Five-stage product validation process from problem research through concept, prototype, pilot and launch.

Evidence should become stronger as investment increases.

Prioritize product ideas

The framework also helps compare competing ideas when time and money are limited. Teams can assess each option through user value, implementation effort, and business impact, then discuss the quality of the evidence behind each rating.

A simple comparison might be using a set of questions like these.

  • How urgent and widespread is the user problem?
  • What technical or operational uncertainty could block delivery?
  • Which measurable business outcome would the idea support?
  • How well does the concept fit the brand and product strategy?

Scores should guide conversation rather than replace judgment. A high total built on weak assumptions remains risky, while a lower score may still point toward a valuable experiment if the learning potential is strong.

The framework can also shape roadmap sequencing. A small feature may unlock the evidence needed for a larger opportunity, while a technically difficult initiative may become more practical after foundational work. Prioritization improves when teams consider dependencies and learning value alongside immediate impact.

Common Framework Mistakes

The most common mistake is treating user requests as proof of desirability. Requests can point toward a problem, but they rarely define the best solution. Teams still need to understand motivation, frequency, context, and willingness to act.

Another mistake is leaving viability until the concept feels finished. Business logic influences scope, audience, channels, content, and the product promise. Bringing it in late can force major changes after the team has become attached to the work.

Teams also overestimate feasibility when they focus only on initial development. Long-term support, governance, migration, security, and content operations can determine whether the experience remains reliable. A launch plan without an ownership model is incomplete.

A further risk is using the framework as a ceremonial template. Filling three boxes during a workshop creates an appearance of rigor, while the real value comes from evidence, disagreement, and repeated testing throughout development.

Four common mistakes when applying the desirability, feasibility and viability framework

Better framework use depends on evidence and repeated testing.

The framework does not guarantee success because markets can move without warning, and customer behavior can surprise even careful teams. It still improves the quality of the questions, sharpens decision-making, and makes uncertainty easier to manage.

Conclusion: Build Products That Deserve to Exist

Desirability, feasibility, and viability helps teams judge ideas with greater clarity.

  • Desirability proves that a meaningful problem exists.
  • Feasibility shows that the organization can deliver and support the solution.
  • Viability connects the work to sustainable commercial or strategic value.

Together, the three dimensions create a more holistic view of product decisions. They help teams protect resources, sharpen the brand promise, and build experiences that hold up beyond the presentation deck.

Strong products solve real problems, work reliably, and make business sense. When internal teams lack the research, strategy, or delivery capacity to test those conditions properly, experienced UX design consulting firms can bring an outside perspective and a structured design approach. The right partner helps connect evidence, execution, and brand ambition before costly assumptions become permanent.

  • What measurable evidence should teams use for each lens?

    For desirability, look for actions such as sign-ups, purchases, or repeat use rather than positive interview comments alone. For feasibility, test risky integrations, performance, delivery effort, and support capacity. For viability, compare evidence of willingness to pay or measurable savings with acquisition and operating costs, retention, and the product's strategic goals.

  • How can a team test all three lenses with a limited budget?

    Start with the assumptions that could most easily invalidate the idea. Use focused user interviews and a lightweight prototype or landing-page experiment to test demand, a small technical proof of concept to check critical delivery risks, and an initial cost-and-value model backed by customer or pilot evidence. Fund further work according to what those tests reveal.

  • How much evidence is enough to move from concept to pilot or launch?

    There is no universal interview count or score that proves readiness. An early prototype can be justified by credible evidence of a user problem and a plausible delivery and value case; a broader launch calls for stronger behavioral evidence, tests of major technical and operational risks, and business assumptions checked against pilot results. Define the evidence needed for each investment decision before conducting the tests.

  • Should the three lenses be weighted equally when prioritizing ideas?

    Not necessarily. Their relative emphasis can reflect the product's strategy and context, but teams should document the evidence and uncertainty behind each assessment separately. A high combined score should not hide a critical obstacle to adoption, dependable delivery, or sustainable business value.

  • Who should make the final go/no-go decision when teams disagree?

    Assign clear decision accountability to the relevant product or initiative leader, while leaving funding approval with the people authorized to invest. Researchers and designers should provide user evidence, engineers and operations specialists should identify delivery risks, and commercial leaders should examine business value. In Scrum, the Product Owner is accountable for product-value decisions.

  • How can teams test whether customers trust the brand behind a new product?

    Test the concept with the actual brand visible, including relevant pricing and data-permission requests. Observe whether target users proceed or abandon key steps, then investigate concerns about credibility, privacy, or the company's fit with the offer. Stated trust helps explain reactions, but actual decisions provide stronger evidence of adoption.

  • When should a weak lens trigger a pivot or stop decision?

    Revise the concept when a narrower audience, smaller release, different delivery approach, or adjusted business model could address the weakness. Pause or stop investment when credible tests fail to establish meaningful demand, an essential delivery constraint remains unacceptable, or the expected value cannot justify the ongoing cost. Identify the failed assumption before deciding whether another experiment is worthwhile.

  • When should the framework be reassessed after launch?

    Revisit the three lenses when adoption or retention changes, operating costs or reliability diverge from expectations, important technical dependencies emerge, or market and strategic conditions shift. Reassessment should also inform major roadmap and investment decisions rather than ending at launch.