Desirability asks whether a solution meets a meaningful human need; usability asks whether people can use it successfully in context; feasibility asks whether a team can build and deliver it. They overlap, but they are not interchangeable—and the familiar design-thinking triad pairs desirability and feasibility with viability, not usability.
What each term means
| Lens | Core question | Evidence to look for | What failure can look like |
|---|---|---|---|
| Desirability | Do people have this need, value this outcome, and want this solution? | Research into needs, context, motivations, behavior, and reactions to concepts or prototypes | People can use the product but do not care about it |
| Usability | Can specified users achieve specified goals effectively, efficiently, and satisfactorily in the context that matters? | Representative users attempting meaningful tasks; observe outcomes, effort, errors, and satisfaction | People want the outcome but struggle to complete key tasks |
| Feasibility | Can the organization implement, operate, and deliver the solution with its available technology and capabilities? | Technical and operational assessments, including time, distribution, capabilities, and partners | People want and can use the concept, but the team cannot reliably deliver it |
| Viability | Can the solution succeed and continue to be supported under the organization’s economic and stakeholder conditions? | Value proposition, revenue or funding possibilities, stakeholder incentives, and sustainability assumptions | The solution can be built and used but cannot be sustained |
How usability differs from desirability
Desirability is about whether the solution matters to the people it is meant to serve. It is not simply whether someone likes a concept’s appearance or says an idea sounds appealing. The useful question is whether the solution addresses a real need in people’s circumstances.
Usability is about the quality of using a system to accomplish a goal. ISO 9241-11:2018 defines it as the “extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.” ISO says this edition was reviewed and confirmed in 2023 and remains current, according to its standard catalog page.
That definition makes usability contextual, not a universal label. A tool might work well for one group, task, or setting and poorly for another. “Easy to use” is too narrow if people cannot complete the goal effectively, must spend excessive effort, or are dissatisfied with the experience.
Why feasibility is not viability
Feasibility concerns the ability to make and deliver a solution: the necessary technology, skills, operating capacity, time, distribution, and partners. Viability asks whether the solution can be sustained within the organization’s and stakeholders’ real-world conditions. A technically buildable service may still lack a credible funding source or a reason for the organization to keep supporting it.
IDEO’s commonly used design-thinking framing balances desirability, feasibility, and viability. Usability remains an important product-quality concern, but it is not another name for viability. IDEO’s overview describes design thinking as bringing together people’s needs, technological possibilities, and business requirements; it attributes that formulation to former IDEO CEO Tim Brown: “Design thinking is a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” See IDEO’s design-thinking overview.
Human-centered design and design thinking are related, but not identical labels: IDEO describes human-centered design as a mindset and design thinking as a process for putting that mindset into practice. IDEO’s FAQ explains the distinction.
How to assess all four lenses
- Define the user, goal, and context. State who will use the system, what they need to accomplish, and under what conditions. Without those specifics, a claim that a product “is usable” cannot be evaluated meaningfully.
- Investigate desirability with people. Learn about needs and behavior before committing to a favored idea. Show intended users a concept or prototype and explore whether it addresses the need—not just whether they like its look.
- Evaluate usability through tasks. Ask representative users to attempt important tasks with a prototype or product. Observe whether they reach the intended outcome, how much effort or friction they encounter, and how satisfied they are. Use problems observed to improve the design.
- Check feasibility with delivery partners. Examine technical and operational requirements, time, distribution, organizational capabilities, and potential partners. Surface constraints without ruling out imaginative ideas before exploring workable approaches.
- Assess viability separately. Examine the value proposition, possible revenue or funding, stakeholder incentives, and whether ongoing support is realistic. For public-interest or nonprofit work, sustainability may mean securing continuing support rather than making a profit.
- Revisit assumptions as the work changes. Prototype, test, and update the evidence. These lenses are not necessarily one-time gates in a fixed order; findings in one area can change what the team should investigate in another.
IDEO and the Interaction Design Foundation both describe design work as involving these connected considerations, real-user feedback, and iteration. See the Interaction Design Foundation’s testing-stage guide and its guide to feasibility and viability.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
Using the distinctions to make decisions
Keep the questions separate when reviewing an idea. Strong evidence that people need an outcome does not show that they can use a proposed interface. A successful usability test does not prove broad demand. A working prototype does not establish that the organization can operate it or sustain it.
- If the need is uncertain, learn more about people’s context and behavior before polishing the solution.
- If people want the outcome but cannot complete key tasks, investigate the usability barriers and iterate.
- If the concept works for users but cannot be delivered with current capabilities, explore technical or operational alternatives.
- If the solution is wanted, usable, and deliverable but lacks a path to ongoing support, revisit its viability assumptions.
The lenses help teams expose assumptions and choose what to learn next. They support judgment and iteration; they do not mechanically guarantee an optimal solution.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
