Lencioni’s pyramid of team dysfunctions
Humans are a big part of what makes up a project. Depending on the size of the project, the project team can consist of anything from a single person to several hundred people, everyone working towards a common goal. No matter the size of the project, the project management will have to make a decision about how they want to manage one of their important resources, namely the people. The project management body of knowledge (PMBOK) defines four stages of managing project human resources; Plan human resource management, Acquire team, Develop team and Manage team. Following this it becomes apparent that creating an efficient and effective project team is one of the project manager’s important tasks. In his book The five dysfunctions of a team, Patrick Lencioni describes what he claims are five dysfunctions that keep a team from performing optimally, and that need to be overcome in order to create a successful team. This article will describe how the project manager can assess these five dysfunctions, and how to overcome them.
The big idea - Stages of human resource management
What is human resource management?
As a project manager, a big part of the job will be interacting with the team, being a leader and a mentor, and being responsible for making sure that the team performs optimally. As people make up such a big part of any project, it is natural that human resource management is a key factor to analyse when analysing project management. Personnel are also a constraint, as it is often a significant part of the budget, so it is also important for the economical aspect of a project to make sound human resources decisions. The project management body of knowledge (PMBOK) names human resource management as one of the six fundamental functions of project management.  PMBOK goes on to define human resource management as the processes that organize, manage and lead the project team. Cite error: Closing </ref> missing for <ref> tag in which he presented the Forming Storming Norming Performing model. This model describes the stages of development most teams go through in order to reach optimal performance. It was later revised to add a 5th stage, adjourning.
Forming: The team members get to know each other and the project and agree on responsibilities.
Storming: The work is starting, and in this phase the group is susceptible to conflict if the members are not open to differing ideas.
Norming: In this phase the members get closer, start working better together and gain a common understanding of the work to be done.
Performing: Groups that reach this stage work effectively together, they are able to work independently and work through issues smoothly.
Adjourning: This added phase is appropriate for project groups as projects are temporary and the adjourning phase describes the completion of work and breaking up of the team.
Main challenges in team management + APPLICATIONS
Lencioni's five team dysfunctions
In his book The five dysfunctions of a team, Patrick Lencioni describe the five factors he claims cause a dysfunctional team and that these dysfunctions need to be overcome in order to become a functional team. He lays it out like a pyramid shown in figure x. Resembling Maslow’s hierarchy of needs, the pyramid illustrates that in order overcome the dysfunctions at the top, and thus achieving excellence, all the levels underneath have to be consolidated.
Absence of trust
This is the most basic of the dysfunctions and without ensuring that the team members have trust in each other this will, according to Lencioni, lead to more dysfunctions. Trust, in this case, is not necessarily to trust a person to fulfil their task, but more along the lines of trusting that you can disclose your insecurities without being judged.
Fear of conflict
If there is trust in a group, the members are more likely to be able to engage in discussions and be open to new points of view. Discussions are a healthy way of improving the way forward, and if the members are fearful of the way their ideas will be received or that what they say will be used against them they are less likely to disclose their opinions.
Lack of commitment
When members are afraid of sharing their opinions with the group and partaking in the discussion it is likely that they will end up agreeing to a solution that goes against their opinion. This will lead to ambiguous solutions without proper direction, which can be very demotivating for the members.
Avoidance of accountability
Every team member should feel accountable for all decisions made by the team if they are committed to it. When team members are not committed to the cause they will also be less likely to call out others that are slacking. If a team has come this far in the pyramid, then they should know that if they receive criticism it is not a personal attack and be willing to listen to the feedback without digging in their heels.
Inattention to results
Humans put a lot of emphasis on fairness. When they observe someone on their team not doing their fair share of work they themselves are more likely to end up not contributing as intently.
Using the pyramid
As a project manager, being aware of these dysfunctions can be useful in the two last phases of the stages of human resource management; developing and managing the team. In his book, Lencioni provides an assessment method to evaluate where the team is lacking. This assessment consists of a series of statements the team will give a score from 1 = never to 5 = always. Examples of statements are “Team members admit their mistakes” and “The team ensures that poor performers feel pressure and the expectation to improve” . The different questions correspond to one of the levels in the pyramid, and the score for each level is averaged based on the answers. The different levels are then given a high, medium or low grade according to the average value from the assessment. The description of each level can be seen in figure.
Lencioni also provides concrete examples of steps the project manager can take to aid the team in overcoming the dysfunctions.
To help build the trust level in the team, the project manager can lead by setting a good example, asking for help, owning up to his or her own shortcomings and daring to be vulnerable in front of the team, while at the same time encouraging the team to do the same.
To encourage a healthy conflict level it is important to clearly state that conflicts are not an inherently bad thing. By practicing the ways healthy conflicts look like, giving feedback, and praising good examples the team can agree on the ways they want their exchanges should look like. The project manager can also “mine for conflict”, appointing a devil’s advocate for every meeting, where that person is responsible for asking the opposing questions to make the team more open for new points of view.
Having clear and well-communicated plans is the main way to overcome lack of commitment. At the end of every meeting the team should leave, knowing exactly what they need to do, what others are doing, when the deadlines are, and contingency plans in case of unforeseen circumstances.
When a team has reached the level of accountability, they should already
Importance during the different stages of the project
Importance of the personnel factor
In the traditional view that has been presented thus far in this article, the human aspect, or the so called ”personnel factor”, is viewed as critical in regards to the success of a project. Some researchers, however, question this view and claim that the personnel factor has a limited impact on the project success. According to an empirical study performed by Pinto and Prescott the only factor that was marginal for the project success was indeed the personnel factor. This was also backed up by a study by Belout and Gauvreau , concluding that although there is some correlation between the personnel factor and the success of a project, this effect was so limited that it did not seem to have a significant impact. This can indicate that human resource management may not be as critical to project success as previously believed. Both studies do, however, note that the limitations of the correlation studies they have performed can
Project Management Institute "A Guide to Project Management Body of Knowledge" (2013), 5th Edition: Project Risk Management (chapter 9)
The PMBOK is a "subset of the project management body of knowledge that is generally recognized as a good practice" . Chapter 9 revolves around the human resource management processes and tools in a project, and elaborates on the points introduced in the Big Idea section in this wiki.
Lencioni, P (2002), The five dysfunctions of a team.
In this book, Lencioni presents his theories about the five dysfunctions of a team and describes the many pitfalls a project manager or team can fall into. It is written as a so-called "business fable", where he illustrates his points using a story telling technique.
Lencioni, P. (2005) Overcoming the Five Dysfunctions of a Team.
As a follow up to the previous source mentioned, Lencioni wrote another book focusing on the techniques a project manager or team leader can use to bring the team forward.
Pinto, J. & Prescott, J. (1988) , Variations in critical success factors over the stages in the project life cycle, Journal of Management 14 (1988) - 5
This article focuses mainly, like the name would imply, on how the different success factors vary as a function of project progression. This research is based on an empirical study they conducted, questioning 408 members of the Project Management Institute. One of the success factors they analyse is the Personnel factor, which they, contrary to their hypothesis, discover to not be critical to project success.
- ↑ A. Belout, C. Gauvreau / International Journal of Project Management 22 (2004) 1–11, Factors influencing project success: the impact of human resource management
- ↑ https://norulesjustwords.files.wordpress.com/2012/09/5dysfunctions.png
- ↑ Lencioni, P. (2005) Overcoming the Five Dysfunctions of a Team. Jossey Bass
- ↑ Project Management Institute "A Guide to Project Management Body of Knowledge" (2013), 5th Edition: Project Risk Management