Leading Through Influence Without Knowing Everything

Why do the best developers often make the worst software architects? The skills that make someone a hero developer can become the habits that hold their team back once they move into architecture.

In this episode, Lee Atchison, software architect and author of “The Software Conductor”, explains what changes when you move from writing code to leading through other people. He shares why he rewrote his book three times before settling on a story format, and how the orchestra conductor analogy captures the architect’s role. Lee walks through the four ways architects fail in hero mode, the five questions a conductor asks that architects can use to spot problems early, and why most system failures are really broken connections between people. He also explains why architects should act as mentors who remove obstacles and offer a test for whether you taught or just decided. Finally, he shares his view on AI, why judgment matters more than any particular role, and why he expects the dark factory trend to fade.

Key topics discussed:

• Why the hero developer mindset fails in architecture roles
• The four ways architects fail when they stay in hero mode
• Five conductor questions that expose problems before they break
• Why most system failures are really broken team connections
• A simple test: can the decision be made without you?
• Why architects work with sand, not big rocks
• Why judgment matters more than role titles in the AI era
• Why AI-native apps should embrace non-determinism

Timestamps:

• (00:00) Trailer & Intro
• (02:53) What Is the Story Behind Writing “The Software Conductor”?
• (06:22) Why Do Promoted Heroes Struggle as Software Architects?
• (10:52) What Does a Fractional Software Architect Actually Do?
• (12:29) Is Software Architecture an IC or Management Path?
• (16:08) Do You Need to Know Everything to Lead with Influence?
• (18:08) What Are the Four Ways Architects Fail in Hero Mode?
• (21:06) What Five Questions Help Architects Spot Problems Before They Break?
• (25:57) Why Is Empathy at Scale a Crucial Skill for Software Architects?
• (29:34) Why Should Software Architects Act as Mentors Rather Than Dictators?
• (33:49) How Do Architects Manage Constant Context Switching?
• (37:37) Why Was AI Excluded from “The Software Conductor” Book?
• (40:24) Does AI Really Turn Every Software Developer into a Tech Lead?
• (44:34) Is AI Policy and Governance Part of the Software Architect Role?
• (48:41) What Are the Dangers of the AI Dark Factory Trend?
• (53:23) What Are the Most Important Aspects of Being an AI-Native Team?
• (57:52) 3 Tech Lead Wisdom

_____

Lee Atchison’s Bio
Lee Atchison is a software architect, author, and speaker focused on cloud computing, scalable system design, and the developer-to-architect transition. He is the author of Architecting for Scale (O’Reilly), Overcoming IT Complexity (O’Reilly), and The Software Conductor, and the creator of courses for O’Reilly Media and LinkedIn Learning. He writes the Software Architecture Insights newsletter and guest hosts on Software Engineering Daily. With three decades in the industry, including seven years at Amazon and AWS and eight at New Relic, Lee has worked with engineering teams at Nike, Disney, Starbucks, MLB, and Bank of America, and presented at AWS re:Invent and similar conferences. He works with organizations through his practice, Atchison Technology, and most recently served as CTO at Product Genius.

Follow Lee:

• LinkedIn – linkedin.com/in/leeatchison
• The Software Conductor – thesoftwareconductor.com
• Software Architecture Insights – softwarearchitectureinsights.com
• Personal Website – leeatchison.com

Like this episode?
Show notes & transcript: techleadjournal.dev/episodes/270.
Follow @techleadjournal on LinkedIn and Instagram.
Buy me a coffee or become a patron.