Last Updated: November 12, 2026
The Five Dysfunctions of a Team conflict resolution model examines four obstacles that can prevent a team from resolving an issue: individual, relationship, environmental, and informational obstacles. Start by defining the issue, then investigate what is preventing the team from addressing it.
For CEOs and their management teams, another question matters:
Who has authority to turn the discussion into a decision?
A team can debate openly and remain stuck. Managers can understand one another’s positions while operating under conflicting priorities, overlapping responsibilities, or unclear approval rules.
Better conversation matters. It does not settle an authority question the organization has never answered.
Patrick Lencioni’s framework provides a way to examine obstacles to productive conflict. Rainmaker extends the examination to the organizational conditions surrounding the disagreement.
The goal is not more debate. It is a clear decision, explicit commitments, and a reliable way to act.
What Is Productive Ideological Conflict?
Productive ideological conflict is disagreement about ideas, assumptions, priorities, and trade-offs, not an attack on the people presenting them. Lencioni distinguishes this debate from personal conflict and emphasizes examining different perspectives before making decisions.
The difference is practical.
“This proposal assumes we can absorb the additional workload. What evidence supports that assumption?” examines the proposal.
“You never understand what our department does” attacks the person and leaves the decision unresolved.
A productive discussion makes relevant information and reasoning available for examination. It does not require hostility, raised voices, or manufactured disagreement.
A quiet meeting is not proof of alignment. A loud meeting is not proof of candor.
The test is whether the relevant concerns were considered and the team knows what happens next.
For the broader framework, read How to Overcome the Five Dysfunctions of a Team.
Build the Foundation: Vulnerability-Based Trust
In Lencioni’s model, vulnerability-based trust supports productive conflict. Team members must be able to acknowledge mistakes, limitations, and uncertainty without making every discussion a defense of their personal standing. Fear of conflict arises when preserving artificial harmony displaces useful disagreement.
The CEO belongs inside that expectation.
Consider a CEO who invites challenge but dismisses objections before examining them. The invitation and the response contradict each other. Asking managers to speak more openly leaves that contradiction intact.
Examine both sides: whether managers raise relevant concerns and what happens when they do.
Trust also does not require unrestricted disclosure. Managers should not have to share private experiences to demonstrate commitment to the team. Sensitive concerns need an appropriate reporting route.
Our article on vulnerability-based trust and the CEO’s role explores that foundation.
Healthy Conflict Is an Ongoing Discipline
Think of healthy teamwork as organizational hygiene. One shower does not complete personal hygiene. One Five Dysfunctions of a Team workshop does not complete the work of maintaining a healthy management team.
The comparison repetition, not simplicity.
Developing and maintaining a cohesive leadership team is ongoing work. Healthy conflict belongs in that continuing practice.
Managers must keep raising relevant concerns, testing assumptions, and clarifying commitments. The organization must establish the authority and operating rules that allow those commitments to hold.
The management team owns the discipline. The organizational design must support it.
Lencioni’s Conflict Resolution Model: The Four Obstacles
Lencioni’s Overcoming the Five Dysfunctions of a Team: A Field Guide for Leaders, Managers, and Facilitators includes the detailed conflict-resolution model and related exercises.
The starting point is issue definition. Take a typical sales example.
“Sales and finance do not work well together” describes a broad complaint.
“Who can authorize this customer discount, using which criteria?” identifies a decision.
Confirm that everyone is examining the same issue. Otherwise, one pricing exception can become an argument about the entire relationship between two departments.
Then examine the obstacles.
| Obstacle | What to examine |
| Individual | Differences in experience, knowledge, perspective, and responses to disagreement. |
| Relationship | History, reputation, status, and unresolved interactions between the people involved. |
| Environmental | Culture, organizational politics, morale, and the setting surrounding the discussion. |
| Informational | Facts, assumptions, opinions, and differing interpretations of the available information. |
These categories direct attention to what may obstruct resolution. They are not labels for diagnosing colleagues. More than one obstacle can affect the same disagreement.
Ask questions that clarify the issue rather than assign motives.
Which experience informs this concern? Is an earlier disagreement affecting the current discussion? What happens when someone challenges the prevailing view? Which assumption is being treated as a fact?
The objective is to understand what prevents resolution, not to explain away someone’s position.
What Is Actually Keeping This Conflict Unresolved?
Our experience adds an organizational-design inquiry to the examination.
The following guide is Rainmaker’s application, not an additional Lencioni assessment or a claim that every disagreement has a structural cause.
| Observable pattern | Question to investigate | What may require attention |
| Managers reach different conclusions from different information. | Are they using the same facts, definitions, and assumptions? | Shared information and explicit decision criteria. |
| Objections appear privately after the meeting. | What happens when someone disagrees during the formal discussion? | Trust, the consequences of candor, and appropriate reporting routes. |
| Debate continues without a decision. | Who is authorized to resolve the trade-off? | Decision authority and escalation boundaries. |
| Departments defend incompatible priorities. | Are their objectives or incentives pulling them in different directions? | Shared outcomes and cross-functional priorities. |
| Decisions are made and quietly reversed. | Who can reconsider a decision, on what grounds, and with whose knowledge? | A legitimate reconsideration process rather than informal vetoes. |
A recurring pattern establishes a question to investigate. It does not establish a complete diagnosis.
Where expectations and authority are clear but a manager fails to fulfill a commitment, address that failure. Where responsibility or authority is unclear, address the design problem as well.
Structure does not remove personal responsibility. It must make that responsibility explicit and workable.
Conflict Resolution in Action: Sales and Finance Keep Fighting About Discounts
Consider a hypothetical management team.
Sales wants to approve a discount for a strategically important customer. Finance objects because the agreement falls below the expected margin.
Both managers explain their positions. Both understand the other’s concern. Yet similar decisions repeatedly return to the CEO.
The initial explanation sounds reasonable:
“Sales and finance need to communicate better.”
Now examine the obstacles.
Individual: The sales manager emphasizes commercial opportunity. The finance manager emphasizes financial exposure. Examine the evidence behind each position rather than reducing the disagreement to personality.
Relationship: A previous pricing exception became a source of blame. Determine whether that unresolved event is shaping the current discussion.
Environmental: Sales is evaluated primarily on bookings. Finance is evaluated on margin. Neither manager has explicit authority over pricing exceptions.
Informational: The managers are using different assumptions about servicing costs, customer value, and the likelihood of future business.
The examination identifies more than a communication problem.
The organization needs consistent decision information, a way to evaluate the company-wide trade-off, and defined authority over exceptions. It also needs to address the unresolved relationship issue rather than assume a new approval rule will erase it.
The CEO and management team must establish which pricing decisions can be delegated, what consultation is required, and which exceptions remain with the CEO.
The managers remain responsible for debating honestly and honoring the resulting commitments.
Another conversation cannot, by itself, resolve conflicting expectations and undefined authority.
The team can discuss the issue. Why can it not settle it?
When the same cross-functional disagreements repeatedly require CEO intervention, examine the authority, ownership, and competing expectations surrounding them.
Before This Issue Returns to the Next Meeting
Use the following decision brief for a consequential disagreement.
This is Rainmaker’s application guide. It records what must become explicit; it does not replace investigating the underlying obstacle.
| Question | What the team must establish |
| What decision is required? | State the choice, not merely the topic. “Approve this pricing exception” is more precise than “Discuss alignment.” |
| Which shared outcome governs the trade-off? | Identify the company-level objective and the constraints that must be respected. |
| What do we know, and what remains uncertain? | Separate verified facts, assumptions, forecasts, and missing information. |
| Whose input is required, and who decides? | Distinguish consultation from decision authority. |
| Who owns the resulting commitment? | Name the responsible role, expected outcome, and timing. Confirm that authority and resources match the obligation. |
| When can the decision be reconsidered or escalated? | Define legitimate triggers, the authorized route, and who must be informed. |
A completed template does not create authority. It exposes whether the organization has established it.
The decision-maker is not automatically the CEO. The appropriate authority depends on the decision, its consequences, and the organization’s governance.
Nor must every decision wait for unanimous agreement. Lencioni distinguishes commitment from consensus: a team can consider differing views and commit without every member preferring the selected option.
Participation establishes whose perspective is considered. Authority establishes who decides. Commitment establishes what happens afterward.
Establish Conflict Norms That Protect Candor and Commitment
High-performing teams have explicit conflict norms: expectations the team agrees to follow when engaging in difficult discussions.
For CEOs and management teams, those expectations should cover both the discussion and its consequences.
Challenge the Reasoning
Identify the assumption, evidence, consequence, or trade-off in question. Do not substitute a judgment about someone’s character.
A useful challenge identifies what needs examination. “I disagree” becomes more useful when followed by the specific risk, fact, or assumption behind the disagreement.
Surface Relevant Concerns Before Commitment
Ask what has not been considered. Invite perspectives that have not entered the discussion.
“Mining for conflict” should surface relevant disagreement, not manufacture confrontation or pressure people into personal disclosure.
Do not treat silence as reliable evidence of either agreement or opposition. Confirm the person’s position through an appropriate conversation.
Close Meetings With Explicit Commitments
Close the meeting with what was decided, who owns the outcome, and what remains unresolved.
Have affected managers explain their obligations and authority in their own words. This tests whether the group shares an understanding rather than merely a positive impression of the meeting.
Preserve a Legitimate Route for Reconsideration
New information may justify reopening a decision. Private lobbying should not quietly replace the agreed process.
Specify who can authorize reconsideration and how affected people will learn about the change.
These norms do not authorize humiliation, intimidation, or retaliation. Confidential concerns need an appropriate reporting route, not compulsory public debate.
Healthy conflict is not permission to behave badly. Commitment is not a demand for blind compliance.
What the CEO Must Establish and Stop Undermining
The CEO’s responsibility extends beyond encouraging candor. It includes establishing and respecting the boundaries within which the management team makes decisions.
Consider a CEO who tells managers to resolve disagreements directly but privately overturns their decisions whenever one manager objects.
The formal expectation requires peer resolution. The informal process rewards escalation.
Which process actually governs the organization?
Examine whether decision ownership, required consultation, and escalation boundaries are explicit. Then examine whether exceptions are made openly or through arrangements that leave managers working from outdated assumptions.
An override may be necessary. Make the revised decision, rationale, and responsibilities clear.
A declared process that is routinely bypassed illustrates what we refer to as Organizational Drift™: a gap between intended design and actual execution.
The objective is not to eliminate CEO involvement. Some decisions properly remain with the CEO.
The objective is to distinguish necessary executive authority from dependence created by unclear or unreliable rules.
What Role Should a Five Dysfunctions of a Team Workshop Play?
A Five Dysfunctions of a Team workshop provides a structured setting for examining trust, conflict, commitment, accountability, and collective results.
The workshop is an event. The discipline must continue afterward.

