O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Rocket Powered      BicyclesAvoiding Over and Under Engineering your                Product
Chris Burnor•   GroupTie•   StartupDigest•   LinkedIn•   DataDrivenSafety
Outline•   What is a Product?•   A Scientific Approach•   An Unusual Example
The Problem
Over Engineering
Under Engineering
Why is this bad?It always pays to ask the questions no one else is
What is a Product?
Product connects business prioritieswith user experience
Product connects business prioritieswith user experience
So why is      over/under    engineering bad        again?•   Fails to realize business priorities•   Fails realize user e...
Shouldn’t we plan for     the future?
“Ay, there’s the rub”
Product is also a         story•   Idea•   Market Validation•   Traction•   Market Dominance•   Useless Patent Wars
How to build enough  for the present but plan for the future
Science!
Scientific MethodIdea   Test   Conclusion
Idea•   Think about business priorities•   Think about user experience
Aside: Empathy•  Desinging a product isfundamentally empathetic exercise•   Think in your users’ minds•  Don’t let your te...
Test•   Minimum Viable Product•   Product: Viable Minimum
PVM•   Focus on Product first•  Focus on Viability to achieve thatproduct aim second•   Focus on minimalism last
Aside: Scale•   The scale of your tests will vary•  Lack of big tests means no greatgrowth or ideas•  Lack of small tests ...
Conclusion and Re-    evaluate•   Vital!•   Evaluation must drive next step
How does this solve  the problem?• Separates the analytical from theempathetic•   Focus on next step (Occam’s Razor)•   Do...
An Unusal Example:      Apple•  Focus clearly on product first: user experience, business priorities•  Focus on viability ...
Questions?• Ask me now?• Ask me later? • @chrisburnor • chrisburnor.com
Próximos SlideShares
Carregando em…5
×

Rocket-Powered Bicycles: Avoiding Over and Under Engineering Your Product

808 visualizações

Publicada em

Chris Burnor, Co-founder and CTO at GroupTie, explains how to avoid over- or under-engineering your product.

Publicada em: Negócios
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Rocket-Powered Bicycles: Avoiding Over and Under Engineering Your Product

  1. 1. Rocket Powered BicyclesAvoiding Over and Under Engineering your Product
  2. 2. Chris Burnor• GroupTie• StartupDigest• LinkedIn• DataDrivenSafety
  3. 3. Outline• What is a Product?• A Scientific Approach• An Unusual Example
  4. 4. The Problem
  5. 5. Over Engineering
  6. 6. Under Engineering
  7. 7. Why is this bad?It always pays to ask the questions no one else is
  8. 8. What is a Product?
  9. 9. Product connects business prioritieswith user experience
  10. 10. Product connects business prioritieswith user experience
  11. 11. So why is over/under engineering bad again?• Fails to realize business priorities• Fails realize user experience
  12. 12. Shouldn’t we plan for the future?
  13. 13. “Ay, there’s the rub”
  14. 14. Product is also a story• Idea• Market Validation• Traction• Market Dominance• Useless Patent Wars
  15. 15. How to build enough for the present but plan for the future
  16. 16. Science!
  17. 17. Scientific MethodIdea Test Conclusion
  18. 18. Idea• Think about business priorities• Think about user experience
  19. 19. Aside: Empathy• Desinging a product isfundamentally empathetic exercise• Think in your users’ minds• Don’t let your technical decisionsdrive your product• Let your product drive yourtechnical decisions
  20. 20. Test• Minimum Viable Product• Product: Viable Minimum
  21. 21. PVM• Focus on Product first• Focus on Viability to achieve thatproduct aim second• Focus on minimalism last
  22. 22. Aside: Scale• The scale of your tests will vary• Lack of big tests means no greatgrowth or ideas• Lack of small tests means too muchto do at one time• The measurement of scale is ‘doesthis test measure what we’re trying to
  23. 23. Conclusion and Re- evaluate• Vital!• Evaluation must drive next step
  24. 24. How does this solve the problem?• Separates the analytical from theempathetic• Focus on next step (Occam’s Razor)• Don’t lose sight of the vision
  25. 25. An Unusal Example: Apple• Focus clearly on product first: user experience, business priorities• Focus on viability second: It just works• Focus on minimalism third: No LTE, No RFID, no technolgies until ready
  26. 26. Questions?• Ask me now?• Ask me later? • @chrisburnor • chrisburnor.com

×