The CTO Playbook

What if the biggest impact you have as a leader isn’t the strategy you set, but the signals you leave behind in every interaction?Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.In this episode, Paul Kinkaid, a former British Army officer, founder of Forensic Outcomes, and executive leadership coach, introduces a principle from forensic science: every contact leaves a trace. Those small moments, the way you listen, the way you respond, the way you make decisions, shape how your leadership is experienced across an organization.The focus is on the smallest behaviours that most leaders overlook, and how those behaviours shape trust, culture, and performance.Leadership isn’t just about decisions or strategy. It’s about the signals you send every day.You’ll Learn:[00:00] Introduction[00:06:02] What leadership presence is and why people listen before you speak[00:09:10] Why pressure exposes the difference between real and performative leadership[00:12:04] How small behaviours shape trust, clarity, and psychological safety[00:21:36] What happens when leaders send the wrong signals without realizing[00:34:12] Why the gap between intention and impact grows over time[00:48:27] How communication patterns shape culture more than strategy[01:02:14] What it takes to notice and shift the signals you sendResources Mentioned:Locard Exchange Principle by Saferstein, R., et al. | ArticleGet Paul’s book, Forensic Leadership, in print or audiobook and start noticing the signals you’re sending every day. Find more from Paul on LinkedIn, and visit his DactoApp landing page at Forensic Outcomes.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

What if the most dangerous thing we build as leaders is certainty?Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.Today, I sit down with fellow technology leader Joe Thompson, to examine how ethical technology leadership shows up in the smallest day-to-day decisions, not the mission statements. A CTO mindset shifts once it becomes clear that the products being shipped shape how people work, think, and feel long after the roadmap is finished. Responsibility enters the work through a design-led lens that starts with user research and carries through product strategy grounded in usability, accessibility, and cognitive load.Earlier in my career, optimizing metrics felt sufficient. That belief changed after seeing software become a primary work tool for thousands of people who had little choice but to live inside it every day. Tech for good emerges here as a leadership posture rather than a side initiative, rooted in intention, influence, and awareness. Digital transformation sharpens that responsibility further, with the power to narrow or expand who technology truly serves as analog channels steadily disappear.If you’re navigating scale, pressure, and trade-offs as a technical leader, this episode is an invitation to slow down, ask better questions, and lead with impact rather than assumption.You’ll Learn:[00:00] Introduction[03:01] Why design-led products start with user research, not features[04:27] How optimizing for one metric creates invisible usability and accessibility debt[07:12] When you realize your software becomes someone’s full-time work environment[23:04] Why teams ship products without thinking through real-world user impact[29:18] How engagement algorithms shape behavior and quietly reward harmful patterns[31:07] What ethical leadership looks like without lecturing or moral grandstanding[35:02] Why AI feels revolutionary while productivity barely moves[42:21] Where tech leaders should start when thinking about impact and responsibility[47:00] How values, influence, and intent guide better technology decisionsResources Mentioned:No Silver Bullet Essence - Accident in Software Engineering by Brooks F. | ArticleYou can connect with Joe and his work through his LinkedIn here.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

What if the strongest part of your engineering organization isn’t your tech stack, but the culture you protect every day? Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.In this episode, I’m joined by CTO Pasha Jam, who has grown an engineering team from three people to 110, expanded internationally, and navigated company acquisitions while keeping culture a central focus. We define what a healthy engineering culture looks like, and why it consistently outperforms strategy and process.Culture became a priority after working in environments that were difficult to enjoy, even when the products and compensation were strong. Psychological safety is explored through the lens of engineering teams, including the ability to ask questions, raise risks, challenge decisions, and fail without fear.Culture’s impact on hiring, onboarding, and communication across teams in multiple countries is explored, along with why people who leave often say they miss the culture and sometimes choose to return.If you’re responsible for engineering teams and want to think more intentionally about culture, leadership, and long-term team health, this episode offers practical perspective grounded in lived experience.You’ll Learn:[00:00] Introduction [05:18] Why job dissatisfaction often traces back to culture instead of pay or products[06:42] What psychological safety looks like when engineers challenge decisions without fear[11:07] How empowerment leads teams to take ownership without being pushed[24:21] Why fixing incidents together matters more than assigning blame[28:36] How putting people before process changes commitment and delivery[30:14] Why micromanagement quietly erodes trust and culture[33:09] What it looks like when leaders carry culture forward without seeking credit[35:27] Why culture must evolve as teams scale and contexts changeResources Mentioned:Agile Manifesto | WebsiteNeed car repairs but not the upfront cash? If you're in the UK, get approved in seconds and pay interest‑free over time, apply with Bumper today and stay on the road.You can connect with Pasha Jam on his LinkedinFind more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

