
It Depends: Lessons in Technology Leadership
by Kevin Goldsmith
Insights from recent episode analysis
Audience Interest
Podcast Focus
Publishing Consistency
Platform Reach
Insights are generated by CastFox AI using publicly available data, episode content, and proprietary models.
Est. Listeners
Based on iTunes & Spotify (publisher stats).
- Per-Episode Audience
Est. listeners per new episode within ~30 days
10,001 - 25,000 - Monthly Reach
Unique listeners across all episodes (30 days)
25,001 - 75,000 - Active Followers
Loyal subscribers who consistently listen
5,001 - 15,000
Market Insights
Platform Distribution
Reach across major podcast platforms, updated hourly
Total Followers
—
Total Plays
—
Total Reviews
—
* Data sourced directly from platform APIs and aggregated hourly across all major podcast directories.
On the show
Recent episodes
Becoming a Business Leader
Apr 26, 2026
30m 22s
Working with the CEO: Close Enough to Influence, Independent Enough to Be Honest
Apr 12, 2026
36m 06s
Don't Let Your Boss Do Your Job
Mar 29, 2026
26m 32s
Every Organization Is a System. Are You Designing It or Just Living in It?
Mar 15, 2026
37m 08s
The Director to CTO Path: How to Follow It, or How to Mentor It
Mar 1, 2026
41m 15s
Social Links & Contact
Official channels & resources
Official Website
Login
RSS Feed
Login
| Date | Episode | Description | Length | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 4/26/26 | Becoming a Business Leader | 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 four contexts where technical leaders either build this skill or fail to: P&L, sales and customer work, fundraising and investor relations, and strategy. This one is for senior engineering leaders eyeing an executive seat, current CTOs who want to stop being read as specialists at their own exec table, and anyone whose career has started to feel capped despite shipping well. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 30m 22s | ||||||
| 4/12/26 | Working with the CEO: Close Enough to Influence, Independent Enough to Be Honest | 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 to operators who are completely hands-off on tech, and why your approach has to change depending on which one you're working with. There's also an honest look at what happens when the relationship starts to erode, how to spot the warning signs on both sides, and when repairing it is worth the effort versus when it's time to go. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) "The Five Dysfunctions of a Team: A Leadership Fable" by Patrick M. Lencioni (Amazon Link) | 36m 06s | ||||||
| 3/29/26 | Don't Let Your Boss Do Your Job | 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 between ownership and accountability, and why "I was planning to handle it" doesn't count if you never said so out loud. He also gets honest about a trap he still falls into: being too busy to delegate the things he's too busy to do himself. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) Team of Teams: New Rules of Engagement for a Complex World, General Stanley McChrystal (Amazon Link) | 26m 32s | ||||||
| 3/15/26 | Every Organization Is a System. Are You Designing It or Just Living in It? | 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 mapping it, to understanding how it constrains and enables your teams, to intervening with awareness of cascading effects. Kevin shares a story about a time he built the right system but failed to communicate it to his peers, and what that cost him. He also talks about how AI is making systems thinking more urgent, because speeding up one part of your process without understanding the whole system just creates new bottlenecks. Whether you're a new manager trying to think more strategically or a senior leader who wants to get better at teaching this skill to others, this episode gives you concrete exercises you can try this week. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) Thinking in Systems: A Primer, Donella H. Meadows (Amazon Link) Management 3.0: Leading Agile Developers, Developing Agile Leaders, Jurgen Appelo (Amazon Link) | 37m 08s | ||||||
| 3/1/26 | The Director to CTO Path: How to Follow It, or How to Mentor It | 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 unfamiliar teams, to aligning your team's work with company strategy, even when the company is moving in a direction you didn't expect. Kevin also covers the mentoring side. If you're already a VP or CTO, how do you identify high-potential leaders and intentionally develop them? He talks about delegation, transparency, and giving feedback that's aimed at the next level, not just the current one. Whether you're a director trying to figure out what VP-level thinking actually looks like, or a CTO thinking about how to grow the leaders behind you, this episode gives you a concrete framework for both. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 41m 15s | ||||||
| 2/15/26 | Talking to Executives: That's Not a Derailment, That's the Meeting | 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, Context, Consequence, and Control. He also talks about why executives interrupt, why they sometimes just get up and leave, and why protecting your credibility matters more than protecting your ego. Whether you're presenting to senior leaders for the first time or trying to get better at it, this episode will help you walk in with more confidence and a better understanding of what's actually going on in the room. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 33m 19s | ||||||
| 2/1/26 | The Shift to Managing Managers | 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. Kevin covers the warning signs of overmanaging (managers escalating decisions that clearly belong to them, work slowing when you're unavailable), practical frameworks for delegating effectively, and why feeling indispensable is usually a red flag, not a success metric. A key test: Could you step away for two weeks? Would your managers make good decisions without you? If not, you might be the problem. Using Agile Techniques to Build a More Inclusive Team: https://www.youtube.com/watch?v=Atfxtk2Q90k Every Decision Creates a Policy: https://itdependspod.com/episodes/every-decision-creates-a-policy/ "Turn the Ship Around!: A True Story of Building Leaders by Breaking the Rules" by L. David Marquet: https://amzn.to/49XH2Ty Delegation Poker from Jurgen Appelo: https://medium.com/@jurgenappelo/unclear-team-responsibilities-use-delegation-levels-985537dbea38 Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) ConFoo 2026 (https://confoo.ca/en/2026) | 35m 50s | ||||||
| 1/18/26 | Leading What You've Never Done Before | 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 rely on depth. You’ll learn how to lead through intent, constraints, interfaces, and feedback loops, how to evaluate how decisions are made, not just what decisions were made, and how to stay accountable without becoming a bottleneck. Kevin also shares practical questions you can use in any domain, plus guidance on building trust with specialists, creating space for disagreement, and designing systems that consistently produce good outcomes. If your responsibilities are growing into areas you’ve never owned before, this episode will help you lead them with confidence, and without pretending to be the smartest person in the room. When, why, and how to stop coding as your day job talk: https://www.kevingoldsmith.com/talks/when-why-and-how-to-stop-coding-as-your-day-job.html Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) ConFoo 2026 (https://confoo.ca/en/2026) | 35m 27s | ||||||
| 1/4/26 | Success Makes You Dangerous: Why Comfortable Leaders Stop Growing | 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 group shrinks. The job gets easier because you've seen these problems before. And that comfort is exactly when autopilot kicks in, when you stop asking "why," and when you risk becoming less effective for the people who depend on you. The episode covers Kevin's personal reflection system: a twice-yearly strategic offsite, quarterly goal-setting, monthly calendar reviews, and weekly time-tracking. But he emphasizes you don't need to copy his process; you need to find what works for you and evolve it over time. He shares practical advice on starting small, making time when you feel too busy, and why the practice matters more than perfection. Reflection isn't about having it all figured out; it's about staying deliberate, adaptive, and intentional as a leader. Whether you're a new manager learning to step back from the work, a senior leader feeling too comfortable, or anywhere in between, this episode makes the case that you can't lead others to grow if you've stopped growing yourself. The Personal Strategy Offsite episode: https://itdependspod.com/episodes/the-personal-strategy-off-site/ Own Your Calendar episode: https://itdependspod.com/episodes/own-your-calendar-work-deliberately/ Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) ConFoo 2026 (https://confoo.ca/en/2026) | 24m 20s | ||||||
| 12/21/25 | The Right Amount of Process: Finding the Balance Between Chaos and Bureaucracy | 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 at Google or Amazon. The episode covers the warning signs of too little process (chaos, rework, unclear accountability) versus too much (bottlenecks, loss of autonomy, slow decisions), and why the size and culture of your organization fundamentally changes what works. Through real examples from his career, Kevin addresses common scenarios leaders face: the scrappy startup founder who resists process until the org becomes dysfunctional, the experienced big-company hire who imports heavy processes that crush a smaller team, and the risk-averse leader who adds gates after every incident. He explains the critical difference between enabling process (which helps teams move faster with confidence) and controlling process (which centralizes decisions and kills speed), and why involving your teams in process design dramatically increases adoption. Whether you're an engineering leader wondering if you're choking your team, a founder trying to scale without losing your speed, or a manager navigating the tension between autonomy and coordination, this episode gives you a strategic lens for making better decisions about when and how to add process, and when to remove it. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) ConFoo 2026 (https://confoo.ca/en/2026) | 44m 38s | ||||||
Want analysis for the episodes below?Free for Pro Submit a request, we'll have your selected episodes analyzed within an hour. Free, at no cost to you, for Pro users. | |||||||||
| 12/7/25 | Technical Debt Isn't the Enemy: A Strategic Framework for Engineering Leaders | 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 deeper organizational problems that code fixes won't solve). He explains how to identify each type and, more importantly, how to decide what deserves your team's attention and what doesn't. The episode explores why teams often struggle to get product support for addressing technical debt, how to tie debt decisions to business outcomes, and why some debt is actually a symptom of broken systems rather than poor engineering choices. Kevin shares real examples from his own career, including inheriting a monolith that had outlived its usefulness and intentionally taking on debt at Spotify to learn faster. Whether you're an engineering leader trying to prioritize what debt to fix, a product manager wondering why engineers keep talking about refactoring, or an executive trying to understand which debt threatens business outcomes, this episode provides a strategic lens for making better decisions about the inevitable trade-offs in software development. ConFoo 2026 (https://confoo.ca/en/2026) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 41m 15s | ||||||
| 11/23/25 | Demystifying Board Meetings: A CTO's Perspective | 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 board's composition, and the CEO’s style. He also explains the CTO’s role at the table, how technical topics are translated into business terms, why preparation is critical, and what junior employees often misunderstand about how decisions actually get made. If you’ve ever wondered what happens in those closed-door sessions—or you’re aiming for an executive role in the future—this episode gives you a clear and practical view of how board meetings work and why they matter. ConFoo 2026 (https://confoo.ca/en/2026) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 50m 52s | ||||||
| 11/9/25 | Crafting a Technical Strategy | 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. ConFoo 2026 (https://confoo.ca/en/2026) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 29m 39s | ||||||
| 10/26/25 | Making Technology Choices That Last | 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. ConFoo 2026 (https://confoo.ca/en/2026) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 42m 19s | ||||||
| 10/12/25 | The Hidden Architecture of Engineering: Practical Lessons in Organizational Design | 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. Architecture and Organization talk (https://www.kevingoldsmith.com/talks/architecture-and-organization.html) Reinventing Organizations by Fredric Laloux (https://amzn.to/43fwrRk) Team Topologies by Skelton/Pais (https://amzn.to/4nPHVDA) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net) Your host: Kevin Goldsmith (https://kevingoldsmith.com) | 47m 01s | ||||||
| 9/28/25 | Values → Culture → Everything: Why Company Culture Actually Matters | 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: The difference between stated company values and actual values (and a simple test to tell them apart) Why culture "eats strategy for breakfast" and how it can accelerate or sabotage company success How to build systems that reinforce positive culture through career ladders, hiring, and onboarding When and why firing for culture fit is necessary How to evaluate company culture during job interviews (especially what happens when companies face pressure) Why team culture vs. company culture tensions arise and how to navigate them What to do when company culture shifts rapidly due to acquisitions or leadership changes 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. Taking a Thoughtful Approach to the Job Search Process (https://itdependspod.com/episodes/taking-a-thoughtful-approach-to-the-job-search-process/) Building a Strong Engineering Culture Keynote https://www.kevingoldsmith.com/talks/building-a-strong-engineering-culture.html LeadDev New York (Use code KEVIN25 for 25% off registration) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 1h 04m 24s | ||||||
| 9/14/25 | How to Handle Career Gaps and What CTOs Actually Do All Day | Kevin returns with practical ways to turn an unplanned career break into momentum, then demystifies what a startup CTO actually does all day. | 46m 56s | ||||||
| 8/31/25 | ENCORE: The Myth of the Startup in a Large Company with Kevin Stewart | This is a repeat of an episode originally released on April 13, 2025In 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 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. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith The Guest: Kevin Stewart | 1h 06m 55s | ||||||
| 8/17/25 | ENCORE: Building a technical career path at Spotify | 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 organization. He emphasizes how career pathing must align with company values, as it directly influences what behaviors get rewarded and ultimately shapes your culture. The episode covers Spotify's collaborative approach to creating its "Career Steps" framework, involving representatives from across the organization rather than simply adopting another company's model. Kevin shares their guiding principles, including the crucial shift from focusing on achievements to behaviors, supporting specialists and generalists, and defining career growth by expanding spheres of influence. Whether you're a tech leader contemplating how to structure growth paths for your team or an individual contributor wondering how career frameworks influence company culture, this episode is a must-listen. It offers valuable insights into one of the most foundational aspects of engineering leadership, insights that are relevant and beneficial for both roles. LeadDev New York (Use the discount code “KEVIN15” for 15% off on your registration) Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 45m 38s | ||||||
| 8/3/25 | ENCORE: Addressing the challenges of partially distributed engineering teams | 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. 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: LeadDev New York Video and slides from Leading Distributed Teams The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith The newsletter | 34m 15s | ||||||
| 7/20/25 | ENCORE: Becoming a CTO | 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. Seattle's Got Tech Event at Seattle Startup Week LeadDev New York Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 36m 01s | ||||||
| 7/6/25 | ENCORE: Fail Safe, Fail Smart... Succeed! | 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. Seattle's Got Tech Event at Seattle Startup Week LeadDev New York Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 58m 51s | ||||||
| 6/22/25 | Why I Wrote a Book: A Meta Episode on Self-Publishing and DIY Business | 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: The real reasons tech leaders should (or shouldn't) write books Detailed breakdown of self-publishing vs. traditional publishing Specific tools and workflows: from WordPress to Word, ChatGPT for indexing, and recording audiobooks at home The business side: Amazon KDP vs. Ingram Spark, profit margins, and what actually sells Costly mistakes to avoid (spoiler: don't waste time on fancy tooling) How to promote without feeling like a sleazy self-promoter Perfect for: Anyone considering writing a book or starting a content business Tech leaders thinking about building their personal brand Entrepreneurs curious about the nuts and bolts of launching a creative venture Even if you never plan to write a book, Kevin's approach to learning a new business from scratch offers valuable lessons for any side project or career pivot. Plus, you'll get the honest truth about royalties, sales numbers, and whether it's actually worth the effort. This episode doubles as both a practical how-to guide and a case study in DIY entrepreneurship. Kevin's Gen X, do-it-yourself approach (honed from years running a record label) provides a refreshing alternative to the usual "scale fast or die" startup mentality. Seattle's Got Tech Event at Seattle Startup Week LeadDev New York Will Larson's Blog Post on self-publishing vs traditional publishing Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 45m 12s | ||||||
| 6/8/25 | Answers That Depend: Tech Leadership Q&A Part 3 | 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. Finally, he addresses a thoughtful question about advocating for accessibility and inclusive design in fast-paced startup environments. Kevin provides actionable advice on how individual contributors can influence technical strategy, make the business case for accessibility, and demonstrate measurable impact even when leadership views frontend work as "just making things pretty." Throughout the episode, Kevin emphasizes that context matters in every decision, offering nuanced perspectives rather than one-size-fits-all solutions. Whether you're a staff engineer trying to drive collaboration, a technical leader scaling an AI platform, or an IC passionate about inclusive design, this episode delivers practical insights for navigating complex organizational challenges. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 42m 02s | ||||||
| 5/25/25 | Answers that Depend: Tech Leadership Q & A pt 2 | Host Kevin Goldsmith responds to six listener questions covering common leadership and career challenges in technology organizations. Episode Content: 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 specific weekly questions and bullet journaling methodology. Organizational Change Management - A manager struggles with department heads who verbally commit to transformation initiatives but show limited follow-through. Kevin addresses the brutal reality that sometimes personnel changes are necessary when key people resist required organizational shifts. Technical Debt vs. Immediate Delivery - A healthcare technology professional faces pressure to implement quick patches while advocating for proper architectural redesign. Kevin emphasizes the importance of understanding business context and having frank discussions with leadership about trade-offs. Early Career Overwhelm - A junior data engineer, hired as the first data person at a startup, feels overwhelmed balancing immediate requests with infrastructure foundations. Kevin provides perspective on realistic expectations for junior professionals and the importance of focusing on current competency over long-term planning. Product-Engineering Team Dynamics - A product team leader experiences friction with engineering counterparts who prioritize their roadmap over product initiatives. Kevin identifies this as a fundamental structural issue, advocating for unified backlogs and shared accountability between product and engineering functions. The episode offers direct, sometimes blunt advice about leadership realities, emphasizing practical frameworks over theoretical approaches. Kevin shares specific processes he uses personally and addresses the difficult decisions leaders must sometimes make. Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6 The book: It Depends: Writing on Technology 2012-2022 Your host: Kevin Goldsmith | 42m 48s | ||||||
Showing 25 of 61
Sponsor Intelligence
Sign in to see which brands sponsor this podcast, their ad offers, and promo codes.
Chart Positions
2 placements across 2 markets.
Chart Positions
2 placements across 2 markets.
