What does it mean that conflict as a team cognitive resource?

Healthy disagreement — task conflict about ideas, approaches, and interpretations — improves team decisions. The absence of conflict does not signal harmony. It signals suppression of the cognitive diversity the team needs to think well.

Example: Two engineering teams at a cloud infrastructure company faced similar architectural decisions about migrating to event-driven systems. Team Maple was known for its collegial culture — members got along well, meetings were pleasant, and decisions were reached quickly. When the migration was proposed, the team discussed it for twenty minutes, agreed it was a good idea, and moved forward. Team Oak had a more contentious culture — members regularly challenged each other's proposals, debated trade-offs vigorously, and sometimes left meetings frustrated. When the same migration was proposed, the team spent three meetings debating it. The senior engineer argued that event sourcing would add unacceptable operational complexity. The junior engineer countered that the current synchronous architecture could not scale. The tech lead pushed back on both, arguing for a hybrid approach. The debates were intense but focused on the technical merits, not personal attacks. Team Maple's migration failed after four months — they had not anticipated the operational complexity of debugging event-driven systems, a concern that no one had raised. Team Oak's migration succeeded, taking six months instead of Maple's projected three — but the final architecture incorporated safeguards for the exact problems that Maple encountered, because those problems had been surfaced and addressed during the contentious planning discussions. The conflict cost Team Oak time. The absence of conflict cost Team Maple the project (Jehn, 1995).

Try this: Assess your team's conflict profile using Jehn's three-type framework. For each type, rate your team on a 1-5 scale. (1) Task conflict — 'Team members regularly disagree about ideas, approaches, and technical decisions.' (2) Process conflict — 'Team members disagree about who should do what and how work should be organized.' (3) Relationship conflict — 'Team members experience personal friction, tension, or animosity.' The healthy profile is: task conflict 3-4, process conflict 1-2, relationship conflict 1-2. If your task conflict score is below 2, your team is likely suppressing disagreement. If your relationship conflict score is above 3, conflict has become personal and is eroding trust. For the next week, track each disagreement that surfaces in team discussions. Classify it as task, process, or relationship conflict. At the end of the week, review: Is your team generating enough task conflict to think well? Is any task conflict leaking into relationship conflict?