Leadership Systems Thinking Beats Managing People One at a Time

An abstract depiction of a system

Most leaders focus on the wrong unit of analysis. They evaluate their organizations component by component rather than as an integrated system.

John Hammond, the visionary entrepreneur behind Jurassic Park, did exactly that. He viewed the park as a collection of attractions, technologies, and people "so astounding that they'd capture the imagination of the entire planet." To Hammond, the T. rex was the star attraction. The raptors were a security challenge. Dennis Nedry was an IT employee. The electric fences were a safety system.

But Jurassic Park wasn't simply a collection of attractions, technologies, and people. It was a system.

The park didn't collapse because a dinosaur escaped its enclosure. It collapsed because of the interactions among genetics, technology, human behavior, weather, and human decisions. A disgruntled employee disabled the security system just as a tropical storm approached. Electrified fences failed. Animals behaved in ways no one anticipated. The catastrophe emerged from the interactions among those parts, not from any single part alone.

Hammond optimized the parts. He failed to understand the interactions among them. In complex systems, interactions, not parts, determine how the system operates.

Many leaders make the same mistake as Hammond. They spend enormous time hiring, developing, and evaluating talented people while overlooking how those people work together. If you're trying to understand organizational performance, the appropriate unit of analysis often isn't the employee. It's the interactions among employees.

Leadership Systems Thinking Starts With Interactions, Not People

Talented people are essential. But talent alone doesn't create organizational performance. Organizational performance emerges from how talented people coordinate, communicate, adapt, and solve problems together.

Consider an interaction between a leader and their direct report. The direct report admits to a mistake, placing himself in a vulnerable position. Instead of criticizing him, the leader thanks the employee for being honest, reassures him that mistakes are part of learning, and shifts the conversation toward preventing the mistake in the future. That interaction teaches the employee that honesty about mistakes will be met with support rather than punishment, strengthening his perception of psychological safety. It also gives the leader evidence that the employee is willing to be honest about difficult issues rather than hide them.

Neither psychological safety nor trust belongs to either individual on their own. They emerge from repeated interactions. As interactions like this repeat over time, they become stable patterns that shape how the leader and employee behave in future exchanges.

Because organizational performance emerges from repeated interactions, leaders who focus exclusively on individual performance may be misdiagnosing the problem. They also leave one of the organization's greatest sources of value creation unmanaged.

Leadership isn't just about hiring, developing, and evaluating talented people. It's also about intentionally designing the conditions under which those people interact.

Designing Better Interactions

You don't need a degree in organizational design to start leading this way. Here are three simple moves you can make this week:

Leaders ought to focus on designing the right conditions that shape how people interact. Clear team norms shape how people interact, and leaders should design them intentionally. For example, when a leader assigns a devil's advocate to each decision, scrutinizing the decision becomes the norm and team members come to expect pushback. The leader hasn't changed anyone's personality. They've changed the norms that shape the team's interactions. Over time, those interactions reshape expectations, reduce defensiveness, and improve the quality of decisions.

One way to think about designing interactions is to trace the pathway from a leadership decision to the organizational outcome it creates:

• Leadership Design Choice: Assign a devil's advocate

• Interaction: People come to expect respectful challenge and no longer interpret disagreement as personal criticism.

• Emergent Property: Psychological safety around disagreement.

• Outcome: Better decisions.

The Bottom Line

The next time you're trying to improve outcomes, don't start by asking who needs to change. Start by asking which interactions need to change.

FAQs

What is leadership systems thinking? Leadership systems thinking is the practice of managing the interactions between people rather than managing people in isolation. Instead of asking who needs to improve, leaders ask which relationships or handoffs need to change.

Why do interactions matter more than individual talent? Talent sets the ceiling, but coordination determines whether a team reaches it. Psychological safety, trust, and decision quality all emerge from repeated interactions, not from any one person's skill set.

How can a leader start applying systems thinking? Start with the norms that shape how people engage with each other. Assigning a devil's advocate to major decisions, for example, changes nothing about anyone's personality but reshapes how disagreement gets handled on the team.

What's the connection between systems thinking and psychological safety? Psychological safety isn't a trait either person carries into the room. It builds through repeated interactions where honesty gets met with support rather than punishment, and it strengthens or erodes based on how leaders design those moments.