{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"How I Tested That","title":"Martin Eriksson | How I Tested The Decision Stack","html":"","width":"100%","height":180,"duration":2694,"description":"Summary\n\nIn this episode, I’m joined by Martin Eriksson, founder of Mind the Product and author of The Decision Stack, to talk about how organizations can make better decisions from strategy all the way down to everyday execution.\n\nWe talk about the difference between speed and velocity, why empowered teams still need strategic context, and how assumptions exist at every layer of an organization, not just inside individual products.\n\nWe also explore what AI changes and, maybe even more importantly, what it doesn’t. Building has become drastically faster and cheaper, but that doesn’t eliminate the need to understand the customer, the business, and whether or not you should be building something in the first place.\nIf you want to learn more about how strategic choices connect to everyday decisions and how assumptions can be tested throughout your organization you’ll love this episode.\n\nTakeaways\n\nSpeed without direction is not enough. Teams can build, ship, and test faster than ever, but without strategic alignment they may simply move in different directions more quickly. Martin frames this as the difference between speed, velocity, and organizational momentum.\nEmpowered teams still need strategic context. Autonomy works best when teams understand where the business is going, how it plans to get there, what matters now, and how their work connects to those choices.\nAssumptions exist at every layer of the organization. They are not limited to products or experiments. Vision, strategy, objectives, opportunities, and execution all rest on assumptions that can become dangerous when they remain unspoken.\nStrategy is a series of connected choices. The value of a decision stack is not just having vision, strategy, objectives, opportunities, and principles—it is making sure those decisions connect from the top down and can be traced back from everyday work.\nUse testing and discovery on strategic decisions, not only product decisions. Teams have become good at de-risking...","thumbnail_url":"https://img.transistorcdn.com/hRAQ0Cvexq2Nhl7H1KPLfxWZ14skSKkH4xG8JMRnoOM/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzUwMDU0LzE3MDg3/MTI0NTQtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}