Most CTOs fail not because of bad decisions, but because they stop asking why.Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact. In this episode, I sit down with Massimo Belloni, Head of Machine Learning and Data Science at Docplanner, to discuss what real technical leadership looks like when the answers aren’t obvious.We dig into bold CTO leadership, why engineering leadership is mostly about people, and how curiosity in leadership builds trust faster than authority ever will. Massimo shares hard-earned lessons from leading ML teams across industries, and why the job isn’t about being the smartest person in the room, but creating conditions where teams thrive.If you’re navigating CTO mindset shifts, managing high-performing engineering teams, or feeling the quiet weight of imposter syndrome in tech leadership, this conversation will land. We talk about invisible leadership work, asking better questions, and why progress only makes sense in hindsight.Iif you’re leading through complexity and change, this episode is your reminder: certainty isn’t the goal, clarity is.You’ll Learn:[00:00] Introduction[02:14] How Massimo realized leadership is about people, not technical mastery[05:48] Why trying to be the smartest person in the room backfires[09:37] What changes when you lead systems you don’t fully understand[13:22] Why most leadership problems aren’t actually technical[17:54] How asking why builds trust faster than giving answers[22:41] Why strong teams come from safety, not fearlessness[27:36] How invisible leadership work compounds over time[33:18] The question Massimo uses to measure leadership progress[38:47] Why leadership only makes sense in hindsightResources Mentioned:The CTO Playbook episode on The Key Relationship That Drives Startup Growth with Steven Renwick | Spotify or AppleSteve Jobs Stanford Commencement Speech | YouTubeYou can connect with Massimo on LinkedIn and learn more about his work on his substack here.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

What if the biggest challenge in scaling your organization isn’t execution, but knowing where you actually are?Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.In this episode, I sit down with James Webster, former Amazon engineer and founder of Sheep CRM, to unpack a deceptively simple idea that cuts through years of confusion around operational maturity. James introduces his Three Mountains model, a practical way for CTOs to assess reality without ego, optimism, or wishful thinking.We talk about what CTO leadership really looks like during hypergrowth, why engineering leadership breaks when teams skip stages, and how misaligned expectations quietly derail even strong organizations. Drawing from James’s experience inside Amazon and years working with scaling teams, we explore why clarity beats speed, and why naming constraints honestly is a leadership advantage, not a liability.If you’re navigating startup scaling, leading teams through change, or trying to align technology with business reality, this conversation will help you reset your internal compass.This episode is about perspective, precision, and building from where you are, not where you wish you were.You’ll Learn:[00:00] Introduction[01:08] Why scaling fails when leaders misread where they actually are[02:21] How Amazon hypergrowth reshaped James Webster’s view of pace and pressure[03:37] Why constant role change breaks traditional playbooks[14:26] Why thinking too far ahead undermines real transformation[41:12] How repeated problems signal when process really matters[42:18] Why “sloppy” processes beat perfection early on[43:34] How optimism bias keeps leaders from seeing reality[47:09] Why losing your position on the map becomes dangerous at speed[48:22] How choosing the right problem changes everythingYou can connect with James on LinkedIn and learn more about his work on his website here.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

