Mental Fitness

The Team Under Pressure: Saboteurs, the Five Dysfunctions, and the Trust a Growth Decision Requires

Patrick Lencioni gave us the anatomy of a struggling team. Shirzad Chamine's work explains what is happening inside each person in the room while that anatomy forms. Read together, they stop describing behaviour and start explaining it.

Steve Kopecky · 11 minute read

The fable, read a second time

In Patrick Lencioni's leadership fable, a new chief executive inherits a Silicon Valley technology company with a strong board, funded balance sheet, better technology than its competitors — and a leadership team that cannot make a decision stick. Lencioni's diagnosis is structural: five dysfunctions stacked as a pyramid, each one resting on the tier below it. Absence of trust makes real conflict impossible. Without conflict there is no genuine commitment. Without commitment, accountability is unenforceable between peers. Without accountability, attention drifts from collective results to individual status.

Most executives who have read the book accept the model and then discover the same thing: knowing the pyramid does not change the room. The team agrees it needs more trust, schedules an offsite, and returns to the same meeting behaviour within a quarter.

The reason is that the pyramid describes what a team produces, not why each individual produces it. Read the fable again with attention on the individuals rather than the team, and something more useful appears. Each character is not being difficult. Each is running a highly practised, self-protective response to pressure — and each response is coherent, effective earlier in that person's career, and invisible to them.

The five dysfunctions are not five problems. They are the predictable output of a room full of untrained pressure responses.

What is actually happening inside each person

In Positive Intelligence® terms, the master pattern is the Judge: the internal voice that finds fault with yourself, with others, or with circumstances, and delivers its verdict with the felt authority of fact. The Judge recruits accomplice Saboteurs — Controller, Avoider, Pleaser, Hyper-Achiever, Hyper-Rational, Hyper-Vigilant, Restless, Stickler, Victim — each of which was useful at some point and each of which now runs automatically under load.

That mechanism is physical, not attitudinal. Threat circuitry fires before appraisal completes; attention is pulled toward the perceived threat; and evidence suggests prefrontally-dependent capability — working memory, flexible reasoning, perspective-taking — degrades under acute stress while habitual responses strengthen (Arnsten, Nature Reviews Neuroscience, 2009). The executive is not choosing to withhold the objection. The capability required to voice it well is temporarily narrowed, and the practised response takes the wheel.

Now put five or seven of those responses in the same room, with capital at stake and a decision that will expose someone. Trust is the first casualty, because disclosure is exactly what every Saboteur is organised to prevent. And once the base tier is compromised, the rest of the pyramid follows without anyone intending it.

Exhibit · FOUNDATION™ · Grouping 20

A high-performing team is not a mood. It is a structure — and the structure is drawn.

Read at three levels: the individual under pressure, the team's behavioural contract, and the vocabulary that makes the load-bearing tier reachable. All three are read inside Compass Enterprise Architecture™, which is what turns insight into an architected next phase of growth rather than a good session.

Order of precedence

01

Compass Enterprise Architecture™

The enterprise model comes first: economic truth, the vital few, decision rights, cadence and the architecture of the next phase of growth. The instruments serve it; it does not serve them.

02

FOUNDATION™ — where teaming sits

Mental Fitness is diagnostic grouping #20 inside FOUNDATION™. Team behaviour is read here because it determines whether the architecture above it can be operated honestly.

03

Instruments, then a system change

PQ®, the team read and DISC produce evidence, not a verdict. Every claim ships with a visible change to decision rights, roles, standards or cadence, closed through ARC™ — Analyze · Refine · Commit.

CompassOS™ carries the instruments, the evidence and the record. It is the layer the work runs on — never the work itself.

Level 01 · The individual under pressure

Before a team fails to disclose, a nervous system decides disclosure is unsafe.

Engraved midline section of the human brain on a navy field, annotated for the regions involved under pressure
Interhemispheric traffic, drawn. Judge, Saboteur, Sage and PQ® are terms from the work of Shirzad Chamine and Positive Intelligence, LLC.
  • Threat circuitry fires first. The alarm system does not distinguish a hard question in a boardroom from physical danger. The body commits before the argument is examined.
  • The Judge narrates. Its accomplice Saboteurs borrow the urgency, and the story is experienced as fact rather than as one reading of the evidence.
  • Sage capability narrows. Deliberate judgment, perspective-taking and empathy are the first functions to degrade — which is precisely what a team needs most at that moment.
  • Training is physical. Deliberate exercise develops the human brain and its connections. Repetition strengthens the pathways used under load and lets unused ones weaken — the same principle as loading a bone once it is stabilised.

Level 02 · The team's behavioural contract

