When Teams Slowly Decay by Anointing a Hidden Dictator | Nigel Baker

Summary

Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches

Episode: When Teams Slowly Decay by Anointing a Hidden Dictator
Guest: Nigel Baker
Host: Vasco Duarte
Date: March 3, 2026

---

Episode Overview

In this episode, Vasco Duarte and returning guest Nigel Baker dive into a subtle but damaging team dysfunction: how teams gradually self-destruct by unconsciously appointing a “hidden dictator” instead of truly embracing self-organization. Through personal stories and practical advice, Nigel explores team dynamics, decision-making responsibility, and actionable techniques for Scrum Masters to counteract this anti-pattern.

---

Key Discussion Points and Insights

1. Influential Books for Agile Practitioners (01:26–05:48)

• Nigel's Relationship with Agile Literature

  • Nigel notes he found little inspiration in classic Agile books because real-world practices were ahead of the literature when he started. He prefers works adjacent to Agile or from different industries.
  • Quote: “What was happening in the real world was ahead of the literature... a lot of books I picked up, I was like, yeah, this is great... but nothing new in it, nothing inspiring.” (02:01, Nigel)

• Books Nigel Highlights

  • Leading Self-Directed Work Teams by Kim Ball Fisher: Inspired the Scrum Master role and shows parallel ideas without Agile jargon.
  • Strategyzer series by Alex Osterwalder: Particularly Testing Business Ideas and Business Model Creation for broad, business-focused thinking.
  • Scrum Mastery by Geoff Watts: Strong foundational Scrum Master text.
  • Facilitator’s Guide to Participatory Decision Making by Sam Kaner: Not a cover-to-cover read, but a vital reference for real-world facilitation.
  • Quote: “[This book is] a great reference guide for participatory decision making, which is the big issue that's coming up for me next.” (04:43, Nigel)

2. How Teams Decay: The “Hidden Dictator” Phenomenon (06:09–09:37)

• The Real Danger Isn't Conflict—It's Apathy

  • Teams don't usually fail with explosive conflict, but rather with slow apathy and avoidance of responsibility.
  • Quote: “My great fear is not teams exploding like a bomb... The big thing for me is teams caring. Right. If I'm angry and I hate you, there's a reason for the hate... my horrible thing with teams, I see it again and again is teams that decay slowly with whimper.” (06:21, Nigel)

• Symptoms of Team Decay

  • Decay sets in when teams stop taking responsibility and start dodging decisions.
  • Teams may attempt to “anoint a dictator,” overtly or covertly—deferring decisions to one person (sometimes the manager; often an outspoken team member).
  • Even organizations vigilant about avoiding formal dictatorships can see teams subconsciously appoint a decision-maker. Meetings default to seeking this person’s approval or direction.
  • Quote: “So what people will often try and do is self organize themselves out of self organization. So they effectively anoint a hidden dictator… Everyone looks at them in a meeting to say, what do you think?” (08:01, Nigel)

• The Scrum Master's Challenge

  • Coaches and Scrum Masters may themselves become the unwitting dictators. It’s easier as a coach (less direct power) but much harder when you’re embedded as the team’s Scrum Master.

3. Practical Techniques to Counter the “Dictator” Anti-Pattern (09:37–14:06)

• Raising Awareness

  • First step: Openly discuss the tendency to defer to a single person during facilitated team discussions. Use structured meetings to surface and de-normalize the behavior.

• Day-to-Day Tools for Empowerment

  • The “Yes, And…” Approach (Improv technique)

    • Instead of negating ideas (“yes, but”), build on them (“yes, and”) so ownership stays with the original suggester.
    • Example: “We’re thinking of ordering some balloons for the party.” / “Yes, and maybe we could ask the office what color they’d like.”
    • Quote: “It’s a great trick to use with teams that try and get you to make decisions... I’m not taking it from them by saying yes, but. I’m making the final decision. I'm making the ownership stay with them.” (11:13, Nigel)

  • Powerful (Socratic) Questioning

    • Use follow-up questions to reflect ownership back to the team (“What do you think?”, “How would you solve it?”).
    • Nigel cautions: Don’t overdo it. Sometimes the team genuinely needs practical advice, not just coaching questions.
    • Quote: “So I remember Jeff doing this to me when I was a developer and thinking, ‘Oh, for God’s sake, Jeff, give me a straight answer.’ But the point was he was trying to get me to make the decisions so I would use that.” (12:13, Nigel)
    • Quote: “The key word in Agile coach isn’t agile—it's coach. But ... in real life, sometimes they do need help... I don’t need therapy – I just need to know which server the files are on.” (13:23, Nigel)

