{"id":27803,"date":"2023-03-28T06:47:18","date_gmt":"2023-03-28T10:47:18","guid":{"rendered":"https:\/\/www.3pillarglobal.com\/?p=25212"},"modified":"2024-10-02T12:44:48","modified_gmt":"2024-10-02T12:44:48","slug":"how-to-drive-outcomes-over-output","status":"publish","type":"podcast","link":"https:\/\/www.3pillarglobal.com\/insights\/podcast\/how-to-drive-outcomes-over-output\/","title":{"rendered":"How to Drive Outcomes Over Outputs, with Josh Seiden"},"content":{"rendered":"\nDo you know the difference between focusing on outcomes versus output in product development \u2014 and why the distinction can make or break a product? On this episode of The Innovation Engine<\/em>, we explore how shifting the focus from churning out features to driving business outcomes can help product teams deliver more value to users and have an infinitely greater impact for organizations.\n
\n
\nOur guest, Josh Siden, is a designer, strategy consultant, and the author of the book Outcomes Over Output: Why customer behavior is the key metric for business success<\/em><\/a>. \n
\n
\nThe inspiration for the book was the two years Josh spent working on a stock trading app for a major financial services company that just\u2026never shipped. The experience taught him the importance of delivering incremental value frequently and putting products in customers\u2019 hands \u201cunreasonably early,\u201d as he says during the episode.\n
\n
\nJosh draws on his experiences and lessons learned working on this product and many others as he highlights how product teams can work with senior leadership to jointly navigate the inherent uncertainty of product development.\n
\n
\nOne recommendation Josh has for product leaders is to use three \u201cmagic questions\u201d that will ensure they\u2019re focused on driving outcomes rather than falling into the trap of being a feature factory. He explains the importance of telling a specific story about the user journey, highlighting key moments that make a difference, and building a shared perspective and understanding to make collaborative prioritization decisions. Finally, Josh discusses the benefits of outcomes-based roadmaps vs. the traditional “roadmap to nowhere.” Unlike their predecessors, outcomes-based roadmaps provide context for why the team is focusing where they are and outlines the key questions the team is looking to answer and hypotheses they’re looking to validate.\n
\n
\nTune in to the full conversation below to hear valuable insights into how product development teams can shift their focus from a feature-based approach to a business outcomes-based approach, delivering greater value to both users and the organization.\n
\n
\n