Hello Future Leaders,
In today's issue, we talk about why the smartest person in a meeting often has the least say in what gets decided. You'll see what a study of 699 people found about what makes a group smart and how one diplomat's read of a single man shaped the end of the Cuban Missile Crisis.
The idea nobody heard the first time
You had the best idea in the meeting. You said it early, clearly, with a number to back it up. Nobody picked it up. It’s like no one cared.
Forty minutes later, a senior colleague said nearly the same thing. The room nodded, and it went into the action items with their name next to it.
Your idea was fine. Two other things were off: the timing and the target. The people who look senior in every room are running a different calculation before they open their mouths.
What 699 people revealed about smart groups
In 2010, researchers from Carnegie Mellon, MIT, and Union College ran a simple experiment. They put 699 people into groups of two to five. Each group worked through a mix of tasks, from brainstorming to puzzles to negotiation. The results, published in Science, were surprising. A group's performance was not strongly tied to the average intelligence of its members. It wasn't tied to the smartest person in the group either.
Performance tracked other things. Groups did better when members scored higher on social sensitivity. Researchers measured this with a test where people read emotions from photos of eyes. Groups also did better when everyone got a fair share of the conversation. When one or two people dominated, results dropped.
A later study of 312 people found that individual IQ mattered far more than the original paper suggested. So treat the result as a strong signal rather than a fixed rule. Still, the practical point holds up well. Reading the people in the room is a measurable skill. And it changes what a room produces.
The section is now about 25 words longer than before. If the issue is already close to the 1,000-word limit, you'll need to trim a little somewhere else.
The man who read Khrushchev
On the morning of October 27, 1962, President Kennedy's advisers had a problem. Two letters from Soviet leader Nikita Khrushchev sat on the table. The first had arrived privately the evening before. It offered to remove Soviet missiles from Cuba if the US promised not to invade. The second was broadcast publicly that morning. It added a new demand involving American missiles in Turkey.
Which one should the United States answer?
Llewellyn Thompson had recently returned from years as ambassador in Moscow. Secretary of State Dean Rusk called him "our in-house Russian." Several people at that table outranked him. Nobody there had spent more hours watching Khrushchev up close.
Thompson urged the president to answer the first letter and set the second aside. His reasoning is preserved in the ExComm record: "The important thing for Khrushchev, it seems to me, is to be able to say 'I saved Cuba; I stopped an invasion.'"
That evening, Kennedy sent his reply. It responded to the October 26 letter. It offered assurances against an invasion of Cuba once the missiles were removed. The next day, Khrushchev announced the missiles would be dismantled.
Thompson won the argument by reading the other side. He knew what Khrushchev needed to be able to say afterward.
Read one: who is actually deciding?
Titles lie in meetings. Watch where eyes go after someone makes a proposal and whose question closes a topic. That person is your audience, even if someone else is running the agenda. In a project meeting, it may be the product lead everyone glances at before committing to a date, while the person sharing their screen runs the slides.
Reading the decider also tells you when to wait. Hold your point while the decider hasn't weighed in yet, while a colleague is mid-presentation, or right after bad news lands and the room is still absorbing it. A good point dropped into any of those moments reads as interrupting, however sharp it is.
Read two: what does the decider need to say afterward?
Thompson's question works in every office. Your manager may need to tell their boss, "We stayed on budget" or "No surprises this quarter." Frame your idea so it hands them that sentence.
Script: "This keeps us inside the Q4 budget and gives you something concrete for Thursday's update with [VP's name]."
The same read works with anyone who has to sign off. A client may need to say, "This won't disrupt my team." A professor grading your capstone may need to say, "The method is sound." Find their sentence first, then build your point so it ends right there.
Read three: is the room exploring or deciding?
Early in a discussion, people are generating options, and a fully formed answer gets ignored because nobody is ready to choose. Offer it as one option: "One option could be moving the launch to March. Is there a downside anyone sees?"
Listen for the switch. Someone summarizes, someone asks, "So what are we doing?" or the senior person goes quiet and then asks a sharp question. That's your moment to speak with a clear recommendation.
Big decisions often start before the meeting too. If something matters to you, find the decider for five minutes the day before. Script: "I'm bringing a proposal on the launch date tomorrow. What would make it easy for you to say yes?" You walk in knowing their objection, and they walk in having already heard your idea once.
The real decision often gets finalized after the meeting, in the recap. Whoever writes it frames what everyone remembers agreeing to. Send it within an hour: "Quick recap: we agreed to [decision]. [Name] owns [task] by [date]. Flag anything I missed by end of day."
Your 10-minute rule
In your next meeting with four or more people, stay silent for the first 10 minutes. On a notepad, draw three columns: who people look at, what that person seems worried about, and whether the room is exploring or deciding.
At minute 10, make one contribution, aimed at the person in column one and framed around their worry. A typical page might read, "Maya. Worried about the vendor deadline. Still exploring." That tells you to offer your idea as an option that protects the deadline, aimed at Maya.
After the meeting, write one line about whether it landed and why. Do this once before Friday.
Until next time, Future Leader
