{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Engineering Evolved","title":"The Product Thinking Framework","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/3709880e\"></iframe>","width":"100%","height":180,"duration":1745,"description":"Most engineering leaders would fail miserably as product managers. They'd get fired for shipping features nobody wants, ignoring user feedback, and measuring the wrong things. But here's the thing - your engineering team IS a product. And the techniques you use to build great products are exactly what you need to build a great engineering organization.In this episode, I break down the Product Thinking Framework: a radically different approach to engineering leadership that will change how you think about your team forever.In This Episode:Why most engineering improvements fail (and the shocking similarity to shipping features nobody asked for)The uncomfortable truth: Engineering leaders make decisions about tools and processes without understanding what engineers actually needReal story: The team drowning in infrastructure that thought they needed more people (spoiler: they didn't)Pillar One - Product Discovery for Engineering: How Engineering Office Hours helps you uncover what your team actually needsPillar Two - Customer Empathy: Why you should spend a full day working as an IC on your own team (quarterly)Pillar Three - MVP Approach to Infrastructure: How to cut any project down to a 2-4 week learning experimentThe microservices migration that would have cost millions (and what we did instead)The mindset shift: From manager to product manager - falling in love with problems, not featuresMeasuring outcomes (shipping speed, learning, enjoyment) not outputs (story points, commits)Common objections: \"My engineers don't know what they want,\" \"We need long-term thinking,\" \"I don't have time\"Real results: The team that went from 3-day deployments to 30 minutes without hiring anyoneKey Takeaways:1. Set up Engineering Office HoursOne hour per week, open attendance for any engineerFocus on discovery, not problem-solving in the sessionAsk: \"What's slowing you down?\" and dig deeper with \"Tell me more\"Share action items within 48 hours2. Shadow your engineers quarterlySpend...","thumbnail_url":"https://img.transistorcdn.com/PxMdoqfN_29mQkukm_nn1W_IIYV1IIAUO08NXqUzges/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wNTI4/MmI4OTJkZTVkNjZi/YTExNjA5ZTFlYjRm/M2U0NC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}