Skip to main content
A solution can pass every other test and still be a bad idea. Users love it - but it costs more to deliver than you can charge. It solves the problem - but it creates a legal liability. It works technically - but it cannibalises your most profitable product line. Business viability testing is the check that ensures what you’re building is actually good for the business, not just good for the user 🤔

​
The fourth dimension of discovery

Teresa Torres frames discovery risk across four dimensions in Continuous Discovery Habits: value, usability, feasibility, and business viability. Most teams are reasonably good at the first three. The fourth gets skipped because it feels like someone else’s job - finance’s job, legal’s job, leadership’s job. But if PMs don’t own business viability questions, nobody does. And solutions that fail on this dimension are just as dead as ones that fail on value.

​
What you’re testing

Business viability covers a wide range of concerns depending on your context: Commercial viability - Can we make money from this? Does the unit economics work? Is the willingness to pay high enough to justify the cost of delivery? Legal and compliance - Does this solution create regulatory exposure? Are there data privacy, IP, or contractual constraints we haven’t accounted for? Strategic fit - Does this align with where the company is going? Does it strengthen or undermine other parts of the product or business? Operational viability - Can the business actually support this at scale? Do we have the support infrastructure, the sales motion, the onboarding process? Reputational risk - Could this damage how customers, partners, or the market perceives us?

​
How to test it

Unlike value or usability testing, business viability isn’t tested with users - it’s tested internally, with the stakeholders who own each risk dimension. The practical approach: before committing to a solution, identify the key business assumptions it relies on and validate them with the right people.
  • Loop in legal early on anything touching data or contracts
  • Run commercial assumptions past finance or your pricing lead
  • Stress-test strategic fit with your CPO or equivalent
  • Talk to sales and customer success about operational implications
This isn’t a gate or a sign-off process - it’s a conversation. The goal is to surface constraints early so they inform the solution, not kill it after you’ve built it.

​
The common failure mode

Business viability tends to get checked at the end - in a review, a legal sign-off, or a leadership presentation - rather than throughout discovery. By that point, the team is committed to the solution and constraints feel like blockers rather than inputs. Lesson learned: the earlier you involve the people who own business constraints, the more likely they are to help you find a solution that works rather than just veto the one you have 👊