Team Dysfunction Coaching Framework: From Model to Action

A team dysfunction coaching framework helps a team investigate recurring failures in how it works: hidden uncertainties, unexamined disagreements, ambiguous decisions, missed commitments and competing priorities. Patrick Lencioni's five-part model offers one way to organize that discussion. Its labels should lead to better questions about actual work, rather than judgments that colleagues are defective.

The practical task is to identify a consequential pattern, test competing explanations and agree a change the team can actually carry out. A capacity shortage, conflicting role or inappropriate conduct may need organizational action alongside coaching. This guide develops the five areas, then follows a fictional proposal team through a complete decision, a failed warning, a corrected readiness claim and a bounded review.

Understand Lencioni's five areas and their limits

In The Five Dysfunctions of a Team and The Table Group's primary overview, Lencioni presents a layered model. Vulnerability-based trust supports debate about ideas; debate supports commitment; commitment supports peer accountability; accountability supports collective results. That is the model's proposed logic. It is not a demonstrated universal sequence for every team problem.

The following applications are original coaching guidance, not a reproduction of the publisher's assessment. If the team chooses a proprietary assessment, use its authorized administration, interpretation and permissions. Do not convert these questions into an invented validated score or infer a team's weakest layer from one workshop.

1. Make task uncertainty discussable and useful

An admission needs a response. A delivery manager can say, “I used last month's estimate, but I have not checked the new requirement.” The team then needs to decide whether to check it, reduce scope or withhold a commitment. Inviting admissions without changing the work can leave the person exposed while the original risk persists.

Ask for a recent example, what information was available and how the leader responded. Invite people to describe a task-related uncertainty they choose to discuss, with a pass option. Do not require childhood stories, health disclosures or public confessions as evidence of trust. A team can examine a flawed estimate without granting everyone access to its members' private histories.

Amy Edmondson's 1999 primary field study examined 51 work teams in one manufacturing company. Team psychological safety was associated with learning behavior, and the study supported links involving learning and performance. This concerns a shared belief about interpersonal risk taking, not the same construct as every form of trust. It does not establish that a vulnerability exercise causes performance gains or validate Lencioni's entire sequence.

Use the evidence as a reason to examine the conditions around speaking up, alongside task and organizational design. Observe whether the useful question receives an answer, whether the person is belittled and whether an unresolved dependency is actually handled.

2. Examine the proposal without turning disagreement into hostility

A useful disagreement identifies something the team needs to decide: an assumption, a trade-off, an alternative or a missing fact. “This option needs two reviewers and we have one” is different from “Your department never helps.” Ask people to locate the proposal they challenge and explain what evidence could change their view.

The primary 2012 meta-analysis by de Wit, Greer and Jehn combined 116 studies involving 8,880 groups. Relationship and process conflict showed stable negative associations with group outcomes. Task conflict had a more conditional relationship, including more favorable associations when it was less entangled with relationship conflict. These are heterogeneous research associations, not permission to manufacture arguments or a guarantee that more task conflict improves performance.

Give people time to formulate concerns before responding. The leader can hear others before announcing a preference. Offer an appropriate private route for a concern that should not be debated publicly. When a comment becomes insulting, address that conduct rather than praising the meeting for finally becoming honest.

Not every issue belongs in a facilitated team debate. Allegations of misconduct, an employment dispute or a concern requiring protected reporting may need a different process. The separate team conflict coaching guide develops the choice of route.

3. Close a decision so people can use it

Specify the decision process before asking for input. The authorized leader may decide after consultation; a board may have reserved authority; the team may make a recommendation rather than a final commitment. Calling all these processes consensus confuses participation with decision rights.

At the close, identify what was chosen, what was rejected, the conditions, the owner and the next review. Ask each affected person to explain their next action. That tests understanding more directly than a room full of nods.

A person can implement an authorized decision they did not prefer while retaining a documented concern. Specify the trigger for reopening it, such as new evidence or a missing approval. Do not demand loyalty to an outdated decision after a material condition changes. Equally, name what remains undecided, so a provisional date does not become a confirmed customer promise through repetition.

