Feasibility
Feasibility assumptions are the assumptions product teams make about why they think they can build their proposed solutions. These assumptions go beyond technical feasibility to include whether teams have the necessary skills, knowledge, and ability to build the solution.
What does feasibility include beyond technical feasibility?
The most common feasibility assumptions are engineering assumptions. Do teams have the necessary skills, knowledge, and ability to build these solutions? Does the necessary technology exist?
But feasibility isn't limited to technically possible. Teams should also examine compliance, legal, and security assumptions as part of feasibility assumptions. Teams can and should enumerate assumptions around why legal or compliance will sign off on solutions, or why solutions won't expose any security risks.
Teams might even push feasibility to include assumptions around why they think a solution is feasible in their organization. Every organization has solutions they would never consider. We've all heard, "That will never work here." If an organization won't sign off on it, then it's not feasible.
Feasibility is one of five key types of assumptions—along with desirability, viability, usability, and ethical—that product trios must evaluate when building products.
Learn more:
- Assumption Testing: Everything You Need to Know to Get Started
- Evaluating Solutions: The 5 Types of Assumptions that Underlie Our Ideas
Related terms:
- Assumptions
- Desirability
- Viability
- Usability
Last Updated: October 25, 2025