I used to think leadership meant having the answer.
I spent years in the Army training myself to be the person who knew what to do next. In tech leadership, this conditioning deepened. Every room I walked into, I arrived with a position. I had done the analysis. I was ready to drive the decision. This was my job.
It took a quiet engineer named Marcus to break me of it.
We were in a planning session, working out an architecture decision blocking the team for weeks. I walked in with my recommendation already written. I gave it. Heads nodded. We were about to move on.
Then Marcus said, "I don't think this solves the Thursday problem."
Nobody knew what the Thursday problem was. Marcus explained it in two minutes. It was something he had seen in the data over three months of late-night log reviews. My recommendation would have created a cascading failure every seven days. It would have taken down production every Thursday morning like clockwork.
I had been the smartest person in the room. Right up until the room corrected me.
The Expertise Trap
There is a particular kind of leader who is deeply intelligent, experienced, and wrong. Not wrong about everything. Wrong about the single most important thing: they believe their job is to be the expert.
I was this type of leader for years.
It feels like competence. When you arrive prepared, when you drive meetings toward decisions, when people look to you and you have an answer... this feels like leadership. The problem: you are optimizing for the appearance of expertise, not the quality of the outcome.
When you lead every meeting with your own view, you do not get the benefit of eleven other people's knowledge. You get eleven people performing agreement.
Performance of agreement is one of the most expensive things a company buys.
The people in your team see things you do not. They work closer to the problem. They sit with the logs at 11pm. They hear the customer complaints firsthand. If the meeting's purpose is to validate your conclusion, their knowledge does not enter the room. It stays at their desks, unspoken and unused.
What the Research Shows
In 2010, researchers Anita Woolley and Thomas Malone ran a study across 192 groups and 699 individuals. They were looking for a group equivalent of individual IQ... a collective intelligence factor, or c-factor.
They found it.
Teams with high c-factor consistently outperformed teams with lower c-factor across a range of tasks: puzzles, negotiations, moral reasoning, brainstorming. The c-factor predicted performance better than the average IQ of team members.
So what determined c-factor? Three things:
- Social sensitivity ... the ability of team members to read each other, to notice when someone has something to say, to pick up on who is holding back.
- Equal speaking time ... teams where conversation was distributed performed better. Teams where one or two people dominated performed worse.
- Proportion of women in the group ... women scored higher on social sensitivity measures, and teams with more women showed higher collective intelligence.
Here is what did not predict collective intelligence: group cohesion, member satisfaction, motivation, or... crucially... how smart the individual members were.
Read it again. The average IQ of the people in the room did not determine how smart the room was.
The dominant voice did.
If You Talk the Most, You Cost the Most
Most leaders think their job in a meeting is to contribute. The more they contribute, the better they are doing. They ask: Did I add value? Did I steer things in the right direction?
Wrong question.
The right question: Did I hear things I would not have heard if I had spoken first?
The Woolley research is clear. Teams where a few people dominated conversation had less collective intelligence than groups where everyone took turns. You are not only failing to hear good ideas when you dominate the room. You are actively suppressing the intelligence of the team. You are making the group dumber by being in it.
A hard thing to sit with, if you built your career on being smart.
Fewer than one in four employees are engaged at work, according to Gallup. One major driver of disengagement is feeling unheard. When your team learns meetings are a performance of your conclusions, they stop bringing their best thinking. They arrive with nothing and leave with nothing. The cost is yours alone.
Three Things I Changed
After the Marcus incident, I changed how I ran meetings.
First, I stopped sharing my position at the start. I had a position, but I stopped opening with it. Instead I opened with the question. "We need to solve X. What are you seeing?" This felt uncomfortable for about a week. Then it started surfacing things I had not thought of.
Second, I started tracking who had not spoken. Not to call people out. To notice when the room's intelligence was being wasted. If someone had been in the room for forty minutes and said nothing, either they had nothing to say... unlikely... or the conditions were wrong for them to say it. My job was to fix those conditions.
Third, I got genuinely curious about being wrong. Not performatively curious. Not "great point, I will factor it in" while privately dismissing it. Genuinely curious. The Marcus incident helped. I had been completely wrong about something I was confident about. Once it happens once, you look for the next Marcus. You want to find them before the system goes down.
The Smartest Leaders I Have Known
Every leader I genuinely respect shares one quality: they think the people around them are interesting.
Not useful. Not subordinates. Not resources. Interesting.
They walk into rooms expecting to learn something. They treat disagreement as information. They know their own thinking has blind spots, and they treat other people as what fills those blind spots.
This is not soft. It is not about feelings or psychological safety as a buzzword. It is an intelligence strategy. You are running a group decision-making system, and the inputs to it are the perspectives of your team. Throttling those inputs to run your own conclusions through the group is expensive waterfall design.
The best teams I have been part of were not the ones with the smartest individuals. They were the ones where the least senior person in the room felt their idea would be heard. Where the quiet engineer would stop a project cold if they had seen something in the logs. Where the room corrected you.
The Question Worth Asking
Think about the last important meeting you ran.
Who talked the most?
If the answer is you, think about what you did not hear. Think about who had something to say and did not say it. Think about the Marcus in the room... who watched you build your recommendation and said nothing, because the room had been trained your recommendation was the destination.
The smartest person in the room is the room. Not a feel-good platitude. A design principle. The question is whether you are building conditions for the room's intelligence to operate, or whether you are shorting it out every time you speak.
Worth sitting with.