It Depends: Lessons in Technology Leadership

A CTO needs to hire more engineers, and the numbers are working against the argument. Engineering spend has fallen as a share of revenue because the company grew faster than the team, so on paper it looks like efficiency. In practice, one resignation could sink the roadmap. Kevin Goldsmith's advice was to stop arguing from within and examine the organization as an acquirer would.

Kevin has led due diligence as an acquirer at large companies and startups, and he's been examined as a target through acquisitions and investor rounds. From both seats, the same pattern keeps showing...

A vendor the security team wanted, budgeted two years in a row, and never actually bought. When Kevin Goldsmith finally tried to spend the money, his CFO asked what the ROI was, and he didn't have an answer good enough to win the argument. Not long after, a new board arrived and told him he was underinvesting in cybersecurity. Same company, same customers, same risk, completely different verdict.

Every technology leader owns budgets where the best possible outcome is that nothing happens. Security, compliance, reliability, backups, disaster recovery. They're the easiest money in the company to cut...

A developer builds a working replacement for an internal platform over a weekend using AI tools, then asks leadership why they can't ship it on Tuesday. The code is clean, the architecture is real, and the team is confused about the holdup. Kevin Goldsmith explores what happens when AI-powered development speed outpaces the organizational guardrails that once kept teams aligned.

This episode explores the tension between team autonomy and organizational coherence in an era when building software has become dramatically faster, but deciding what to build has not. Kevin draws on Spotify's aligned autonomy model, his own...

The spreadsheet says building is cheaper now, and the spreadsheet isn't wrong. A vendor's annual license on one line, a couple of developers and some tokens on the other. What that comparison leaves out is that building has always had two costs, and AI only made one of them smaller.

Kevin has spent most of his career firmly on the buy side, with a mantra he gave his teams for years: don't invent things that already exist. This episode is him revising that position rather than abandoning it, and being specific about how much smaller the revision...

Chapter 3 from It Depends: Writing on Technology Leadership 2012-2022

In this episode, we discuss my experience building an exercise to better understand what is important to me in a role or company, and how I used the results to prepare for job interviews. I also discuss some of the mistakes people make when interviewing for roles during a downturn, particularly in how they present themselves. If you're currently looking for a job, or think you will in the future (we all will), this episode will be helpful.

Some links:

This chapter discusses what you can do as a manager to protect your team from layoffs: Ensure the team is aligned with company goals. Raising the visibility of the good work of the individuals on the team. Managing performance. All of these things will help when someone is deciding whether anyone on your team should be laid off. This episode provides more information for individuals and explains that managers are judged more by their team's work and less by their own contributions.

Links:

Teams create their own languages organically, which is essential to team bonding and belonging. Understand this and use it to improve how your team works together and make onboarding new members easier.

Links:

A room full of managers agrees on a better way to do something. Everyone nods. Six months later, every team is still working exactly the way it did before. The idea was sound. Nobody had to change, so nobody did.

That gap is the subject of this episode: driving change across teams you don't manage and can't order around. Kevin Goldsmith calls it managing sideways, and it runs on influence without authority, one of the most useful leadership skills and one of the hardest to build. He works through why the two obvious moves, forcing it yourself...

Some of the most valuable people in any company are those who consistently deliver. Their teams are healthy, the feedback is good, and the reward for all that reliability tends to be the same thing every time: more work, rarely more authority. Kevin Goldsmith calls this the reliable team trap, the point where being trusted to execute quietly stops translating into being trusted to decide.

Kevin works through why it happens, drawing on seven years he once spent running a project that kept succeeding without ever advancing his own career, plus two leaders he currently mentors whose...

Most leadership advice is about how to have a hard conversation. Far less of it is about when. In this episode, Kevin Goldsmith argues that the when is usually where things break, and that the conversations leaders end up regretting are rarely the difficult ones they had. They're the easy ones that they kept postponing until they weren't easy anymore.

This episode makes the case for the earlier, smaller, cheaper version of every difficult conversation, the one most leaders talk themselves out of by insisting they don't have enough information yet. Kevin draws on two of his...

Have you noticed that every conversation in tech leadership now circles back to AI, and that none of those conversations actually feel resolved? That's because AI adoption is not a tooling problem. It is an organizational redesign happening in real time, whether you lead it or not.

In this episode, Kevin gets off the fence about a topic he has been deliberately avoiding. He walks through how his thinking about AI in engineering organizations has evolved over the last two years, and introduces a four-layer model for understanding where AI adoption actually breaks down: tooling, process, structure...

Most technical leaders assume the path to executive is paved with more technical excellence. It isn't. At a certain level, the ceiling stops being technical and starts being about business fluency, and that ceiling is invisible until you've hit it.

