Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: The Hidden Dangers of AI at Work With Ari-Pekka Skarp
AI is usually sold as a productivity tool, but Ari-Pekka Skarp argues that the real story is what it does to the conversations, skills, and purpose that hold teams together. In this BONUS episode, Ari-Pekka explores why organizations are rushing to use AI "as efficiently as possible" without defining what efficiency means, and what that rush is quietly costing us.
Organizations Are Conversations
"The organizations are actually conversations, conversational patterns between people."
 
Ari-Pekka's path from software engineering in 1999 to psychology, psychotherapy, and change leadership was driven by one thread: how the mind works, both individually and socially. Meeting Ralph Stacey, Esko Kilpi, and Douglas Griffin at Nokia changed how he saw organizations. Instead of a machine made of parts, an organization is a living pattern of conversations — people responding to each other's gestures, again and again. George Mead added the idea that the human mind itself is not individual but relational. This matters for AI because a large language model is a new kind of player in those conversations, not just a tool that moves data between them.
The Efficiency Fetish
"It's like how much people are pressing the acceleration pedal in the car. It doesn't tell anything where the car is going."
 
Many organizations are trying to use AI "as efficiently as possible," but Ari-Pekka points out that few have defined what efficiency means. What he sees instead is measurement of AI usage itself — how many people are prompting, how many tokens are flowing. He calls this tokenmaxxing. The car metaphor is the key: pressing the accelerator harder says nothing about direction, and going fast in the wrong direction is more costly than going slow. Efficiency only has meaning against a purpose, and purpose is itself a conversational achievement — something a team has to talk its way into.
De-Skilling Is the Hidden Cost
"If there's nobody in the room who could review what AI has produced and say whether it's correct or not, it's not an AI strategy. It's a liability."
 
The risk Ari-Pekka worries about most is de-skilling. When we offload cognitive work to AI, we lose the friction that builds learning. There is neurological evidence that people who rely heavily on AI do not develop the same brain structures as those who work through challenges manually. Some skills are fine to lose — nobody needs machine code anymore — but the ability to review and judge AI output is critical, and it is exactly what erodes when we skip the slow work. The result is a double bind: senior experts burn out under the review burden of fast-produced AI output, while juniors never get the time to build the expertise they would need to review it.
We Need Speed Limits for AI
"We can't optimize individual going as fast as possible... we need a collective... boundaries for individuals."
 
Ari-Pekka reaches for a historical analogy. Our biological rate of processing information is roughly ten bits per second, and it is not going to change. When we only had horses, we did not need speed limits. When we built cars that could go 200 kilometers per hour, we had to invent rules and boundaries to protect the system. AI is the same: we have reached a threshold where optimizing individual output — more code, more stories, more messages — can damage the whole organization. The control mechanism Ari-Pekka proposes is cognitive friction, deliberately added back into the system so that speed serves the system rather than breaking it.
The Tokenization of Work
"It's very easy to lose the purpose where you are going if you are only doing fragments of work."
 
Ari-Pekka's article The Tokenization of Work describes what happens when the unit of work is no longer a job, a profession, or even a task. Digital tools make it easy to fragment work into tiny pieces and spread them across AI agents, and in the process the boundaries that gave work its meaning vanish. Purpose is what protects us from burnout: with a clear purpose, people can do very demanding work without burning out, because the work feeds them. Without purpose, exhaustion arrives fast. For Scrum Masters, this means grounding the work in why it matters is more important now, not less.
AI Is an Echo Chamber, Not a Mirror
"The AI is more kind of an echo chamber in a sense that it doesn't push back so much."
 
Ari-Pekka compares AI to George Mead's "generalized other" — the internalized sense of how others see us. AI can play that role, but with a dangerous twist: it is programmed to be agreeable, so it behaves more like an echo chamber than a mirror. Real people push back, point out mistakes, and keep disagreeing. That friction is where learning, competence, and self-awareness grow. Ari-Pekka's practical move is to prompt AI for three different and conflicting perspectives rather than one, using it to go wider rather than only faster. It is not a perfect fix — the model still tries to merge them into one — but it is better than a single agreeable answer.
A Three-Second Pause
"Take a three-second pause... and just ask yourself, what are you doing?"
 
