In this episode of It Depends: Lessons in Technology Leadership, Kevin Goldsmith breaks down what it really means to craft a technical strategy that aligns your engineering organization with business goals. Drawing on decades of experience as a technology leader and CTO, he explains why simply having a plan in your head isn’t enough: a strategy must be documented, shared, and revisited regularly if it’s going to guide meaningful decisions.

Kevin outlines practical steps for building an effective strategy, including identifying business-aligned guiding principles, defining realistic technical bets, validating them with peers, and ensuring that every level of the organization maintains alignment. He also explores common pitfalls, including confusing strategy with a roadmap, making it too vague or too prescriptive, or failing to communicate it. He describes how a well-articulated strategy makes decisions easier, reduces friction, and gives teams greater autonomy and purpose.

It’s a clear, grounded guide for any engineering leader preparing for the new year, whether you’re a CTO shaping company direction or an EM ensuring your team’s work supports broader goals.

Avoiding shiny object syndrome, encouraging curiosity, and building a system for smart adoption

Every few years, a new wave of technology arrives promising to change everything. Right now, it’s generative AI, but it wasn’t long ago that we were saying the same thing about mobile, cloud, or Web3.

In this episode, Kevin Goldsmith reflects on how leaders can navigate emerging technologies without falling for the hype. Drawing from decades of experience adopting everything from public cloud to AI tooling, he shares how to evaluate what’s worth your team’s attention and when to wait.

Kevin outlines a practical framework for making technology decisions that stick: discover → experiment → evaluate → adopt deliberately. He also explores how to guide both the eager early adopters and the skeptical veterans on your team, turning curiosity into a disciplined system for learning and innovation.

In this episode, Kevin digs into the often-ignored side of engineering leadership: organizational design. He explores how structure shapes communication, culture, and even software architecture. Conway’s Law still applies. Kevin shares practical ways to diagnose bottlenecks, refactor teams, and evolve your organization with intent. From mapping the flow of work to understanding team topologies, this is a grounded guide to designing organizations that actually work.

Kevin Goldsmith revisits his influential 2013 keynote on engineering culture, expanding the conversation beyond just engineering teams to address anyone navigating workplace dynamics. This episode breaks down the real mechanics of how organizational values create culture, and how culture shapes everything from hiring decisions to performance reviews.

What you'll learn:

Drawing from his experiences at Microsoft, Adobe, and Spotify, Kevin shares both successes and failures in culture building, including why he stayed at some companies for years and left others. He offers practical frameworks for managers building strong team cultures and individuals seeking workplaces aligned with their values.

Whether you're a team lead trying to strengthen your engineering culture, an individual contributor evaluating your current role, or someone interviewing for new positions, this episode provides actionable insights for understanding and navigating the often-invisible forces that shape our daily work experience.

In this episode of It Depends: Lessons in Technology Leadership, Kevin returns from a summer break with a new podcast format and two big topics. First, he shares practical advice for navigating an unplanned career break—whether due to layoffs or a tough job market. From reframing “career break” on your résumé, to launching a consultancy, building a startup, or contributing to open source, Kevin outlines concrete ways to stay relevant, keep your skills sharp, and strengthen your positioning for the next opportunity.

Then he pulls back the curtain on what a CTO really does all day. Drawing on his experience at mid-stage startups, Kevin explains the balance between executive responsibilities, one-on-ones, cross-functional collaboration, strategic thinking, and even the occasional coding. He highlights how priorities shift depending on company size, culture, and market, and why visibility, prioritization, and time management are crucial at the executive level.

This episode blends career survival strategies with an honest look at senior leadership—helpful both for those navigating career uncertainty and those aspiring to the CTO role.

This is a repeat of an episode originally released on April 13, 2025

In this special episode, Kevin Goldsmith is joined by longtime friend and peer Kevin Stewart, SVP of Engineering at Splice, to challenge the familiar yet flawed narrative: that a team within a large company can "operate like a startup." Drawing on their shared experiences at Adobe and divergent paths through startups, they explore why innovation often stalls inside large organizations and what makes real startup environments fundamentally different.

This wide-ranging conversation explores culture, risk, incentives, and why resource contention, rather than imagination, hinders corporate innovation. Whether you lead a startup or a legacy company trying to move faster, this episode offers a valuable perspective.

This is a repeat of an episode originally released on March 2, 2025

In this episode of the "It Depends" podcast, host Kevin Goldsmith shares his unique experience designing Spotify's engineering career framework. As the leader of this initiative, Kevin provides a behind-the-scenes look at how Spotify's distinct career pathing system was developed, a system that reinforced its unique engineering culture rather than undermining it.

This is a repeat of an episode originally released on August 4, 2024.

Whether you're a tech leader navigating the post-COVID landscape or simply interested in the future of work, this episode provides actionable insights and practical advice for fostering successful distributed teams

links:

If you are on the technology management track, the final role is Chief Technology Officer. Still, the path to the role is not obvious because the role itself differs greatly from company to company. The episode includes chapter 10 from "It Depends: Writing on Technology Leadership 2012-2022," "Becoming a CTO." This chapter discusses the common skills needed for the CTO in almost any company and how the role differs between early-stage and mid-stage companies.

We discuss how critical failure is to innovation and how to handle it effectively. We discuss how software used to be written, Clippy, and why it was bound to fail. We also explore how Spotify utilizes the Think It/Build It/Ship It/Tweak It framework to build fail-safe products, and more.