Five tiers, drawn as structure: each one carries the weight of everything above it.

PLATE I · THE TEAM BEHAVIOURAL CONTRACTFive tiers. Each one carries the weight of everything above it.MODEL · P. LENCIONIDYSFUNCTIONTHE BEHAVIOUR THAT REPLACES IT05Inattention to ResultsLocal wins rise; the result stalls.Collective focus on outcomesARC™ — RENEW AROUND RESULTS04Avoidance of AccountabilityThe standard falls to what is tolerated.Peer-to-peer accountabilityGROW — DESIGN FOR CONSISTENCY03Lack of CommitmentDecisions are relitigated; dates drift.Clarity and buy-inLEAD — OWN THE STANDARD02Fear of ConflictThe real debate moves to the hallway.Unfiltered, productive debateSIMPLIFY — SURFACE THE REAL CONSTRAINT01Absence of TrustImpression management wins.Vulnerability-based trustFOUNDATION — UNLOCK POTENTIALLOAD-BEARING TIERNo tier above this one performs better than the disclosure the team can survive.Model: The Five Dysfunctions of a Team — Patrick Lencioni, Jossey-Bass (Wiley).Drawn plate, load-bearing read and discipline mapping: Compass Performance, Inc. Not affiliated with, nor endorsed by, Patrick Lencioni, The Table Group or Wiley.

01 · Vulnerability-based trust

People can say "I was wrong", "I don't know", "I need help" without cost.

The Judge makes disclosure feel dangerous. Avoider hides the issue, Controller overrides it, Hyper-Achiever performs competence instead of admitting need.

02 · Unfiltered, productive debate

The team argues about ideas in the room, not in the hallway afterwards.

Pleaser keeps the peace, Avoider changes the subject, Controller wins the exchange. The disagreement does not disappear — it relocates.

03 · Clarity and buy-in

Decisions leave the room intact, with an owner and a date.

Stickler and Hyper-Rational keep refining, Restless reopens the option set, Victim quietly withholds. Ambiguity becomes the safest position.

04 · Peer-to-peer accountability

Peers hold the standard without routing every correction through the leader.

Avoider defers the hard conversation, Pleaser protects the relationship, Hyper-Vigilant escalates instead of addressing. The standard drifts to the lowest tolerated level.

05 · Collective focus on results

One scoreboard outranks status, turf and function.

Hyper-Achiever optimises personal record, Controller protects territory, Restless chases the next thing. Local wins accumulate while the enterprise result stalls.

Level 03 · The shared vocabulary

A team cannot practise disclosure until difference stops being read as a verdict.

PLATE II · THE SHARED VOCABULARYDifference read as pace and outlook — never as a verdict.MODEL · DISC (MARSTON LINEAGE)DDOMINANCEIINFLUENCESSTEADINESSCCONSCIENTIOUSNESSFASTER PACEMORE MEASURED PACEPEOPLE-FIRST OUTLOOKTASK-FIRST OUTLOOKTHE READING · WHAT EACH STYLE GIVES, WHAT IT GUARDS, AND THE FIRST REPD · DominanceDecides early, drives to the resultGives: the hard thing, said earlyGuards: a verdict before the room speaksFirst repName one uncertainty before deciding.I · InfluenceMoves fast through people and ideasGives: the opening, and the warmthGuards: precision, traded for harmonyFirst repResolve the issue; do not smooth it.S · SteadinessHolds steady; keeps commitmentsGives: a room safe enough to speak inGuards: disagreement, held back for peaceFirst repRaise the objection in the meeting.C · ConscientiousnessWorks to evidence and standardGives: decisions built on real evidenceGuards: analysis, used as coverFirst repCommit, and state the open risk.Model: DISC, in the lineage of William Moulton Marston; assessed through independent publishers' instruments, including Everything DiSC® (John Wiley & Sons, Inc.).Drawn plate, plotting and interpretation: Compass Performance, Inc. No affiliation, sponsorship or endorsement implied.

Style is a starting point, not an explanation and not an excuse. The plate suggests where a given team may find the first tier hardest and what the first repetition looks like — a reading worth examining together, not a classification of people.

Why it belongs in the architecture

A powerful team uses Compass Enterprise Architecture™ to face economic truth and architect the next phase of growth. Mental Fitness and the team contract are how that team stays able to do it under pressure — which is the only condition that ever matters.

Evidence from these instruments is read separately and never averaged into a single score. Where causality is unproven, the reading says so.

Instruments and attribution

