Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: When Burnout Looks Like Productivity—The Hidden Risk to Your Team's Innovation Capacity
In this BONUS episode, Alison Campbell shares the research that reframes burnout as a measurable threat to a team's ability to innovate. We learn why your most productive people may be your biggest innovation risk, how to spot capacity draining out of a team before the output drops, and where Scrum Masters have the leverage to protect the one thing that keeps teams building: the space to think.
From the ER to the Research
"I kept normalizing the stress, the exhaustion, eventually the stomach aches as, well, this is just the price of entry. This is part of being a busy, full-time executive and working mom."
 
Alison spent nearly twenty years in corporate roles—moving from finance to e-commerce to HR tech, with analytics as the through line and a love for the building phase inside companies. The pandemic was the turning point. With two young kids at home and a global team to hold together, she pushed through eighteen months of warning signs she had normalized, until severe stomach pain landed her in the emergency room needing surgery. That was the stop moment. What started as private shame—the feeling that she alone had failed while everyone else "had it all figured out"—became a research question the moment she started talking about it and heard the same story mirrored back from colleague after colleague. This wasn't one exhausted mom at a hard moment. It was a design and systems problem worth studying.
When Burnout Looks Like Productivity
"Even when that innovative work behavior was high, when burnout was high, that segment of our sample had the lowest innovation capacity of the entire group we surveyed."
 
The counterintuitive finding at the center of the research: activity, busyness, and visible output stayed high even when burnout was high. Burnout doesn't always look like withdrawal, disengagement, or someone who has already collapsed. Often it looks like the person still shipping, still moving fast, still showing up to every meeting—while the deeper capacity underneath quietly erodes. Alison's study measured this through two separate constructs, and the gap between them is the whole point:
 
Innovative work behaviors — the visible signs of innovation: coming to meetings, generating creative ideas, being present and active.

Innovation capacity — the cognitive and strategic bandwidth to hold complexity, make hard decisions, collaborate well over time, and translate ideas into durable, long-term company value.

 
The people scoring high on visible activity while burned out were exactly the people whose capacity to do the deep work had already dropped the lowest.
What Innovation Capacity Actually Is
"Not just, am I coming to the meetings, am I visibly showing up—but do I have the ability to translate these ideas into durable, long-term company value?"
 
This isn't only about product features or new products. Innovation capacity shows up in every layer of the work: the micro decisions, the macro strategy, the processes, the willingness to try a new tool or approach at all. Innovation capacity is present when people have the mental space to be curious, to ask questions, to explore, to want to play with something new. When that space disappears—when the answer to every new idea is "we don't want to hear no, we don't want to hear that there's a problem"—the work turns tactical and reactive. People narrow their thinking and just chip away. That's the moment you stop getting the best from your team, even though they look every bit as busy as before.
The Signals to Watch For
"Can I name what is blocking progress? Do I feel safe enough to say, this is what's at risk? Or is this a culture where we don't talk about what's not going according to plan, and we just keep our heads down and keep going?"
 
The conditions most strongly correlated with high burnout and low innovation capacity clustered around a few themes: uncertainty—especially about the role of AI in someone's work—unclear meeting outcomes where a lot of meetings produce little clarity on the next action, and a general cluster of fear and ambiguity. The fix isn't to make everything finite and remove all agility—that's the wrong message in a genuinely uncertain world. It's to provide bounds. Communicate clearly about what you do know and why, so teams can operate confidently even through an uncertain pivot. For Scrum Masters, this maps directly onto AI adoption conversations: when curiosity turns into anger, frustration, or blanket anti-AI resistance, that's a signal worth investigating. Get at the why—both by taking a genuine pulse on the team, and by making sure the team understands the bigger-picture why the whole company is driving toward. As Alison put it, strip it all down and you land on good communication and psychological safety: the conditions where people can name what's blocking them and still do their best work.
Fragmented Work and the Myth of the Finished List
"It's about baking in periods of rest and reset, and being comfortable with this notion that the list is quite literally never going to be done."
 