• Balancing Coaching and Direct Support

  • Find the practical midpoint: use empowerment tools but provide direct answers when necessary to help the team become capable and accountable.

4. Memorable Moments & Quotes

• On Slow Team Decay

  • “The world won’t end with a bang but with a whimper.” (06:10, Nigel, paraphrasing T.S. Eliot to describe team don’t self-destruct dramatically but decay quietly)

• On Participatory Decision-Making

  • “If you have a big meeting coming up... you can go to the book and you can actually look up ideas... it has very concrete strategies and techniques you can use.” (05:17, Vasco, on Sam Kaner’s book)

• On the Limits of Coaching

  • “We’ve got a whole range of coaches out there who are almost life coaches where all they have is, ‘What do you think?’ And actually in real life, sometimes they do need help.” (13:37, Nigel)

---

Timestamps for Key Segments

• 01:26–05:48 — Influential books and references for Scrum Masters
• 06:09–09:37 — Story of slow team decay and the “hidden dictator” anti-pattern
• 09:37–12:18 — Practical facilitation tools (“yes, and” and powerful questioning)
• 12:18–14:06 — Balancing coaching vs. giving direct answers; final takeaways

---

Takeaways for Listeners

• Watch for the subtle shift from self-organization to informal dictatorship in teams—it’s often gradual and hard to spot.
• Use group discussions and practical facilitation techniques to keep responsibility and decision-making distributed.
• Lean on practical tools (“yes, and”, Socratic questioning) but don’t default to coaching in every scenario—give practical help when the team needs it.
• Foundational texts on facilitation and real-world strategy can greatly expand an Agile practitioner’s effectiveness beyond classic Agile literature.

---

This episode challenges Scrum Masters to reflect on the slow erosion of effective team dynamics and equips them with practical ways to spot and reverse that drift—empowering teams to truly self-organize, not subtly abdicate.

Transcript

[A]

Hey there, agile adventurer, just a quick question. What if for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame warfree and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's the Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

[B]

Hello everybody. Welcome to our team Tuesday. This week we have with us Nigel Baker. Hey Nigel, welcome back.

[C]

Hi. It's good to be back. I'm so glad to come back this next day. We've been whole 24 hours since we last spoke.

[B]

Well, for some that is exactly true. Although many people do listen to the whole week in one go a week later, which is a great way to kind of stay in the context of the guest's universe. We'll explore teams and how they self destruct in a minute, Nigel. But before that, share with us what was the book that most inspired you in your career as a Scrum Master?

[C]

This is a hard conversation because I'm not sure I've been inspired by many books or when I say many, I'm gonna knock the m off any because when I got into this it was kind of what was happening in the real world was ahead of the literature. So the literature was coming behind like a baggage train.

[B]

Still is, but that's another discussion.

[C]

Yeah, well, a lot of people though, the literature is the only access they've had to the ideas. So that's, that's fine, that's okay. But it meant that a lot of books I picked up, I was like, yeah, yeah, this is great. I agree the hell out of it, but it doesn't, nothing new in it, nothing inspiring. The books that got me interested in terms of ideas were ones that were more adjacent to agile than agile. So I remember reading back in the day Kim Bull Fisher's leading self directed work teams, which is kind of one of the inspirations for the Scrum Master role. I don't know if people say that anymore, but it is. If you read it, you can see where people have gone and Control C, control V, some content out of it. But what I like about it is it avoids all the jargon. So it's got its own jargon, but it's not talking in the very loaded terminology we have in the Agile and Scrum space. So you can kind of see a whole different industry, a whole different world exploring similar principles and similar techniques. So I quite like that one. Other books I particularly enjoyed that have really influenced me, well, all the Strategizer stuff by Alex Osvaldo and Extra, because that was an area I didn't pick up in work, I had to pick up outside as a coach.

[B]

So what was that book by?

[C]

There's multiple books by Ostavalda like Testing Business Ideas.

[B]

Yeah, yeah.

[C]

