Show Notes
I nearly turned my own summer into the cautionary tale. The thing that saved me was a last-minute week in the Swedish mountains.
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 came home with a small number of clear thoughts about my business that I couldn't have produced at my desk, and they fade fast once you're back. This episode is for anyone heading back into work in the next fortnight, because how we come back in late August shapes the rest of the year more than almost anything else in September.
Real intent goes in on day one. The stack gets attacked head on. Two or three weeks later, we're extremely busy and have moved nothing forward.
There's a spaceflight analogy in here about why the most dangerous part of any return is the descent, and the one small decision that sets the angle for everything after it. Most of us come in too steep, and the queue gets to decide what matters so we don't have to. The cost is specific: the decisions only you could have made never surface, because they're never the loudest thing in the queue. There's a practical exercise at the end.
You'll Learn:
[0:00] Introduction [2:05] The summer move that nearly made me the cautionary tale [4:16] How spacecraft reentry explains a bad return to work [6:52] Why late August beats January for real resolutions [9:36] Career trains every leader to choose the steep angle [10:52] Heavy first week is the friction doing its job [12:37] Naming your own re-entry angle before the queue decides [17:14] A controlled re-entry playbook in four steps
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.