Something recently I’ve been pondering over is the concept of when the right time to launch is. One of the big things pushed in the startup world is the concept release “early and often”. Which I’m finding out sounds great in theory but harder in practice (or so it seams).
Push it out it will be great! Bugs? Smmeh….
My previous work a large corporation felt like the exact opposite of this. You get to push when you have bug tested it yourself, had it peer reviewed, sent it to QA, get a managers approval, deploy it, personally verify it in production, have QA verify it in production. Phewy. Thats a lot. It was often a long drawn out process that I highly disliked. Though it was something so burnt into my brain that coming into the startup world I’ve had to unlearn. In many ways its made me gun shy. Great for corporations bad for startups?
I had a great experience on a recent project I was developing for a client. The client was pretty outspoken about getting just getting it out. I was barely finished with the project and hadn’t fully bug tested it, yet the client just told me to launch it. I’m well… ok. There we’re definitely bugs, but once thing it didn’t get rid of real fast was the idea that everything had to be perfect. Also that if there were bugs that all of your customers somehow will leave you. Again, not true.
Of course you don’t want everything to be crap. But everything has to start somewhere. Maybe being crappy is better than not launching at all. At least you actually launched right? It hits right at the core of why most startups don’t go anywhere, because your a sissy little girl that’s afraid to make mistakes. (No offense any sissy little girls actually reading this)