LEADERSHIPMonths to result

The Challenge Network

Surround yourself with thoughtful critics, not just supportive cheerleaders

Problem it solves

ineffective leadership

Best for

["leaders and founders in decision-making roles","teams that have become too harmonious and stopped innovating","individuals who realize they are surrounded by yes-people"]

Not ideal for

["new teams that have not yet built basic trust and psychological safety","environments with high relationship conflict that needs resolution first"]

Overview

Why this framework exists

Grant distinguishes between a support network (cheerleaders who encourage you) and a challenge network (critics who push you to rethink). Both are necessary, but most people over-invest in support and under-invest in challenge. He draws on organizational psychologist Karen Jehn's research distinguishing task conflict (clashes about ideas and opinions) from relationship conflict (personal, emotional clashes).

In a study of hundreds of new Silicon Valley teams, high-performing groups started with low relationship conflict and kept it low, but they had high task conflict from the beginning. They did not hesitate to surface competing perspectives. Meanwhile, poorly performing teams started with high relationship conflict, which prevented them from challenging each other on ideas. A meta-analysis of over a hundred studies confirmed that relationship conflict is generally harmful, but task conflict can improve performance.

The Wright Brothers exemplified this. Despite their deep bond, Wilbur and Orville argued so intensely about their airplane designs that their shouting could be heard down the street. These arguments forced them to stress-test their ideas and discover solutions neither would have reached alone.

Core principles

5 total
  1. A challenge network is at least as important as a support network for good decision-making
  2. Task conflict about ideas improves performance; relationship conflict about personalities destroys it
  3. Frame disagreements as debates rather than personal attacks to keep conflict productive
  4. Identify your most thoughtful critics and explicitly invite them to question your thinking
  5. Tell critics why you respect their pushback so they know dissent is safe and valued

Steps

4 steps
  1. Identify your current network composition
    List the people you most frequently consult for advice or feedback. For each one, honestly categorize them as primarily a cheerleader or primarily a challenger. If most are cheerleaders, you have a gap.
  2. Recruit your challengers
    Think about who gives you the most uncomfortable but useful feedback. These people are your challenge network candidates. Approach them explicitly: tell them you value their critical thinking and want them to push back on your ideas. Explain where they typically add the most value.
  3. Structure productive task conflict
    When presenting ideas to your challenge network, frame the discussion as a debate, not a personal evaluation. Define the question clearly, present your reasoning, and then explicitly ask: What am I missing? Where is this weakest? What would you do differently?
  4. Separate task conflict from relationship conflict
    Monitor emotional temperature. If a debate starts feeling personal, pause and redirect to the task. Acknowledge that you respect the person and value their perspective. If relationship friction is present, address it separately before attempting productive task conflict.

Checklist

Saved in your browser

Examples

1 cases
The Wright Brothers' productive arguments

Wilbur and Orville Wright argued so intensely about their airplane designs that their shouting could be heard by neighbors. Despite their deep personal bond, they did not shy away from questioning each other's ideas about wing shape, engine design, and control systems. Their father once urged them to stop arguing, but it was this constructive conflict that drove their breakthroughs.

OutcomeTheir willingness to challenge each other's thinking led to the first successful powered airplane flight at Kitty Hawk, solving problems neither brother could have solved alone.

Common mistakes

3 traps
Surrounding yourself only with agreeable people
A support network feels good but creates an echo chamber. If everyone around you validates your ideas, you lose the mechanism for catching errors and rethinking assumptions. You need people who will argue with you, not just cheer for you.
Allowing task conflict to escalate into relationship conflict
When debates get personal, people stop engaging with the ideas and start defending their egos. The poorly performing Silicon Valley teams had so much personal friction early on that they could not challenge each other's ideas even when they needed to.
Punishing disagreement
If you invite challenge but react defensively when you receive it, your challengers will quickly learn that dissent is unsafe. You must demonstrate through your reactions, not just your words, that pushback is welcome.

Origin story

How this framework came to be

Grant studied the Wright Brothers' working relationship and found that their legendary collaboration was defined not by harmony but by intense disagreement. They argued so vigorously that their father once wrote them a letter urging them to stop, but it was precisely this productive conflict that led to breakthroughs in wing design. Grant paired this with Etty Jehn's research on Silicon Valley teams, showing that the best teams fight about ideas early and often while maintaining personal respect.

Source

Traced to primary
Source · BOOK
Think Again: The Power of Knowing What You Don't Know
Adam Grant · 2021
Open source →

Related frameworks

Browse all Leadership →