Felia Kochanek
Felia Kochanek

Team development - 7 mistakes in team decisions

Team development can be quickly disrupted when making decisions in a team. Maybe you know that? There is an important team decision to be made, but after the meeting do you feel like you haven’t really been heard and overall does everything feel a bit like a lazy compromise? Then you are not alone! Because many team decision-making processes are far less structured and rational than they should be. Here you will learn about seven typical thinking mistakes, the reflection of which will help you with team development and team decisions:Ā 

1. Mistake in thinking: alternative blindness

Star investor Warren Buffett is an exceptional thinker because he is not blind in one eye. He follows the principle ā€œEvery one of our deals is measured against the second-best deal that is possible at a given time – even if it means doing more of what we are already doing.ā€ But the Buffetts of this world are few and far between, and we ordinary citizens have a strong tendency to compare option A not with its alternatives B to F, but with the status quo. For example, an empty room in the office building may be converted into another storage room, with the justification: ā€œBetter a storage room than not using the space at all.ā€ But you shouldn’t really be asking whether a storage room is better than vacancy, but better than a relaxation room for employees or a soundproofed office for the person who makes a lot of phone calls, or, or, or… 

2. Mistake in thinking: Salience effect

The most obvious, the most salient characteristic is not necessarily the decisive one and should therefore not be weighted as such. And yet we often let ourselves be blinded by shrill information and apparent connections. For a high-quality decision, however, we should always consult all available information and not just the readily available information. For example, the applicant looks very attractive - and we already find him likeable. Does that really make sense? An important effect when ā€œshaping team developmentā€ is on the agenda.

3. Mistake in thinking: social proof

Just because a lot of people say something is not automatically true. Just because a lot of people buy a product doesn’t mean it’s high quality. And just because a lot of people make the same decision, it’s not automatically good. Because even if it makes sense from an evolutionary point of view to orientate yourself on the behavior of other people, this endeavor can lead us to absurd concessions in decision-making situations. Ever heard of the Solomon Ash experiment? No? Then you can right here Read everything about it and gain further exciting insights into group thinking.Ā 

4. Mistake in thinking: Authority biasĀ 

Would you give someone extremely electric shock just because an expert in a white coat tells you to do it? Your inner answer is hopefully no, but psychological experiments (including Milgram, 1978) and history have shown that we humans are very susceptible to authority bias and that experts trust and follow almost blindly. This can be fatal for us when making decisions in a team. Therefore, always check statements and suggestions for their content quality and don’t let white coats, expensive suits and a supposed expert status blind you. It should always be about what was said and not who said it!Ā Ā 

5. Thinking mistake: Not-Invented-Here syndrome

How often do you think about your own ideas ā€œWhat a flash of inspiration!ā€ or ā€œMillion Dollar Idea!ā€? And how often does something great actually come from these ideas? Exactly :) We have a pronounced tendency to applaud our own ideas and our own work disproportionately strongly and to subordinate everything foreign. But just because something wasn’t invented here doesn’t mean it’s bad! And just because something was invented here doesn’t mean it’s good! Remain critical of your own ideas and open to foreign ones. If you want to shape team development, team members should be made aware of this.

6. Mistake in thinking: Explanation of expenses / Effort Justification

Have you ever worked on a project for a very long time and in the end it was just not very good, to say the least? And could you hardly part with it anyway? Classic case of Effort Justification! Because we attach a higher ideal and / or monetary value to things for which we had to (very) make an effort. Why else do you see the self-assembled Billy shelf as the crown of interior design and the university fraternity with the almost inhuman shooting rituals as a desirable union of great people? It is therefore important to always check when making decisions in a team as to whether it is really a good idea and a good job, or just a complex one! Then it should read ā€œ Bye bye miss and off to new shores. %E2%80%9D Even if it’s difficult!

7. Mistake in thinking: fatigue in decision-makingĀ 

It is not just a matter of how you make decisions, but also when! Because decisions are exhausting! Anyone who has ever put together their own sandwich in a fast food store and has chosen the sandwich of the day after exhausting exhaustion knows this! To make really well thought-out decisions and to try something new, we need strength! This is why important team decisions should be made when all employees are as well rested as possible and equipped with solid blood sugar levels. And that is not necessarily right before lunch break or shortly before work.

Make team development sustainable?

The software Echometer makes it possible to reflect behavioral patterns in the team and to promote the further development of the team through the exchange.

Learn More

Avoid cognitive errors in team decisions - practical tips

