What Is a High-Performing Team?
A high-performing team is a group of people who consistently meet and exceed expectations. They do this through rigorous collaboration — lots of disagreement with the goal of delivering the most perfect product they can together.
To an untrained eye, the productive disagreement inside a high-performing team can look rocky. But that friction is not a sign of dysfunction — it is the mechanism of excellence. Collaboration is just a productive disagreement, one focused on a great output, one that works to improve the product and the relationships simultaneously.
High-performing teams put mission above self because they feel the higher calling of the mission. And they don’t just execute goals — they interrogate them. They’ll tell you early when the goal is wrong and find a better path to the actual intent.
A team is defined as: a stable group, interdependent in achieving a shared goal. Each word matters. Without stability, you can’t build trust. Without interdependence, you have parallel workers, not a team. Without a shared goal, you have activity without direction.
The Four Pillars
After 20+ years leading teams that design and build complex, high-consequence systems, I’ve found that high-performing teams are built on four interdependent pillars. These are not a checklist — they are a system. Each pillar enables the others. Cohesion is load-bearing: without it, the other three are harder to build and easier to break.
The four pillars are: Cohesion — the team knows and cares for each other as humans; Alignment — the team shares identity, purpose, and priorities; Psychological Safety — the team speaks up, challenges, and discloses; and Transparent Processes — the team can see what is happening and intervene.
Pillar One: Cohesion
We cannot tell the precise moment when friendship is formed. As in filling a vessel drop by drop, there is at last a drop which makes it run over; so in a series of kindnesses there is at last one which makes the heart run over. — Ray Bradbury, Fahrenheit 451
What Is It?
Cohesion is the difference between a group of coworkers and a team that actually knows each other. It is not friendship — though friendship can grow from it. Cohesion is a professional bond: mutual respect, genuine interest in one another, and a sense of shared belonging.
Brené Brown’s distinction is useful here: fitting in is being in a place where you want to be but nobody else cares you are there. Belonging is when they also care. Fitting in is a lonely feeling. Belonging is not. Cohesion is what makes the team feel like home rather than a stranger’s house — and when you feel at home, you speak up more, you ask for help more, you give honest feedback more. Cohesion is not soft. It is load-bearing.
Why Does It Matter?
When people are comfortable with each other and genuinely care for each other at a human level, they are more likely to help each other without being asked, to be honest about what they find hard, to ask for help, and to challenge each other’s work constructively. The payoff of cohesion isn’t warmth — it’s the functional stuff: honesty, help-seeking, and productive friction. Cohesion is the foundation that makes the other three pillars possible.
The Story: Steve and Fred
I was once on loan to another office for what was supposed to be six weeks. I stayed seven months. On my third day, a colleague named Fred came to me with a problem: he needed someone who knew about board-mounted pressure sensors. I said I didn’t, but I’d find someone who did.
I spent several hours introducing myself around the office, asking questions. I finally got a name — Steve was the expert. I went looking for Steve. He sat directly next to Fred. They had been neighbors for three months yet I introduced them on my third day.
That is what a low-cohesion team looks like: two people sitting three feet apart, unknown to each other, holding the answer to each other’s questions.
What Breaks It?
Hub-and-spoke management — when the manager becomes the communication channel between team members, people have no structural reason to know each other. Organizational trauma — layoffs, reorganizations, fear of job loss cause people to keep their heads down and avoid connection. Remote and hybrid work without intentional design — physical separation doesn’t break cohesion, but ignoring it does. No shared experiences — cohesion is built drop by drop; without shared moments, the vessel never fills.
How to Build It: Three Actions
1. Intentionally Welcome New Teammates
Make sure every new team member has lunch with someone on the team every day of their first week. This is not a nice-to-have — it is the manager’s job. You are engineering belonging, not just orientation. The goal is for the new person to feel that the team also cares they are there.
2. Know People as People
Learn the names of your team members’ spouses, kids, and dogs. Know their hobbies and their aspirations. Write these things down if you need to — I do. Add birthdays to your calendar. This builds one-to-one cohesion between leader and each team member. It also models the behavior you want the team to have with each other.
3. Engineer Peer-to-Peer Recognition
I once bought a trophy that could only be given peer-to-peer, once a month. I never gave it out myself. I seeded it by asking my best engineer — a man everyone loved and respected — to give out the first award. The recipient then had to recognize a peer at the next monthly department meeting. It was on the agenda. This forces people to pay attention to what their teammates are doing. Cohesion builds in the noticing.
4. Find Ways to Celebrate as a Team
Bring the team to lunch once a quarter if you can. Facilitate the conversation — if you know someone is headed on vacation, ask them what they are most excited about. Make sure everyone is in conversation. If you don’t have budget, make it a potluck. In 2020, during COVID, I hosted the only holiday potluck in our building. Technically it was a meeting with food, following all health guidelines. It went very well. I also threw a BBQ at my house during a monthly meeting — it was the first time many on the team had seen each other in person in over a year. Find a way.
Pillar Two: Alignment
What Is It?
Alignment is about shared identity and a shared common goal. The diagnostic question is simple: if you ask five different members of your team why they are there, what they are working on, and what the priorities are — will you get the same answer?
An aligned organization points all of its resources in the same direction. Think of it as a vector diagram: misaligned teams have forces that partially cancel each other out. An aligned team compounds. The math makes the point.
Why Does It Matter?
You can see alignment failure most clearly in how a team critiques its work. A misaligned team directs critique at people: “Jane did this thing wrong and then I had to fix it.” An aligned team directs critique at the work: “This didn’t quite match my understanding — I think it looks more like this. What do you think, Jane?” The difference is subtle, but it is everything. When we know we are all trying to accomplish the same thing together, the work is what we are trying to get perfect — not each other.
Misalignment also shows up at the interfaces: team members pulling against each other, other departments not cooperating, tradeoffs that can’t be resolved because people don’t have enough shared goal to know when to yield. IT won’t approve the software you need. HR won’t move fast enough in a hiring surge. These larger frictions are often alignment failures in disguise.
What Breaks It?
Never setting it — the manager holds implicit knowledge they never made explicit. The curse of knowledge — once you know something, it is almost impossible to remember what it was like not to know it. As a manager, you are in rooms your team is not in, gaining context they never receive. That gap becomes misalignment. Setting it and not returning to it — the Why becomes a plaque on the wall instead of a living filter. Undefined Whats — projects launched without charters, action items without documented purpose. People execute their interpretation of what you wanted, not what you actually wanted.
How to Build It: The JFK Play
JFK declared the Moon Shot at Rice University, but he didn’t invent the idea. He wanted a big national priority to align the country, and he found it by talking to his team about what was possible. That is what you will do.
Step 1: Run the Stakeholder Loop
Start by asking your team members — in one-on-ones — what they are working on and why. Then visit your peers and your boss and ask them what they think your team’s purpose is, what output is expected, and what is frustrating. Find where they are saying the same things, and where they diverge. Bring the disconnects back to the same stakeholders. Some gaps get pruned, some get adopted.
Step 2: Write the Why
At the end of the stakeholder loop, you will have the raw material for a Why statement — the shared identity of the team. The Whats serve the Why. Document both. For a new team, this lives in a charter. For action items, the What and Why get documented in Jira or equivalent. This is alignment made explicit.
Step 3: Revisit on a Cadence
The Why gets revisited at minimum quarterly. Every What gets evaluated against the Why. If it serves the Why, you do it. If it doesn’t, you prune it — give it to a different team or let it go. If it doesn’t serve the Why but still makes sense, you revisit the Why itself. Alignment is not a destination. It is a practice.
Pillar Three: Psychological Safety
When psychological safety is low, people hide mistakes to protect themselves. Hidden mistakes get repeated. When psychological safety is high, people disclose mistakes to protect the group. — Amy Edmondson
What Is It?
Psychological safety is best explained by its opposite. When people feel psychological danger — when they believe they may be embarrassed, reprimanded, or otherwise personally attacked for sharing an idea, concern, or question — they stay quiet to protect themselves. When they feel psychological safety, they share that idea, concern, or question to protect the group.
Unsafe teams hoard information to survive. Safe teams share it to win.
There are two distinct ways safety breaks down. The first is that it feels dangerous to speak — people fear embarrassment or punishment. The second, and sneakier, is that it feels useless to speak — people have raised things before and nothing ever happened. Why bother? Both produce silence. Both are the manager’s problem to solve.
The simple contract underneath it all: we are all imperfect people, just trying to collaborate to get this thing we’re working on as perfect as we can.
The Teaching Exercise: The Green 7
When I teach psychological safety, I put a green 7 on the screen. While I talk, I say it is the color of the sky, that it is divisible by 2 and by 4. I want people to feel confused and uncomfortable — what they are hearing does not align with what they can see. I am clearly showing a 7 and talking about an 8.
If people feel safe, they’ll say something. And I can enable that safety by accepting the feedback when I receive it — which can be hard when you’re in the talking seat. It takes vulnerability. Then I continue: this is a simple example. What if it’s a project plan, a solution, a schedule? What if someone sees something that doesn’t make sense, but doesn’t say anything? That is what psychological danger costs us.
What Breaks It?
Forgetting to say thank you — when someone raises an issue, the manager’s visible reaction in that moment either opens the door wider or quietly closes it. Needing to be the smartest person in the room — managers who stifle ideas, whether through narcissism or well-intentioned confidence, teach the team that their input is not wanted. Mistaking silence for agreement — both at the group level (nobody says anything in a meeting) and at the individual level (one person sees a problem but defers to groupthink). Not acting on what is raised — speaking up becomes useless when it produces no response. The team stops.
How to Build It: Six Actions
1. Assign a Dissenter
If nobody is disagreeing, assign someone to play devil’s advocate. Make it a rotating role. Name it. Normalize it. Productive disagreement doesn’t happen naturally in most teams — you have to engineer it.
2. Bring the Quiet Person In
If someone is silent, ask them specifically: do you have any questions or comments? Assume they have questions. Silence is rarely agreement — it is usually calculation. Your job is to make speaking up the easier choice.
3. Use Team Rules
Collaboration is a constructive argument, and people need to know what is expected of them on both the giving and receiving end. I use a small set of Team Rules — typically three or four from this menu — to establish the collaboration norms before the work begins: Improve the program, system, or process and this team at the same time; afford everyone the assumption of best effort and best intentions; if you don’t know, say so; be empowered representatives and respect the decisions made by the team; make and recognize repair attempts; get it right over being right.
4. Model Acceptance
Use language that signals comments are expected: “I may not have this right.” “Tell me what I’m missing.” When feedback comes, receive it visibly. Your reaction in the moment is the culture signal the team is watching.
5. Use Active Listening — RASA
I use Julian Treasure’s RASA framework: Receive, Appreciate, Summarize, Ask. The goal is to close the communication gap. Every message passes through four filters: what you meant, what you actually said, what they heard, and what they think you meant. Active listening works to bridge those gaps — and it models the behavior you want the team to practice with each other.
6. Facilitate Group Decision-Making
Get all ideas into the open before evaluating any of them (divergent thought). Then let the team prioritize together — dot voting, discussion, whatever fits the context (convergent thought). This prevents the loudest voice from winning and ensures everyone’s input has been genuinely heard before decisions are made.
Pillar Four: Transparent Processes
What Is It?
Processes are the connective tissue between vision and reality. They are how a team consistently delivers on its promise. Results without process are not repeatable. Process without results is futile.
Transparency means we don’t create metrics for metrics’ sake. We want measures that come directly out of our management tools — so that when they indicate something, we can actually take action. We want to know when something is stuck. That is what allows us to intervene.
A metric without a rhythm is just a number. Every metric needs a cadence — a repeatable moment where someone is accountable for looking at the indicator and asking: what do we do about this? The cadence is what turns data into decisions.
The Story: The Training Metric
A corporate president once asked our VP of Engineering how many people in a particular engineering leadership role had completed a required training. It should have been a simple question. It wasn’t.
First, we couldn’t determine who was in the role — not everyone had the correct job code. So we first had to identify who should be trained. Then we compared against course roster reports. The number was 60%. Low, but at least we had it.
Six months later, he asked again. The number was worse. Why? No courses had been scheduled in the intervening period. We had a metric but no mechanism.
Visibility without process is just embarrassing scorekeeping.
The fix wasn’t trying harder. It was building the system: correct job codes enabled systematic training assignment, which enabled a training backlog, which enabled courses to be offered at a rate that guaranteed anyone in the role would be trained within two months of attaining it. The metric became a managed metric.
What Breaks It?
Undocumented processes — doing everything as though it is the first time, every time. Institutional knowledge lives in people’s heads and leaves when they do. Ad hoc metrics — picking measures informally and never mechanizing them. The metric depends on someone manually compiling a spreadsheet. That always eventually breaks. No rhythm — if there is no meeting, no repeatable point to review the metric and make corrections, the backlog it is indicating will never get addressed.
How to Build It: Three Actions
1. Document the Process
Write it down. Every repeatable process should have a documented form — a charter for a new team, a defined workflow for recurring work, a standard operating procedure for common tasks. If it only exists in someone’s head, it is not a process. It is a dependency.
2. Determine Meaningful Measures
Not everything needs a tracked metric. Some measures are watched as part of daily work. Others need a number that gets tracked over time. The test: if this number changes, can I take an action? If yes, it is worth tracking. If the number changes and you don’t know what to do about it, it is noise.
3. Instrument the Process
The meaningful metrics should be yielded by the process tracking mechanism itself — not by a separate manual effort. When the metric is a byproduct of doing the work, it is self-sustaining. When someone has to compile it separately, it is fragile. Build the instrumentation into the process from the start.
The Most Common Mistake
They keep doing when they should spend their time seeing.
Most managers who struggle to build high-performing teams share a single root problem: they never made the identity shift from individual contributor to leader.
They try to be the smartest person in the room rather than facilitating collective intelligence. They fix their team’s work rather than providing feedback — essentially competing with their own reports. They hoard work instead of delegating it. These are not three separate problems. They are three symptoms of a manager who is still trying to win as a player instead of developing a winning team.
The thing that got them promoted — being an exceptional individual contributor — is the exact thing that will hold them back as a manager. The shift is from doing to seeing. From solving to facilitating. From having the answer to asking the question that gets the team to the answer.
I needed to make this shift myself. I was such a good doer, I couldn’t stop. I needed to delegate. I needed to request help and be really clear about what I was seeing — but also let people bring their whole selves to the table rather than dictating what needed to be done. It’s a delicate balance I wish I had known I needed to learn earlier.
The Turnaround: All Four Pillars in Practice
Years ago, I was managing a business with 160 people spread across many teams and both coasts. One team was in crisis. They had been yelling at their client for months. The client had been yelling back. The meeting notice sent to address it read: “There has been enough cross talk and emails to give reason for this discussion. We are running out of time so bring your hate and discontent.”
It felt like it could all catch fire.
Here is what I did — and how each of the four pillars was present in the recovery.
Cohesion: Call Every Person
Before anything else, I called every person on the team. There were about 20 people. The first five to ten minutes of every call was personal — vacation plans, kids, catching up. I was doing this out of genuine interest. I was also building cohesion. A team that knows each other communicates better. I needed them calm enough to receive a difficult conversation, and I needed them to trust me before we got to the hard part.
Alignment: The Shared Why
In each call, I also ensured we were aligned on the same goal — both the infinite goal (the Why) and the finite goal (the What). “I think this got emotional because everybody just wants to get it right. I’m here to be your boss’s trusted partner in executing this high-consequence mission. And to do that, we need this project to be successful.” Everybody’s response: “Yeah — that’s why I’m here too.” In five minutes per call, we were aligned.
Psychological Safety: Team Rules and Active Listening
When the client rep started yelling on the conference call, I performed a trick I use to maintain emotional distance: I pretended he had yelled into Siri and all I got was a text message with no tone of voice. I listened for the content underneath the volume. I used active listening to play it back: “Let me repeat to make sure I understand your concern: you believe our solution will not meet your requirements because of these three reasons. Is that right?” He agreed. I think it was the first time he had felt listened to in a while.
When we got the teams in the room together, I wrote Team Rules on the whiteboard before anything else. Every concern that was raised, I wrote it down and confirmed I had captured it correctly. I watched people in the room start to nod. Once the heads were empty, we prioritized together. Dot voting — three dots each. Volunteer for the first priority, the second, the third. Sub-teams went off and worked. Reported back. New problems captured. New top three voted. Move out.
Transparent Processes: The Whiteboard as System
The root of the conflict was a transparent process failure: the team had not been tracking client questions in a way that would allow them to defer answers reliably. Questions went unanswered. Frustration built. The client started yelling. The team shut down.
The whiteboard became our process. Every concern was visible. Every priority was voted on publicly. Every sub-team reported back to the group. The rhythm was 7am, noon, 4pm. New problems, new top three, volunteer, move out. The cadence transformed individual knowledge into shared understanding.
The Result
On Wednesday morning, I came in at 7:45 with donuts. The team had started at 7am without me. They presented the plan to me. They didn’t need me to facilitate any longer. They were a self-organized team.
On Thursday night, a team that had been yelling at each other for three months all joined me at a baseball game. Best ticket purchase I’ve ever made.
On Friday afternoon, a team that had been in conflict for months nearly completed their project in five days.
We did not lower standards. We increased safety. And we built all four pillars in the process.
The One Thing I Wish Someone Had Told Me
You have to make a shift — from doing to facilitating. The sooner you know that’s the shift, the sooner you can start making it.
I was a strong individual contributor. That is why I got promoted. And for a long time, I kept doing what made me successful — solving problems, having answers, working the hardest. That is exactly the wrong instinct for a leader.
The shift is from doing to seeing. From having the answer to asking the question. From filling the whiteboard yourself to facilitating the room until the team fills it. From dictating what needs to be done to letting people bring their whole selves to the table.
It is a delicate balance. And the first step is knowing the balance exists. A book that gave me the language for this shift was The Performance Pipeline by Stephen Drotter — it describes what changes at each level of a leadership hierarchy. I wish I had it sooner. It describes how to build a functional hierarchy, not how to organize for teamwork — which is exactly the gap this framework is designed to fill.