Fragmented work—context switching, too many things in flight, the sprawl of tools and issue trackers—came up as a real innovation-capacity killer, and it's something agile teams can actually measure. The study asked about context switching, interruptions, and how many channels people move between; a deeper follow-up study is now underway focused specifically on AI-driven uncertainty and tool-switching. Alison's guidance isn't "do less and stop switching," because that reality isn't going away. It's to design rhythm into the work: periods of sprint followed by a deliberate pull-back—reflective work, postmortems, space to talk about what didn't go to plan. She didn't put a number on the right ratio of recovery to sprint; it's contextual to the industry, the stage of the business, the size of the team. The leadership move is to look at the actual rhythm of the business, and to proactively plan and openly name the recovery after a big push—instead of treating "recovery" like a bad word.
Why Managers Are at Higher Risk
"Managers were 1.7 times more likely to experience high burnout—and about three times more likely to say, yes, I delay complex problems or hard decisions."
 
When the data was split between managers and individual contributors, the extra management layer showed up as a measurable source of additional pressure. Managers reported high burnout at 1.7 times the rate of individual contributors, and were roughly three times as likely to strongly agree with the statement "I delay complex problems or hard decisions"—a direct marker of eroded innovation capacity. There's more to unpack there, and a second paper is coming in September that adds caregiving as a third dimension, building toward a "responsibility index" that looks at how obligations outside of work—an aging or sick family member, for example—compound the burnout picture. For a Scrum Master, the takeaway is that the pressures draining a team's capacity are often invisible from the outside, and they land hardest on the people carrying the most responsibility.
One Thing to Start Tomorrow
"Not another meeting—but a reflective question first. Rate your energy, rate your stress, and look at where your time actually got spent versus the goals you had."
 
Alison's concrete recommendation for anyone who suspects something is off: start a weekly check-in. First an individual reflection—rate your energy and stress for the week, and compare where your time actually went against the goals you set. Then bring that same question into a Friday stand-up or retrospective and ask the team to weigh in: what was the team's stress and energy, and were there major constraints nobody saw coming? The first few weeks people may be hesitant to answer honestly. But keep the practice going week over week, and you build a real data set on how the team is actually feeling—and start surfacing the systemic blockers getting in the way of good work.
 
About Alison Campbell
 
Alison Campbell is the founder and CEO of unBurnt® and Executive in Residence at Bentley University's Center for Health and Business. Her 2026 research — "When Burnout Looks Like Productivity: The New Risk to Innovation Capacity" — surveyed 544 professionals across 17 industries and reframes burnout as a measurable threat to an organization's capacity to innovate. unBurnt® · Research · LinkedIn
 
You can link with Alison Campbell on LinkedIn and read her research at getunburnt.com.

Joshua McDonald: Product Owners Earn Team Loyalty By Showing Up, Learning, And Deciding
The Great Product Owner: Vulnerable Enough To Learn The Technical Details
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.
 
"I've seen developers be fiercely loyal to their product owner who makes that type of effort." - Joshua McDonald
 
Joshua describes the great Product Owner as someone who connects with the team even without a technical background. They do not pretend to know everything. Instead, they get into refinement with curiosity, write stories with the developers, and say, "I think this is what needs to be done, but correct me if I'm wrong." That vulnerability creates a strong partnership. Developers see the effort and often respond with loyalty, to the point where they may refuse to continue important discussions without the Product Owner in the room. The lesson is useful for Scrum Masters coaching Product Owners: deep technical expertise is not the entry ticket. Presence, curiosity, and the willingness to learn with the team are what create trust.
 
Self-reflection Question: How does your Product Owner show the team they are willing to learn the product with them?
The Bad Product Owner: The Dependent Note Taker
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.
 
"Sometimes you ask the product owner, you're the bus driver, where do you want us to go? And they say, let me go talk with the product manager." - Joshua McDonald
 
The Product Owner anti-pattern Joshua highlights is the dependent PO: the person who shows up as a note taker rather than a decision maker. This often happens when a Product Manager sits behind the PO and every decision has to be checked elsewhere. The day-to-day symptoms are easy to spot: camera off, muted, disconnected, asking people to repeat questions, missing meetings they scheduled themselves, and leaving the team without timely answers. Joshua's coaching response starts with one-on-ones, support, and curiosity. He asks how they are doing, what support they need, and what signals would help the team see they are engaged. When the product feels too technical, he sits beside them, learns with them, and helps them build confidence instead of leaving them exposed.
 
Self-reflection Question: Where is your Product Owner dependent on someone else for decisions, and how is that affecting the team?
 