4. Check the agreement before challenging the person

Accountability needs an accepted, feasible commitment and an observable completion condition. A request made in passing is not necessarily the same as an owner accepting responsibility. Check the actual record, the person's understanding and the resources available before labeling non-delivery an attitude problem.

Use a factual opening: “We agreed an update by Thursday at noon. It is Friday and the record has no update. What happened, and what now needs correcting?” Listen for different causes. An overlooked warning, an unavailable external decision and an unrealistic allocation need different responses, even when the work remains unfinished.

Agree who can alter scope or timing, and how early a risk should be raised. Preserve the original failure when recording the repair. Receiving a late update does not mean the early-warning agreement was fulfilled. Peer discussion also does not displace a manager's responsibilities or an employee's right to use an appropriate reporting route.

5. Make the shared result compatible with real responsibilities

Define a result the team can influence and the safeguards it must respect. A sales target can encourage promises that delivery cannot meet. A quality target can become unhelpful if nobody has defined the required review. The answer is not simply to ask everyone to care more about a common number.

Ask which definitions, incentives and decisions would make cooperation rational. The person authorized to change a target or allocation needs to be involved. A coach cannot revise compensation or approve a customer commitment by facilitating enthusiastic agreement.

The HSE's current primary guidance on role clarity and work demands emphasizes clear, compatible requirements and achievable demands within agreed hours. Its relationships standard also addresses unacceptable behavior and routes for raising concerns. These are work-design and organizational responsibilities, not a team-coaching efficacy claim. They help prevent a behavioral framework from concealing conditions that management must address.

Set a complete fictional engagement around actual proposals

All people, work records, dates and results below are invented. Uma leads sales, Owen delivery, Mei quality and Rafi the business unit. Nila, the chief executive, sponsors coaching with Joss. The team says it has “an accountability problem” because proposals are repeatedly discussed without becoming dependable commitments.

Joss agrees a 90-minute team session on 16 November 2026 and a 60-minute review on 30 November. All four choose to participate. They agree that coaching examines how they make proposal commitments, while customer decisions, staffing and employment matters stay with the company. Nila will receive only a team-approved summary of the trial and its limits. Individual preparation answers will not be routine sponsor material.

Before the first meeting, each member prepares one recent proposal event using an original worksheet. They identify the requested decision, their understanding, a relevant work record and one unanswered question. They can omit sensitive client detail or discuss an appropriate concern privately with Joss. The exercise does not ask them to rate colleagues' personalities.

They examine one actual fictional event. Uma had called a target start date “agreed” in an internal summary. Owen understood it was provisional until workload was checked. Mei had requested a specific review but received no acknowledgment. Rafi had told the team to send more proposals while giving Owen too little review time. More than one explanation fits the apparent lack of accountability.

Run the first meeting with decisions and a staffing condition

Joss uses the first 15 minutes to confirm purpose, participation and conduct. Twenty minutes go to the event and different accounts, 20 to options and disagreement, 20 to the decision and capacity check, and 15 to read-back and owners. That totals 90 minutes. It is an illustrative agenda, not a proprietary intervention schedule.

When Mei raises her concern, Rafi says, “Quality keeps blocking us.” Joss stops the characterization and asks which review is actually disputed. Rafi acknowledges that he generalized about Mei's role and restates the issue: “I do not know which review is required before we call a proposal ready.” Mei supplies the relevant internal requirement. The team checks it against the proposal, rather than voting on whether her caution is excessive.

Uma: “If every date stays provisional, sales cannot give an answer.”

Owen: “I can check feasibility, but seven expected requests need three and a half hours. I have two hours allocated for this trial.”

Mei: “We can distinguish an initial response from a confirmed proposal. I need the required review visible before either is described as complete.”

Rafi: “I can move 90 minutes from the internal presentation work. That gives Owen three and a half hours, but no reserve.”

Joss: “What can you authorize now, and what must stay conditional?”

Rafi: “The internal trial and that allocation. No extra proposal volume or customer start date is authorized by this meeting.”

