How to Fail and still be a sucess


Published on Bizcamp Dublin

Published in: Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Hi My name is Caelen King and I‘m the founder and CEO of Today I‘m going to talk to you about something that is really under-rated – failure. Failure is something that I like to think that I‘m good at – after all I have enough experience. Everyday I come to work and every day I‘m wrong but at the end of the month or a year something good and right has been created out of that failure
  • How to Fail and still be a sucess

    1. 1. How to be wrong every day and still be right Caelen King CEO and Founder
    2. 2. <ul><li>Founder & CEO of </li></ul><ul><li>Previously VP Product for NewBay Software </li></ul><ul><li>Previously Product Manager for Baltimore Technology </li></ul>Who am I?
    3. 3. Most of us want to do something NEW
    4. 4. The Emotional Rollercoaster – Stage 1 <ul><li>This is going to be great . </li></ul><ul><li>We just do A+B+ C and... </li></ul><ul><li>WE RULE THE WORLD </li></ul>
    5. 5. Emotional Rollercoaster – Stage 2 <ul><li>What was I thinking </li></ul><ul><li>I am so totally screwed </li></ul>
    6. 6. Emotional Rollercoaster – Stage 3 OK Let’s do it Again
    7. 7.
    8. 8.
    9. 9.
    10. 10. <ul><li>Bounce rate went from 45% to 51%, </li></ul><ul><li>Page view reduced by 25% worst of all </li></ul><ul><li>Conversion rate went from 7.2% down to 2.4%. </li></ul><ul><li>IT WAS KILLING 75% OF OUR REVENUE! </li></ul><ul><li>After a week of counting the cost we pulled it out and brought back the old design. </li></ul>Results
    11. 11. <ul><li>In Baltimore I launched 5 product lines – ONE SOLD </li></ul><ul><li>In NewBay I launched another 5 product lines – TWO SOLD </li></ul><ul><li>In of the 4,000+ feature/UI changes logged in basecamp about 500 are used </li></ul><ul><li>We re-invent on a daily basis </li></ul>Nearly Everything is Binware
    12. 12. <ul><li>Concentrate on your core functionality – copy everything else </li></ul><ul><li>Write you own documentation </li></ul><ul><li>Get it out early </li></ul><ul><li>Use it yourself </li></ul><ul><li>Recognise failure as a success </li></ul>What to do
    13. 13. <ul><li>Don’t try and be 100% right </li></ul><ul><li>Don’t pull a feature before giving it time to bed down </li></ul><ul><li>Don’t worry about colours </li></ul><ul><li>Don’t code for scalability </li></ul><ul><li>Don’t add ‘nice to haves’ </li></ul><ul><li>Don’t spend a lot of money getting expert advice hoping that it will stop you from being wrong </li></ul><ul><li>Don’t stubbornly insist that you got it right and the world is wrong </li></ul>What not to do
    14. 14. <ul><li>You fail because you got it wrong – this is good </li></ul><ul><li>You fail because you couldn’t be bothered – this is bad </li></ul>Two Types of Failure