Informative

Does thinking get in the way of agility?

Automatic translation · View original

Topic illustration: Does thinking get in the way of agility?

Agile teams talk about evidence, but they often decide based on their own biases. What if the biggest source of anti-agility were in the mind, not in the process?

A few days ago I came across a book about how our mind can deceive us, and I remembered Aaron Beck and cognitive therapy. He was the one who identified cognitive distortions: "thinking errors" that lead us to interpret reality in a biased way.

Can they also creep into agile teams? In agility we talk about transparency, inspection, and adaptation. But... what happens when what distorts reality is not the data, but our way of processing it?

A few examples make this evident:

  • When we believe that "if we don't deliver everything, we've failed," we fall into dichotomous thinking (we only see black or white).
  • When an error in the demo overshadows the entire sprint, we suffer from selective abstraction (we focus on one detail and lose the context).
  • When we assume that "the client is always right" without data, we fall into arbitrary inference (conclusions without data).

And there's more:

  • Overgeneralization leads us to treat a one-off failure as a law ("the last experiment went wrong, so these techniques don't work").
  • Magnification or minimization exaggerates the negative or minimizes the positive ("that bug ruined everything... even though it was minor").
  • Catastrophizing turns any risk into an imminent disaster ("if this sprint doesn't go perfectly, we'll lose the client").

💬 If you've experienced any of these distortions, how have you dealt with them?

🔒 Restricted Poll

Please log in to your Scrum Manager account to do this.

Log in
Share:

Comments (8)

Log in to your Scrum Manager area to comment


Avatar
Guest
8 Dec 2025 11:03

Excellent Marta, talking about cognitive biases, one of the topics that impact at an individual level and therefore at a collective level.
Applied to a Scrum Team, it's an antipattern and there's a lot to discuss about it. It's one of the most important parts to work on with a team, starting with internalizing it at an individual level.
Open mind without biases and focused on the problem, being collaborative and empathetic with the problem, the user, and my teammates. So easy and so difficult to carry out.
Maybe, and I say maybe, the environment and the rules of behavior, and the knowledge of my teammates can influence these biases.
Thanks for the reflection

Automatic translation · View original

Reply Reactions
Marta Berné ★
9 Dec 2025 10:56

Thank you for your reply! Yes, I think the environment and the information we have about it completely influence these biases. And in the face of this, the best solution is honest communication.

Automatic translation · View original

Reply
Avatar
Guest
9 Dec 2025 06:38

Dear Marta Berné, excellent reflection. I think it is key to recognize that cognitive distortions affect not only individuals but also agile teams. Ultimately, transparency and inspection lose their force if the interpretation is biased.

In my experience, arbitrary inference is especially dangerous: deciding without evidence can lead to wasted energy, lost focus, and eroded team trust. That is why cultivating a culture of data and continuous feedback is more than an agile practice: it is an antidote to bias.

When a team learns to identify these "thinking errors" and turns them into opportunities for conversation, the door opens to true adaptation. It is not just about improving processes, but about training the collective mind to think clearly, question assumptions, and make more conscious decisions.

My invitation is for each leader and each team to ask themselves: what distortions are we tolerating today that limit our potential? The answer may be the beginning of a profound change.

Automatic translation · View original

Reply Reactions
Marta Berné ★
9 Dec 2025 10:58

Absolutely! Even at the individual level, asking yourself that question can change your day-to-day quite a lot. Humans tend strongly to "rumination" (getting stuck in a loop around an idea that is a generalization, for example). And these loops can be stopped by asking yourself that kind of question. A bit of metacognition never hurts.

Automatic translation · View original

Reply
Jorge Sánchez López ★★★
9 Dec 2025 09:09

Marta, excellent reflection. We talk a lot about transparency and inspection, but if interpretation is biased, agility stays a slogan.

In my experience, the biggest anti-patterns aren't in Scrum or in the process; they're in the team's mindset. Arbitrary inference is one of the most dangerous: deciding without evidence wears people down, makes us lose focus, and breaks trust. Without critical thinking, ceremonies are theater.

The key isn't to "eliminate" biases (that's impossible), but to make them visible and open to discussion: question how we think, what we take for granted about the client and about the team itself, and rely on data and continuous feedback as an antidote.

Good opportunity for every leader and every team to ask themselves: what distortions are we tolerating today that are holding us back? That's where real change begins. Thanks for opening the can of worms.

Automatic translation · View original

Reply
Marta Berné ★
9 Dec 2025 11:01

What you say makes me think: to what extent is it not possible to eliminate biases? Being aware that they exist or may exist and doing a bit of metacognition, perhaps it is possible to eliminate them before falling into them.

Automatic translation · View original

Reply Reactions
Jorge Sánchez López ★★★
9 Dec 2025 11:28

In a team, people live in an environment that may already be biased by the client, the system, or the organization. Obviously it can and surely does emit biases before reaching the team. What I mean is that there may be biases the team cannot change or simply does not detect. Maybe that can happen, don't you think?

We cannot "turn off" biases, but we can use metacognition, as you say:
thinking about how we think, observing our own mind in action
and catching ourselves when autopilot trips us up.

In teams we can bring it down to something very practical, like Start / Stop / Continue:
Start
What new thinking patterns should we incorporate?
Stop
What biases or wrong assumptions do we need to stop feeding?
Continue
What cognitive strengths work well for us and we want to keep?
And this is just one tool. There are many more.

The real question is something else:
👉 Do we have time to truly think, or are we relying on our mental GPS (biases) all day long?

Automatic translation · View original

Reply Reactions
Marta Berné ★
9 Dec 2025 14:22

Yes, I agree. And I think that to avoid running on autopilot, we have retrospectives for exactly that purpose. Many of the activities, like the one you mention, are precisely meant for this.

Automatic translation · View original

Reply Reactions