Informative

¿El pensamiento pone trabas a la agilidad?

Original text in Spanish · View translation

Topic illustration: ¿El pensamiento pone trabas a la agilidad?

Los equipos ágiles hablan de evidencia, pero deciden muchas veces desde sus propios sesgos. ¿Y si la mayor fuente de anti-agilidad estuviera en la mente, no en el proceso?

Hace unos días encontré un libro sobre cómo nuestra mente puede engañarnos y recordé a Aaron Beck y la terapia cognitiva. Fue quien identificó las distorsiones cognitivas: “errores de pensamiento” que nos hacen interpretar la realidad de manera sesgada.

¿Llegan a colarse también en equipos ágiles? En agilidad hablamos de transparencia, inspección y adaptación. Pero… ¿qué pasa cuando lo que distorsiona la realidad no son los datos, sino nuestra forma de procesarlos?

Algunos ejemplos lo hacen evidente:

  • Cuando creemos que “si no entregamos todo, fracasamos”, caemos en pensamiento dicotómico (solo vemos blanco o negro).
  • Cuando un error en la demo eclipsa todo el sprint, sufrimos abstracción selectiva (nos fijamos en un detalle y perdemos el contexto).
  • Cuando asumimos que “el cliente siempre tiene razón” sin datos, caemos en la inferencia arbitraria (conclusiones sin datos).

Y hay más:

  • La sobregeneralización nos hace tomar un fallo puntual como una ley (“la última experimentación salió mal, así que estas técnicas no sirven”).
  • La magnificación o minimización exagera lo negativo o minimiza lo positivo (“ese bug lo fastidió todo… aunque fuera menor”).
  • La catastrofización convierte cualquier riesgo en un desastre inminente (“si este sprint no sale perfecto, perderemos al cliente”).

💬 Si has sufrido alguna de estas distorsiones, ¿cómo la has gestionado?

🔒 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