This is one of my biggest pet peeves. I've abandoned a project because my non-tech partner constantly came up with new ideas why we couldn't launch and that we needed more features before we launched. This resulted in me being highly demotivated and frustrated.
Not to sound trite, but that sounds like a lack of planning -- in the form of a question, what's your MVP? If you're clear on that, you point to the doc and say "how does this new idea/feature help accomplish this?" and force a specific answer.
How We Fooled Ourselves Into Waiting Too Long To Launch
31–40 of 57 posts
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#32This is not just a software/startup problem. Every single web project / eCommerce site / anything online that requires work, should be rolling out a variation of an MVP. I had a meeting with the brother earlier today. He runs an online wholesale business (I do all the tech stuff). I've been leaning towards launching a retail arm in our one EU country, and launching 3 new wholesale websites translated into Dutch, Fren…
Dutch and French. :-)
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#33We launched early, asked for money right away, and have been doing excellent ever since. Now our problem is defining what makes a 'final, out of beta, stable' version. Defining it, and then meeting it. We're constantly going 'this isn't good enough for a final release'. But hey, almost 300 paying users right now is motivation to make it better for THEM, and not for us and our imaginations of what is better. With thos…
You have no idea how I like reading this. I'm sick of all those new websites that offer their service for free, hoping to figure out how to monetize later.
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#34There exist many, many businesses where V1.0 of the product can be the CEO scrambling with a cell phone, Gmail, and a spreadsheet. This is especially true for business process innovation type businesses like e.g. ZeroCater (which actually started out pretty much exactly like that). After you learn exactly where the painful bits are you can code to prevent them rather than coding for problems which may not ever be exp…
I can't agree more. It took me a while to get there but in the end it's exactly what everybody should do.
As of right now I'm manually creating the accounts of new customers (has something to do with creating new database tables which is done half-automatically). Right now there is only a trickle of new customers (due to the lack of marketing) and it's not worth it (yet) to program a fully automated registration process which would require a registration form, payment processing and above mentioned account creation.
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#35This is not just a software/startup problem. Every single web project / eCommerce site / anything online that requires work, should be rolling out a variation of an MVP. I had a meeting with the brother earlier today. He runs an online wholesale business (I do all the tech stuff). I've been leaning towards launching a retail arm in our one EU country, and launching 3 new wholesale websites translated into Dutch, Fren…
whatever they speak in Belgium Dutch and French. :-)
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#36There exist many, many businesses where V1.0 of the product can be the CEO scrambling with a cell phone, Gmail, and a spreadsheet. This is especially true for business process innovation type businesses like e.g. ZeroCater (which actually started out pretty much exactly like that). After you learn exactly where the painful bits are you can code to prevent them rather than coding for problems which may not ever be exp…
[...] those tasks were never common/important/etc enough to justify even an hour writing up a tool to automate them. I can't agree more. It took me a while to get there but in the end it's exactly what everybody should do. As of right now I'm manually creating the accounts of new customers (has something to do with creating new database tables which is done half-automatically). Right now there is only a trickle of ne…
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#37Earlier quoted context omitted.
whatever they speak in Belgium Dutch and French. :-)
That doesn't help. If I listen to the 10 o'clock news in the Netherlands, do I get a choice of languages? Newspapers in two languages? Parliamentary questions and interviews in 2 languages? Seriously?
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#38It seems like the real problem here is just not knowing your customers. By all means you should be beta testing with your friends and anyone else you can guilt into helping you. Don't launch blind.
Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#39Re: How We Fooled Ourselves Into Waiting Too Long To Launch
#40Earlier quoted context omitted.
whatever they speak in Belgium Dutch and French. :-)
That doesn't help. If I listen to the 10 o'clock news in the Netherlands, do I get a choice of languages? Newspapers in two languages? Parliamentary questions and interviews in 2 languages? Seriously?