Knowing about errors in thinking when making decisions in a team is the first step in avoiding them and thus shaping team development. In addition, we have three tips for you so that you can protect yourself from them even more effectively.Ā 

Tip 1: The Thinking Mistake ChecklistĀ 

So simple, so good! Put together a checklist of the thinking mistakes described above (and possibly also others) and work through them whenever a decision is pending in the team.

Tip 2: Advocatus DiaboliĀ 

Depending on the team size, assign one or more cognitive errors to each team member and make him or her an expert on this special pitfall. Whenever a decision is to be made, everyone critically and intensively examines it for ā€œtheirā€ bias. But everyone else still thinks along! After all, we don’t want to fall victim to the Authority Bias ;)

Tip 3: separate idea from evaluation

We have learned that we seem to be extremely foggy from our own ideas and can hardly rationally check their quality. Therefore you should separate the generation of ideas from their evaluation. Divide your team into two groups and let one develop ideas and the other evaluate these ideas with the unfiltered lens of objectivity. With this you beat multiple thinking mistakes!

Ā 

Ā 

Literature recommendations for mistakes in thinking

Rolf Dobelli - The art of clear thinking (2011) and Rolf Dobelli - Die Kand wise action (2012)

Team development sources

Asch, SE (1951). Effects of group pressure upon the modification and distortion of judgments. Organizational influence processes, 295-303.

Buehler, R., Griffin, D., & Ross, M. (1994). Exploring theā€ planning fallacyā€: Why people underestimate their task completion times. Journal of personality and social psychology, 67(3), 366.

Cialdini, RB, & Cialdini, RB (1993). Influence: The psychology of persuasion.

Katz, R., & Allen, TJ (1982). Investigating the Not Invented Here (NIH) syndrome: A look at the performance, tenure, and communication patterns of 50 R & D Project Groups. R&D management, 12(1), 7-20.

Loewenstein, G., Read, D., & Baumeister, RF (Eds.). (2003). Time and decision: Economic and psychological perspectives of intertemporal choice. Russell Sage Foundation.

Milgram, S., & Gudehus, C. (1978). Obedience to authority.

Norton, MI, Mochon, D., & Ariely, D. (2012). The IKEA effect: When labor leads to love. Journal of consumer psychology, 22(3), 453-460.

Plous, S. (1993). The psychology of judgment and decision making. Mcgraw-Hill Book Company.

Blog category

More articles on "Teamwork"

View all articles in this category
10 Simple & Important Agile Retrospective Ground Rules

10 Simple & Important Agile Retrospective Ground Rules

Agile retrospectives are an essential part of any agile team. They give team members the opportunity to reflect on their work, identify opportunities for improvement, and set goals for the next spr...

How can you improve communication in a remote software development team?

How can you improve communication in a remote software development team?

There are various measures and approaches to improve communication in virtual or remote engineering teams of software developers and software engineers. It is irrelevant whether they are front-end,...

Sprint retrospective isn’t necessary? Yes, it is: 7 tips

Sprint retrospective isn’t necessary? Yes, it is: 7 tips

Many say that the retrospective is the most important ceremony in Agile. Woody Zuill puts it this way: If you adopt only one agile practice, let it be retrospectives. Everything else will follow. W...

Checklist: 21 Habits for (new) People Managers (PDF)

Checklist: 21 Habits for (new) People Managers (PDF)

Have you ever thought about how much your team observes you on a daily basis? Not out of mistrust - but because your behavior as a manager has a direct impact on motivation, performance and satisfa...

4 tips for team building in distributed remote teams

4 tips for team building in distributed remote teams

"Remote teams" are the trend. So how do you deal with the coordination and management of teams spread over several locations?

Getting started with agile work - Agile Explorers

Getting started with agile work - Agile Explorers

At first glance, the agile world can seem very overwhelming. You can hear Kanban, Scrum & Co. and ask yourself the question: How does it all fit together and what can I start with? In this article...

Motivating teams - The basics of committed teams (Part 1)

Motivating teams - The basics of committed teams (Part 1)

How do you motivate teams? This can be done very easily if you start out correctly. We give you the 1x1 of motivated and committed teams.

What makes a really good team

What makes a really good team

It's not just about team members. What makes a good team is much more complex. Here is a collection of the most important facts ...

Psychological Safety in Agile Teams

Psychological Safety in Agile Teams

Psychological Safety - Just Another Trend Around a Buzzword? A look into Google Trends reveals that psychological safety is currently experiencing a historic high search demand. This is not least d...

Echometer Newsletter

Don't miss updates on Echometer & get inspiration for agile working