Why Doesn’t It Exist Today?March 11, 2013 7:37 am
okay, you have an idea for building an app or a service – and the idea does not seem to go away. Before you open your IDE, here is a suggestion to avoid some pitfalls in defining the features:
Spend some time, thinking about this: Why Doesn’t It Exist Today?
And make a list of 5-10 points that you think are the reasons why the service or product does not exist today (or) if it has been tried before, the reasons why it did not work. You might need to do some additional digging – for example, there might be some regulatory hurdles a few steps down the line – but it is an interesting thought exercise that will definitely help you define your product better.
This is obviously a corollary to the more popular Why Now? question – but the results of the “Why Doesn’t It Exist Today?” are actually more actionable – it will take you through a path of alternatives, substitute processes, and a set of warning items that you can directly put in your assumptions and add to your watch-list.
While many of us definitely do this, failing to actionize the results is as bad as not doing it at all. Because if there is a reason it doesn’t exist today, and if you believe it can exist tomorrow, you must be doing something around those reasons to make it exist. At the very least, you should find a way around those reasons to make it exist.
Why Doesn’t It Exist Today? What can you do to change that?