Show Notes
Etienne sits down with Adam Bahret, whose unique journey has fueled his passion for creating robust product designs that can outperform the competition. The conversation reveals how prioritizing reliability can significantly impact a product's success and why reliability often trumps marketing. Tune is as Adam introduces his innovative R-Three blueprint which balances cost, features, and risk to ensure successful product launches without regrets. He also discusses the often overlooked issue of technical debt in software development, emphasizing the importance of early risk assessment. With his insights being drawn from his book Devastate the Competition: How to Take Market Share through Robust Design, he aims to connect product development with achieving business objectives, and he and Etienne engage in insightful dialogue about the challenges and solutions in reliability engineering. They discuss Adam's experiences living in Denmark and the cultural differences that shaped his approach to learning and working in engineering. Their conversation also touches on the differences between reliability and quality, illustrating how these concepts play important roles in the design and manufacturing processes. Adam also highlights the importance of using proper methods for early risk assessment, ensuring a more dependable final product. He shares his creative approach to making reliability concepts accessible to everyone through comic book guides, aimed at simplifying complex tools and techniques. Listen in to gain valuable insights into how robust product design can lead to dominating the market, the significance of balancing multiple factors in product development, and practical tips for incorporating reliability engineering principles across various industries! Time Stamps:[1:29] - Adam, born in New York, now lives in Boston after working in Denmark for two years.[3:54] - Adam shares how he pretended not to understand Danish so that a homeless person switched to English for spare change.[5:00] - Learn where the title of Devastate the Competition comes from.[6:17] - Adam explains the concept of reliability engineering.[8:48] - Quality ensures consistency in manufacturing, while reliability creates robust designs for durable, useful technology.[10:00] - Adam touches upon why he wrote Reliability Culture and why he wrote Devastate the Competition.[13:07] - Adam aims to prevent regrets in product development by establishing processes for wise, efficient decisions.[14:46] - Adam explains his R-Three blueprint.[16:50] - Adam emphasizes the importance of product ratio factors in decision-making.[18:24] - Adam suggests prioritizing robust design for proactive decision-making and smoother processes.[21:29] - It’s important to align individual goals with overall business objectives for success.[24:00] - Etienne discusses how individuals in different roles prioritize their incentives, possibly leading to deviations from the intended path.[25:10] - Adam advocates for measuring "time to reliability" for better decision-making.[28:54] - Adam explains the sawtooth pattern in software reliability curves.[31:00] - Reduce software bugs by identifying and eliminating infrequently used code through script scanning.[32:02] - Hear how Adam simplifies reliability concepts via comic books, aiming to make fundamental tools more accessible.[35:20] - Adam explains why he finds the term HALT (Highly Accelerated Life Test) misleading.[37:26] - Adam compares reliability tools to car controls, advocating for their accessibility and understanding.[39:13] - Etienne discusses technical debt, emphasizing the trade-offs made in software development for faster time to market.[41:21] - Where can listeners reach Adam? We have 200+ CTOs in peer groups: Quick Testimonials Video Contact Etienne: Website / YouTube / LinkedIn / X / Instagram / The CTO Podcast WebsiteContact Adam: Website / Instagram / LinkedInAdam's Books: Devastate the Competition / How Reliable Is Your Pro
More from The CTO Podcast
“We’re not doing software development anymore. We’re engineering a factory.” That single line from Matt Ferguson captures a fundamental shift happening in technology leadership. As CTO of Roof Maxx—a nationwide roofing brand with 385 dealerships—Ferguson has spent the past year transforming how his team builds software. The methodology he’s championing isn’t new, but its implications in the age of AI are profound. It’s called Document-Driven Development. And if you’re still measuring your engineering team by lines of code, you may be optimizing for the wrong century. The Cost of Software Is Collapsing Ferguson opens with a provocative claim: “The cost of software goes to zero.” He’s quick to acknowledge this is a euphemism—a deliberate exaggeration meant to spark conversation. But the directional truth is harder to dispute. When a team that once needed 100 engineers can now accomplish the same work with 10, or when the same team can produce 10x the output, the economics of software fundamentally change. “If they’re not taking into consideration the risk of their business when the cost of software goes to zero,” Ferguson says of potential vendor partners, “then they’re not gonna be a partner in two years because they’re gonna be out of business.” The data on AI-assisted coding tells a more nuanced story. A recent randomized controlled trial from METR found that experienced developers were actually 19% slower when using AI tools—despite believing they were 20% faster. Meanwhile, studies from GitHub and Microsoft show gains of 20-55%, with the strongest improvements among junior developers tackling well-defined tasks. The takeaway isn’t that AI doesn’t help. It’s that how you use it matters enormously. And that’s where Document-Driven Development enters the picture. What Is Document-Driven Development? At its core, Document-Driven Development flips the traditional software process. Instead of diving into code and documenting later (or never), teams invest heavily upfront in requirements, specifications, and architectural documentation—then use AI to generate code from those artifacts. “Our document-driven development is the concept of writing down what you want to do, what your problem is that you want to solve, in a descriptive enough way that the AI can interpret and plan the work, and through that plan can execute the code,” Ferguson explains. The approach has been championed by Ryan Vice, CEO of Vice Software, through his DocDD.ai methodology. GitHub recently validated the concept with their “Spec-Driven Development” toolkit, and AWS published their “AI-Driven Development Lifecycle” framework—both emphasizing documentation as the critical input to AI-assisted coding. Ferguson’s team has taken this further than most. His developers now spend roughly 90% of their time writing and refining requirements, and only 10% reviewing code. “Documents are your new code,” he says. “Treat them like code, put them in your GitHub repository as code, and iterate on them as your source code.” The Goal: One-Shot Code Generation The ambition behind Document-Driven Development is what Ferguson calls “one-shotting” the code—generating production-ready software on the first attempt. “We’re not here to pull the old slot machine and see what we get,” he explains. “Oh, all jacks. That’s wonderful. Oh, we didn’t win that one. Try again. Until AI gives us the right answer. That’s not what we’re after.” This stands in stark contrast to “vibe coding”—the practice of giving AI a rough prompt and iteratively debugging whatever emerges. Ferguson sees this as a recipe for unreproducible results and mounting technical debt. “If you’re not putting time into governance and you’re giving everybody free reign to do whatever they want,” he warns, “you’re gonna get different results. And when you try to build that piece of software six months from now, you might get a different result—which is not acceptable.” The key insight is that the “one shot” doesn’t mean one
In this conversation, Nishant interviews Kathy Keating, Etienne de Bruin, and Scott Graves, co-authors of LIQUID: How CEOs and CTOs Unlock Flow and Momentum in Complex Systems. They discuss how the idea for the book was born, the challenges of co-authoring as three CTOs, and how they shaped the narrative through the fictional characters Alice (CEO) and Theo (CTO). The authors share how their distinct voices and strengths fused together: Scott’s deep knowledge of complex adaptive systems, Kathy’s operational lens, and Etienne’s ability to simplify and communicate concepts. Together, they created a framework that blends philosophy, practice, and story. The conversation highlights the importance of seeing organizations as complex adaptive systems and the risks of companies becoming either “boiling” (chaotic) or “frozen” (rigid). The authors emphasize that true leadership comes from navigating toward liquidity, the state where flow and adaptability are preserved. They reflect on the critical role of CEO-CTO partnership, the necessity of boundaries, and the difficulty of shifting culture once it stagnates. They also explore why the timing of LIQUID is especially relevant today. As technology accelerates, craft alone is not enough. Leaders must become sense-makers and problem-solvers at the systems level. About the Book LIQUID takes readers inside the hidden systems that drive every organization. Using the fictional journey of Alice, a founder-CEO, and Theo, her engineer-turned-CTO, the book shows how teams often slide into boiling chaos or frozen rigidity without realizing it. By illustrating the patterns of complexity through story, the authors make abstract concepts tangible and immediately useful. At its core, LIQUID argues that the most important role of the CTO is not simply delivering technology but stewarding the entire system so that people and processes remain in flow. The book introduces accessible frameworks, practical language, and vivid scenarios that help leaders spot when their organizations are shifting out of balance and how to guide them back to a liquid state. Whether you are a CEO, CTO, or executive navigating rapid change, LIQUID is a blueprint for unlocking resilience, adaptability, and momentum in your company. It bridges systems thinking with real-world leadership and equips you to see and influence the invisible dynamics that make or break technology organizations. Time Stamps 00:00: Introduction: Why LIQUID matters now02:00: Behind the authors: creativity, systems, and personal lenses07:00: Discovering each other’s strengths during the writing process13:00: Pivoting the book: from frameworks to storytelling17:00: The origin story: from CTO failures to systemic insights23:00: Defining the role of the CTO in complex systems28:00: Why now: AI, accelerated change, and systems thinking33:00: The 7CTOs connection and levels of complexity40:00: Why Alice and Theo: storytelling as a teaching tool46:00: Subjective perspectives in complex systems52:00: The hidden world of complexity and CTO boundaries59:00: CEOs and CTOs as co-sensemakers1:04:00: Simple versus complex language in leadership communication1:12:00: Culture as the hardest complexity to shift1:20:00: Coaching example: boiling versus frozen organizations1:28:00: The CEO’s challenge: orchestrating boundaries1:31:00: Partnership, empathy, and trust at the executive level1:33:00: If LIQUID had a soundtrack LIQUID: LinkedIn / Website Contact Nishant: LinkedInContact Etienne: Website / YouTube / LinkedIn / X / Instagram / The CTO Podcast WebsiteContact Kathy: Website /LinkedInContact Scott: Website / LinkedIn
RSVP to the 13th CTO Colloquium on 4/17/25 In this episode, Steven Zgaljic, CTO of Jahnel Group, joins host Etienne de Bruin to share a personal story about his daughter’s health challenges. Faced with the need to meticulously track symptoms and daily activities, Steven leveraged his technical expertise to create a custom AI-powered solution using tools like N8N and Superbase. The conversation highlights how AI can transform complex problems into actionable insights, even in personal contexts. Steven discusses the challenges of using traditional methods like pen and paper for symptom tracking, leading him to build an automated workflow integrated with Slack. By applying AI for data validation and pattern recognition, he gains real-time insights into potential triggers and patterns in his daughter's symptoms. Beyond his personal use case, Steven reflects on the broader applications of AI in problem-solving and the necessity of human oversight in AI-driven systems. This conversation explores the intersection of personal challenges, technological innovation, and the potential of AI to improve lives. Timestamps 00:00 Introduction and Overview 01:00 Steven Zgaljic's Background and Family Story 03:00 Challenges with Tracking Medical Symptoms for His Daughter 05:00 Using Slack for Family Communication 07:00 Applying AI to Track and Analyze Symptoms 09:00 Exploring N8N, Superbase, and AI for Automation 11:00 Creating Validation Models for AI Accuracy 13:00 Building a Custom AI System for Health Tracking 15:00 AI Insights and Pattern Recognition in Health Data 17:00 Future Plans for AI Health Analysis 18:00 Reflections on AI in Problem Solving We have 200+ CTOs in peer groups: Quick Testimonials Video Contact Etienne: Website / YouTube / LinkedIn / X / Instagram / The CTO Podcast WebsiteContact Steven: Website /LinkedIn Great news! The CTO Podcast has been featured on Feedspot's list of Top CTO Podcasts. Huge thanks to our amazing guests and listeners for being part of these conversations. Check out the full list here: Feedspot’s Top CTO Podcasts.
In this episode of the CTO Podcast, host Etienne speaks with image strategist Zayna Rose about the importance of personal branding and leadership presence for technology leaders. They discuss how visual identity, color psychology, and intentional self-expression can enhance a leader's credibility and connection with others. Zayna emphasizes the need for tech leaders to be mindful of their appearance and how it impacts their professional image, while also encouraging them to embrace their authentic selves. The conversation highlights practical tips for improving one's image and the significance of digital presence in today's world. Time Stamps 00:00 Introduction to the CTO Podcast and Guest Zaina Rose 03:06 Understanding Leadership Presence 05:29 The Importance of Visual Identity 09:55 Casual Power Looks for Tech Leaders 12:18 Strategic Wardrobe Levels 16:30 Choosing Colors That Work for You 21:17 Tailored vs. Standard Looks 23:38 Experimenting with Self-Expression 30:14 Leveraging Digital Assets for First Impressions 34:33 Practical Steps for Improving Personal Branding 38:42 Enhancing Stage Presence and Communication 42:45 Closing Thoughts and Call to Action
In this episode of the CTO Podcast, host Etienne de Bruin speaks with Lena Skliarova-Mordvinova, CTO and Co-Founder of the Good Face Project. They discuss the origins of the Good Face Project, which aims to educate consumers about the ingredients in personal care products and promote safer alternatives. The conversation delves into the role of generative AI in analyzing ingredient safety, the challenges of navigating the venture capital landscape, and the importance of parenting in the digital age. Lena shares her insights on balancing technology and family life, as well as cultural perspectives on parenting from her experiences in Ukraine. In this conversation, Lena shares her experiences navigating the challenges of leading a tech team in Ukraine during the ongoing war, highlighting the resilience and determination of her team. She discusses the importance of maintaining a sense of normalcy and connection amidst chaos, the innovative tech stack they are using in AI, and the complexities of regulatory environments in the personal care industry. Additionally, she reflects on her passion for space research and the evolution of data mining technologies. Time Stamps 00:00 Introduction to the CTO Podcast and Guest 03:01 The Good Face Project: Origins and Mission 06:01 Understanding Ingredients: The Science Behind Personal Care 08:53 Generative AI in Personal Care: Innovations and Challenges 12:12 Venture Capital Landscape: Navigating the Hype 15:07 Parenting in the Digital Age: Balancing Technology and Family 21:04 Reflections on Parenting: Learning and Growing Together 26:56 Cultural Perspectives on Parenting: A Global View 34:03 The Power of Connection in Uncertain Times 39:14 Resilience Amidst Chaos: The Ukrainian Experience 45:09 Innovations in AI: Tech Stack and Models 53:39 Navigating Regulations in Personal Care and Supplements 01:02:22 Passion for Space: A Journey Through Research We have 200+ CTOs in peer groups: Quick Testimonials Video Contact Etienne: Website / YouTube / LinkedIn / X / Instagram / The CTO Podcast WebsiteContact Lena: Website /LinkedIn