Question
How do I apply the idea that conflict as a team cognitive resource?
Quick Answer
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.
The most direct way to practice is through a focused exercise: 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?
Common pitfall: Two symmetric failures. The first is conflict avoidance — treating all disagreement as negative and working to eliminate it. Teams that avoid conflict achieve false harmony at the cost of suppressed information, unexamined assumptions, and decisions that reflect the preferences of the most conflict-averse members rather than the best available thinking. The second is unmanaged conflict — allowing disagreements about ideas to escalate into disagreements about people. When task conflict becomes relationship conflict, the cognitive benefits of disagreement are destroyed: team members stop engaging with each other's ideas and start defending their identities. The team needs a culture that distinguishes the two — where vigorous debate about a technical approach is celebrated and personal attacks are immediately addressed.
This practice connects to Phase 81 (Team Cognition) — building it as a repeatable habit compounds over time.
Learn more in these lessons