{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Product Engineering Podcast","title":"Outcome Driven Engineering Explained","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/5455a149\"></iframe>","width":"100%","height":180,"duration":925,"description":"What changes when you stop giving an engineering team features to deliver and instead give them an outcome to achieve?\nIn this episode of The Product Engineering Podcast, James explores Outcome-Driven Engineering: an operating model where product managers and engineers share accountability for creating measurable product impact.\nRather than starting with a predetermined solution, an outcome-driven team starts with the change it wants to see in customer behaviour or the product. The team then works together to understand the problem, decide how success will be measured, experiment with possible interventions and learn from the results.\nIn this episode\nWhat an outcome actually means in Product Engineering\nThe difference between delivering a feature and delivering an outcome\nExamples including basket abandonment, product engagement and feature adoption\nWhy Product Engineering is a cross-functional team model, not simply a job title\nHow product managers and engineers retain different skills while sharing the same measure of success\nWhy individual engineering metrics shouldn't replace team-level outcome accountability\nHow an outcome-driven team moves from an outcome to measurement, experimentation and delivery\nWhy you should decide how you'll measure success before you build\nUsing prototypes and small interventions to test ideas quickly\nHow learning can cause a team to refine, change or even abandon its original outcome\nWhy shipping software is only part of the job — the real question is whether anything changed\nThe central idea is simple: instead of asking a Product Engineering team “What did you ship?”, ask them “Did you drive the outcome?”\nNext episode: Accountability — how to create an accountability structure that matches the kind of work a Product Engineering team is doing.\nFind out more at doproductengineering.com.","thumbnail_url":"https://img.transistorcdn.com/tOpN0tMoB9dtDg__O2XafuXKrZuomc_ze_mLWYIpO7A/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS83Mjc4/NGQwOThhMzkyZGVm/ZmFjYmQ3N2NkMDcz/YWNlYS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}