The Five Dysfunctions of a Team model, the team pyramid, and the fifteen-statement team assessment are the work of Patrick Lencioni, published by Jossey-Bass, a Wiley brand. Used here for facilitated development purposes with attribution. Compass Performance, Inc. is not affiliated with, nor endorsed by, Patrick Lencioni, The Table Group, or Wiley.

Positive Intelligence®, the PQ® Score, and the Saboteur model are trademarks and the work of Shirzad Chamine and Positive Intelligence, LLC. Compass Performance, Inc. does not own them and claims no rights in them; Compass is an independent user of these licensed instruments. The Compass service is Mental Fitness™, and the reading, interpretation and commentary here are Compass's own. No affiliation, sponsorship or endorsement by Shirzad Chamine or Positive Intelligence, LLC is implied.

DISC is a behavioural model in general professional use, originating in the work of William Moulton Marston and developed commercially by a number of independent publishers, including Everything DiSC® (a registered trademark of John Wiley & Sons, Inc.). Compass Performance, Inc. owns the Compass reading, the plotting and the interpretation presented here, claims no rights in any publisher's instrument or trademark, and implies no affiliation, sponsorship or endorsement.

The pyramid, tier by tier, with the pattern that erodes it

Vulnerability-based trust asks a leader to say "I was wrong", "I don't know", or "I need help" without cost. Avoider changes the subject, Controller overrides, Hyper-Achiever performs competence instead of admitting need. The team concludes it has a trust problem; what it has is a room of people protecting themselves competently.

Unfiltered debate asks for the disagreement in the room rather than in the hallway. Pleaser keeps the peace, Avoider defers, Controller wins the exchange. The conflict is not removed — it relocates to side channels, where it costs more and resolves nothing.

Clarity and buy-in asks that a decision leaves the room intact with an owner and a date. Stickler and Hyper-Rational keep refining, Restless reopens the option set, Victim withholds quietly. Ambiguity becomes the safest position available to everyone.

Peer-to-peer accountability asks colleagues to hold the standard without routing every correction through the leader. Avoider postpones the hard conversation, Pleaser protects the relationship, Hyper-Vigilant escalates rather than addresses. The standard settles at the lowest level the team tolerates.

Collective focus on results asks that one scoreboard outrank status, turf and function. Hyper-Achiever optimises personal record, Controller protects territory, Restless chases the next thing. Local wins accumulate while the enterprise result stalls — which is the condition most often mistaken for a strategy problem.

Read this way

Two axes, never averaged

Score the tier and name the pattern separately. A weak tier with a clear pattern is trainable behaviour. A weak tier with no pattern usually means the operating system — decision rights, priorities, information, cadence — is producing the behaviour, and no amount of individual work will fix it.

Why DISC belongs at the base of the pyramid

Vulnerability is the hardest thing to ask of a leadership team, because the request sounds like an invitation to be exposed in front of people whose judgment they have not calibrated. DISC solves a narrow, decisive part of that problem: it gives the team a neutral, non-pathologising vocabulary for difference. Pace and outlook, not character.

When a fast, task-first colleague understands that a measured, people-first colleague is not obstructing but sequencing, and the measured colleague understands that directness is not contempt, the interpretation layer changes. Difference stops being read as a verdict. That is the precondition for disclosure: people become vulnerable with colleagues whose responses they can predict.

DISC also makes the first rep concrete for each style. Dominance slows the verdict and names one thing it is unsure of. Influence stays on the specific issue long enough for it to resolve rather than smooth. Steadiness puts the objection on the table inside the meeting. Conscientiousness commits with the evidence available and states the residual risk. Four small, observable acts — and the base tier of the pyramid starts to carry weight.

Used carelessly, DISC becomes a label and Saboteur language becomes an insult. Both are read the same way at Compass: as a description of a response under conditions, never as a permanent statement about a person, and never separate from the system that evokes and rewards that response.

People do not become vulnerable with people they trust. They become vulnerable with people whose responses they can predict.

The part that earns board time

None of this is a wellbeing programme. The commercial argument is narrower and harder: the decisions that change an enterprise's trajectory are all decisions that trigger pressure responses. Naming the product line that must be de-invested. Stating the real margin on the largest customer. Telling a founder that the capability that built the company is now the constraint. Agreeing that a senior leader is in the wrong seat.

A leadership team that cannot hold those conversations does not get a smaller version of the growth decision. It gets a substitute: an improvement plan that moves the result toward the limit of the current design, while the design itself — and therefore the limit — goes unexamined.

This is why Mental Fitness sits inside FOUNDATION™ in Compass Enterprise Architecture™ rather than beside it. A high-performing team is not the goal; it is the instrument. It is what lets a business face its own economic truth — where value is actually created, what complexity actually costs, which capacity is committed to work that no longer earns it — and then architect the next phase of growth rather than negotiate with the current one.

