Tim, couldn't have said it better. Agree entirely. I think the really hard bit is not so much the perfection, but the process of deciding w Hat features to add to your MVP. A lot of startups just make it worse.
On Wednesday, November 2, 2011, Tim Bull <tbull...@googlemail.com> wrote: > My perspective on this has changed as our product matures. Actually I > posted on exactly this issue a couple of weeks back > http://timbull.com/rosl100-is-your-minimum-viable-product-mvp-ac > > Key thoughts were: > > "The goal of a startup is to find the sweet-spot where minimum product > and viable product meet–get people to fall in love with you. Over > time, you listen to your customers, make improvements and raise the > bar on what viable means–making it more expensive for competitors to > jump in." > > As your product grows, what constitutes an MVP needs to grow with it. > Yes, you can still probably get away with things like links that go > nowhere and measure clicks to test if users want features, but if you > chose to deliver the feature, it has to match the user expectations > that are dictated by the lifecycle of your product. > MVP is a valuable tool and something we still live by. But we've > realised two important lessons. > * You don't have to be Feature Rich, but you do have to be Feature > Perfect (if you're going to do it, do it right). > * The definition of Feature Perfect grows with every new user. Mockups > are great for users 1 - 10, but won't get you to user 10,000. In the > same way, a poor UX might get you a few thousand users, but won't get > you the growth you need to get to 10's of thousands. > > On Nov 2, 1:39 pm, simran <sim...@dn.gs> wrote: >> i'm all one for, do a little bit do it well... >> >> aka, after you have enough functionality for a "minimum viable product" - >> get the design right... be perfect in that... homosapiens have sight as >> probably our most common used and interactive sense, and perfection for >> that sense is possibly initially the most critical... >> >> for example, on seek i notice that the apply button in the small popup >> window often is out of "the visible area" (and on lion, we often don't even >> see scroll bars by default, until you start scrolling that is, so you don't >> even know it's a scrollable area!)... bad! bad! bad! >> >> even details such as having the wrong font, or something as trivial as the >> wrong radius on the round-edge on one of the buttons on a page, we >> "intuitively" pick up on these, and it somehow doesn't "feel right"... >> >> IMHO, in terms of "list of features to give even for a first ever release", >> do a "minimum viable product" list, but for design, go for absolute >> perfection, nothing less will do! >> >> simran. >> >> On Wed, Nov 2, 2011 at 1:17 PM, Mathew French < >> >> >> >> >> >> >> >> mathew.fre...@subscribe-hr.com.au> wrote: >> > Bit late on this one... >> >> > I sometimes run my self around in circles, driving perfection. Must be the >> > old OCD. But then reality kicks in... Customers will drive the final 10-15% >> > of product/feature dev. >> > And this probably gets it to where it needs to be in the best shape. In >> > the interest of sanity, u have to let go a little and trust in this process >> > and it will work out. >> >> > This has worked for us and are releasing every 4-6 weeks. As part of our >> > overall dev startegy though, there is consolidation, which is driven by >> > us... we have just arrived here after about 15 Months of hard core >> > releasing. Linkedin Integration, Yammer, Seek, MyCareer, Payroll >> > Connectors, etc. Now we are pulling this all together using wizards, cause >> > now we have seen how the customer interacts with the product. >> >> > Hope this makes sense. >> >> > Cheers, >> >> > MF >> >> > On Wed, Nov 2, 2011 at 1:21 AM, Pat <disrupt...@gmail.com> wrote: >> >> >> Agree with Adam here - the minimum viable product concept is key, and >> >> it's brutal to adhere to it properly. Clearly, trying to build the >> >> whole idea perfectly in one hit is impossible. >> >> >> That said, (as the author of the post referred to) I'm a firm believer >> >> in "perfecting" the minimum viable product to the greatest extent >> >> possible without mass market testing. Not striving for perfection on >> >> the kernel of the enterprise is dumb. >> >> >> Who knows how many websites would have made it but for their sloppy >> >> design? Rushing from one project to the other, hoping to uncover a >> >> kind of platonic form in the ether that guarantees a win doesn't work >> >> in the overwhelming majority of cases. Most of us aren't inventing >> >> Twitter, so without a highly addictive concept persae, striving for >> >> perfection is the best way I know to increase the chances of success >> >> in the real world. >> >> >> In my view, you win by grabbing every advantage you possibly can. A >> >> website is nothing without the experience of the people using it - >> >> you're shooting yourself in the foot if you let that slide. >> >> >> On Nov 2, 12:30 am, Brian Dorricott <brian.dorric...@meteorical.co.uk> >> >> wrote: >> >> > +1 >> >> >> > Eric Ries introduced a good term for this in 2009: Minimum Viable >> >> Product. There's an entry on Wikipedia that explains the term well: >> >>http://en.wikipedia.org/wiki/Minimum_viable_productIt is well worth a >> >> read. >> >> >> > Regards, >> >> >> > Brian >> >> >> > U:http://www.meteorical.co.uk >> >> >> > > Yea, I agree that you definitely need to get the product in front >> >> >> > > of people. It challenges all the assumptions you previously made, >> >> >> > > provides many new use cases and gives you immense motivation to >> >> >> > > keep working and improve the product. >> >> >> > > There is a great saying that I've heard a few times (something >> >> >> > > like) "If you aren't embarrassed by what you launched then you've >> >> >> > > launched too late." >> >> >> > > If you worry too much about perfection in the very beginning then >> >> >> > > you risk releasing the most amazing product 2008 has ever seen but >> >> >> > > in 2011. >> >> >> > > Thanks >> >> >> > > Adam >> >> >> -- >> >> You received this message because you are subscribed to the Silicon Beach >> >> Australia mailing list. Visthttp://siliconbeachaustralia.orgfor more >> >> >> Forum rules >> >> 1) No lurkers! It is expected that you introduce yourself. >> >> 2) No jobs postings. You can usehttp://siliconbeachaustralia.org/jobs >> >> >> To post to this group, send email to >> >> silicon-beach-australia@googlegroups.com >> >> To unsubscribe from this group, send email to >> >> silicon-beach-australia+unsubscr...@googlegroups.com >> >> For more options, visit this group at >> >>http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en >> >> > -- >> > Regards, >> >> > Mathew French >> >> > -- >> > You received this message because you are subscribed to the Silicon Beach >> > Australia mailing list. Visthttp://siliconbeachaustralia.orgfor more >> >> > Forum rules >> > 1) No lurkers! It is expected that you introduce yourself. >> > 2) No jobs postings. You can usehttp://siliconbeachaustralia.org/jobs >> >> > To post to this group, send email to >> > silicon-beach-australia@googlegroups.com >> > To unsubscribe from this group, send email to >> > silicon-beach-australia+unsubscr...@googlegroups.com >> > For more options, visit this group at >> >http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en > > -- > You received this message because you are subscribed to the Silicon Beach Australia mailing list. Vist http://siliconbeachaustralia.org for more > > Forum rules > 1) No lurkers! It is expected that you introduce yourself. > 2) No jobs postings. You can use http://siliconbeachaustralia.org/jobs > > > To post to this group, send email to > silicon-beach-australia@googlegroups.com > To unsubscribe from this group, send email to > silicon-beach-australia+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en > -- You received this message because you are subscribed to the Silicon Beach Australia mailing list. Vist http://siliconbeachaustralia.org for more Forum rules 1) No lurkers! It is expected that you introduce yourself. 2) No jobs postings. You can use http://siliconbeachaustralia.org/jobs To post to this group, send email to silicon-beach-australia@googlegroups.com To unsubscribe from this group, send email to silicon-beach-australia+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en