In this episode, Kevin walks through the shift that CTOs, VPs, and directors need to make to actually lead at the executive level, and why the skills that got them there are the ones they have to partially unlearn. He shares a framework he calls the four moves of business fluency (translate, trade off, commit, compound) and...

The CTO-to-CEO relationship is the highest leverage relationship in your career as a technology leader, and it's the one where getting the balance wrong has the biggest blast radius. You need to be close enough to influence, independent enough to be honest, and aligned enough to execute even when you disagree. Most people get at least one of those wrong.

This episode lays out a framework for building CEO trust around four foundations: competence, candor, commitment, and context. It also gets into the different types of CEOs you'll encounter, from founder-developers who still have strong technical opinions...

Your boss doesn't step into your area because they want to micromanage. They step in because nobody said "I got it," and silence looks the same as not paying attention. This episode is about the ownership behavior that separates leaders who are trusted to run their area from leaders whose bosses keep checking in.

Kevin introduces the Ownership Triangle (Signal, Route, Verify), a simple loop that works at every level from engineering manager to CTO. He talks about the lesson his CEO taught him at his first CTO job about catching problems before they escalate, the difference...

Have you ever felt like you're solving the same problems over and over, just in different forms? That's usually a sign you're working transactionally, fixing what surfaces instead of addressing the structures underneath.

In this episode, Kevin tries to do something he should have done a long time ago: actually teach how to develop systems thinking. He's talked about its importance plenty of times on the show, but he realized he'd never given people a practical path to build the skill. So he lays out a four-stage progression, from learning to see the system around you, to...

The path from Director to CTO isn't a single ladder. It's a gradual expansion across three dimensions: your focus widens from your team to the company to the industry, your orientation shifts from execution to operations to strategy, and your technical breadth grows from narrow specialist to broad generalist.

In this episode, Kevin maps out what that progression actually looks like at each level, drawing on his own career through Adobe, Spotify, and multiple startups. He shares practical ways to develop the skills you need before you need them, from taking finance people to lunch and shadowing...

Have you ever had an executive interrupt your presentation and completely take the conversation somewhere you weren't expecting? That's not a derailment. That's the meeting.

In this episode, Kevin talks about executive communication from both sides of the table. Early in his career, he learned the hard way that being right doesn't matter if you're not being understood (a Microsoft VP made sure he never forgot that lesson). Now, as a CTO, he watches people make the same mistakes he did.

Kevin shares a practical framework for communicating to executives: the Four C's of Clarity...

Moving from managing individual contributors to managing managers requires a fundamental shift that many leaders struggle with. In this episode, Kevin shares lessons from his own difficult transition, where staying too close to the work actually limited both his team's growth and his own.

The core challenge isn't autonomy versus control. It's leverage versus comfort. When you focus too far down into your organization, you become an information bottleneck, your managers lose ownership, and your own leadership growth stalls. The job fundamentally changes: your leverage no longer comes from making decisions, but from providing context.

...

Leading What You’ve Never Done Before is an episode about a leadership challenge almost everyone hits as they grow: your scope expands faster than your resume.

Most technology leaders start out managing what they already know, then suddenly find themselves responsible for domains they’ve never personally practiced. That can feel exposing, especially if you built your credibility as “the expert.” In this episode, Kevin breaks down why trying to become the expert in every new area is a trap, why ignoring unfamiliar teams is even worse, and what effective leadership looks like when you can’t...

In this episode, Kevin tackles a paradox that most leaders don't see coming: the moment you get comfortable in your role is often the moment you stop improving. Drawing on his decade as a CTO, he explains why success and experience can become dangerous if you're not deliberately reflecting on how you work, why you make the choices you make, and where your blind spots might be hiding.

Kevin breaks down why reflection isn't optional for senior leaders. At the C-level, you don't get much feedback or development; you're expected to figure it out yourself. Your peer...

In this episode of It Depends: Lessons in Technology Leadership, Kevin Goldsmith tackles one of the most contentious topics in growing companies: process. Drawing on decades of leadership experience from IBM and Microsoft to Spotify and Adobe, he explores why process is neither inherently good nor bad; it's a tool that must fit the problem you're solving.

Kevin introduces a practical framework for deciding when to add process and when you have too much. He explains how to identify the coordination problems you're actually trying to solve and find the lightest-weight solution, rather than copying what works...

In this episode, Kevin tackles one of the most misunderstood topics in software development: technical debt. Drawing on his experience at Microsoft, Spotify, and early-stage startups, he challenges the common assumption that all technical debt is bad, explaining why healthy teams intentionally take on debt as part of shipping software effectively.