One further discipline, which Compass treats as non-negotiable: individual awareness is never claimed as an intervention on its own. Every mental fitness or teaming claim ships with a system change alongside it — decision rights, roles, standards, cadence, or the measure pair the team is now held to. Awareness without a system change is a workshop. Awareness with one is architecture.

Use it this week

  • Team Health AssessmentThe fifteen-statement read of the five tiers, scored and placed on the pyramid, with the tier the team should work first.
  • Mental Fitness Team ReadingEach person enters their own PQ® Score and top three Saboteurs and receives their own reading; the team sheet reports the pattern, never a comparison of named individuals.
  • Team Health with DISCThe same five tiers read against the team's behavioural composition, including the styles nobody on the team leads with.

Exhibit

Reading a tier honestly

For each tier, record what the team does, the pattern most visible when it is under load, and the system change that must ship with the behavioural work. Small enough to reproduce on a whiteboard.

TierWhat it asksPattern under loadSystem change that must ship with it
01 TrustSay "I was wrong", "I don't know", "I need help"Avoider, Controller, Hyper-AchieverA standing agenda slot where error and risk are reported without consequence
02 ConflictArgue in the room, not the hallwayPleaser, Avoider, ControllerDecision rights stated before the debate, so the argument has a purpose
03 CommitmentLeave with an owner and a dateStickler, Hyper-Rational, RestlessA written decision record read back at the close of every meeting
04 AccountabilityHold the standard peer to peerAvoider, Pleaser, Hyper-VigilantA published standard and a weekly review the leader does not chair alone
05 ResultsOne scoreboard outranks turfHyper-Achiever, Controller, RestlessA shared measure pair across the value stream, not per function

Two axes are read separately and never averaged: behaviour, and the system that evokes it.

Symptoms worth examining before your next growth decision

  • The real conversation happens after the meeting, in ones and twos.
  • Decisions are relitigated weeks later by people who were in the room.
  • Correction only travels through the leader, never between peers.
  • Nobody has said out loud what the largest customer or product line actually earns.
  • The team can describe an improvement plan in detail and the design assumption behind it not at all.
  • One executive's directness, or another's caution, is discussed as a character issue rather than as a pattern under conditions.

A team does not become high-performing by liking each other more. It becomes high-performing when its people can be predictable to each other under pressure, name the economic truth without flinching, and then use that clarity to architect what comes next.

Share this

LinkedInX

Download this article

The French and Spanish sheets are translated at board register on request; the structure, exhibit and checklist are identical in all three.

Kept on this device — no address collected, nothing emailed.

The other side of the argument

Send a question or an insight

Nothing here is published. Your note goes directly to Steve Kopecky, who reads every one — reader questions decide what gets written next.

What kind of note is this?

0 of 4000 characters. Please leave out client names and confidential detail.

Or email directly

Aligned to FOUNDATION™

Present reality, leadership capability, purpose and organizational health.

Continue reading

Organization Design

Clean Sheet Organization Design: Building the Structure the Strategy Requires

A clean sheet design starts from the strategy and the vital few opportunities, not from the current org chart. This is the process, the ownership and the SIPOC that governs it.

Organizational Architecture

The Eight Culture Types Are Not Types. They Are Eight Reinforcement Patterns Your Design Is Already Running

The eight culture descriptors in circulation describe what an organization rewards, tolerates and discourages. Read that way they stop being labels to pick and become findings to trace back to the mechanism producing them.

Program & Project Management

The Next Phase Is Delivered Across Boundaries — Which Is Why Program Management Becomes a Capability, Not a Role

The functional strength that carried an organization to its current size is the same boundary its next phase has to cross. Program and project management is how work becomes deliverable across those boundaries.

Front-to-Back 80/20

Chasing Revenue, Paying for Complexity — Global Growth Dynamics and the Twenty Percent That Actually Earns the Growth

Growth pursued as revenue funds the vital few and the trivial many on the same terms. Here is the cascade that follows, the quartile and quad decision that answers it, and the mental strength a leadership team needs to change a design that earned its respect.

Program & Project Management

Programs Rarely Slip on Schedule. They Slip at the Hand-Off Nobody Owns.

By the time a program date moves, the real failure is weeks old. It happened at a hand-off between two functions, where the work left one owner and arrived at nobody.

Program & Project Management

“Herding Cats” Is Not a People Problem. It Is Undeclared Authority.

You are accountable for an outcome and you manage nobody who produces it. The advice is to influence without authority. The honest read is that authority was never declared.

Personal Effectiveness

