Evolution and Product Development
On a couple of occasions this week I have been reminded of the power of iteration in business. While we all aim to be perfect the first time around, it is a pipe dream. Great products and services are born out of trial and error. Only with iteration will a company get the feedback it needs to inch closer and closer to a product that best meets customer needs. And part of that process of iteration is trying stuff out early and often -- broken stuff will get fixed (and, occasionally, fixed stuff will get broken) and in the process solid products will emerge.
Take for example the Treo 600. Two years ago, attendees of the TED conference were given the opportunity to buy the first generation Treo at a big discount. I, like a substantial portion of the TED crowd, am a gadget freak and very happily signed up to get the first generation Treo. The only problem is it sucked. No offense Handspring, but the first Treo was a mediocre PDA and a terrible phone. It was a big fat flip phone that did many things but did nothing particularly well (ok, the address book and dialing integration was pretty cool but that was about it).
I'm back at the TED conference this week and have yet again been given the opportunity to get the latest Treo -- the Treo 600. As a warmup to receiving the Treo 600, Peter Skillman, the lead product designer, gave a brief talk on the evolution of the Treo. He discussed what his team had learned from the initial Treo design (first and foremost, people want a phone that looks and feels like a phone). And he showed a bunch of drawings and models of proposed Treo 600 designs that ultimately lead to the device that is being sold today. Of the design process, Skillman summed up his philosophy this way, "it's about failing -- big time." While many of the prototypes and drawings were indeed failures, the resulting device seems to me the best smart phone available to date. By using an iterative process, Handspring has been able to create a much better product than it would have otherwise produced.
Similarly, I have always viewed as one of the key strengths of building a web business, the ability to rapidly evolve a product or service based upon specific, quantifiable user feedback. Successful web businesses have never sought to put out the perfect product. Rather, they have put out products that can be measured and tracked, and have been quick to revise those products based upon the direct feedback they receive. The more agile a company is in responding to that user feedback, the more likely it will ultimately build a product or service that best meets the needs of its customers.
As I sit at TED pondering the interaction of technology/science and design, my conviction about the value of the iterative design process seems self evident to me. Great product development is an evolutionary process. Just as sophisticated organisms like mantis shrimp or bonobo monkeys were not born over night, nor were sophisticated devices like the Treo 600. Only through trial and error can a company build great products and services that truly meet the needs of their customers.
Categories
Conferences , Consumer Electronics & Gadgets , Consumer Internet & Media , Hardware & Systems , Software7 TrackBacks
Listed below are links to blogs that reference this entry: Evolution and Product Development.
TrackBack URL for this entry: http://ventureblog.com/cgi-bin/mt/mt-tb.cgi/177
It's amazing how much time you have to think when you're at home alone thinking. It's also amazing what you have time to think and read about when you browse through your entire Blogroll reading the last month's entries. Some blogs I hadn't read in a w... Read More
David Hornik writes about the power of iterative design, discussing the Handspring Treo phone/PDA and then generalizing the experience. A quote: Similarly, I have always viewed as one of the key strengths of building a web business, the ability to rapi... Read More
Great products and services are born out of trial and error. Only with iteration will a company get the feedback it needs to inch closer and closer to a product that best meets customer needs. Read More
Great products and services are born out of trial and error. Only with iteration will a company get the feedback it needs to inch closer and closer to a product that best meets customer needs. Read More
David Hornik considers the Treo 600 in Evolution and Product Development. "Only through trial and error can a company build great products and services that truly meet the needs of their customers."... Read More
VentureBlog: Evolution and Product Development I'm doing some more thinking on XP, and to some extent the failure of the BigDesignUpfront. There are so many unknowns in product development. I rea... Read More
Here's a blog entry about the Handspring Treo 600 that discusses iterative product design, listening to the customer and giving them what they want - Evolution and Product Development The first version of the Treo was awful. The Treo 600 Read More
The concept of iteration is actually quite old. More than 20 years ago, Fred Brooks wrote the very readable and seminal book The Mythical Man Month and one of the things he proposes is to build a "throwaway prototype", a quick and simple version 1 which quickly leads into a version 2 built from scratch (or close to it).
Until this day, too many companies attempt to launch complex new projects with a big bang approach. "We need ALL these features in version 1 and it has to work, scale, be extensible, etc ,etc" and what they often get instead is a big, expensive, and late failure.
The idea put forth by Brooks is that we can never get the first version right, no matter how sure we are of the requirements if it has never been done before. That it is important to build a proof of concept prototype to check and see if the requirements and assumptions have been correct before building the "big one".
I couldn't agree more with the comment above. Starting small and building features into your product - after you see how users respond is absolutely the best way to design anything. Designer can rarely anticipate all of the features and needs of users.
I couldn't agree more with the comment above. Starting small and building features into your product - after you see how users respond is absolutely the best way to design anything. Designer can rarely anticipate all of the features and needs of users.
I sure wish more investors and Venture Guys understood this. Rapid innovation can not be put into a business plan. The impatient nature of investors is the enemy of interation. Can someone explain to me how you can put in a business plan how you plan to fail faster than anyone else. Microsoft can just keep plugging away until it gets it right, yet countless companies have had the plug pulled because they need to plug away and the investors/board/venture capital has a shorter time frame.
Imagine is Tom Watson had to deal with the short attention span that a lot of Venture guys are so proud of?
I just got around to reading this last comment, and the more I think about it, the more upset I get. Most professional investors are not impatient per se, they simply want the entrepreneur to execute the plan that sold them on the deal in the first place. If the plans are realistic, and match the abilities of the founders with the present market, then there shouldn't be a timing problem. I believe that investors should give their deals enough time to learn and grow, but not coddle them either. All entrepreneurs, by definition, fall in love with their own deals - and this alone makes the relationship with investors difficult from their perspective. From an investors perspective, the deal will always have unforseen problems, which is why they have to think about protecting their money, and not drink the kool-aid, as so many entrepreneurs do all too often.