The document discusses how to take a lean approach to product development. It notes that teams are often asked to build products based on inconsistent requirements without clear performance metrics. It advocates adopting a lean process of creating minimum viable products, testing assumptions through experiments, continuously improving based on user testing and metrics, and designing solutions that are relevant to the current context but can adapt over time. The key aspects of lean highlighted are challenging assumptions, setting measurable goals, iterating through testing, and designing for an ideal future state while accounting for real-world constraints.
3. Some of our guidelines
≒build!for!every!scenario!!
≒inconsistent!requirements!
≒stakeholder!vs.!user!needs!
≒too!many!features!
≒no!key!performance!metrics!
7. Good intrapreneurs take baby steps,
reframe things, and are subversive.
≒ask!inquisiUve!quesUons!!
≒support!data!for!idenU鍖ed!
problem!
≒gaps!between!the!current!
system!and!the!idealized!state!
≒create!smaller!smart!goals!
9. From Build this to How can
we measure success?
≒Declare!assumpUons!
≒IdenUfy!constraints!!
≒Understand!the!current!ecoQ
system!
≒DemocraUze!the!product!
vision!
14. Lean is not about action, assumptions
or jumping to conclusions.
15. Lean is about
making things actionable.
≒ All!designed!elements!should!challenge!
assumpUons!
≒ Benchmark!success!with!measurable!
goals!
≒ Iterate!with!MVP!test!builds!and!assess!
feedback!
≒ The!idealized!design!thrives!and!adapts!
within!a!complex!system!