Join almost any team meeting in any company and you'll see the same thing. Six people, maybe sixteen. Someone shares their screen. There's a list of work. Assignments are handed out, owners are named, and the meeting ends. Everyone puts their headphones on and works. Alone. Problems go up to the manager. Answers come back down. Tomorrow they do it again.
Most leaders look at this and see a team. I see a group.
That difference is the subject of my new book, The 5X Effect, and it explains most of the performance gap I've seen in forty years of building software and coaching the teams that build it.
The thirty-second diagnosis
I can tell whether I'm looking at a team or a group in about thirty seconds.
A group is quiet. The chat channel is mostly status updates and "any update on this?" from the manager or product owner. Everyone was told what to work on, and they're all working on different things. Problems go up, answers come down, and the manager or product owner is the traffic cop. Every decision waits for that one person.
A real team is noisy. There's constant conversation: quick calls that end as soon as the question is answered, people helping each other with work outside their specialty, people picking up the next piece of work when they're ready instead of waiting to be assigned. The team decides who does what and how.
Most organizations have far more groups than teams. The org chart says "team," the Slack channel says "team," and the meetings happen on schedule. But nobody shares ownership of the work, nobody decides together, and nothing holds the people together except the label. I call these phantom teams.
Same people, different system
The gap between a phantom team and a real one isn't small. I've coached many teams to five times their starting performance: five times the work finished and the value delivered. Same people. Same budget. What changed was how they worked together.
One example from the book. A team had spent nine months on a customer-facing feature that management had promised to the board and to key customers. Smart people, solid engineering, and every two weeks the list of "almost done" items got longer.
When I sat in on their planning, I noticed that every conversation about what to build included three or four other things they "should probably handle while we're in there." Reporting. Edge cases for customers who weren't in scope. A half-promised integration. Nobody had ever told them to do those things. Nobody had ever told them not to, either.
So we wrote down what was out of scope and got management to agree to it in writing. The feature they'd been almost finishing for nine months shipped in six weeks. They didn't work harder. They stopped working on things nobody needed yet.
At another organization, the developers had always worked on separate items. When they tried working together on one item at a time until it was finished, the amount of work they finished more than doubled in a single two-week stretch.
Neither of those changes required new people or more money. Both required a different system.
Why this matters more with AI
AI tools make the difference between a group and a team much larger.
Give a group AI tools, and each person produces far more work, alone, with nobody else looking at it. The manager in the middle now has more questions to answer and more work to check. More gets started and not much more gets finished.
Give a real team the same tools, and the extra output goes somewhere useful. The team already shares the work of checking, already decides together what's finished and already moves people to where the work is piling up. The tools make a group busier. They make a team faster.
Why most attempts to fix it fail
Most organizations that have tried to build real teams installed a process: new meetings, new boards, new roles. Then the consultants left, and the teams went back to working alone, with more meetings than before.
The process wasn't wrong. It was missing the part that matters: changing how people think about their work, their decisions and each other. That can't be installed. It has to be built, in the right order, one stage at a time, and it gets harder before it gets easier.
That's what the book is about: the five stages that take a group to a team that manages itself, what each stage asks of the leader, and what goes wrong along the way.
The 5X Effect is out now. I'm walking through the core of it in a free live webinar on Wednesday, November 11, with time for your questions. / and the book's free scorecards and tools.