* have at least 10 customers willing to buy my service when it's done. During the time of development they would commit to spend time with me validating my product hypothesis.
* prepare spec for a _REAL_ mvp.
* clearly _describe_ problem that I'm trying to solve. (now I know that it takes multiple iterations to achieve this - most importantly discussing the problem with your future customers)
We are fixing this right now. First idea was to use Disqourse (we still have disqourse.com) because discourse.com was taken. Now we've seen that Google is changing all the queries from disqourse to discourse so we've changed our domain name to discoursehq.com :)
Google ChromeOS and Google Wave share some similarities in terms of marketing messaging behind those products. In both cases biggest value of both products is in business - they should never be marketed as a consumer products.
I agree with Paul that ChromeOS with its current market target will fail - just like Wave did.
But there is still hope for ChromeOS. Google should target bigger companies with it. Make it a hardware extension of their Google Apps offering. IT departments and CFOs will love them.
And you know what? I think that they are thinking about this already - that is why we've seen Citrix client there.
There was an interesting blog post about this problem few weeks ago on HN. In general you can defend your b) or c) or d) situation with on word "Timing".The only problem is that you must convince people in the audience that Timing is right and why it was hard/impossible before and right now is easier/possible.
What we are looking for here is something like an Instapaper for email. I often open an email - scan in and if I find something important I make this email "unread" again...
That would be interesting- but I think this is something that should be built into mail apps natively. The way people are using email has evolved past it's current functionality.
* have at least 10 customers willing to buy my service when it's done. During the time of development they would commit to spend time with me validating my product hypothesis.
* prepare spec for a _REAL_ mvp.
* clearly _describe_ problem that I'm trying to solve. (now I know that it takes multiple iterations to achieve this - most importantly discussing the problem with your future customers)