A workshop can expose the obstacle. The organization must address the authority, ownership, or competing expectations that the discussion reveals.
Use a consequential disagreement to examine how the management team actually operates. Identify the obstacles, test possible explanations, and establish which decisions remain unresolved.
An external facilitator is highly-recommended. The CEO needs to participate rather than lead the discussion, or when familiar arguments repeatedly prevent examination.
The facilitator does not acquire organizational authority by running the session. The appropriate executives must make and uphold the relevant design decisions.
Assessment feedback can inform the discussion. It does not, by itself, establish whether the cause is interpersonal, informational, structural, or a combination. Read How to Action Your Five Dysfunctions of a Team Assessment for that distinction.
Rainmaker uses frameworks, assessments, and facilitated discussions as inputs.
Where the constraint is structural, redesign is the mandate, not completion of another workshop.
How Do You Know Productive Conflict Is Working?
Review actual disagreements and their consequences. Do not measure team health by the volume of debate.
Use these questions as review criteria, not universal performance benchmarks.
| Review area | Evidence to examine |
| Decision delay | How long do comparable decisions remain unresolved, and what prevents resolution? |
| Repeated debate | Is the issue returning because of new evidence or because the original decision was never clear? |
| Commitment clarity | Can responsible managers independently explain the decision, their obligations, and their authority? |
| Escalation quality | Does the issue exceed delegated authority, or is nobody certain who decides? |
| Consequences | Did the decision address the intended outcome, and what should the team learn from what followed? |
Faster decisions are not automatically better. Fewer escalations are not progress when concerns are being concealed.
The useful test is whether the team can examine an issue, decide through legitimate authority, fulfill its commitments, and reconsider the decision when circumstances warrant it.
Conflict is productive when it improves the work, not merely when the conversation becomes more animated.
Frequently Asked Questions About the Five Dysfunctions Conflict Resolution Model
Does productive ideological conflict require everyone to agree?
No. Managers can support a decision without having preferred it. Productive ideological conflict provides team members a genuine opportunity to raise concerns, challenge assumptions, and have their reasoning considered. It does not require everyone’s preferred option to win.
The management team must also know who has authority to decide. Once the decision is made, confirm what each manager understands, supports, and commits to deliver. Being heard does not automatically establish buy-in; check it rather than treating silence as agreement.
Managers who commit should communicate the agreed direction consistently and honor their obligations—not quietly operate under a different decision. Commitment does not require concealing material new information, delivery constraints, or serious concerns. Those need an appropriate review or reporting route.
The goal is not identical opinions. It is a clear decision and commitments the team will honor.
What should we do when the same disagreement keeps returning?
First establish whether circumstances have changed - or whether the original discussion left something unresolved. Confirm what was decided, who had authority to decide, and what each manager understood and committed to.
New information may justify reconsideration. But when the same issue returns without a material change, examine what keeps it unsettled: concerns that were never addressed, conflicting priorities, unclear responsibilities, unresolved relationship issues, or a commitment that was not honored.
Match the response to the finding. Unclear authority requires a decision about who decides. Competing priorities require an authorized trade-off. An explicit, workable commitment that was ignored requires accountability - not another general conversation about teamwork.
Before closing the discussion, establish who must act, which commitments remain in force, and what would justify reopening the decision.
The goal is not to silence disagreement. It is to resolve what keeps the same issue returning.
Who decides when the management team cannot reach agreement?
The role authorized to make that decision - not automatically the CEO. Required consultation gives relevant perspectives a fair examination; it does not mean everyone must approve the outcome.
Establish who can decide, whose input is required, and which matters exceed that authority. Those boundaries should reflect the decision’s scope and consequences - not who argues most forcefully. Escalate when the decision exceeds delegated authority, not simply because managers disagree.
If nobody has authority—or two roles both claim the final say - the organization must resolve that ambiguity. Another discussion about the merits of the options cannot substitute for assigning the decision.
Once the authorized decision is made, clarify the resulting responsibilities and communicate any changed commitments.
Debate informs the decision. Clear authority establishes who can make it.
How can a management team challenge the CEO without making the discussion personal??
Challenge the reasoning, not the person. Identify the assumption, evidence, or consequence that needs examination. For example: “This delivery date assumes capacity we have not confirmed. Which existing commitments would need to change to make it achievable?”
That raises a business question without assigning motives or attacking the CEO’s judgment.
The CEO has a responsibility too: examine the concern on its merits, explain the resulting decision, and distinguish disagreement from disloyalty. Considering an objection does not require accepting it. It does require more than inviting input and immediately dismissing it.
If managers are encouraged to speak openly but penalized for doing so, better phrasing will not resolve the contradiction. Establish how concerns are raised, examined, and escalated - and address responses that undermine that process. Sensitive concerns should use the appropriate confidential reporting route rather than require a public confrontation.
Decision authority does not put the CEO’s reasoning beyond examination.
When is reopening a decision appropriate?
Reopen a decision when its basis needs examination, not simply because someone still prefers another outcome. Material new information, changed circumstances, implementation evidence, or a previously overlooked risk can justify review.
Distinguish the right to raise a concern from the authority to change the decision. Give affected managers a clear route to request reconsideration. Establish who can retain, revise, or replace the decision and what remains in force while the review occurs.
When a change is authorized, address its consequences. Which commitments, deadlines, or resource allocations change? Who must act differently? Inform those people before they continue working under outdated instructions.
A private conversation should not quietly overturn an agreement while others remain accountable for delivering it.
Commitment does not make a decision immune to correction. It requires changes to be authorized, explicit, and communicated.
When does recurring conflict require organizational redesign?
When the evidence shows that the organization’s design keeps the issue unresolved. Repetition alone does not prove a structural problem.
Examine one recurring disagreement. Establish who owns the outcome, who can authorize the necessary trade-off, whether departmental measures reward incompatible results, and what the escalation rules actually permit.
If managers understand the issue but lack the authority to resolve it, another request to collaborate leaves the constraint intact. If their targets require conflicting choices, greater commitment does not settle which priority governs.
Rainmaker examines those patterns to determine whether outcome ownership, decision authority, measures, or escalation rules require redesign.
Where the obligation is explicit, authority is sufficient, and someone fails to follow through, address that failure directly. A structural gap and an accountability failure can coexist. One does not excuse the other.
Do not ask people to compensate indefinitely for unresolved design. Do not use redesign to avoid holding someone accountable for a clear, workable commitment.
The Team Can Discuss the Issue. Why Can It Not Settle It?
When the same cross-functional disagreements repeatedly require CEO intervention, examine the system surrounding the discussion.
Who owns the outcome? Who decides? Which priorities govern the trade-off? What allows the decision to be reversed?
The Rainmaker Group redesigns organizational systems so management teams can own decisions, address commitments, and pursue collective results without making the CEO the permanent point of escalation.
Bring one recurring example. The conversation begins with whether the constraint requires structural redesign.
For CEOs and management teams prepared to examine how their organization is designed.
Organizations produce exactly what they are designed to produce.
More Powerful Five Dysfunctions of a Team content:
Chris Young is a Trusted Advisor To Founders / CEOs | Certified Scaling Up Coach | Builder of People, Leaders, Teams & Economic Moats | Strategist and proud founder of The Rainmaker Group.

