A solution that is usable, feasible, and viable

A solution that is usable, technically feasible, and viable from a business perspective

I used these very words in a recent post, without digging deeper into what it meant. I did this intentionally, as there is a huge amount to unpack in a single sentence.

Let’s start by looking at each of the key phrases individually:

1.      Usable – is your solution intuitive for your target market? The individual using your solution needs to know how to use your product with very little to no guidance. The goal is to get them to get to the ‘Aha’ moment as quickly as possible. If they find your interface confusing or difficult to use, they are likely to move on quickly.

2.      Technically feasible – are you able to build your solution? It is surprising how often this question is ignored. The solution is handed over to the engineers, only to later discover that it isn’t technically feasible. You then have to start all over again. This is one of the main reasons for including engineers in the solution discovery stage. Not only are they a great source of ideas, but they will also validate the technical feasibility.

3.      Viable from a business perspective – is your solution a good fit for the business? For example, if you have an existing business, is it a good fit for your brand or your sales/revenue model? If you are only starting on your journey, you must decide whether the solution fits you from a personal perspective.

If your solution solves a genuine problem for your target market, and it meets the three requirements above, then you have a strong foundation upon which to build your product.  

Note: Credit to Marty Cagan for highlighting the need to have these three elements in a viable solution.