Ari-Pekka leaves listeners with a small challenge. A few times a day, when you are about to prompt an AI, pause for three seconds and ask what you are actually doing: are you seeking information, or seeking confirmation? Then consider whether it would be better to call a person and have a real conversation. It is a tiny practice, but it points at the whole episode's message: AI is not neutral infrastructure. It changes the conversations, the skills, and the purpose of work, and the people who notice that — Scrum Masters and Agile coaches especially — are the ones who can keep it from quietly reshaping their teams.
About Ari-Pekka Skarp
Ari-Pekka Skarp is a psychologist, psychotherapist, Lead Change Coach, organizational psychologist, and author. He wrote Mindfulness, mielenselkeys ja myötätunto, hosts Mielen laboratorio, and researches nondualism. His work connects psychology, complexity, Agile, and AI at work.
 
You can link with Ari-Pekka Skarp on LinkedIn. You can read Ari-Pekka's Finnish writing at tietoisuustaidot.com and his English blog at Fractal Sauna. You can also find Ari-Pekka's previous Scrum Master Toolbox Podcast episodes on his guest page.

Deborah Colombari: Product Owners Who Protect Focus and Enable Ownership
In this episode, we refer to INVEST criteria and Behavior Driven Development.
The Great Product Owner: Clear Outcomes, Strong Refinement, and Space for the Team
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"He doesn't say how. That allows the team to own the solution." - Deborah Colombari
 
Deborah describes a great Product Owner who came from project management, but learned to work deeply with upstream discovery and refinement. This PO uses INVEST criteria, Behavior Driven Development-style acceptance criteria, and explicit policies so that developers understand what needs to be done and why. He writes down expected outcomes at the epic and feature level, not only at the story level. Because he does not have a developer background, he depends on the tech lead, and Deborah sees that as a strength when the collaboration works. The PO brings business outcomes and clarity. The team brings technical options and owns the solution. That split creates room for trust.
 
Self-reflection Question: Does your Product Owner make the outcome clear while still leaving the solution to the team?
The Bad Product Owner: Adding Work Without Understanding the Consequences
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"He was doing whatever he wanted without thinking of the consequences." - Deborah Colombari
 
Deborah's Product Owner anti-pattern is a cross-team PO who accepted incoming requests and simply added them to the Sprint. There was no clear requirement discussion, no Definition of Done check, no Definition of Ready conversation, and no technical refinement with someone who could expose complexity. The PO treated every request as urgent, even when it was not, and told developers to stop their current work to pick up the new item. The result was more parallel work, broken Sprint Goals, less predictability, and a destabilized team system. Deborah eventually had to step partly into the Product Owner space to limit WIP and protect delivery. The lesson is blunt: Product Owners who ignore consequences turn priority into chaos.
 
Self-reflection Question: What is the cost of every "small urgent request" your team accepts mid-Sprint?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Deborah Colombari
 
Deborah is an Enterprise Agile Coach with a decade of experience championing Agile principles across organizations. Passionate about collaboration and continuous improvement, Deborah genuinely loves what she does—empowering others to work smarter, deliver value, and thrive in dynamic environments.
 
You can link with Deborah Colombari on LinkedIn.

Deborah Colombari: Stable Agile Teams Make Delivery Predictable
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"When I have a stable team, I have reliable data." - Deborah Colombari
 
For Deborah, success as a Scrum Master comes down to one word: stability. A stable team communicates better, shares knowledge, avoids hero-driven delivery, and becomes predictable enough that the Scrum Master can use historical data instead of wishful thinking. Deborah connects stability with flow metrics and statistical thinking. When an expedite request appears, a stable team can look at its own history and forecast with a useful level of confidence. An unstable team, by contrast, creates silos, overloads key people, and turns every new request into a crisis. Vasco connects Deborah's answer to systems thinking and statistical process control: the team is part of a wider system, and its delivery capability reflects that system. The point is not to force the team to commit beyond what the system can support. The point is to observe the system, improve it, and use real data to forecast what is likely to happen.
 
Self-reflection Question: Do you know your team's delivery capability from evidence, or are you still depending on optimistic commitments?
Featured Retrospective Format for the Week: The 4Ls Retrospective
Deborah recommends the 4Ls retrospective: liked, learned, lacked, and longed for. She adds one practical extension: an action-items column. Deborah likes the 4Ls because the quadrants help the team see the same issue from different angles. Something the team longed for may connect to something they learned. Something they liked may expose what was previously missing. The action-items column matters because complaint is easy, but turning a complaint into a concrete experiment is harder. Deborah uses those actions to create or update team agreements, making the retrospective outcome last beyond the meeting.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Deborah Colombari
 
