5 Signs You're Leading a Group Instead of a Team
- Jonno White
- 3 days ago
- 15 min read
Last updated: July 2026
Here is the direct answer: you are leading a group instead of a team if your people agree in the room and diverge the moment they leave it, if accountability always points sideways to a function instead of upward to a shared result, if problems get escalated to you rather than solved between peers, if decisions keep getting relitigated after meetings end, and if the outside world experiences your leadership as several voices rather than one. Each sign below is a structural symptom, not a verdict on anyone's character.
As of July 2026, the distinction between a group and a team is not academic. Global employee engagement fell to 20% in 2025, its lowest level since 2020, and manager engagement (the layer most responsible for translating a leadership team's direction into daily work) dropped nine points over the same period, according to Gallup's 2026 State of the Global Workplace report. A separate 2025 Atlassian study found only 7% of executives feel confident they know how each team's work supports the organisation's biggest goals. Both numbers describe the same underlying pattern this piece is about: a collection of capable people, coordinating on paper, not actually operating as one team.
My read on those figures is that they describe a design problem before they describe a people problem. A group of skilled individuals, each managing their own patch well, can look identical to a team from the outside right up until the moment something requires them to move together. I am a Certified Working Genius Facilitator, certified through Patrick Lencioni's Table Group, and the author of Step Up or Step Out, and the pattern below draws on that difficult-conversations and delegation framework to explain why the group-versus-team gap is so easy to miss from the inside.
What follows are five checkable signs, not a personality test. Each one names a specific, observable behaviour, explains the research behind why it happens, and points to what changes once you see it clearly. None of them require replacing anyone on the team, and none of them are fixed by a single offsite or a values statement, which is precisely why they are worth naming precisely rather than treating as one vague alignment problem.
Key Takeaways
A group coordinates individual effort; a team owns a shared outcome together, and that difference is structural, not a matter of trying harder.
If a strategy agreed in the leadership meeting quietly reverts to five different functional priorities within a week, that is a structural symptom, not a personality clash.
Psychological safety, not personality fit, is the factor most consistently linked to team performance in the research literature.
When decisions get relitigated after the meeting ends, the fix is clearer decision rights, not more meetings.
Real team accountability means the whole team owns the collective result, not just each person's own slice of it.
Why Leading a Group Instead of a Team Feels Fine, Until It Isn't
A working group and a team can look the same on an org chart. The difference only shows up under pressure: when a decision needs everyone to move together, when a target is missed and someone has to own it collectively, or when the organisation needs one consistent message rather than five accurate but different ones. Groups are built for coordination. Teams are built for shared outcomes.
Neither structure is automatically wrong. A group of specialists with genuinely separate mandates, each accountable for a distinct outcome, can be exactly the right structure for that function. The problem is not that groups exist. The problem is leading a group as if it were a team: expecting the collective ownership, trust and follow-through of a team, from a structure that was never built to produce them.
The five signs below are how that mismatch shows up in practice.
Some genuinely useful working groups exist inside organisations that also run genuine teams elsewhere. A group of regional managers, each fully accountable for their own territory with little practical interdependence between territories, may be led perfectly well as a group. A group of specialists brought together briefly for a single cross-functional project, then dispersed back to their own reporting lines, is often better served by clear individual accountability than by an artificial push toward shared ownership that will not outlast the project. The signs below are only a problem where the leader has decided, explicitly or by default, that this collection of people needs to function as a team, and the structure underneath has not caught up with that decision.
1. Strategy Agreed in the Room Doesn't Survive Contact With the Door
The clearest sign you are leading a group instead of a team is that agreement in the meeting does not travel. Everyone nods at the strategy, then returns to their function and quietly re-prioritises it through their own lens. Nobody is lying in the room. The agreement was real. It just was not built to survive contact with five separate sets of competing local pressures.
A 2025 Atlassian study, cited via a workplace-research roundup, found that only 7% of executives feel confident they know how each team's work supports the organisation's biggest goals. That is not a communication problem you can fix with a better slide deck. It is what happens when alignment is treated as an event (the meeting) instead of a structure (shared metrics, shared language, and a standing mechanism for catching drift before it compounds).
A landmark 2015 Harvard Business Review study by Stanford's Behnam Tabrizi, examining 95 teams across 25 corporations, found that roughly three in four cross-functional teams failed on at least three of five basic success measures, including staying aligned with company goals. That figure is a decade old, but the underlying dynamic, that cross-functional alignment decays without a structure to hold it, shows up just as clearly in the newer data above.
My interpretation is that this sign is the most forgivable and the most expensive at once. Forgivable, because every leader in the room genuinely believed the strategy when they agreed to it. Expensive, because the gap between "agreed" and "executed" compounds every week it goes unaddressed, and by the time it surfaces as a missed target, it looks like an execution failure rather than what it actually was: a structural one.
2. Accountability Points Sideways to a Function, Never Up to a Shared Result
A second sign is that every individual's numbers can look fine while the collective result slips, and nobody quite owns the miss. In a group, each person is accountable for their own domain. When the shared outcome falls short, the honest answer from each individual is technically correct: their part held up. That is precisely the structural gap. A team is built so that the whole group owns the collective result together, not just their own slice of it, which is why Key Takeaway four above matters more than it first appears to.
Imagine a leadership team where sales hit its number, product shipped on time, and customer support closed its tickets within target, yet the company still missed its overall growth goal for the quarter. Every individual scorecard is green. The collective outcome is red.
In a group, that gap has nowhere to land, because no single measure of success was ever shared in the first place. In a team, that gap is everyone's problem the moment it appears, because the scorecard that matters most was never individual to begin with.
This is one of the clearest practical differences between a group and a team: not effort, not talent, but what gets measured and who is on the hook for it. Shifting from individual to shared accountability is uncomfortable, because it means a strong individual result can no longer fully protect someone from a weak collective one. That discomfort is often exactly why leadership teams avoid making the shift explicitly, even when they can describe the problem accurately.
The tell is usually in the language a leadership team uses about its own results. A group talks about outcomes in the third person plural about its parts: "sales did well, but marketing missed its number." A team talks about the same result in the first person plural about the whole: "we missed our number, and here is what each of us is doing differently next quarter." The shift from the first phrasing to the second is not a communications exercise. It only becomes honest once the underlying measurement actually is shared, which is why leaders who try to force the language before changing the measure usually find it rings hollow to the people saying it.
3. Problems Get Managed Upward Instead of Solved Sideways
A third sign is that issues between functions get escalated to the leader rather than resolved between the peers who own them, which is what functional silos look like in practice. Google's Project Aristotle research, one of the most cited studies on team effectiveness, analysed more than 180 teams over two years and found that psychological safety, not seniority, personality mix, or even talent, was the factor most strongly correlated with team performance out of five measured dynamics (psychological safety, dependability, structure and clarity, meaning, and impact).
Picture a function head who notices another function's approach is quietly creating problems downstream. In a team with genuine psychological safety, that gets raised directly, peer to peer, because the relationship and the shared stake in the outcome can absorb the friction. In a group, it gets carried upward instead, framed carefully, because raising it directly with a peer feels riskier than raising it with the boss.
Gallup's 2026 data adds a second layer here: manager engagement dropped nine points from 2022 to 2025, and managers account for a large share of the variance in how engaged their teams are. A disengaged manager layer is less likely to model the kind of direct, safe peer conversation that stops small friction from becoming an escalation habit.
My read is that this sign is the hardest for a leader to see from the inside, because escalation feels like diligence. People are bringing you real problems. What is harder to notice is that they are bringing them to you instead of to each other, and that the habit of routing every cross-functional friction point through the top is itself the symptom.
4. Meetings Produce Agreement, Not Resolution
A fourth sign is that the same decisions keep resurfacing after the meeting that supposedly settled them. A decision gets made, everyone leaves aligned, and within two weeks it is quietly reopened in a side conversation, a different forum, or a follow-up email that walks it back. This is different from sign one. Sign one is strategy failing to translate into daily priorities. This sign is narrower: specific decisions, already made, not holding.
Suppose a leadership team agrees to prioritise one major initiative over another for the quarter. Two weeks later, a function head raises the deprioritised initiative again in a different meeting, not maliciously, but because the original decision was never actually theirs to defer to. Nobody was assigned clear ownership of holding the line. An Atlassian-sourced 2025 figure found only 20% of knowledge workers feel confident their team has an effective process for quickly informing other teams of decisions that affect them, which is a close cousin of this exact problem: decisions exist, but the infrastructure for them to stick and to be visible does not.
The fix for this sign is rarely "more meetings" or "better minutes." It is assigning explicit decision rights before the meeting, not just discussing the topic in it, so that everyone leaves knowing not just what was decided but who owns making it stick.
5. The Team Only Exists Inside the Room
A fifth sign is that outside your leadership meetings, the organisation experiences multiple different voices rather than one team. Customers hear one message from one function and a slightly different one from another. Staff two levels down get inconsistent signals about what actually matters this quarter, depending on which leader they report to. Inside the room, everyone agrees. Outside it, the team does not appear to exist at all, only its individual members do.
This sign is the most externally visible and the most commonly misdiagnosed, because it usually gets treated as a communications or branding problem rather than a leadership team structure problem. My interpretation, reasoning from the engagement data above rather than from a specific measured study of this exact pattern, is that inconsistent external representation is close to always downstream of one of the first four signs: if strategy does not travel, if accountability does not point to a shared result, if problems do not get solved sideways, or if decisions do not hold, then of course the people representing that team externally will sound like individuals rather than a unit. This is why it sits last: it is usually the visible symptom of the other four, not a separate root cause in its own right.
Staff two or three levels down the organisation are often the most reliable diagnostic instrument for this sign, more reliable than a customer survey or a board observation. They sit close enough to several functions to notice when the messages genuinely conflict, and far enough from the leadership team itself to describe it plainly rather than diplomatically. A leader who wants an honest read on whether their team exists as one voice outside the room could do worse than asking a handful of people two levels down what they believe the team's top priority actually is this quarter, and comparing the spread of answers.
Common Mistakes Leaders Make Trying to Fix This
The most common mistake is treating every one of these signs as a communication problem and responding with more meetings, more updates, or a better slide template. Communication makes an aligned team more efficient. It does not create alignment where the underlying structure, shared metrics, clear decision rights, psychologically safe peer relationships, was never built. More meetings on top of an unclear structure usually just produces more of sign four: decisions that get discussed again without actually holding.
A second common mistake is trying to fix accountability with a single culture statement or values refresh rather than a change to what is actually measured and reviewed. Teams do not become collectively accountable because a leader says the word "team" more often. They become collectively accountable when the measure that matters most stops being purely individual and starts being shared, and when that shared measure is reviewed as seriously as anyone's individual scorecard.
A third mistake is assuming psychological safety is a personality trait some teams have and others do not, rather than something a leader can deliberately build through consistent practice. Google's own Project Aristotle research treated psychological safety as buildable, not fixed, which is part of why it remains one of the most replicated findings in team-effectiveness research nearly a decade on.
A fourth mistake is reaching for an offsite or a team-building event as the primary fix before any of the underlying structure has changed. An offsite can be an excellent forum for having the conversations these five signs require, naming which measure will become shared, agreeing explicit decision rights, testing whether a peer relationship can actually hold direct feedback. It is a poor substitute for those conversations. A leadership team that returns from a well-run retreat with warm feelings but no change to what gets measured, escalated, or decided will usually see the same five signs reappear within a few months, because the event addressed the mood in the room rather than the structure underneath it.
Turning a Group Into a Team: What Actually Changes
The starting point is naming which of the five signs is present, specifically, rather than reaching for a generic team-building exercise. A team that struggles with sign one (strategy not translating) needs a different intervention than a team struggling with sign three (problems escalating instead of resolving between peers), even though both would be described from a distance as "alignment issues."
For the strategy-translation sign, the practical fix is treating alignment as a structure rather than a single meeting. That means a standing, short mechanism, a fortnightly check where each function reports specifically on where its own priorities have drifted from the agreed strategy, not just on progress against its own targets. The difficult-conversations work behind Step Up or Step Out is directly relevant here: most drift is never named out loud in the room, because naming it feels like accusing a peer of disloyalty rather than describing a structural gap, and a team needs an explicit, low-friction way to raise that gap before it compounds into a missed quarter.
For the accountability sign, the practical shift is moving at least one meaningful measure of success from purely individual to genuinely shared, and reviewing it in the room together rather than only in one-on-ones. My Replace Yourself framework, built originally for delegation, applies here in a specific way: a leader who has replaced themselves on individual tasks has more capacity to build and protect a shared measure that the whole team is accountable for, rather than defaulting back to managing five separate individual scorecards because that feels more controllable.
For the psychological-safety sign, the Fuel or Drain? lens is a useful diagnostic before any structural fix: is raising a problem with a peer currently a fuel behaviour (rewarded, modelled, safe) or a drain behaviour (subtly punished, avoided, routed around) inside this specific team. Leaders often assume they have already answered this question when they have not actually tested it against how their own team behaves under real pressure, not in a workshop.
For the decision-rights sign, Working Genius facilitation (a framework created by Patrick Lencioni, of which I am a Certified Facilitator through the Table Group) is useful because it gives a team a shared, non-personal language for who is naturally suited to which stage of getting a decision made and, critically, held. Assigning decision ownership by working genius type rather than by seniority alone tends to make the decision stick, because the person holding it is genuinely suited to defending and following through on it.
For the external-representation sign, the fix is rarely a communications policy. It is closing the other four gaps first, because a team that has already built a shared measure, direct peer problem-solving and decisions that hold will find that consistent external representation follows almost automatically. Trying to enforce "one voice" externally while the internal structure still produces four different sets of priorities usually just pushes the inconsistency underground, where it shows up as quiet, hard-to-trace confusion rather than an obviously mixed message.
Frequently Asked Questions
What is the real difference between a team and a group at work?
A group coordinates individual work toward related but separate goals, while a team shares collective ownership of one outcome together. The practical test is what happens when something goes wrong: in a group, individuals can point to their own results as evidence they did their part; in a team, the whole group owns the miss regardless of any one person's individual performance.
How do you know if you are leading a team or just a group of individuals?
Check what happens after a decision leaves the room: if it holds without drifting, you are likely leading a team, and if it quietly reverts to separate functional interpretations within days, you are likely leading a group. The five signs in this piece, strategy not translating, sideways-only accountability, upward-escalated problems, relitigated decisions, and inconsistent external representation, are the checkable version of that test.
Can a group of talented individuals still outperform a poorly functioning team?
In the short term, yes, particularly where the work genuinely is separable and does not require real interdependence. Over time this gets harder to sustain, because a group has no shared mechanism for absorbing a shock that affects the whole system at once, which is exactly the scenario a genuine team is built to handle.
What is the fastest way to start turning a group into a team?
Pick one measure of success and make it genuinely shared rather than individual, then review it together as a group rather than only in separate one-on-ones. This single change forces several of the other signs to surface quickly, because a shared measure makes sideways-only accountability, relitigated decisions and unresolved cross-functional friction far harder to ignore.
Does every team in an organisation need to function as a true team rather than a group?
No, because some functions are genuinely better served by a group structure, where each person owns a distinct, separable outcome and coordination is all that is required. The mistake this piece is about is not that groups exist, it is expecting team-level trust, shared accountability and follow-through from a structure that was deliberately built for coordination, not collective ownership.
How long does it typically take to shift a group into functioning as a real team?
There is no fixed timeline, because it depends on how many of the five signs are present and how entrenched the individual-accountability habits already are. What tends to move fastest is the accountability shift itself, since making one measure genuinely shared changes behaviour within a single reporting cycle, while rebuilding psychological safety after it has eroded typically takes sustained, consistent practice over several months rather than a single conversation or offsite.
Final Thoughts: What Changes Once You Stop Leading a Group Instead of a Team
None of these five signs are a verdict on the people in the room. They are structural, which is the good news, because structures can be changed deliberately in a way that personalities cannot. The shift from a group to a team rarely requires replacing anyone. It requires naming, specifically, which of the five patterns is present, and then changing what is measured, how problems are allowed to move between peers, and how decisions are assigned and defended once they are made.
The reason this distinction matters more in 2026 than it might have a decade ago is straightforward: engagement is at its lowest recorded level in years, and a team that only exists on paper has less margin for absorbing that pressure than one that genuinely shares ownership of its outcomes. Naming the gap honestly is the first, most practical step toward closing it.
It is worth being honest, too, about what naming the gap does not do. Recognising that you are leading a group instead of a team does not, by itself, change a single measure, decision right, or peer relationship. It only makes the next choice visible: keep leading it as a group, deliberately, because that is genuinely the right structure for this function, or start the specific, unglamorous work of building the shared accountability, safety and decision-holding that a real team requires.
Both are legitimate choices. Continuing to lead a group as if it were already a team, without choosing either path, is the only option that keeps costing you quietly.
If you are recognising your own leadership team in more than one of these signs, it is the kind of pattern I work through directly with executive teams, school leadership teams and nonprofit boards. If that is you, reach out and I would be glad to help, since helping people through exactly this is what I specialise in. You can reach me at jonno@consultclarity.org.
About the Author
I am a Certified Working Genius Facilitator, certified through Patrick Lencioni's Table Group, and the author of Step Up or Step Out. I work with schools, corporates, and nonprofits around the world. If that is useful for your team, you can reach me at jonno@consultclarity.org.
Sources
Gallup, State of the Global Workplace: 2026 Report, https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx
Behnam Tabrizi, "75% of Cross-Functional Teams Are Dysfunctional," Harvard Business Review, June 2015, https://hbr.org/2015/06/75-of-cross-functional-teams-are-dysfunctional
Google re:Work, "Understand Team Effectiveness" (Project Aristotle), https://rework.withgoogle.com/intl/en/guides/understand-team-effectiveness
Atlassian, State of Teams 2025, cited via Deviniti, "35 System of Work Statistics for 2026," https://deviniti.com/blog/leadership-teamwork/35-system-of-work-statistics/