Show Notes
What if speed as a CTO has less to do with urgency and more to do with discipline?
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 Bastien Duret, CTO at a French-American company building web-based products in the clinical trials space, to unpack what “moving fast” really means in complex technical environments.
As CTOs, we’re taught to value urgency. But when you’re debugging memory leaks across fragmented Android devices or responding to a vendor outage that brings your entire service down, speed starts to look different. The real question becomes when to stem the bleeding and when to slow down long enough to actually learn.
We get into what that shift looks like in practice, how leadership changes when problems become learning opportunities, how postmortems build long-term velocity, and why incident response reveals the true operating system of your team.
If you’re responsible for uptime, technical strategy, and building resilient teams, this episode will challenge how you think about speed, progress, and sustainable execution.
You’ll Learn:
[00:00] Introduction [04:32] Why fragmented Android devices force you to rethink what quality really means [06:48] How crash reports expose flawed assumptions you didn’t see [08:21] The difference between fixing pain fast and learning from the mistake [09:47] What to do when a vendor outage takes down your entire service [11:18] The tension between contractual SLAs and your own uptime standards [18:36] Why firefighting feels productive but fuels repeat failures [28:14] How postmortems turn incidents into long-term acceleration [39:52] The mindset shift from frantic execution to smooth acceleration
Clinical research shouldn’t be limited to a handful of sites. See how Inato helps sponsors reach more diverse patients, faster.
You can connect with Bastien 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.