Owen accepts the allocation for seven forecast requests at 30 minutes each. Rafi actually records the 90-minute presentation deferral in the unit work plan. This is a management decision, separate from the coaching team's willingness to cooperate. If that allocation had remained only a proposal, the trial would have retained a resource condition.

Write and read back the actual trial agreement

The team uses this original record for requests arriving during 17–27 November. The company proposal register is the authoritative record. Rafi approves the internal operating change, and all four confirm their next action before leaving.

Uma reads back that an initial response is not authorization. Owen explains how he will record an incomplete answer. Mei confirms which review she supplies. Rafi confirms his approval responsibility and the resource decision. Joss asks whether any concern remains; Mei notes that the allocation has no spare time, which stays in the record.

Uma's local proposal-volume target has not been formally changed. Rafi tells her in the company work thread that, for this trial, he will review the accepted readiness conditions alongside volume and will not direct her to bypass them. The wider target design remains a question for the authorized company process. A coaching agreement has not silently rewritten it.

Retain two different failures during the trial

Seven requests enter the register. For P5, Uma marks the draft ready on 25 November after reading an earlier quality note. Mei notices that the current version includes a changed requirement not covered by that note. She identifies the exact change; Rafi returns the draft to pending and records why. The team retains the mistaken ready entry and correction.

Mei completes the additional check on 27 November, then Owen spends 20 minutes rechecking delivery implications. Rafi authorizes P5 afterward. The changed requirement has a real time cost: Owen's original 210 minutes of reviews plus the additional 20 becomes 230 minutes. Rafi approves and records a further 20-minute deferral from the same internal presentation work. The revised allocation is 230 minutes, fully used, with no reserve.

P7 is different. Owen had agreed to post an update by 26 November at 12:00, Europe/London. He is waiting for an external estimate but forgets to post the warning. Uma raises the missing update at the 27 November huddle. The team does not claim the external dependency made a warning impossible.

Uma: “The answer may still be unavailable, but we needed to know that yesterday. What is the current status?”

Owen: “Pending the external estimate. I missed the update I accepted. I will record that now and identify the next check.”

Rafi: “Keep it pending. Uma can acknowledge the uncertainty. We cannot describe this as approved to preserve the volume number.”

Owen posts the late status and sends the specific estimate question to the external owner through company email. Uma acknowledges the revised status and uses the agreed initial-response wording. No estimate is received before the coaching closes. Owen owns the next company check on 1 December, whose result remains unobserved. The missing warning is a retained accountability failure, even though the team handles it more clearly afterward.

Complete the review without declaring the team repaired

At 30 November, the seven-request register shows five authorized proposals, P3 held for missing customer information and P7 pending the external estimate. The five include P5 only after its corrected review and authorization. They are current end states, not seven independent tests of every behavior or a first-pass success rate. Customer acceptance, revenue and delivery outcomes are not measured.

Joss asks the team to relate observed events to each area. Owen disclosed limited capacity, and Rafi changed the allocation. Mei's disagreement exposed a real defect, following Rafi's correction of his own characterization. The written decision distinguished initial response from authorization. P7 showed that an accepted warning could still be missed. The readiness safeguards constrained a volume incentive, while the underlying target remained unresolved.

These observations offer more than a positive workshop rating, but they do not establish that trust increased or that all five dysfunctions were eliminated. The same team, register and short period supply the evidence. There is no comparison group, no validated before-and-after scale and no basis for attributing all later behavior to Joss.

The team also accounts for its effort. Four people attending 150 minutes of coaching use 600 staff minutes. Preparation takes four times 15 minutes, or 60. Two 15-minute huddles with four members use 120. Owen's trial-register administration takes 40, and Uma and Owen each spend 15 on the P7 recovery, adding 30. The total is 850 minutes, or 14 hours 10 minutes, within the agreed 15 staff-hour coaching-and-coordination allowance by 50 minutes.

