What Makes a High-Performing Team Is Not What You Think

Why the practices of superteams cannot be installed, and what produces them instead.

Most leadership writing about high-performing teams describes what those teams do.

It does not name what makes those behaviours possible. That is where the actual work lives.

A recent piece in Harvard Business Review captures this pattern clearly. Ron Friedman, drawing on a survey of more than 6,000 knowledge workers, identifies seven research-backed practices that distinguish high-performing teams from average ones. They experiment more. They normalise curiosity. They surface obstacles in meetings. They give feedback that motivates rather than demoralises. They find meaning in the work. The research is solid. The practices are real.

But none of them can be installed in a team whose system does not support them.

This is the gap most team performance writing leaves open. The practices are described as if they were behaviours a leader could choose to adopt. In practice, the leader who tries to install them in a team without the underlying conditions watches the practices stall, get performed superficially, or quietly revert.

The behaviours are downstream of the system. The system is what the work actually changes.

What the research is really showing

Friedman's article makes a structural claim that is easy to miss inside the seven practices. He writes: “At the center of every learning culture is a leader who makes growth a daily priority.” (Harvard Business Review, May-June 2026.)

The research data behind that claim is genuine. Superteam leaders do model these behaviours. They do experiment more, ask better questions, give better feedback, find more meaning. The correlation is real.

What the article does not name is why these leaders can do these things while leaders of average teams cannot. The implicit answer is character or skill. The best leaders are simply better at this. That answer satisfies the surface of the question but does not hold up in practice. Leaders of average teams are often not less curious, less feedback-skilled, or less interested in meaning. They are operating inside systems that make those practices harder to sustain.

A leader who tries to run more experiments in a team that punishes failure does not get a learning culture. They get cautious experimentation followed by a return to safe choices. A leader who tries to make feedback feel like support in a team where feedback has historically been used as evidence in performance reviews does not get a feedback culture. They get nervous silence. A leader who tries to lead with meaning in a team that has learned to be cynical about leadership communication does not get engagement. They get polite tolerance.

The practices land where the conditions support them. They do not land where the conditions do not.

The four practices, read systemically

Take four of the practices Friedman names and look at what each one actually requires beneath the surface.

Running more experiments. The behaviour is observable: high-performing teams try new things more often. But experimentation requires a system that has made failure survivable. The team has to know that when an experiment does not work, the cost is paid by the team, not by the individuals who proposed or executed it. Without that condition, experimentation becomes a career risk that intelligent people avoid. The behaviour you see is risk-taking. The condition you cannot see is that the system has agreed failure is data, not evidence.

Making curiosity contagious. The behaviour is observable: leaders model intellectual humility, say I don't know, ask thoughtful questions. But curiosity is not a personality trait. It is what shows up when authority is not at stake. In teams where saying I don't know costs the leader credibility, leaders do not say it, regardless of how curious they are personally. The condition underneath the behaviour is that the team has agreed authority is not threatened by uncertainty. The same leader, in a different system, models very different curiosity.

Making feedback feel like support. The behaviour is observable: feedback that motivates without demoralising. But this is one of the rarest practices in any team, and the reason is not skill. It is that feedback in most teams has historically been entangled with judgment, evaluation, and consequence. The team has learned to brace for feedback. No amount of better delivery changes this. What changes it is a structural decision the team has made together: that feedback is for learning, not for performance management, and that the two will not be confused. Until that decision is made, feedback continues to land as judgment regardless of how warmly it is delivered.

Leading with meaning, not just metrics. The behaviour is observable: high-performing teams understand why their work matters. But meaning is not something a leader installs through better communication. Teams build meaning through honest conversation about what they are doing, what they care about, and what they are willing to commit to together. In teams where strategic conversation has been replaced by cascade communication, meaning cannot be built. The leader can articulate purpose all day. If the team has not participated in defining what matters, the articulation does not stick.

In each case, the practice is real and useful. In each case, the practice is downstream of a condition that has to be built first.

What the system actually is

The system underneath a team is the set of agreed norms, structural arrangements, and shared understandings that determine what behaviour is possible inside it. Most teams have never named their system out loud. They have inherited it, drifted into it, or absorbed it from the leader's defaults.

This is what coaching the team as a connected system actually changes. Not the practices themselves. The conditions that make the practices possible.

The work begins with the team looking honestly at what is currently happening. Where are experiments being avoided because failure is unsafe? Where is curiosity being suppressed because uncertainty costs authority? Where is feedback landing as judgment regardless of how it is delivered? Where has meaning been replaced by communication?

The questions are not rhetorical. They surface the specific conditions a team is operating inside. Once the conditions are visible, they can be redesigned. The practices then become possible, because the system underneath them has been deliberately built to support them.

This is the difference between a team that adopts the practices for a quarter and a team that becomes high-performing. The first is doing the work at the wrong layer. The second has done it at the right one.

Seeing your specific pattern

The system underneath your team is yours. The specific shape of it is determined by what your team has inherited, what has been left undiscussed, and what conditions have quietly become the norm.

This is what the Grip & Gravity team diagnostic looks at. Using the PERILL framework, it surfaces the dimensions where your team's system is producing the patterns you are seeing. It does not tell you to adopt seven practices. It shows you which conditions in your specific team are making those practices harder than they should be.

The work is not to be a better leader of average teams. It is to build the system that lets your team become a high-performing one.

Where the practices come from

The Thunder, the case study Friedman uses, did not become a high-performing team by adopting seven practices. They became one by building, over years, a system that produced these practices reliably. The practices are the result of the system, not the cause of the success.

This is true for any high-performing team. The practices are visible. The system underneath them is not. Most leadership writing names the visible layer and stops there. The deeper layer is where the work lives.

Which of the conditions in your team is making the practices of a high-performing team harder than they should be?