Answers for developers, sales and business people. How Failing Fast is infinitely better than the alternative
Failing Fast is a good thing – to borrow a phrase from Martha Stewart – and everyone should be practicing it.
You may ask how can Failing Fast possibly be better than succeeding fast? Well, succeeding is not the alternative, not only because most projects don’t succeed fast. The alternative we want to compare here is Failing Slowly.
The idea of Failing Fast is to quickly weed out the ideas and methods that don’t work – and make changes that might turn them around. The question that needs to be asked is: Should you discover quickly that an idea is bad, or after you’ve spent a lot of time, effort and money developing a bad product.
Tony Hillerson, Software Architect at EffectiveUI moderated a conference session at the Web 2.0 Expo in San Francisco recently. The panel brought together leaders from eBay, Google, Adobe and Discovery Channel. They responded to a number of set questions and then took questions from the audience, in the “Failing Fast” session.
The panelists were:
The session is split into bite-sized video chunks.
Failing Fast – User Adoption
How do you know when to add a feature based on user input
Use Proven Technology or Try The Bleeding Edge
How do you protect your brand
How Sales Copes With Uncertainty of Failing Fast
Who Is Attracted To Buzz?
Failing Fast Session Attendees Get Answers
Editor’s Note: Failing Fast isn’t restricted to Web 2.0 – it’s something I always did as a developer and project manager – it can be applied to any project in any industry once you work out how to do it in your culture.
Please make comments by writing to comment at NewsBlaze dot com