What if your team's biggest problem isn't talent, it's the rules you've never written down? Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.In this episode, I'm talking with Gerald Chablowski, a lead developer based in Thailand whose journey from archaeology and history into tech leadership gives him a very human lens on engineering. I’m drawn to the way he thinks less about shiny tools and more about how people organize themselves, how rules get explained, and how work actually feels. His experience leading teams across different countries and cultures makes him obsessed with one question: what happens when we use structure to protect humans instead of control them.Too many engineering teams are playing a game where nobody can see the rulebook, then wondering why everything feels chaotic. Here we get brutally honest about what happens when goals change every week, when leaders “delegate” but still pull every string, and when trust gets treated like a slogan instead of something you earn in tiny daily moments. You’ll hear how simple constraints like clear rules, small pull requests, and real documentation can unlock creativity instead of killing it, especially in environments where people are scared to challenge the plan. You’ll Learn:[00:00] Introduction[03:48] Why tech only matters when it serves people, not the other way around[06:19] What happens when a team works without clear rules or shared understanding[09:14] The reason trust is built through tiny daily behavior, not speeches or titles[11:47] How unclear systems force developers into chaos even when rules technically exist[14:52] Why documentation becomes leverage when knowledge needs to outlive individuals[17:01] The leadership mistake that made a senior dev refuse to work with him[23:08] What learning hard physical skills teaches about leadership discomfort[28:19] How asking people to rewrite a task in their own words exposes hidden gaps fast[34:22] Why tiny pull requests transform code quality when systems enforce them[42:08] How relying on juniors teaches humility and system thinking faster than doing it all yourselfYou can connect with Gerald and his work on his LinkedIn.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

What if your calmest moment showed up in the middle of a crisis?Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.I'm joined by Caroline Elliott, who has made life and death calls in avalanche rescue and now brings that same rescue mindset into high pressure corporate teams. She trained in mountain rescue as a ski patroller, then joined an elite unit in France as a dog handler working avalanches, rubble, gas explosions, and large area searches. In this episode, I pull her mountain stories into the world of tech leadership so you can see what avalanche work can teach us about leading under pressure. We get into what happens to your body when a crisis hits and your team reads every signal you send. I want you to notice how a brief reset and calm language can turn spikes of stress into something you can grow from. And you'll see why staying just a little calmer than the room can change everything when the pressure hits.You’ll Learn:[00:00] Introduction[04:12] Why the body’s first response to crisis can shut down your ability to think clearly[09:47] How a three-second reset changes the entire tone of a high-pressure moment[14:58] The reason stress spreads through a team faster than any words you say[21:36] What happens when leaders use calm language to anchor people who are already overwhelmed[27:44] How a simple breathing sound becomes a reliable reset for staying functional under pressure[33:51] A dog’s reaction in avalanche rescue reveals how humans read stress signals from leaders[39:22] The surprising link between positive reinforcement and team performance when stakes are high[46:05] What shifts inside a team when leaders stay just slightly calmer than the room[51:10] Why caring for your people becomes the deciding factor in whether they’ll stay through hard seasonsResources Mentioned:Fjord’s Mountain Mission: Avalanche Safety Children’s Book by Caroline Elliott | BookYou can connect with Caroline on Instagram or through her website here, where she is happy to do an intro call to discuss how she can help your team.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.

What if the real bottleneck isn’t people or tech but the thing between them?Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact. In this episode, I’m joined by Michael Louis Schank, author of Digital Transformation Success. He’s spent years in the trenches at Accenture, Bank of America, EY, and Citi, then struck out on his own to codify what actually works. We dig into his process inventory framework and how it transforms complexity into clarity without wishful thinking.Most transformations stumble not because teams are bad, but because complexity breeds chaos. The fix starts with mapping what the business actually does, naming owners, and tying change to those specific processes. No buzzwords, just the hard work that kills the telephone game and keeps scope, design, and testing honest. And you’ll see why getting the map right beats chasing shiny tools.You’ll Learn:[00:00] Introduction[10:52] Why alignment and systems thinking are the two foundations every transformation depends on[13:17] What happens when business and tech speak different languages and how to finally bridge that gap[19:40] The real reason “easy buttons” and buzzwords keep derailing enterprise change[27:05] How a simple process inventory turns chaos into clarity across teams[31:14] What mapping COBOL systems taught one bank about risk and modernization[33:42] Why ignoring side effects in process change can quietly destroy entire workflows[43:05] How visualizing current state exposes waste and redundancy no one noticed before[45:11] The hidden danger of optimizing what should’ve been deleted in the first place[56:09] What transformation leaders get wrong about ownership, and the one fix that makes it lastResources Mentioned:Digital Transformation Success by Michael Schank | BookYou can connect with Michael on his LinkedIn.Find more from Adam on LinkedIn and YouTube, and explore coaching, cohorts, and how you can stay up to date at theCTOplaybook.com, helping you build your own playbook for your path at your pace.