The product launch was back on the agenda again.
Three weeks earlier, the management team had discussed the deadline and left the meeting believing it had reached an agreement. Sales began preparing customers. Operations continued working from a different capacity assumption. The product leader knew an important dependency remained unresolved but assumed it would be addressed before the date became final.
Now the deadline was approaching, and the disagreement had reached the CEO.
“I thought we decided this,” the CEO said.
“We agreed to the target,” the operations leader replied. “We didn’t agree that the resources were available.”
The sales leader looked across the table. “Then why didn’t we resolve that before we started making commitments?”
It was a legitimate question. It was also a familiar conversation.
Earlier that year, the team had completed a Five Dysfunctions of a Team workshop. The discussion had been useful. People acknowledged concerns they had previously avoided. They agreed to challenge assumptions, clarify commitments, and hold one another accountable.
For several meetings, they did.
Then a concern went unspoken because everyone was pressed for time. A decision ended without confirming what each department had committed to. A missed expectation became a private conversation instead of a discussion between the people responsible.
None of those moments seemed significant enough to stop the work.
Now they were all in the same room, trying to reconstruct an agreement they had understood differently.
The CEO settled the immediate dispute. The launch had a revised plan, and the meeting moved on. But nobody established who would resolve the same trade-off next time.
The immediate problem had an answer. The recurring problem did not.
The workshop had given the team a useful language. Maintaining the discipline and resolving what continued to undermine it remained their responsibility.
The management team had not rejected trust, productive conflict, or accountability. Its members still believed those things mattered.
What had changed was their consistency.
Raising an uncomfortable concern became something to do when there was enough time. Confirming a commitment became unnecessary when everyone appeared to agree. Addressing a missed expectation became something to postpone until the CEO intervened.
The team’s standards had become intentions rather than dependable practices.
Team Hygiene refers to the deliberate, continuing attention to the standards and operating conditions a healthy team needs.
The broader concept includes hiring, addressing persistent underperformance, leadership development, and succession planning. The Five Dysfunctions of a Team is one pillar: how the management team works together.
The hygiene comparison is straightforward. One shower does not complete personal hygiene. One workshop does not complete the work of maintaining a healthy team.
The comparison concerns repetition, not simplicity. A difficult conversation still requires judgment. A missed commitment still requires attention. A decision still requires clarity.
For the team in this example, the work was not to rediscover why teamwork mattered. It was to make its agreed standards dependable in the next consequential discussion.
Healthy teamwork is maintained, not completed.
Patrick Lencioni’s Five Dysfunctions of a Team identifies five connected breakdowns: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results.
The framework gives the management team a way to examine its experience. The practical question is how the corresponding healthy disciplines apply to the work.
Returning to the launch discussion.
| Team discipline | Question raised by the launch |
|---|---|
| Vulnerability-based trust | Could a manager acknowledge an unresolved dependency, admit uncertainty, or ask for assistance before the situation became urgent? |
| Productive conflict | Were the capacity concerns examined before the launch date was treated as settled? |
| Clear commitment | Did managers leave with the same understanding of the decision and their resulting obligations? |
| Peer accountability | Did managers address missed commitments with one another, or wait for the CEO to intervene? |
| Collective results | Did the team resolve the trade-off against a shared launch objective rather than defend separate departmental interests? |
One difficult launch does not establish failure in all five areas. These questions identify what to examine, not conclusions to impose.
The distinction matters because naming a dysfunction is easier than understanding what happened.
“Commitment was weak” does not explain whether managers understood the decision differently, accepted incompatible obligations, or failed to honor a clear agreement.
“Accountability was missing” does not establish whether peers avoided a difficult conversation or whether nobody had defined ownership of the outcome.
The framework focuses the inquiry. The team still needs to investigate the actual situation.
For a fuller introduction to the model, read How to Overcome the Five Dysfunctions of a Team.
For this management team, maintaining the discipline would change what happens before, during, and after the next launch decision.
The capacity concern belongs in the discussion before sales makes customer commitments. The unresolved product dependency needs to be visible while the team still has choices. Neither concern should disappear because the meeting is running late.
Raising the concern is only the beginning. The team must examine the trade-off rather than treat the objection as resistance.
Operations needs to explain the capacity constraint. Sales needs to explain the commercial consequence. The product leader needs to distinguish what is known from what remains uncertain. Together, they need to evaluate the implications for the company rather than merely defend their functions.
The Five Dysfunctions conflict resolution model provides a deeper examination of what can obstruct that discussion.
Before leaving, the affected managers need a shared understanding of what was decided, what remains unresolved, and what each has committed to deliver.
An agreed target must not silently become an approved customer promise while a required resource decision remains open.
After the meeting, a commitment at risk needs attention while there is still time to respond. Managers should address the issue with the appropriate colleague rather than wait for the next escalation.
These are not additional exercises layered on top of the work. They are standards for how the work gets done.
A review rhythm can keep those standards visible. Select a recent decision, compare what was agreed with what happened, and examine any gap. Use Five Dysfunctions activities where they clarify a real issue rather than as substitutes for resolving it.
The CEO belongs inside these expectations. The team cannot maintain one set of decision rules in its meetings while the CEO quietly operates by another.
But there is another test: what happens when the team practices the discipline and still cannot settle the issue?
Return to the launch discussion.
Suppose the operations leader raises the capacity concern before anyone commits to a date. Sales explains the commercial consequence of delaying. The product leader makes the unresolved dependency explicit.
The team is now having the conversation it previously avoided. That is progress.
But the discussion reveals another problem: nobody has established who can approve a change to the launch date when customer commitments and available capacity conflict.
The managers understand the trade-off. They still cannot settle it.
The team has raised the issue. The organization has not assigned the decision.
At that point, another request for openness or accountability leaves the missing authority untouched.
The organization must establish who owns the launch outcome, who can authorize changes, whose input is required, and which exceptions belong with the CEO. Those choices belong together. Assigning responsibility while leaving the necessary authority elsewhere preserves the problem.
This is where Rainmaker’s organizational-design inquiry extends the examination. It asks whether the recurring pattern is sustained by unclear ownership, conflicting expectations, or authority that does not match responsibility.
The answer is not automatically a new reporting structure. In this example, the required changes may concern authority over launch dates, resource commitments, and customer promises.
The appropriate executives must make those choices explicit and uphold them. If circumstances require an override, the revised decision and its consequences must reach the people responsible for carrying it out.
The management team must then practice the discipline within those boundaries. Concerns still need to surface. Commitments still need to be clear. Missed obligations still need to be addressed.
Where expectations and authority were already clear, address the failure to fulfill the obligation. Do not redesign the organization to avoid holding someone accountable.
The distinction matters.
Maintaining healthy teamwork requires repeated attention. Repeatedly negotiating who owns the same decision points to something the organization has not settled.
Maintain the discipline. Resolve the conditions that keep defeating it.
At the next launch, sales and operations may still disagree. New information may still require changing the date. A decision outside the team’s authority may still need the CEO.
The absence of tension is not the test. The test is what happens to the tension.
Does the capacity concern enter the discussion before a customer commitment is made? Does the team examine the trade-off against a shared objective? Is the decision made by the appropriate role? Do the affected managers leave knowing what they own?
When a commitment becomes uncertain, do they address it directly, or do they wait for the next escalation?
Those are the moments in which Team Hygiene becomes visible.
The CEO remains responsible for decisions that require executive authority. The management team should not need the CEO to reconstruct ownership every time familiar priorities collide.
Progress does not mean eliminating disagreement or preventing every missed commitment. It means the team has a dependable way to examine concerns, make decisions, address obligations, and respond when circumstances change.
A Five Dysfunctions of a Team workshop can establish understanding. The team must maintain the practice. Where authority and responsibility remain unresolved, the organization must address them.
When the same issue keeps returning, begin with that distinction:
What must the team uphold - and what has the organization still failed to make clear?
No. Team Hygiene is Rainmaker’s broader organizing concept for maintaining team health. Patrick Lencioni’s Five Dysfunctions framework provides one pillar concerning trust, conflict, commitment, accountability, and collective results. The framework identifies important teamwork concerns. Team Hygiene emphasizes the continuing responsibility to maintain those practices and examine the working conditions that support or undermine them. It is not a replacement assessment or an alternative version of Lencioni’s model.
Practice the relevant disciplines whenever the work requires them, and set aside deliberate time to examine whether they are holding. A material concern belongs in the decision it affects. A missed commitment should not wait for the next retreat. Choose a review rhythm suited to the team’s work, but do not confuse meeting frequency with team health. The question is whether the standards remain dependable in actual decisions and commitments.
Every management team member is responsible for upholding agreed standards and addressing commitments within their authority. The CEO also bears responsibility for establishing and respecting the conditions under which the team operates, including decision ownership and escalation boundaries. Human resources or an external facilitator may contribute expertise. Neither can take responsibility away from the people making decisions, raising concerns, and honoring commitments.
No. Continuing team discipline is not the same as a permanent facilitation engagement. External support may be useful when the team cannot examine a concern productively or when organizational redesign requires additional expertise. The relevant question is what prevents the team from functioning independently. A workshop should inform the work, not become the only setting in which managers can discuss difficult issues or clarify their obligations.
Accomplished individuals can still belong to a team whose healthy working habits are inconsistent. The assessment examines team members’ experience of those behaviors rather than the quality of their résumés or their potential. A disappointing result should prompt examination of actual decisions and commitments rather than defensiveness or blame. The initial score is a baseline, not a ceiling. Our guide to acting on Five Dysfunctions Team Assessment results explains how to investigate the findings.
Redesign warrants investigation when recurring issues involve unclear ownership, responsibility without sufficient authority, conflicting priorities, or unreliable decision rules. Those patterns establish questions, not an automatic diagnosis. First determine whether the problem is an unmet obligation, an unclear expectation, a design constraint, or a combination. Where the commitment and authority are already clear, address the failure directly. Where the organization has left essential decisions unresolved, another conversation about teamwork will not settle them.
The Rainmaker Group examines recurring patterns and redesigns authority, ownership, and operating rules where the evidence calls for structural change.
The management team owns the continuing discipline. Where the constraint is structural, redesign is the mandate.
Bring one recurring example to our conversation.
Organizations produce exactly what they are designed to produce.