{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Medtech Innovation Podcast","title":"His Secret To Keep Tech Debt From Killing Your Team","html":"","width":"100%","height":180,"duration":3229,"description":"I'm joined by Ryan Schoonmaker, Founder & CEO at Tight Line Solutions, as we explore why growth-stage medtech teams burn out fixing past shortcuts, the two-roadmap discipline almost nobody actually runs, and how to lead engineering through five-alarm fires without breaking your team.\nIn this episode, we dive deep into:\nWhy \"Tight Line\" Is the Right Mental Model for Product Development\n→ Ryan named the company after fly fishing — keeping the right line tension is the instinct great engineering leaders have\n→ Too much tension snaps the team, too little and the program gets away\n→ That nascent expectation level inside a team is rarely written down but drives everything\nCutting Your Teeth at Helbling and Dexcom\n→ Weekly client work at Helbling forced Ryan to communicate engineering decisions, not just make them\n→ Dexcom G6 and G7 taught him that wearable medtech lives or dies on integration points between hardware, firmware, software, and human factors\n→ \"Killer questions\" like battery size or PCB footprint can flip your entire architecture if you don't surface them early\nThe Two-Roadmap Playbook Most Growth-Stage Medtech Misses\n→ Run an iterative roadmap on the product just launched AND a separate technology roadmap five years out\n→ Biggest misstep: putting unproven technology into V1 instead of shipping fast and learning from users\n→ V1 should generate revenue, expose failure modes, and feed Gen 2 — trying to make V1 perfect kills companies\nThe Stairstep Regulatory Strategy Sophisticated Founders Use\n→ Get something cleared, then use it as your own predicate via special 510(k) or letter to file\n→ While FDA reviews your initial submission, your team iterates Gen 2 in parallel\n→ Ryan's seen this used to dodge a de novo pathway when one feature would have triggered it\nDon't System-Architect Yourself Out of Cost Reductions\n→ Most teams assume they'll automate their way to better COGS later — a $750K assembly cell and a year of capex\n→ A smarter Gen 2 with fewer...","thumbnail_url":"https://img.transistorcdn.com/SKJTlzh1Dih_UjWAMpaf9asEOJluhYL_CM3FATuVvVc/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yM2U1/NjA3NjAzY2M1NDA0/ZDZkYTRiY2Y3Mjky/MTRmNi5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}