Deborah is an Enterprise Agile Coach with a decade of experience championing Agile principles across organizations. Passionate about collaboration and continuous improvement, Deborah genuinely loves what she does—empowering others to work smarter, deliver value, and thrive in dynamic environments.
 
You can link with Deborah Colombari on LinkedIn.

Deborah Colombari: Coordinating Global Agile Teams Around One MVP
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"The scope is clear. How we are going to deliver it is not clear." - Deborah Colombari
 
Deborah brings a live challenge from a new global project. Her team carries the deadline, but three other teams must contribute, and those teams do not share the same priority or urgency. The question becomes: how do you align teams when only one of them feels the pressure? Deborah has already tried management alignment meetings, but they have not worked as well as needed. Her next experiment is a one-week workshop inspired by Lean Inception, where managers and teams can write down what is needed, when it is needed, and what each team can realistically contribute. Vasco and Deborah explore three practical moves: define the MVP as a real vertical slice, ask whether a person from each dependent team can join for a Sprint or a few days per week, and reduce dependencies by moving ownership closer to the team that holds the deadline. The coaching conversation ends with a useful image: even vertical slices contain thinner vertical slices. When the deadline is fixed, scope must become flexible.
 
In this episode, we refer to Lean Inception and Minimum Viable Product.
 
Self-reflection Question: When your team depends on others, are you managing the dependency or trying to reduce it?
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Deborah Colombari
 
Deborah is an Enterprise Agile Coach with a decade of experience championing Agile principles across organizations. Passionate about collaboration and continuous improvement, Deborah genuinely loves what she does—empowering others to work smarter, deliver value, and thrive in dynamic environments.
 
You can link with Deborah Colombari on LinkedIn.

Deborah Colombari: The Agile Team Destroyed by a Toxic Feedback Loop
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
 
"Whenever we almost started to achieve norming, we went back to storming." - Deborah Colombari
 
Deborah shares the story of a team of about twelve developers and QA specialists that kept losing people one by one. The early signal was not a technical problem. It was turnover. A toxic direct leader created pressure, blame, and snarky responses whenever the team tried to explain what was happening. Because that leader's own manager behaved the same way, Deborah saw a reinforced pattern rather than an isolated personality problem. The team could not stabilize. Every time it moved toward norming, someone left or someone new arrived, sending the team back into storming. Knowledge walked out the door with the people who left, delivery dates slipped, morale dropped, and a fixed-date call center project was eventually canceled. Deborah's story is a sharp systems thinking reminder for Scrum Masters: sometimes the problem is not inside the team. The team may be showing the symptoms of a system that punishes honesty, overloads people, and teaches them that leaving is safer than speaking.
 
In this segment, we talk about Russell Ackoff, his systems thinking interview with Haynes Media Works, and the Tuckman model.
 
Self-reflection Question: What turnover or morale signals are you treating as team problems when they may be system problems?
Featured Book of the Week: Russell Ackoff Interview by Haynes Media Works
Instead of a book, Deborah recommends an old Russell Ackoff interview from Haynes Media Works. She connects Ackoff's thinking to Donella Meadows and to the practical work of Scrum Masters. Deborah highlights how Ackoff explains that the outcome a system is designed to produce affects how the whole system behaves. Her example is health care: if the system rewards treating sickness, it becomes a disease-care system instead of a health system. For Scrum Masters, the lesson is direct. Teams are systems, companies are systems, and the incentives around them shape what they do. Deborah uses Ackoff's work to remind us to look at feedback loops before assuming people are the problem.
 
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
 
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
 
Buy Now on Amazon
 
[The Scrum Master Toolbox Podcast Recommends]
 
About Deborah Colombari
 
Deborah is an Enterprise Agile Coach with a decade of experience championing Agile principles across organizations. Passionate about collaboration and continuous improvement, Deborah genuinely loves what she does—empowering others to work smarter, deliver value, and thrive in dynamic environments.
 
You can link with Deborah Colombari on LinkedIn.