Get a top-rated gantt chart for free, forever.

Discover why companies like Amazon, Netflix, and Nike manage their projects with TeamGantt.

Create your free project plan
Free forever. No credit card required.
Get a top-rated RACI chart free, forever.

Discover why companies like Amazon, Netflix, and Nike manage their projects with TeamGantt.

Create your free project plan
Free forever. No credit card required.
Team Productivity

4 Science-Backed Reasons Your Team Is Dysfunctional

Daniel Threlfall
January 23, 2017
Choose your template
Free, online RACI chart
Easy-to-use and tied to your project plan. Completely free with 1+ million users!
Free forever
Way better than an Excel template.
or
Boring Excel template
A standard, premade Excel RACI chart template for assigning project roles.
Check your email. šŸ˜ƒ
Oops! Something went wrong while submitting the form.
Enter your email to download.
Subscribe to blog & access downloads
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Download the

When weā€™re part of a team, weā€™re involved with a complex structure. A team is a machine with multiple moving parts, and all those parts have to work in unison. We can use research to fix problems, but more importantly, we need to understand why these problems are occurring to begin with.

If we know the reasons behind team dysfunction, we can both fix the issues and make sure they donā€™t happen again. But we need to look in the right places.

My research surfaced 4 reasons for a teamā€™s dysfunction.

Rather watch than read? Check out the video below.

1. Your team is cross-functional.

On paper, cross-functional teams seem like a good idea. They ostensibly allow a company to make the most of its workers. However, when Behnam Tabrizi surveyed 95 cross-functional teams for a Harvard Business Review piece, he discovered that a whopping 75% of the teams were dysfunctional.

Tabrizi used 5 criteria for measuring a teamā€™s dysfunction:

  1. Meeting a planned budget
  2. Staying on schedule
  3. Adhering to specifications
  4. Meeting customer expectations
  5. Maintaining alignment with corporate goals

Dysfunctional teams all failed at least 3 of these criteria.

Tabrizi explained it this way:

Cross-functional teams often fail because the organization lacks a systemic approach. Teams are hurt by unclear governance, by a lack of accountability, by goals that lack specificity, and by organizationsā€™ failure to prioritize the success of cross-functional projects.

When cross-functional teams lack guidance, they turn into a mess. They donā€™t have a clear goal in sight, and often, they donā€™t even know where to start.

If you lead or are part of a cross-functional team, there are some crucial changes you can make or suggest to get the ball rolling again.

  1. Make sure the team is being managed by a higher-up. As Tabrizi notes, ā€œunclear governanceā€ can kill a cross-functional team, so make sure the governance is present and obvious.
  2. Make sure the team has a common goal that's aligned with the companyā€™s goals. If a team isnā€™t seeing the big picture, they have a huge chance of failing. Each team member should have a lucid understanding of the objectives, and those objectives should fall in line with corporate.
  3. Encourage all team members to communicate about project requirements and specifications. If thereā€™s a specific budget that needs to be adhered to, each team member needs to be constantly aware of that. If there are certain guidelines for the project at hand, everyone should be constantly aware of that too.

Being alert to the inherent problems of cross-functional teams can often help solve the issues. When you know the underlying troublemaker at hand, you can more easily target and deal with it.

2. Your team isnā€™t collaborating.

Collaboration is one of the most important forces behind a successful team. But weā€™ve all been in teams where not everyone pulls their weight. Some teams can seem like multiple individuals instead of one group.

But thereā€™s a trickier question here: Why does team collaboration matter? If the individuals in a team can each pull their own weight and contribute on their own, isnā€™t that enough? The answer is no.

To uncover why, letā€™s take a look at an analog to the workplace: the classroom. In a study performed at Edith Cowan University in Australia, researchers analyzed 2 teamsā€”1 successful and 1 unsuccessful.

They found that the unsuccessful team members were focused on their own tasks instead of contributing to the group. They also communicated poorly and didnā€™t want to discuss problems.

On the other hand, the successful team ā€œfelt that they had a responsibility toward the other members of the team and that the success of the project was based upon each team memberā€™s contribution.ā€

Collaboration is well explained in the age-old maxim: ā€œTwo heads are better than one.ā€ One person in isolation may come up with great ideas, but in a team environment with othersā€™ feedback, those ideas tend to thrive and create new ideas.

