Inspired: how to create tech products customers love

<!-- START_TEMPLATE --> <ul> <li> Source: </li> <li> Tags: </li> </ul> <!-- END_TEMPLATE --> <ul> <li> title: Inspired: how to create tech products customers love </li> <li> authors: Marty Cagan </li> <li> year: 2018 </li> </ul> <p> Has some interesting insights on how product teams need to be organized to be the best versions of themselves. </p> <p> Topics that I found interesting: - <a class="wikilink" href="/product_vision_and_product_strategy/"> Product vision and product strategy </a> - <a class="wikilink" href="/product_vision/"> Product Vision </a> - <a class="wikilink" href="/okr_for_product_management/"> OKR for product management </a> - <a class="wikilink" href="/roadmaps_for_product_development/"> Roadmaps for product development </a> - Understanding the <a class="wikilink" href="/minimum_viable_product/"> minimum viable product </a> as a <a class="wikilink" href="/minimum_viable_prototype/"> minimum viable prototype </a> . - Defining <a class="wikilink" href="/who_are_product_stakeholders/"> who are product stakeholders </a> and bring this back to the product team. If the product teams delivers and then there's a veto, trust of the product team will be eroded ( <a class="wikilink" href="/build_trust_in_a_team/"> build trust in a team </a> ). The <a class="wikilink" href="/product_manager/"> product manager </a> needs to be sure to understand the constrains and work towards finding <em> solutions </em> . - Communicating product learnings along the way. What worked and (especially) what didn't work. It needs to be concise and short, probably handled by VP Product during all-hands meetings (with different cadences). </p>