Balancing Features and Technical Debt: Effective Engineering Practices | Thanos Diacakis | 338

In this episode of SaaS Fuel, Thanos Diacakis shares battle-tested advice for scaling SaaS teams, streamlining delivery, and maximizing developer happiness. Drawing on his experiences at startups and tech giants like Uber, Thanos reveals counterintuitive strategies for improving software output, optimizing technical debt, rethinking backlogs, and harnessing new mental models. He breaks down the importance of incremental value, cross-functional collaboration, and avoiding the traps of over-planning. Whether you lead a small startup or an enterprise-scale engineering team, this conversation will challenge the way you think about speed, quality, backlog management, and long-term success.Key Takeaways 00:00 "Checklists vs Software Complexity" 03:19 Bug Fixing: Intuition vs Strategy 08:24 Buckets: Features, Bugs, Investments, Risks 09:47 Optimizing Feature vs. Platform Focus 14:39 "Minimize Work in Progress" 19:20 "Bug Backlogs: Input vs Output" 20:39 Kanban Team Structure Guidelines 26:38 "Rapid Progress in Coding Tools" 28:21 "Minimal Planning, Bias for Action" 31:48 "Delivering Incremental Customer Value" 36:23 Collaborative Workflow Over Silos 39:35 "Building Products That Inspire Use" 42:53 "Accelerate: Building Effective Teams" 44:11 Team Workflow Optimization Framework 47:50 "Explore Mental Models Online"Tweetable Quotes Why Slowing Down Software Releases Might Backfire: One of the things that would happen is if you slow down, how you ship to production is you'll have bigger batches and bigger batches, which means you might ship more bugs all at once and have to find them in a bigger QA cycle.  — Thanos Diacakis  "I also think we sometimes convince ourselves that we know more than we actually do and that we can plan a really long way out."  — Thanos Diacakis  Viral Product Development Mindset: "If you engage engineers and product in these creative discussions, you might find out, oh, I scoped out these 10 things, but turns out the customer gets 80% of the value from this one thing."  — Thanos Diacakis  Bureaucratic Bottlenecks in Big Companies: "They try to optimize locally for one particular function rather than optimize globally for shipping things out the door." — Thanos Diacakis  Viral Topic: "Why Every Team Should Read Accelerate": So I think if I give anyone advices, if you haven't read Accelerate, then go read that book. Because it's basically lays out in terms of, and this is in terms of like core technical and procedural sort of infrastructural things that teams ought to have to be productive. — Thanos Diacakis SaaS Leadership Lessons Bias Towards Action Over Perfection Avoid waiting for perfect plans, especially with innovative projects; instead, learn by doing and iterating. Increase System Visibility Make work in progress and team capabilities visible; this surfaces bottlenecks and areas for investment. Balance Short-Term and Long-Term Goals Strategic investment in tooling, tech debt, and risk mitigation ensures sustainable delivery and value realization. Prioritize Collaboration Across Functions Breaking down silos between product, engineering, and design dramatically accelerates delivery and reduces defects. Ship Small, Ship Often Frequent, incremental releases drive faster customer learning, boost agility, and reduce risk. Cultivate a Shared Language for Outcomes Use terms like investments and risk (not just features and bugs) to align business and technical priorities and drive meaningful...