Owen's 230 minutes of substantive proposal review belong to ordinary proposal delivery, tracked separately from that allowance. The other members' normal proposal and quality work are also outside it; this is a coordination budget, not a total project-cost calculation. Joss's own facilitation and preparation time are also separate. Showing one budget does not make either body of work free.

The four approve this actual fictional sponsor summary:

“The team tested a clearer proposal-readiness agreement on seven requests. At close, five are authorized, one is held for information and one is pending an external estimate. One mistaken ready entry required a further check; one required warning was late. Both remain visible in the record. Owen's review allocation was increased through explicit deferrals and was fully consumed.

“We will retain the readiness agreement internally for four weeks under Rafi's authority. We are not recommending higher proposal volume, a finding that team trust has improved or a new coaching engagement. The unresolved external estimate and wider volume-target question remain company responsibilities.”

Rafi sends the approved text to Nila by company email, and Nila acknowledges its limited purpose. Joss's engagement ends after the review. The future four weeks, external estimate and target decision are not reported as completed outcomes.

Choose a different route when the problem is different

In a contrasting fictional service team, a leader calls repeated missed handoffs “avoidance of accountability.” The work record instead shows two managers assigning simultaneous duties to one person. The authorized manager removes one duty for the next shift and confirms the revised allocation with both managers and the employee. Coaching can help examine communication afterward; it does not supply the missing person-hours.

Likewise, a report of bullying needs an appropriate response and reporting process. Do not require the employee to confront the alleged perpetrator in a trust exercise as a condition of being heard. A coach can explain the limits of the engagement and coordinate appropriately without conducting an unqualified investigation or promising confidentiality that conflicts with applicable duties.

For a wider service design, use the executive team coaching framework. The present framework is narrower: use specific patterns to choose a feasible change and check what happened next.

Support the agreed work in Coachful

Coachful is our #1 recommendation for organizing team coaching preparation and follow-through. In this case, Joss uses a group Program/cohort containing exactly the four participants and checks the actual membership and staff access before sharing anything.

He deliberately assigns the original event worksheet, explains that individual responses are visible to the authorized coach and does not present them as an anonymous team survey. A private resource link alone is not an access grant. A licensed assessment, if chosen, remains a separate authorized process.

Members post permitted preparation questions in the restricted Program community thread; Joss replies in that same thread about the two contracted meetings. Its audience is the four members and Joss. An individual can instead send a private preparation concern in one-to-one Messages to Joss, with the actual staff audience checked. That does not create extra individual coaching or authorize inclusion in Nila's report.

After explicit team approval, the shared community can hold a cleaned copy of the operating agreement and review summary. The live proposal register, customer details, external estimate and company approvals remain in the company system. Client actions can record agreed follow-through, but a completed task does not prove a proposal was authorized or a team became effective. Explore the relevant Coachful features with those distinctions intact.

Frequently asked questions

Is Lencioni's model a diagnosis?

It is a leadership discussion framework. Use actual events and consider competing explanations. A proprietary assessment has its own permissions and evidence; this article's original questions are not that assessment or a clinical test.

Must every team begin with a trust exercise?

The model places trust first, but an immediate resource, conduct or authority problem still needs the appropriate action. Task-related uncertainty can be examined without compulsory personal disclosure. Start with the consequential work and the conditions around it.

Does productive disagreement mean more conflict is better?

No. Research distinguishes different forms and contexts of conflict. Examine proposals with evidence while addressing insulting or coercive conduct. Do not create confrontation merely to show that the team is now candid.

What counts as commitment when people disagree?

Clarify the decision authority, what was chosen, accepted responsibilities and the conditions for review. A person can retain a concern while understanding implementation. Commitment does not mean suppressing new evidence or bypassing required safeguards.

How should a coach handle a missed commitment?

Check what was accepted, what happened and what resources or dependencies mattered. Agree the correction with the appropriate owner. Keep the original missed event visible rather than reporting a late recovery as timely delivery.

How can the team know whether coaching helped?

Define the intended change, observe relevant work and include failures, costs and alternative explanations. A short descriptive trial can inform a bounded decision. It does not by itself prove a causal improvement, enduring trust or financial return.