In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss the importance of having an implementation plan in software development. They emphasize the role that written plans play in fostering collaboration and scaling projects. Through a candid conversation originally recorded in the summer of 2024, they dive into the nuances of translating business requirements into code, the core competencies required for engineering leaders, and best practices for creating effective implementation plans.

The episode also addresses common challenges engineers face, such as decision paralysis and the reluctance to share early ideas, while offering strategies for overcoming these hurdles. The hosts also share a comprehensive checklist for determining when a written implementation plan is necessary, touching on topics like schema changes, new technologies, and coordination across teams. The importance of a supportive, feedback-rich culture in engineering teams is highlighted as a key factor in successful project execution.

• 00:00 Introduction to the Podcast
• 00:48 The Core Skill in Software Development
• 02:29 Coaching Engineers on Implementation Plans
• 04:06 The Importance of Written Implementation Plans
• 06:02 Challenges and Solutions in Implementation Planning
• 09:57 Creating a Collaborative Culture
• 18:11 Guidelines for Formal Implementation Plans
• 23:09 Conclusion and Call to Action
• 23:34 Outro and Credits

Resources:

• How Many CTOs Pod: https://howmanyctospod.com
• Scott Porad: https://www.linkedin.com/in/scottporad/
• Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/