Product Fit Lecture 3 H4D Stanford 2016
•Als PPTX, PDF herunterladen•
1 gefällt mir•30,965 views
This document discusses factors that can cause solutions to fail due to poor product fit. It identifies several reasons why solutions may be too big, heavy, incorrectly shaped, or durable. Additionally, it notes solutions can fail due to being too complex for a user's needs, or due to improper or lack of integration. The document contrasts individual versus group decision making and available data versus time constraints. It closes by listing additional barriers like users' inability to envision solutions, lack of user input, champions, costs of change, single purpose products, and poor training.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Product Fit Lecture 3 H4D Stanford 2016
Ähnlich wie Product Fit Lecture 3 H4D Stanford 2016 (20)
Mehr von Stanford University
Mehr von Stanford University (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Product Fit Lecture 3 H4D Stanford 2016
- 1. Product Fit Doing the right thing the right way This work is licensed under a Creative Commons Attribution-Non Commercial 4.0 International License
- 2. What causes a solution to fail? • Size – too big • Weight – too heavy • Form Fit – “just not right” • Durability – in the conservative estimate of the user • Complexity – in the user’s cognitive ecosystem • Integration - too early or not at all
- 3. Forward Operating Base (FOB) Observation Post (OP) Mission Planning UAS Aviation Route Clearance Security Patrol Logistics Patrol Mission Planning UAS Route Clearance Security Patrol Logistics Patrol Battlefield Calculus
- 4. • Multiple minds vs one mind • Computer power vs brain power • Available data vs time to make a decision • Peripheral vision vs tunnel vision • Single point of failure vs multiple points of failure • Multiple paths to success vs single path to success Looking for conflict?
- 5. What else gets in the way? • Users don’t know what they want until they see it • Problem solvers who don’t listen to users • No champion on the ground • Cognitive cost of making a change • One trick ponies and a lack of integration • Inability to scale (vendor, suppliers, contracts, $) • Poor training (not the 1st time, but the 2nd & 3rd)
- 6. Questions?
Hinweis der Redaktion
- Battlefield Calculus shows how two identical sounding missions (and their inherent problems) are actually radically different based on what echelon of force executes them, by the size of force, their location, even by how well they are trained. In this example the challenges and proposed solutions to logistics operations for a large base (Forward Operating Base) are completely inappropriate for that of a small base (Observation Post). Despite the obvious, people still try to deliver "one-size-fits-all" solutions. To properly insure a solution is actually used it is important to become familiar with the pattern of life of the user and their unit.
- Slide 4 - Looking for Conflict. This is the list of places to look for conflict between what may have been provided to solve a similar problem and the solution you are about to recommend. Are the circumstances similar? Or are their a myriad of conditions present that will invalidate what was a good solution under different circumstances? I've presented on this slide a list of places to look for that conflict.