Episode Summary

In this hosts-only episode, Dan Hammond and Pia Lee start with an uncomfortable question: what's your P(doom), the probability you'd put on AI destroying humanity? They quickly move past it. Their view is that the bigger near-term risk is not the technology but who governs it, and that most leaders can't control that anyway. The question that matters is the one inside your own sphere of influence: how do you bring AI into your team without hollowing it out? Organisations are spending heavily on AI adoption with little clarity about why, cutting roles and then rehiring for them. People increasingly ask AI rather than a colleague, and polished "slop" is moving around organisations with no human owning it.

What changes the picture is treating AI as a team capability rather than an individual productivity hack. Research suggests teams using AI outperform both individuals and teams working without it, and AI can act as a neutral facilitator that helps groups get aligned faster. Pia maps a recent HBR piece on leadership mindset for AI adoption onto Squadify's Three Cs. The pairs are clarity over certainty, exploration over expertise, and emotional insight over emotional control. Together they make the case that AI adoption is a leadership job, not a tooling decision. Dan adds a reminder to look after the whole person, because individualised, always-on AI work can lead to brain fry and isolation.

Key Themes & Takeaways:

• The real AI risk most leaders can influence is not doom but fragmentation: AI can turn a team into a "company of one" where everyone works alone to prove their individual value.
• Teams using AI are significantly more likely to reach high-quality solutions than teams without it, so design AI in as a team sport, not a private shortcut.
• AI can act as a neutral teammate: teams report getting on the same page faster when AI clusters and wordsmiths their ideas, because nobody's ego owns the output.
• Leaders can't offer certainty right now, but they can build clarity, and confusing the two leaves people chasing something that isn't available.
• Exploration beats expertise in new territory; holding tight to past expertise out of fear is how teams go down with the ship.
• You are accountable for your output: if you pass on AI-generated work you haven't owned, you're handing colleagues slop they'll just feed back into AI to summarise.
• When people ask AI instead of a colleague, it is often to avoid wasting that colleague's time; leaders need to judge when a conversation is worth more than the efficiency.

Three Reasons to Listen:

1. Listen if your organisation is spending on AI without being able to say what it's for, or has cut roles it may have to rehire.
2. Listen if you've received a polished document, suspected no human really wrote it, and been tempted to ask AI to summarise it for you.
3. Listen if you think of AI adoption as a tech rollout. Dan and Pia argue it's a leadership challenge, and that the human skills of pausing, reading the room and exploring matter more now, not less.

Notable Quotes