I claim that no product ever failed because it was ahead of its time. It doesn’t mean that products can’t fail for other reasons. Of course not. I guess what I am trying to say is that “ahead of its time” is just papering over something else, and this something else comes in two forms:
- The product is behind (as opposed to ahead of) its users expectations. In other words, it’s just a bad product. It doesn’t solve any problem, and if it does solve a problem it does so in a way that is somehow deficient from the point of view of the user. The technology may not be there yet, it’s slow, ugly, whatever. Bottom line is: it just doesn’t live up to the user’s expectations. This is the product/market fit that everyone talks about so much.
- The product is ahead of its ecosystem. Obviously some products just don’t make sense without certain complements, infrastructure, business models, etc. Sometimes the stuff that you have to stand on hasn’t been invented yet. The users would love to use the product, but the product cannot survive on its own, it needs a certain business or technology ecosystem. Agreed, the notion of ecosystem can be very vague, but it’s basically stuff you have no control over. Some of this can be filled in with enough money thrown at it, but mostly the ecosystem problems are too large for one company to tackle.
What does it have to do with what we are trying to build?
Well, 1 is up in the air until we let our first users play with the application. Right now we are running on a set of assumptions about user wants that we need to validate. So once we have the alpha we’ll have the first indication of whether the product is decent, i.e. whether somebody is willing to use it and on what terms. Frankly I can’t wait.
2 is easier. The coast is clear in terms of ecosystem. The things that we think we’ll need are already there. Of course, once we start tracking 1 better, we may realize that there is something in 2 that doesn’t exist and is needed to satisfy 1. We’ll see.