92: The CTO Playbook: How to Build Trust, Consistency, and Psychological Safety in Engineering Teams
The CTO PlaybookShow Notes
The difference between a good CTO and a trusted one often comes down to a personal playbook.
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.
Sam Boswell is the CTO of Terralayr, an energy tech company focused on solving global energy storage challenges. With a background in high-risk infrastructure and scaling engineering teams, he brings a practical lens to how leadership actually works.
At the center of that philosophy is a simple idea. Engineers don’t follow leaders because they’re the most technically brilliant person in the room. They follow leaders who are consistent.
That consistency doesn’t happen by accident. It comes from a personal playbook. A set of lived principles that shape how decisions are made, how problems are approached, and how people are treated.
We get into how that playbook forms over time, why documenting how you think matters more than most leaders realize, and what happens inside teams when that consistency is missing.
The result is a grounded look at leadership that moves beyond theory. It shows what it takes to build trust, create safety, and lead in a way people actually want to follow.
You’ll Learn:
[00:00] Introduction [05:12] The shift from coding to leading people [07:45] Turning ideas into outcomes without touching the code [12:18] Why consistency earns trust faster than brilliance [15:42] Writing as a tool for clearer thinking and better leadership [18:36] What breaks inside teams when leadership is inconsistent [22:04] The power of a personal user manual for faster trust [26:31] There’s always a move, even when you feel stuck [30:12] Small principles that compound into better decisions [36:48] Psychological safety as the foundation of real performance
Resources Mentioned:
OODA Loop | Wikipedia The Joel Test: 12 Steps to Better Code | Website Notion | Website Knolling | Website Tom Sachs’ 10 Bullets | Website Time Enough for Love by Robert Heinlein | Book or Audiobook Joyful Militancy: Building Thriving Resistance in Toxic Times by Carla Bergman and Nick Montgomery | Book or Audiobook Eve Online | Video Game Kanban Tool | Website
Find more from Sam on 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.
More from The CTO Playbook
Most leaders treat impostor syndrome as something they need to overcome. But what if the belief that you're not good enough is actually serving a purpose?
AI has made building software dramatically faster. The problem is that the rest of the engineering system hasn’t caught up. AI agents can now produce code, tests, documentation, migrations, and pull requests at a pace most engineering organisations weren’t designed to handle. But when everything around code review accelerates, review becomes the bottleneck. Pull requests pile up, reviewers spend more time reconstructing intent, and experienced engineers can end up reduced to repeatedly saying yes or sending work back for fixes.
AI adoption is getting easier for everyone. The harder question is whether you're using it to optimise the game you're already in, or to build a position that changes the game.
AI isn't just changing how engineers work. It's forcing technology leaders to rethink what makes management valuable.
Quantum computing may not be breaking your security today, but the decisions you make now could determine how exposed your organization is when it does. Conor Deegan explains why CTOs need to start preparing before Q Day arrives.