A Message on Personal Habits: The Private Architecture Behind Every Executive Result

Architecture determines performance — and that is as true of a person as it is of an enterprise. A long-form message on habit design, 80/20 daily management, and the self-talk that governs behavior.

Organizational Architecture

The Architecture That Created Today's Success Rarely Produces Tomorrow's Results

The structure that carried a business to its current size is usually the constraint on its next stage. That is a design problem, not a people problem.

Organizational Architecture

The Engagement Layer: Why Slack Sits at the Center of Every Compass Partnership

Most advisory relationships depend on quarterly meetings and email chains. Compass designs the engagement as an operating layer — and Slack is where it lives.

Growth & Value Creation

The Second Curve Begins Before the First One Ends

The right moment to build what comes next is while the current business is still strong — which is precisely when no one feels the need to.

Simplification

Complexity Quietly Consumes Margin, Capacity and Leadership Attention

No one approves complexity. It accumulates one reasonable decision at a time, and it is paid for in margin, speed, and executive attention.

Simplification

FOCUS: The Vital Few Constraints That Create Economic Value

FOCUS is not doing less. It is concentrating effort on the customers, products, and markets that produce disproportionate value — and removing the complexity mirror they cast inside the organization.

Organizational Architecture

What Is Enterprise Business Architecture — and Why Does It Determine Performance?

Enterprise business architecture is the deliberate design of how an organization decides, aligns, and executes. It sets the ceiling on performance long before effort does.

Organizational Architecture

The Ten Elements of an Enterprise Architecture — and Why They Only Hold Together

Strategic intent, simplification, leadership, governance, planning, cadence, decision rights, performance, enabling systems, and renewal. Designed together, or not designed at all.

Strategy & Execution

Architecture vs. Improvement: Why Better Execution Cannot Fix a Flawed Design

Improvement makes the current system perform closer to its limit. Architecture changes the limit. Confusing the two is the most expensive mistake in the mid-market.

Organizational Architecture

Every Organization Is Producing Exactly What Its Design Allows

Decision rights, cadence, reporting lines, incentives and leadership habits are not background. Together they are the machine producing the number on the books.

Organizational Architecture

Effort Cannot Solve a Design Problem

Pressure produces a short improvement, then the system pulls the result back to where the architecture says it belongs.

Organizational Architecture

Architecture Is Designed, Not Discovered

The work is concrete: name the few outcomes that matter, place each decision where it is properly made, remove the complexity consuming margin, and rebuild the cadence so commitments close.

The CEO / Owner Lens

The Chief Executive Is Not Supposed to Be the Integration Mechanism

When strategy only reaches the work through the chief executive, growth adds volume to an unresolved design. The fix is structural, not personal.

The CHRO / People Lens

Turnover Is Usually a Structural Reading, Not a Hiring Result

When roles, capability, managers and recognition point in different directions, capable people leave — and the organization reads it as a recruiting problem.

The Operations Lens

Performance That Depends on Who Is on Shift Is Not Performance

Where the process is undefined, capable people carry it. The result looks like variable performance and is read as a discipline problem.

The ERP / Systems Lens

An ERP Program Is a Process Decision Wearing a Technology Budget

Systems enable the management system; they never replace it. Configuring before the process is designed automates the current mess at scale.

The Exit / Succession Lens

A Buyer Discounts Precisely What the Owner Cannot Hand Over

Transferable value is documented processes, governed data, named successors and results that hold when the founder is not in the room.

The Leadership Team Lens

A Team That Meets Often and Decides Rarely Is Compensating for a System

When reviews end in discussion rather than dated commitments, the same root cause is rediscovered every quarter.

The AI & Data Lens

Pilots Demonstrate Capability. Designed Processes Produce Results.

AI moves a measure inside a process. Where the process is undesigned and the data ungoverned, there is nothing for it to move.

The Transformation Lens

Exhaustion Is Routinely Misread as Resistance

Change fails at the point of absorption far more often than at the point of design. Capacity, honesty about recent change, and reinforcement decide the outcome.

The Strategic Program Lens

Becoming Efficient at Work You Never Chose

Portfolios fail at intake far more often than in delivery. Unranked work consumes the capacity that strategy was supposed to direct.

The Next-Curve Lens

The Next Curve Is Absorbed by the People Already at Capacity

A next curve is designed on paper and delivered by an organization that must also run the current one. Readiness is whether the system can carry both.

The next step

See this in your own organization.

Reading about the operating system is one thing. Seeing yours clearly is another. Start with where you actually are.

Not sure where to start?

Three questions, and we point you to the right instrument.

Under a minute. From this page, most leaders begin with The organization.