83: Are We Building the Right Things? A CTO’s Guide to Influence, Ethics, and Responsible Innovation
The CTO PlaybookShow Notes
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 decisions
Resources Mentioned:
No Silver Bullet Essence - Accident in Software Engineering by Brooks F. | Article
You 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.
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.