Engineering Leadership in Turbulent Times Sarah Wells, Pat Kua & Daniel Terhorst-North

The podcast explores the distinctions between technical leadership and technical management, emphasizing that leadership involves inspiring teams and shaping vision, while management focuses on systems, resources, and accountability. It delves into strategies for organizational change, particularly in unstable or dysfunctional environments, advocating for leveraging existing instability ("organizational jiu-jitsu") and addressing systemic challenges through structured approaches like the "Three Threes Model." Career transitions into leadership roles are discussed, with anecdotes highlighting the shift from technical expertise to influencing systemic change, often requiring skills like stakeholder engagement, negotiation, and adaptability to ambiguity. The content underscores the importance of fostering high-performing teams, balancing technical and leadership responsibilities, and cultivating leadership in others through empowerment and shared ownership.

Key themes include the need for technical leaders to advocate for their teams visibility, use creative communication strategies (e.g., repetitive messaging, storytelling), and navigate resistance to change by aligning with individual motivations. It addresses challenges like managing technical debt, aligning product and technical priorities, and sustaining organizational culture through shared values and continuous improvement. The discussion also highlights the role of adaptability in navigating evolving tech landscapes, the importance of incremental progress in long-term planning, and the value of learning from external expertise or consulting to drive internal change. Practical frameworks, such as "Harvest and Amplify," are presented to scale effective solutions organization-wide, while Stoic principles guide leaders in focusing on controllable factors and managing trade-offs in large teams or complex systems.

• What if you apply the "Harvest and Amplify" strategy to your own project or team?

  • Move: Identify a small, effective solution your team has implemented (e.g., a tool, process, or code pattern) and actively promote it to other teams or stakeholders.
  • Why Now?: Organizations often overlook localized successes in favor of large-scale initiatives; amplifying these can build credibility and drive systemic improvement.
  • Expected Upside: Increased visibility for your work, faster adoption of proven practices, and potential recognition as a technical leader within your organization.

• What if you use the "Three Threes Model" to onboarding yourself into a new leadership or advisory role?

  • Move: Spend the first 3 hours listening to your team's challenges, the next 3 days fixing one immediate pain point (e.g., a broken build system or unclear process), and the first 3 weeks aligning on long-term goals (e.g., a roadmap for technical debt reduction).
  • Why Now?: Transitioning into leadership without context risks misaligned efforts; this approach ensures you address short-term friction while building trust for strategic change.
  • Expected Upside: A team that feels supported by immediate fixes and aligned with future aspirations, reducing churn and fostering collaboration.

• What if you create a "Testing on the Toilet"-style campaign to advocate for a technical initiative youre passionate about?

  • Move: Design a low-effort, repetitive, and creative campaign (e.g., a series of sticky notes with bullet points, a Slack bot reminder, or a visual infographic) to promote a specific practice (e.g., automated testing, code reviews, or CI/CD adoption).
  • Why Now?: Teams often ignore ideas that arent shouted from the rooftops; repetition in a distracting environment helps ideas stick.
  • Expected Upside: Higher adoption of the technical initiative, increased peer recognition, and a culture where small, persistent advocacy leads to measurable improvements.

• Implement the "Three Threes" Model for Role Transitions: Use the first 3 hours for active listening to understand team dynamics, the first 3 days to address immediate issues, and the first 3 weeks to align on long-term goals and system improvements. This structured approach helps solo operators smoothly transition into leadership or managerial roles while managing both urgency and strategic direction.

• Advocate for Technical Work with Visibility: Use repetition, creative communication (e.g., posters, internal campaigns), and external expertise (e.g., inviting industry leaders) to ensure your technical contributions are seen. Engineers often underestimate the need for visibility, but proactive advocacy is critical for influencing change and gaining recognition.

• Apply the "Harvest and Amplify" Strategy: Identify effective solutions within your team or projects (e.g., a successful code pattern or process) and promote them organization-wide. This helps scale technical excellence, build your personal brand, and establish credibility without needing formal leadership titles.

• Clarify Stakeholder Priorities Through Negotiation: Practice stakeholder engagement by aligning competing priorities across departments (e.g., product, marketing, engineering). Use structured negotiation techniques to secure time for critical work (e.g., debt reduction or system upgrades) while meeting business goals.

• Cultivate a Culture of Continuous Improvement: Encourage small, incremental actions (e.g., testing campaigns, documentation improvements) that solve immediate problems and foster learning. This builds momentum for larger changes, reinforces team ownership, and aligns daily efforts with broader strategic goals.