Kevin introduces a practical four-part framework for understanding technical debt: pragmatic debt (taken on deliberately to validate ideas or meet constraints), required debt (that directly impacts reliability, security, or delivery capability), incidental debt (stable, low-risk code that's safe to ignore), and symptomatic debt (a signal of...

In this episode, Kevin breaks down what really happens inside a company board meeting: why they exist, what gets discussed, and why they carry so much weight for an executive team. Drawing from a decade of attending and presenting in boardrooms across startups and later-stage companies, he explains the board’s role as the company’s oversight body and why each quarterly meeting functions like a performance review for the entire organization.

Kevin covers how boards think about risk, strategy, financial performance, and leadership effectiveness, and why these dynamics can shift depending on the company’s stage, the bo...

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 ever...

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...

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:

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. Dra...

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

In October 2025, I will once again be speaking at the Lead Dev New York event. Registration and information are available here. You can use the discount code “KEVIN15” to receive 15% off your registration.

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 throug...

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.

Kevin explains the delicate balance of timing when implementing a career framework. Waiting too long (as Spotify did) can cause problems, but implementing too early can stifle a growing o...

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

In this episode of the It Depends podcast, host Kevin Goldsmith delves into the complexities of managing partially distributed engineering teams.

Kevin discusses the nuances of communication, collaboration, and culture in partially distributed teams, emphasizing the unique challenges that arise when some team members work remotely while others remain in the office. He highlights his experiences at companies like Adobe, Microsoft, and more, offering valuable lessons on effective management strategies and the importance of maintaining human connections in a digital work environment.<...

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.

This is a repeat of an episode originally released on April 28, 2024.

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.

This is a repeat of an episode originally released on January 20, 2024.

In this season finale, Kevin pulls back the curtain on his entire book-writing and self-publishing journey. What started as a collection of blog posts became "It Depends: Writing on Technology Leadership, 2012 to 2022" – but why go the DIY route instead of working with a traditional publisher?

You'll learn:

In this third and final Q&A episode of the season, Kevin addresses three challenging questions that many tech leaders face daily. First, he delves into the tension between competitive performance review systems and collaborative culture, drawing on his own experience at Microsoft to explain why some systems actively discourage the teamwork they claim to promote.

Next, Kevin explores how to balance innovation with product roadmap commitments, and whether guild structures can help break down team silos while fostering technical creativity. He shares practical strategies for channeling brilliant engineering ideas into strategic objectives without derailing quarterly deliverables.<...

Host Kevin Goldsmith responds to six listener questions covering common leadership and career challenges in technology organizations.

Learning and Development on Limited Resources - A team lead in Lagos asks about fostering continuous learning without access to expensive training programs. Kevin discusses free resources, including conference talks on YouTube, vendor training materials, online courseware, and strategies for organizing local meetups and knowledge-sharing sessions.

Personal Retrospective Systems - An SRE professional in Portland seeks structured approaches for personal leadership reflection. Kevin details his multi-layered system: weekly, monthly, quarterly, and bi-annual review processes, including his...

In this first post-book Q&A episode, host Kevin Goldsmith dives into the real challenges tech leaders face daily, answering questions from listeners around the globe.

The episode unpacks several critical leadership dilemmas:

Luca from Milan asks how to maintain clear accountability while fostering cross-functional collaboration in a matrix organization. Kevin provides practical advice on balancing engineering ownership with product and design partnerships, revealing how to avoid the common pitfalls of siloed thinking without sacrificing sprint commitments.

Tatiana, a data science leader from Estonia, presents two thought-provoking questions. First, how can technically-oriented leaders...

In this episode, Kevin shares the final chapter of It Depends: Writing on Technology Leadership, focusing on what it takes to grow with a scaling company, or recognize when it’s time for new leadership. Drawing on his real-world experience, he discusses succession planning, self-awareness, and cultivating a culture that fosters growth at every stage.

In this special episode, Kevin Goldsmith is joined by longtime friend and peer Kevin Stewart, SVP of Engineering at Splice, to challenge the familiar but flawed narrative: that a team inside a big 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 touches on culture, risk, incentives, and why resource contention, not imagination, derails corporate innovation. Whether you lead a startup or a legacy company trying to move...

In this episode of the "It Depends" podcast, host Kevin Goldsmith discusses the lessons learned from creating Spotify's Technology Career Steps framework. Kevin shares insights from his experience leading the effort to build a structured career path for Spotify's technology team, discussing the process's challenges and successes.

The episode covers key topics such as balancing behaviors versus achievements in career growth, the importance of aligning career pathing systems with company culture, and the complexities of integrating the framework with compensation. Kevin also reflects on how Spotify's technology-driven culture influenced the approach and how the company's evolution affected...