Copenhagen Lean Startup


Published on

Too afraid to fail? Maybe it's about time you fully embraced failure to achieve success!

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • Archive
  • Continutity
  • Security
  • Cloud Computing- Why are we really here and how can you make a success of it. •    Where are we now in the IT cycle and how did we get here? •    Why is Cloud so transformative? •    What are the key drivers behind the ROI from Cloud? •    What are the lessons learnt from moving to the Cloud and how should you approach it?

  • What is the aim of today?
  • The problem is 9 / 10 startups fail.
  • Because I have won and lost
    Lessons from the trenches
  • Learning to walk
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • Who is in the room?
  • Why do entrepreneurs do it?
  • Understanding what motivates you is key to mastering lean startup.
  • Experience?
  • Become Plan A
  • The problem is 9 / 10 startups fail.
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • Your goal is to capture customer value
  • The problem is 9 / 10 startups fail.
  • Normally a lack of customers not a failure of product
  • If they build it, they will come
  • There are two startup fallacies that cause that. 1- it is assumed the problem is known
  • And it assumes the solution is know.
  • The consequence is that costs are front loaded- launch is the goal. Not learning how to solve those issues. Startups have traditionally measured by users and revenue. “traction”
  • If you get it wrong- you really go up in style
  • It’s not about having a better plan A
  • It’s finding a better path to a plan that works
  • That is lean startup. But why is it important?
  • Until now, it’s been based on gut or intuition
  • This usually came out when you were pitching- investors would say “we’re looking for experienced entrepreneurs”. They’re looking for people who’ve made mistakes on other peoples money and can execute.
  • There has been no rigours process for stress testing a plan a- and that is what the lean startup framework provides
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • The AH HA Moment for me was that your ideas- especially the brilliant ones are JUST hypothesis
  • How do you know whether they are right or wrong? And lean startup is a methodology for testing these hypothesis
  • The F-85 was being beaten by the MiGs- they were technically superior to the F86’s
  • They needed a solution
  • Observe, Orient, Decide, Act. Remember- the number of cycles through the loop is key to success, not the quality of each iteration. Then apply lean manufacturing and you create the lean startup loop.

    OODA loop
    From Wikipedia, the free encyclopedia
      (Redirected from OODA Loop)
    The OODA loop (for observe, orient, decide, and act) is a concept originally applied to the combat operations process, often at the strategic level in both the military operations. It is now also often applied to understand commercial operations and learning processes. The concept was developed by military strategist and USAF Colonel John Boyd.
    1 Overview
    2 Application of the OODA loop
    3 See also
    4 References
    4.1 Notes
    4.2 Bibliography
    Diagram[1] of a decision cycle known as the Boyd cycle, or the OODA loop.
    The OODA loop has become an important concept in both business and military strategy. According to Boyd, decision-making occurs in a recurring cycle of observe-orient-decide-act. An entity (whether an individual or an organization) that can process this cycle quickly, observing and reacting to unfolding events more rapidly than an opponent, can thereby "get inside" the opponent's decision cycle and gain the advantage. Frans Osinga argues that Boyd's own views on the OODA loop are much deeper, richer, and more comprehensive than the common interpretation of the 'rapid OODA loop' idea.[2]
    Boyd developed the concept to explain how to direct one's energies to defeat an adversary and survive. Boyd emphasized that "the loop" is actually a set of interacting loops that are to be kept in continuous operation during combat. He also indicated that the phase of the battle has an important bearing on the ideal allocation of one's energies.
    Boyd’s diagram shows that all decisions are based on observations of the evolving situation tempered with implicit filtering of the problem being addressed. These observations are the raw information on which decisions and actions are based. The observed information must be processed to orient it for further making a decision. In notes from his talk “Organic Design for Command and Control”, Boyd said,
    The second O, orientation – as the repository of our genetic heritage, cultural tradition, and previous experiences – is the most important part of the O-O-D-A loop since it shapes the way we observe, the way we decide, the way we act.[3]
    As stated by Boyd and shown in the “Orient” box, there is much filtering of the information through our culture, genetics, ability to analyze and synthesize, and previous experience. Since the OODA Loop was designed to describe a single decision maker, the situation is usually much worse than shown as most business and technical decisions have a team of people observing and orienting, each bringing their own cultural traditions, genetics, experience and other information. It is here that decisions often get stuck,[4] which does not lead to winning, since
    In order to win, we should operate at a faster tempo or rhythm than our adversaries--or, better yet, get inside [the] adversary's Observation-Orientation-Decision-Action time cycle or loop. ... Such activity will make us appear ambiguous (unpredictable) thereby generate confusion and disorder among our adversaries--since our adversaries will be unable to generate mental images or pictures that agree with the menacing as well as faster transient rhythm or patterns they are competing against.[3]
    The OODA loop, which focuses on strategic military requirements, was adapted for business and public sector operational continuity planning. Compare it with the Plan Do Check Act (PDCA) cycle or Shewhart cycle, which focuses on the operational or tactical level of projects. [5]
    As one of Boyd's colleagues, Harry Hillaker, put it in "John Boyd, USAF Retired, Father of the F16" [6]:
    The key is to obscure your intentions and make them unpredictable to your opponent while you simultaneously clarify his intentions. That is, operate at a faster tempo to generate rapidly changing conditions that inhibit your opponent from adapting or reacting to those changes and that suppress or destroy his awareness. Thus, a hodgepodge of confusion and disorder occur to cause him to over- or under-react to conditions or activities that appear to be uncertain, ambiguous, or incomprehensible.
    Writer Robert Greene wrote in an article called OODA and You [7] that
    the proper mindset is to let go a little, to allow some of the chaos to become part of his mental system, and to use it to his advantage by simply creating more chaos and confusion for the opponent. He funnels the inevitable chaos of the battlefield in the direction of the enemy.
    [edit]Application of the OODA loop
    Consider a fighter pilot being scrambled to shoot down an enemy aircraft.
    Before the enemy airplane is even within visual contact range, the pilot will consider any available information about the likely identity of the enemy pilot: his nationality, level of training, and cultural traditions that may come into play.
    When the enemy aircraft comes into radar contact, more direct information about the speed, size, and maneuverability, of the enemy plane becomes available; unfolding circumstances take priority over radio chatter. A first decision is made based on the available information so far: the pilot decides to "get into the sun" above his opponent, and acts by applying control inputs to climb. Back to observation: is the attacker reacting to the change of altitude? Then to orient: is the enemy reacting characteristically, or perhaps acting like a noncombatant? Is his plane exhibiting better-than-expected performance?
    As the dogfight begins, little time is devoted to orienting unless some new information pertaining to the actual identity or intent of the attacker comes into play. Information cascades in real time, and the pilot does not have time to process it consciously; the pilot reacts as he is trained to, and conscious thought is directed to supervising the flow of action and reaction, continuously repeating the OODA cycle. Simultaneously, the opponent is going through the same cycle.
    How does one interfere with an opponent's OODA cycle? One of John Boyd's primary insights in fighter combat was that it is vital to change speed and direction faster than the opponent. This is not necessarily a function of the plane's ability to maneuver, rather the pilot must think and act faster than the opponent can think and act. Getting "inside" the cycle—short-circuiting the opponent's thinking processes—produces opportunities for the opponent to react inappropriately.
    Another tactical-level example can be found on the basketball court, where a player takes possession of the ball and must get past an opponent who is taller or faster. A straight dribble or pass is unlikely to succeed. Instead the player may engage in a rapid and elaborate series of body movements designed to befuddle the opponent and deny him the ability to take advantage of his superior size or speed. At a basic level of play, this may be merely a series of fakes, with the hope that the opponent will make a mistake or an opening will occur, but practice and mental focus may allow one to reduce the time scale, get inside the opponent's OODA loop and take control of the situation—to cause the opponent to move in a particular way, and generate an advantage rather than merely react to an accident.
    The same cycle operates over a longer timescale in a competitive business landscape, and the same logic applies. Decision makers gather information (observe), form hypotheses about customer activity and the intentions of competitors (orient), make decisions, and act on them. The cycle is repeated continuously. The aggressive and conscious application of the process gives a business advantage over a competitor who is merely reacting to conditions as they occur, or has poor awareness of the situation.
    The approach favors agility over raw power in dealing with human opponents in any endeavor. John Boyd put this ethos into practice with his work for the USAF. He was an advocate of maneuverable fighter aircraft, in contrast to the heavy, powerful jet fighters that were prevalent in the 1960s, such as the F-4 Phantom II and General Dynamics F-111. Boyd inspired the Light Weight Fighter Project that produced the successfulF-16 Fighting Falcon and F/A-18 Hornet, which are still in use by the United States and several other military powers into the twenty-first century.
    [edit]See also
    United States Air Force portal
    John Boyd (military strategist)           
    Control theory
    Decision cycle
    Maneuver warfare
    Nursing process
    Problem solving
    SWOT analysis
    ^ Boyd (1995)
    ^ Osinga, passim
    ^ a b Boyd
    ^ Ullman
    ^ Kotnour
    ^ Hillaker
    ^ Greene
    Boyd, John, R., The Essence of Winning and Losing, 28 June 1995 a five slide set by Boyd.
    Greene, Robert, OODA and You
    Hillaker, Harry, Code one magazine, "John Boyd, USAF Retired, Father of the F16", July 1997,
    Kotnour, Jim, "Leadership Mechanisms for Enabling Learning Within Project Teams" in Proceedings from the Third European Conference on Organizational Knowledge, Learning and Capabilities, Proceedings OKLC 2002
    Linger, Henry, Constructing The Infrastructure For The Knowledge Economy: Methods and Tools, Theory and Practice, p. 449
    Osinga, Frans, Science Strategy and War, The Strategic Theory of John Boyd, Abingdon, UK: Routledge, ISBN 0-415-37103-1.
    Richards, Chet, Certain to Win: the Strategy of John Boyd, Applied to Business (2004) ISBN 1-4134-5377-5
    Ullman, David G., “OO-OO-OO!” The Sound of a Broken OODA Loop, Crosstalk, April 2007,
    Ullman, David G., Making Robust Decisions: Decision Management For Technical, Business, and Service Teams. Victoria: Trafford ISBN 1-4251-0956-X
    Categories: Military terminology | Military acronyms | United States Air Force | Intelligence analysis | Strategy
  • Knowledge and creativity of individual workers
  • Shrinking of batch sizes
  • Just in time production
  • Acceleration of cycle times
  • Lean Manufacturing is a technique for constantly removing waste
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • When you bake them together you get:
  • We need to find the least expensive way to test your hypotheses.
  • MVP - In a great market -- a market with lots of real potential customers -- the market pulls product out of the startup.
  • If you’re not embarrassed by it- you’ve waited too long. Don’t worry- be crappy.
  • MVP’s test your hypothesis for Product market fit. Marc Andressen said: MVP - In a great market -- a market with lots of real potential customers -- the market pulls product out of the startup.
  • Achieving product/market fit requires at least 40% of users saying they would be “very disappointed” without your product.
  • What about Pivoting? It’s what you do when you’ve proved or disproved your hypothesis.
  • And focus on verifiable hypothesis
  • Some myths
  • Without them, you become stuffed with Politicians and salespeople
  • Some myths:
  • The problem is 9 / 10 startups fail.
  • And building on verifiable hypothesis
  • Lean Startup is a rigiorous process for iterating from plan a to a plan that works
  • Cloud Computing- Why are we really here and how can you make a success of it. •    Where are we now in the IT cycle and how did we get here? •    Why is Cloud so transformative? •    What are the key drivers behind the ROI from Cloud? •    What are the lessons learnt from moving to the Cloud and how should you approach it?

  • Copenhagen Lean Startup

    1. 1. pasukaru76
    2. 2. on2wheelz
    3. 3. tipiro
    4. 4. dolescum
    5. 5. neilalderney123
    6. 6. matthewbradley
    7. 7. minifig
    8. 8. mescon
    9. 9. Ronan_C
    10. 10. szeke
    11. 11. pasukaru76
    12. 12. cliff1066™
    13. 13. jeffc5000
    14. 14. spaceyjessie
    15. 15. sean dreilinger
    16. 16. Paolo Camera
    17. 17. sean dreilinger
    18. 18. Ben McLeod
    19. 19. Education isn’t magic. Education is the wisdom wrung from failure.
    20. 20. …people learn how to get it right by getting it wrong again and again.
    21. 21. cheesy42
    22. 22. quinn.anya
    23. 23. wwarby
    24. 24. pasukaru76
    25. 25. rondostar
    26. 26. Ev0luti0nary
    27. 27. kurichan*
    28. 28. Ronan_C
    29. 29. Daniel Mohr
    30. 30. Gueorgui Tcherednitchenko
    31. 31. Will Scullin
    32. 32. jeffc5000
    33. 33. bcymet
    34. 34. annethelibrarian
    35. 35. What did they start as game!
    36. 36. kurichan*
    37. 37. Joe Shlabotnik
    38. 38. jeffc5000
    39. 39. Matthew Burpee
    40. 40. wwarby
    41. 41. andrusdevelopment
    42. 42. army.arch
    43. 43. er1danus
    44. 44. Joi
    45. 45. paurian
    46. 46. EOI Escuela de Organización Industrial
    47. 47. NASA's Marshall Space Flight Center
    48. 48. Lean Startup is a rigorous process for iterating from Plan A to a Plan that works
    49. 49. The Goal of a Startup is to Figure out the right thing to build
    50. 50. niznoz
    51. 51. trochim
    52. 52. Nevada Tumbleweed
    53. 53. Annie Mole
    54. 54. Californian Em
    55. 55. Destinys Agent
    56. 56. andrusdevelopment
    57. 57. ckowalik
    58. 58. SteveMcN
    59. 59. RosieTulips
    60. 60. Вεη
    61. 61. Lean thinking defines value as providing benefit to the customer- anything else is waste Eric Ries
    62. 62. yvettemn
    63. 63. David Wulff
    64. 64. wwarby
    65. 65. surlygirl
    66. 66. Tom Raftery
    67. 67. Terry Wha
    68. 68. tnarik
    69. 69. NASA's Marshall Space Flight Center
    70. 70. andrusdevelopment
    71. 71. sasha Find the most effective way to validate your hypothesis
    72. 72. RaeA Minimum Viable Product
    73. 73. LostInInaka If You’re Not Embarrassed: You’ve Waited Too Long
    74. 74. toffehoff In a Great Market: The Market Pulls the Product Out
    75. 75. originallittlehellraiser Before Launch: the 40% Test. Are <40% Very Disappointed?
    76. 76. lovely fig rolls Pivoting?
    77. 77. Phillie Casablanca Change of Direction: Based on Validated Learning
    78. 78. Startup Pyramid: Nail it before you Scale it
    79. 79. Focus on Verifiable Hypothesis
    80. 80. Become Metrics Obsessed
    81. 81. Or Become Politicians and Salespeople
    82. 82. Some Myths:
    83. 83. wwarby Lean Startup is Not Cheap…
    84. 84. jeffc5000
    85. 85. Warren D It is Iterating FAST
    86. 86. David Wulff Build on Solid Foundations
    87. 87. True Startup Productivity is Systematically figuring out the right things to build Eric Ries
    88. 88. Buy the book!
    89. 89. pasukaru76