Business Model Creation, High Impact Teams I think is one of them. Those. I like those. They're great coffee table books. A great read and a great thing to leave laying around. But the final two I wanted to get to and the real ones, I wanted to get to my real ones. Jeff Watts, my first Scrum Master. I've known Jeff 25 years. He is my boss for the first five I've known him 25 years. He's a great brain, he's a great mind. I know he's very famous in the Scrum Master space, but he wrote a great book called Scrum Mastery years ago which I think is a great foundational text. If you want to get going with being a Scrum Master, it's a great thing to get you going, right? But there is a book, a book I've been waiting for. I've had this book on order for I believe it was four and a half years until Amazon canceled the pre order because it's still not coming yet. Which is the latest edition of the Facilitator's Guide to Participatory Decision Making by Sam Kainer et al. I'm on, I think second or third edition. I've been waiting for the fourth for like four and a half years. And so I would get emails every six months from Amazon saying it's delayed and then finally even Amazon gave up. But it's a great book. It's not like a good read, you wouldn't sit down, read it cover to cover. But it's a great reference guide for participatory decision making, which is the big issue that's coming up for me next.

[B]

And the big problem in teams and also A great reference in terms of inspiration. Like if you have a big meeting coming up where you have some high powered stakeholders that need to make a decision, you can go to the book and you can actually look, look up ideas. And I really like how practical it is. So it's not, it's not. I mean it does refer to theory, but. But it's very practical and it has very concrete strategies and techniques that you can use.

[C]

Yeah. Because a lot of times people don't want to be like I say a lot of agile books are very vibey. They're very like, hey, let's have some feelings and some vibes and some principles. And I'm like, that's great. But as a real ordinary person in work, how am I going to do that? I need real things I can actually do as a real person.

[B]

Let's talk about vibing because the next topic is teams and how sometimes they get in their own way. And we want to explore one of those stories, Nigel. So tell us the story of that team. Give us a little bit of the context and walk us through how those vibes deteriorated over time and eventually led to the team self destructing.

[C]

Yeah. So it, I think, I think the world, what's the phrase? The world won't end with a bang, but with a whimper. Okay. So my great fear is not teams exploding like a bomb where they all fall out and disagree. That shows they care. The big thing for me is teams caring. Right. If I'm angry and I hate you, there's a reason for the hate. There's an actual. We have a care of the topic, we have feelings about the topic and at least it's blowing up for creative differences. My, my, my horrible thing with teams, I see it again and again is teams that decay slowly with whimper. Where, you know, Leoni, the, the, the dysfunctions of a team, there's inattention to results. It's. Let it. That's, that is awful. However, my concern is like not taking responsibility in attention to decision making, to being accountable and responsible for something. Teams that try to avoid that responsibility, avoid that account.

[B]

How, how did that happen for this particular team? So first there's a difficulty. Right. Because if teams end up, you know, self destructing.

[C]

Yeah.

[B]

Slowly and over time, it's going to take a lot of effort even from us to detect that early enough to be able to reverse it. So tell us that story.

[C]

Yeah. So this side, now this is for me seeing as a coach. Okay. So I have less power in this situation. But what we're seeing There is effectively, again, it's actually been multiple examples. I've got to be careful which one. I don't jump between them. But it's where a team kind of doesn't want to take responsibility for decision making, doesn't want to take responsibility for the yes or no. And so it handles it in a variety of different ways that kills the team.

[B]

How does that show up?

[C]

Yeah, so a few ways are the teams try to anoint a dictator. So the classic thing with self organization, self organization is a very feeble, delicate frame. It's hard to get a team energized and self organizing swirling and whirling. And it's very difficult to keep it in that state because it's not very natural for people. And so what people will often try and do is self organize themselves out of self organization. So they effectively anoint a hidden dictator. So it's not like sometimes it's just the project manager. So systemically and systematically, the organization just goes, yeah, yeah, you're doing scrum, she's making all the decisions. And then you're kind of lost. Self organization anyway, from a system point of view. But the danger is, even if the organization is intelligent and coherent enough to try and avoid that, the team secretly do it. So they anoint like the big brain, the big mouth to make all the decisions. So everyone looks at them in a meeting to say, what do you think?

[B]

Yeah, what would Nigel say?

[C]

Basically, that type of thing, looking at me because I've got a big mouth and lots of opinions. Right. And so as a coach, it's really hard. Well, actually, no, as a coach, it's easier because a coach, you're like Obi Wan in Star wars when he's dead. So you're kind of. You have no influence over the material universe. You're there going, ooh, go to Dagobah, Luke. But that's about it, really. Advice, Right? But as a scrum master, your real coach on the real pitch, playing the game with everyone else. So it puts you in a lot more difficult spots to avoid that, to avoid being anointed.

[B]

