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)

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)

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)