I often hear a version of the same request from CEOs: “I want a high-performing team.” It’s a fair thing to want, and I usually answer with a question: “How will you know when you have one?”
There’s typically a pause. Then comes a description of a feeling, a frustration or a gap that’s hard to name. That pause has taught me a lot.
I’ve worked closely with around three dozen teams over the years. Most were senior teams, across many industries. Some were very focused on performance. Many were purpose-driven organisations doing important work for their communities. When I look back across them, the same patterns keep showing up. These are beliefs about teams that are widely held, rarely questioned, and often unhelpful. I call them the five myths of teams.
Myth 1: A high performing team is the main goal
It’s very rare for a team to describe itself as high performing. This isn’t because senior teams are falling short. It’s because the target is set up to fail.
Senior leaders tend to be high achievers. There’s always more to do and always a higher bar, so “high performing” never quite arrives. On top of that, few teams can say what high performance actually looks like. And herein lies the paradox. Leaders tend to use the phrase “I want a high-performing team” as a proxy for a problem that the team hasn’t yet named.
The most common of those problems is that people are not working at the right level. The organisational theorist Elliott Jaques gave us a useful way to think about this. He found that organisations with too many levels become overlapping, confusing and inefficient. Those with too few levels create gaps, which also lead to confusion and inefficiency. Jaques described each level in two ways:
-
Time span: how far into the future a role needs to look. An entry-level role might look one to three months ahead. A senior executive role might look five to ten years ahead. At the very top of a large organisation, such as BHP, the horizon may stretch 25 years.
-
Complexity: the nature of the work and the kind of thinking it requires.
When senior leaders aren’t working at their level, they usually end up in the weeds, doing the detailed work that belongs one or two levels below them. I call this role slump. It tends to happen for one of two reasons. Either the leader hasn’t noticed, because detailed work is familiar and satisfying, or they haven’t yet built a team below them that they can trust to do the work.
So what do leaders actually want when they ask for high performance? In my experience, they want high impact: to get the job done well, to bring people with them, and to build a culture people want to be part of.
We fall under the alluring spell of numbers when we measure performance: finances, ratios, quality measures. But more important is measuring impact: culture, safety, belonging, client outcomes, and environmental impact. Once a team agrees on the impact it wants to have, the conversation deepens and becomes far more useful.
Myth 2: One offsite is enough to build a team
Mention a “team-building day” and you’ll usually see a few eyes roll. That reaction is understandable. Many of us have been through a well-meant offsite that changed nothing by the following Tuesday.
What matters isn’t the activity itself. It’s the answer to a simpler and deeper question: who are we to each other?
Offsites can be valuable. They create space away from the day-to-day work to build relationships and understand one another better. But they are a starting point, not the team-building process itself.
Teams strengthen as the work happens. That means making reflection part of the team’s regular rhythm: do, reflect, learn, then do it again.
We use what we call the 2% rule: the most effective teams set aside 2% of their time to focus on their teamwork. That’s roughly half a day each quarter. It isn’t much, but that regular investment gives teams space to step back, reflect on how they are working together and make adjustments.
Put simply, teamwork is a discipline, not a destination. It takes time and practice. Trust in particular builds slowly, and you can’t rush it.
Myth 3: There is one best way to do team development
This leads to the next question: what kind of team are you, really?
One of the most useful distinctions I share with leadership teams is between interdependent and independent teams.
-
Independent teams do work that doesn’t rely heavily on each other. One example was a global HR team in a mining company, spread across regions and reporting lines. Another was a very large executive team in a purpose-driven organisation, with separate divisions for aged care, hospitals and community services.
-
Interdependent teams can only achieve their goals together. A health insurer is a good example: customer insight, product design, delivery and compliance all have to work as one. This is becoming more common as corporate functions such as IT and HR are outsourced and the joins between functions matter more.
It’s worth stopping to ask yourself where your own team sits on a scale of independence to interdependence.
This matters because the right way to build a team depends on the nature of its work. Insisting that an independent team collaborate more can do more harm than good. The evidence, including a meta-analysis of over 7,500 teams, supports a differentiated approach for teams[i][ii]. Four principles stand out for independent teams:
-
Invest in sound structure, not forced collaboration. Design the task well and agree a few clear, light-touch norms, such as when to escalate and when to consult a colleague. Don’t mandate meetings or joint deliverables the work doesn’t need.
-
Build connection through voluntary channels. Peer consultation, knowledge-sharing forums and informal mentoring keep a sense of belonging alive without making people more dependent on each other’s tasks.
-
Align standards, not workflows. Where consistent quality matters, invest in shared standards and regular calibration rather than joint production.
-
Watch for isolation. People’s preference for autonomy is itself shaped by how interdependent their work is. Fully independent structures can slowly weaken people’s connection to the wider organisation, so leaders still need to pay attention to engagement and belonging.
In one large purpose-driven organisation I worked with, the Group Executive Team was quite independent as they looked after discrete business units, but its meeting structure was suited to an interdependent team. It involved a formal monthly, day-long meeting with requests for papers, decisions and approvals. Most of these topics didn’t need this team’s involvement; however, the people proposing the papers were seeking validation and affirmation. Once this was recognised, new decision-making processes were put in place within each business unit, and the CEO replaced the one-day Group Executive Team meeting with a long lunch, once a month, with no agenda. Just the conversations that needed to happen to align thinking and values. It worked extremely well for this independent team.
Myth 4: Your “first team” comes first
The idea of a “first team” has been around for decades. Your first team is the most senior team you belong to. For a CFO, that’s the executive team. For the head of treasury, it’s the finance leadership team.
The intention is good, but I think the idea is flawed, for two reasons.
First, it creates competition. If one team is “first,” another must by definition come second. When the two compete for your time or loyalty, you’re expected to put one of them below the other. Do that often enough and you have silos.
Second, organisations are complex. They need all their parts working together. The first-team idea belongs to an older view of the organisation as a machine, where clear hierarchies and ranked priorities keep things running. A better metaphor today is the organisation as an organism, where every part matters and the whole only thrives when the parts are connected. From this perspective, all teams you are a member of need to thrive, not just one.
Myth 5: Teams know their purpose
This may be the most surprising myth. Most teams I work with aren’t clear on their mandate.
They know what they do. Far fewer can say why their work matters, or what unique part they play that no other team in the organisation can.
This is where real teams begin. When a team can describe its purpose, belonging starts to form: a shared commitment and a sense of “us.” It’s very hard to belong to something you can’t explain.
Teams as sacred spaces
So, where does this leave us?
We’re social creatures, and I think we need to value the idea of a team far more than we do. At its best, a team is a small tribe: a group of people we feel connected to and belong to.
Too often we see teams only in terms of what they produce: the outputs, the deliverables, the dashboards. I invite you to see them as something more fundamental, as one of the most important parts of the human experience at work.
Teams are, in a real sense, sacred spaces. If we treat them that way, we’ll lead with more compassion and have a greater impact on the people we serve.
Reflect on the five myths. Which one is holding your team back?
[i] Courtright, S. H., Thurgood, G. R., Stewart, G. L., & Pierotti, A. J. (2015). Structural interdependence in teams: An integrative framework and meta-analysis. Journal of Applied Psychology, 100(6), 1825–1846. https://doi.org/10.1037/apl0000027
[ii] Wageman, R. (1995). Interdependence and Group Effectiveness. Administrative Science Quarterly, 40(1), 145–180. https://doi.org/10.2307/2393703
Edwin is the CEO of Trevor-Roberts and has spent the last 2 decades exploring how people find meaning through their work. He is also Chair of the Advisory board at the Centre for Work, Organisation, and Wellbeing at Griffith University.