So how would you like. Let's talk to the scrum master out there who maybe started noticing this anti pattern, let's call it that way of naming a dictator or even implicitly deferring to an implicit dictator. How would you tackle that as a scrum master? How would you first bring it up to consciousness and then hopefully over time tackle that anti pattern?

[C]

Yeah. So the three things I tend to do is I tend to. First things first. Let's talk about it as a group. So we're aware of it. So again, that's when you're into the like a nice facilitated meeting. Get yourself a structure, bring these topics up, discuss them in a way, but on a day to day basis. In real life, there's two major tools I use which is the famous yes and the improv idea and Socratic questioning or powerful questioning. So yes, and for me, it's a great tool to get people keeping owning an idea. So if you don't know yes, and this is from the world of teaching English as a foreign language. The difference between yes but and yes and in English yes but negates what you say before. Vasco, you are a champion, a hero. You've been a fantastic legend in our company for so many years. I'm proud to call you a colleague, I'm proud to call you a friend. But like, oh dear, redundancy's coming. And yes, and is building on the idea. So a lot of improv comedians, because people may know I'm great friends with Paul Goddard, famous agile coach who's written loads of books on improv comedy. I'm a huge fan like him of improvised comedy. And improvised comedy works in this way of it's called the offer. You accept what someone says is true and you add to it. So you take that idea and you add to it. You don't negate it, you don't block it. You add to it, then you hand it back. Okay, this is a great trick to use with teams that try and get you to make decisions. So they say, we're thinking ordering some balloons for the party. And you go, yes. And we could ask the office what color they'd like. So they're keeping ownership with the people and I'm adding to their ownership. I'm not adding work, I'm adding to their ownership. I'm not taking it from them by saying yes, but we can't do that. I'm making the final decision. So that's just a verbal trick to keep empowerment where it needs to be. But powerful questioning is a great one. Where, you know, we joked about Obi Wan Kenobi from Star Wars. It's Yoda. It's like, yes, why do you think that? So you could use that to keep the ownership with people. So I remember Jeff doing this to me when I was a developer and thinking, oh, for God's sake, Jeff, give me a straight answer. But the point was he was trying to get me to make the decisions so I would use that.

[B]

I was talking to a colleague who would always come to me with questions, expecting me to give him an answer. And after a few interactions over time, eventually he came to me with a question and then I looked at him, held the silence for a bit, and then he said, you're gonna ask me what I would do, aren't you?

[C]

Yeah.

[B]

Yes, exactly.

[C]

But it's one of the great tools of powerful questioning is like I always joke with people I teach and stuff that, you know, a typical question, like, I am ignorant. You have knowledge. I'm using a question to get knowledge passed from you to me. But Socratic questioning, I'm ignorant. You have knowledge. I'm getting you to pass knowledge from you to you. So it's insightfulness, but it's very hot. And so you've got to be very careful with it. Like, I was one of the great proponents as a coach of saying that the key word in Agile, coach is isn't agile, it's coach. Right? So the idea of coaching skills, and everyone's got into coaching skills in a huge way. I am slightly regretting it because we've got a whole range of coaches out there who are almost life coaches where all they have is the h, what do you think? And actually in real life, for real people in real life, sometimes they do need help. Like, they know I, I don't want to like have therapy on this particular answer. I just need to know which server the files are on. I don't need to therapy. And so again, as a scrum master, so when I see teams like struggling to take accountability, right, I need to understand I can't just use coaching techniques to get them to take accountability. I have to give them advice and support so they can own that accountability.

[B]

And we will explore coaching in a very practical way in the next episode. For now, Nigel, it's been a pleasure. Thank you very much for sharing that story with us.

[C]

It's been great fun. Thank you for having me.

[A]

All right, I hope you liked this episode. But before you hit next episode, here's the deal. This podcast is powered by people like you, the members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day. We're talking access to over 700 hours of agile gold, CTO level strategy talks, summit keynotes, live workshops, E courses, deep dive interviews, books, and if you're into no estimates, we got the pioneers of no estimates in those deep dive interviews as well. Agile business intelligence, creating product visions, coaching your product owner courses, you name it, you'll get invites to monthly live Q&As with agile pioneers and practitioners plus a private Slack community which is free of all of that AI slop you see everywhere. And of course without the flame wars. It's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you so check out all the [e-mail] membership because listening is great, it's important, but doing it together that's next level. I'll see you in the community.

[C]

Slack

[B]

we really hope you liked our show and if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.