Understanding the Five Dysfunctions

In The Five Dysfunctions of a Team, Patrick Lencioni describes a simple but powerful truth:

Teams don’t fail because they lack intelligence or strategy.
They fail because of predictable patterns of behaviour.

He outlines five dysfunctions that sit in a hierarchy. At the base is absence of trust, where team members are unwilling to be open about mistakes or gaps. This leads to a fear of conflict, where healthy debate is avoided. Without that challenge, teams experience a lack of commitment, as decisions are never fully bought into. This then results in avoidance of accountability, where standards are not upheld. At the top sits inattention to results, where individuals prioritise their own success over collective outcomes.

These dysfunctions are not rare. They are the default state of most teams unless something actively counters them.

Who and What Are the PMI and PMP?

The Project Management Institute (PMI) is the world’s leading authority on project, programme, and portfolio management. It has developed globally recognised standards that define how complex work should be structured, governed, and delivered.

One of its most widely adopted frameworks is PMP (Project Management Professional). While often associated with certification, PMP fundamentally represents a structured approach to delivery, covering areas such as scope definition, planning, risk management, stakeholder engagement, governance, and benefits realisation.

At its core, PMP is designed to bring clarity, control, and predictability to delivery. And when applied well, it does something more powerful:

It creates the conditions in which effective team behaviour becomes the norm.

The Shift in Perspective

This is where the connection becomes interesting.

The PMP framework is often seen as a set of processes, controls, and documentation.

But looked at differently:

PMP is a behavioural system disguised as a delivery framework.

Each element of PMP, when applied properly, forces the right team behaviours and directly counteracts the dysfunctions Lencioni describes.

1. Trust → Enabled by Transparency & Structured Communication

Dysfunction avoided: Absence of Trust

How PMP builds it:

• Risk & issue logs create safe, structured disclosure
• Regular reporting creates visibility for everyone
• Lessons learned normalise admitting mistakes

Positive effect:

• Problems are surfaced early without blame
• Teams become comfortable saying “we’ve got an issue”

PMP creates psychological safety through structure, not personality.

2. Healthy Conflict → Enabled by Defined Decision Points

Dysfunction avoided: Fear of Conflict

How PMP builds it:

• Scope definition sessions require challenge of assumptions
• Change control forces formal evaluation of alternatives
• Stakeholder reviews create forums for debate

Positive effect:

• Disagreement becomes part of the process, not a personal risk
• Better decisions are made earlier

PMP legitimises conflict by making it part of the workflow.

3. Commitment → Enabled by Clarity & Formal Agreement

Dysfunction avoided: Lack of Commitment

How PMP builds it:

• Project Charter defines purpose and direction
• Baselines (scope, time, cost) define what success looks like
• Sign-offs ensure visible agreement

Positive effect:

• Everyone understands what has been agreed
• “Silent disagreement” is reduced

PMP replaces ambiguity with documented clarity.

4. Accountability → Enabled by Roles, Governance & Measurement

Dysfunction avoided: Avoidance of Accountability

How PMP builds it:

• Defined roles (e.g. RACI) clarify who owns what
• Governance structures enforce review and challenge
• Performance tracking makes progress visible

Positive effect:

• Accountability becomes peer-driven, not leader-enforced
• Underperformance is visible and addressed early

PMP makes accountability structural, not optional.

5. Focus on Results → Enabled by Business Case & Benefits Tracking

Dysfunction avoided: Inattention to Results

How PMP builds it:

• Business case defines why the project exists
• KPIs and success criteria define what good looks like
• Benefits realisation tracks actual outcomes

Positive effect:

• Teams focus on outcomes, not activity
• Success is measured in business impact

PMP keeps teams anchored to value, not effort.

The Big Insight

When applied properly:

• Trust comes from transparency
• Conflict comes from structured debate
• Commitment comes from clarity
• Accountability comes from visibility
• Results come from measured outcomes

PMP doesn’t just manage projects.
It engineers the behaviours of high-performing teams.

Final Thought

Most organisations implement project management as a set of processes.

The real value is this:

It is a system that removes the need to rely on “good behaviour” by making the right behaviour the easiest path.