[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 Joshua McDonald
 
Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he's already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.
 
You can link with Joshua McDonald on LinkedIn.

Joshua McDonald: Scrum Master Success Means People Feel Heard, Respected, And Safe To Speak Up
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.
 
"I hope you can feel heard and respected at the end of the day." - Joshua McDonald
 
Joshua defines Scrum Master success through the team's comfort with self-organization, respectful pushback, and asking for help when they do not know what they do not know. For him, a successful team is not drama-free because nothing hard happens. It is low-drama because people can raise problems without fear, communicate openly, and keep moving forward even on bumpy roads. Joshua keeps himself honest by reviewing retrospective notes, one-on-one notes, and the commitments he made to follow up. He keeps a running to-do list from Slack messages, meetings, and team conversations so feedback does not disappear after someone shares it. Periodically, he brings past retrospectives back to the team and asks what they accomplished, what changed, and whether anything fell through. That ledger matters because Scrum Masters work through people. If people feel heard and respected, they are more likely to keep working with you, regardless of your title.
 
Self-reflection Question: What system do you use to make sure team feedback turns into visible follow-up?
Featured Retrospective Format for the Week: Personalized AI-Themed Retrospectives
Joshua's favorite retrospective format is never using the same format twice. He noticed teams getting bored and agitated when the same sailboat or standard board appeared every sprint. His answer was to personalize retrospectives around team members' interests: a BMW theme for a developer who liked cars, a beach theme after someone's vacation, or a TV-show theme tied to a person's hobby. He uses tools like Mural, Zoom whiteboards, Microsoft Teams, and AI-generated visual themes to make each retro feel like it was designed for someone in the team. The point is not decoration. The point is listening. When people recognize their interests in the retro, they feel seen as people before they reflect on the work.
 
[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 Joshua McDonald
 
Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he's already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.
 
You can link with Joshua McDonald on LinkedIn.

Joshua McDonald: Using Cycle Time As A Storyteller, Not A Scorecard In Agile Retrospectives
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.
 
"Metrics is not about telling people do better. It's about telling that story." - Joshua McDonald
 
Joshua brings cycle time as his biggest current coaching challenge. The problem is familiar: when a Scrum Master points to a story with high cycle time, developers can feel blamed, even when the intent is learning. Joshua reframes the metric as a storyteller. Instead of asking why someone took too long, he asks what journey the story went through, where it changed hands, where it waited, and what the team now knows that it did not know at the start. He also describes practical tactics: warn people in advance before discussing specific stories, keep the language gentle, avoid forcing people to explain themselves publicly, and sometimes skip the metric conversation entirely when the team needs encouragement more than analysis. Metrics matter because they move coaching away from gut feeling and toward observable patterns. Used well, cycle time becomes a barometer for stress, bottlenecks, missing product owner review, and places where the team needs support.
 
Self-reflection Question: How do you introduce metrics so the team becomes curious about the system instead of defensive about individual performance?
 
[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 Joshua McDonald
 
Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he's already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.
 
You can link with Joshua McDonald on LinkedIn.

Joshua McDonald: The Distributed Agile Team That Hid Problems Behind Follow-Up Stories
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.
 
"They started to separate and call each other out, which is definitely not Agile." - Joshua McDonald
 
Joshua shares the story of a 17-person distributed team spread across time zones, cultures, and communication styles. Some team members were direct and ready to challenge problems in public. Others preferred quieter, one-on-one conversations. Over time, those differences created a blame environment where people stopped asking for help and started hiding problems. Long-running work was closed and replaced with follow-up stories, then part two, then part three, until the real issue disappeared under Jira housekeeping. The result was not better flow, but delayed learning, missed upskilling opportunities, and a stressful team environment where quieter people stopped speaking in standups and retrospectives. Joshua explains what he would do differently now: split the team by communication patterns, listen to what each group needs, act as a mediator, and only bring the whole group together once people feel heard.
 
In this segment, we talk about different communication styles.
 
Self-reflection Question: What signals tell you that people are hiding problems because the team environment does not feel safe enough?
Featured Book of the Week: Never Eat Alone by Keith Ferrazzi
Joshua recommends Never Eat Alone by Keith Ferrazzi because it reframed networking as a relationship practice, not a transaction. The book helped him see that staying connected with people creates learning, support, and a safety net over time. He also mentions the Bible as a daily source for reflecting on respect, peace, and conflict resolution, especially because Scrum Masters often need more than process knowledge to help teams work well together. For Joshua, both recommendations point to the same deeper idea: our work improves when we treat relationships as something to maintain before we urgently need them.
 
[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 Joshua McDonald
 
Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he's already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.
 
You can link with Joshua McDonald on LinkedIn.