Itā€™s easy to see why non-collaborating teams fail. But hereā€™s the more important question: How do you fix them?

  1. Ensure everyone is on the same page with a healthy attitude and a willingness to contribute to the group. In the Edith Cowan case study, the successful team felt like they had a responsibility to contribute, and they valued each otherā€™s opinions. Every team has to have those qualities. When we value the contributions of our team members and create a welcoming atmosphere, we cultivate the best conditions for collaborative teamwork. Members should be unafraid to present their ideas and address problems. Under these conditions, teamwork flourishes.
  2. Make collaboration a priority. This sounds like an obvious remark, but unfortunately, many team leaders set their teams free without ever mentioning collaboration. By emphasizing the importance of collaboration, youā€™ll prime your team to work together and contribute.

3. Your team is too big.

In another classic example of modern workplace thought, weā€™re often told that bigger teams are better. At first glance, this seems like an obvious factā€“ā€“bigger teams have more brains and more brawn, and thus theyā€™re better than smaller teams.

Right? Mm, maybe not.

In 1913, a French professor named Maximilien Ringelmann decided to test out this idea with a rope. In what is now a classic social experiment, Ringelmann asked people to pull on a rope, both by themselves and with a group.

He found, unsurprisingly, that people put in a fair amount of effort into pulling the rope. But when people were put into a group, they put less effort into pulling the rope.

Even more interestingly, as more and more people were added to a group, each member put in less and less effort. (A second study in 1974 underscored this hypothesis, called the Ringelmann effect or social loafing.)

Notice how expanding size of the group is directly proportional to the decreasing effort of its individual participants.

ropepulling

Amazonā€™s Jeff Bezos has a team policy that is built on the Ringelmann effect. His philosophy is called the 2 pizza rule. If a team can be fed by 2 pizzas, thatā€™s an ideal team size. If thereā€™s too many people for 2 pizzas to feed, Bezos makes changes.

Like the Ringelmann effect, thereā€™s some serious science behind the 2 pizza rule. It helps combat the groupthink that tends to occur in larger teams, and it greatly mitigates the amount of social loafing that occurs.

While itā€™s typical to believe that bigger teams produce better results, thereā€™s actually power in smaller numbers. If your teams are too big, they may be sabotaging themselves.

If your groups have more than 6 or 7 people, try downsizing to that range. You might even consider trying 3- or 4-person groups.

Or, if you want to really test the Ringelmann effect, send some team members out on their own. If Ringelmann is right, then your solo members should increase their efforts.

4. Your teams arenā€™t balancing the workload.

Your team might be collaborating, but there could be something sneaky going on under the radar: workload imbalance.

Itā€™s not unusual for 1 or 2 highly driven team members to take on most of the work. While these members think theyā€™re helping the team, theyā€™re actually eclipsing their teammatesā€™ abilities.

On the other hand, the team leader or supervisor may be causing the imbalance. Itā€™s sadly common for leaders to overwork certain high-performing members and deprive those who may get work done more slowly.

Whatever the cause of the workload imbalance, this isnā€™t how teams should operate. If 1 or 2 people are doing all the work, theyā€™re overexerting themselves, and the other membersā€™ skills are going to waste.

As Matthew Swyers says, ā€œA successful team combines individuals who come together to accomplish the defined goal and spread the workload evenly across team members. Each person is necessary to achieve the goal.ā€

This utopian definition of a work team is rarely seen in the real-life workplace. Instead, teams are like uneven seesaws. The work may be getting done, but itā€™s not happening in the most beneficial manner.

The best method of preventing workload imbalance is by assessment. You should regularly speak to each team (and ideally, each team member) about their role. Often, when thereā€™s a workload imbalance, itā€™s because one or more members are unaware of their role.

That study at Edith Cowan University emphasized ā€œappropriate team compositionā€ as a driving factor behind a successful team, saying ā€œteam members need to be fully aware of of their specific team role and understand what is expected of them in terms of their contribution to the team and the project.ā€

The next step is to consider each memberā€™s strengths when distributing the work. If members are receiving assignments that donā€™t gel with their work style, they might offload the work or simply ignore it. But if you assign work according to aptitude, thereā€™s a much higher chance that everyone will feel compelled to contribute.

Thereā€™s no exact science here, which is why regular assessment is important. If a team is imbalanced, work with them to fine-tune the workload. Seek their honest feedback and use it to improve the team experience.

Conclusion

Team dysfunction happens. Rather than beat yourself up for it, try to learn from it. Assess the problem, and seek to fix it.

Fixing a dysfunctional team can be a headache, but itā€™s a small price to pay. When these issues are fixed, teams work like they should.

If you see the signs of team dysfunction in your workplace, speak up about it. Others may not even be aware. Your voice could help save countless hours of wasted time and lost productivity.

Most importantly, when youā€™re leading a team or part of one, do your best to combat team dysfunction. If you see an imbalanced workload, suggest a solution. If your team is too large, ask about splitting it up.