Fragility

On what happens when teams are protected from every difficulty — and what it costs them

This essay is the second in the Beacon series.

Check-in scores had been slipping as the team made its way through high season. Quinn had ideas on how to address it, but with the momentum they had been building, she decided to let her team take the first pass. Based on their training and shared history of solving problems, she had expectations. Collaboration. A deep dive. A well-developed process that would at least partially address the root cause. She also expected to have to refine whatever they produced.

What she received was a reality check. The team's supervisor and one of the lead agents brought their deliverable to her desk two full days early, faces beaming with pride. Quinn thanked them and promised to review the file by week's end. She took it home and read it propped against her headboard that night.

She was at a loss. To say the effort was lacking was generous. She was angry, then frustrated. First with her team, then with herself.

I. The Immune System Argument

The human immune system does not develop resistance by avoiding pathogens but rather through exposure, stress, and recovery. The managed introduction of difficulty - vaccination, exercise, challenge - builds the adaptive capacity that protects us from real threats when they arrive. Remove the exposure and you remove the adaptation.

Nassim Taleb's “Antifragile” framework maps this precisely onto organizational behavior. Some systems are weakened by stress - these are fragile. Others resist it without permanent change - these are robust. A third category of systems is strengthened by stress, developing capabilities they did not previously possess. These systems are “Antifragile,” and they not only benefit from but require controlled exposure to difficulty to build their adaptive capacity.

The organizational equivalent of an immune system is a team's collective ability to solve novel problems under pressure. Like biological immunity, it does not develop in environments that are surgically clean. Teams and cultures protected from all friction lose the adaptive capacity that friction builds. The leader who smooths every rough edge, who takes work back when it disappoints, who solves every problem quickly is building a fragile team.

Quinn was staring at the direct evidence of this principle. Season was passing them by and they could not afford to have scores continue to slip. She was hoping to earn a promotion this summer. How had she judged this so poorly? Why had she not trained them better? She blamed herself and grew more frustrated that she had wasted the time instead of just developing the process herself from the beginning. That was her new plan. Go in early tomorrow, knock it out, have it rolled out by the end of day.

II. What Efficiency Actually Costs

Efficiency and resilience exist in direct tension. You can optimize for one or build toward the other, but pursuing both simultaneously produces neither. The leader who takes over when work disappoints is optimizing for immediate output. The leader who sits with disappointing output and asks better questions is building long-term capability.

The problem is that resilience looks like inefficiency in the short term. It requires tolerating suboptimal performance while the team develops the competencies that difficulty would produce. It requires accepting that the next attempt might also disappoint. It requires choosing development over control, capacity over efficiency, the harder path over the faster one.

This tension is not theoretical. It shows up in resource allocation, deadline decisions, and the daily choice between doing work and teaching work. The organizational immune system — the collective problem-solving capability of the team — atrophies when it is never asked to respond to genuine difficulty. Teams that are protected from challenge become dependent on protection.

Quinn turned off her lamp and collapsed into her pillow, exhausted from the day, the weeks, the years, and now from feeling as if she was failing as a leader. She had a plan for tomorrow. Take it back. Do it herself. Move on.

III. The Behavioral Science of Variability

When the usual response no longer produces the usual result, behavioral systems increase variability. They try different approaches. Different combinations. Novel sequences. This behavioral variability is the engine of adaptation.

Leaders who rescue too quickly short-circuit this process. The team never develops the behavioral repertoire that difficulty would have produced. They never learn what they are capable of solving. They never build the confidence that comes from working through problems without being saved. The leader preserves immediate efficiency at the cost of long-term resilience.

The next morning, Quinn's alarm went off an hour early, and as she moved through her routine, her brain replayed the monologue from the night before. She was pulling into the employee parking lot when she had a change of heart. Why should she take this back from them? Relieving her team of this responsibility would only weaken their resolve and deprive them of an opportunity to learn, to improve, to grow stronger.

IV. What Quinn Chose Not to Do

Would it be harder for her? Uncomfortable to risk more time with an unknown outcome? Absolutely. Was she there to put out fires or develop leaders? The question clarified everything. This was what she was supposed to be doing. Maybe it would reignite her own fire.

She turned off her car and walked toward the entrance, now smiling. She had a new use for the extra hour.

The practical argument for sitting with disappointing output is that it forces both leader and team into the kind of thinking that produces capability. Instead of supplying the answer, you name what is missing without filling in the gap. Instead of redirecting their approach, you ask the question that extends their thinking. Instead of taking over, you let the next attempt be theirs.

Three specific moves distinguish leaders who build capacity from those who substitute for it:

Name what is missing without supplying the answer. "What question should we have asked first?" This surfaces the thinking gap without closing it. It requires the team to identify where their process broke down rather than having it identified for them.

Ask the question that extends their thinking rather than redirecting it. "What would have to be true for this to work?" This builds their diagnostic capability. They learn to interrogate their own assumptions rather than waiting for someone else to do it.

Allow the next attempt to be theirs. Set parameters, timeline, and success criteria, but let them own the content. This builds ownership and competence simultaneously. They develop solutions they can defend because they developed them.

These moves require tolerating the discomfort of a team that is not yet where you need it to be. They require believing that capability matters more than immediate efficiency. They require choosing the longer path because it leads somewhere better.

Quinn spent her extra hour differently than she had planned. Instead of developing the process herself, she developed the questions her team needed to answer. Instead of solving their problem, she identified where their thinking had stalled. Instead of taking over, she designed the conditions under which they could solve it themselves.

It was harder. It was uncomfortable. It required more of her than efficiency would have demanded. When her team delivered their second attempt three days later - a process that actually addressed the root cause, that they could implement with confidence, that they owned because they had created it — Quinn understood what “Antifragile” meant.

Some teams are weakened by difficulty. Some teams resist it. Others are strengthened by it, developing capabilities they did not know they possessed. Those teams require leaders who understand that protection and development are different goals, and that building capacity requires choosing the harder path.

The question worth sitting with:

Where are you solving problems your team should be solving — and what is that costing both of you?

~~~

Further Reading

Berger, Jennifer — Changing on the Job (2012). 

Edmondson, Amy — The Fearless Organization (2018). 

Heifetz, R. and Linsky, M. — Leadership on the Line (2002). 

Kegan, R. and Lahey, L. — An Everyone Culture (2016).

McDougall, Christopher — Born to Run (2007). 

Taleb, Nassim N. — Antifragile (2012). 

Weick, K. and Sutcliffe, K. — Managing the Unexpected (2001).