Great Teams Build Collective Confidence Before Winning

Why Collective Confidence Beats Optimism

Martin draws a sharp distinction between optimism and collective confidence. Optimism, he says, “is really just a forecast of the future.” Collective confidence is different because it’s grounded in evidence. It’s “a conclusion that a team draws” after looking at the capabilities around the table and deciding those capabilities can produce a better result.

That distinction matters because difficult work rarely offers certainty. Leaders can’t promise that a strategy will succeed, but they can create conditions in which people have reason to believe the team has the capacity to respond. As Martin puts it, “harder things require more interdependence.” The confidence multiplier emerges when team members see capabilities around them that they don’t possess themselves.

That’s one reason Martin believes confidence can precede performance rather than merely follow it. Research, he says, shows collective confidence to be “one of the strongest predictors of future team performance.” His interviews with high-performing teams reinforced the point: leaders were routinely doing “small daily things” that raised the group’s belief in its ability to succeed.

Rules of Engagement and the Right Amount of Structure

Ambiguity is expensive. When nobody knows who owns a decision, how conflict gets handled, or what behavior is acceptable, energy leaks into guesswork. Martin’s remedy is explicit “rules of engagement”—clear agreements that reduce ambiguity. The best teams, he says, turn their processes into “the engine that allows confidence to turn into consistent, repeatable performance.”

Structure matters more as work gets harder. As Martin puts it, “harder things require more interdependence.” Simple tasks can be handled by a strong individual; consequential work requires people with different skills to rely on one another. Confidence grows when team members see capabilities around them that they don’t possess themselves.

The balance is delicate. Martin points to West Point cadets who organized elementary-school recess with lines, stations and tightly timed activities—overengineering what experienced teachers handled with three rules: stay out of the parking lot, don’t chase balls over the fence, don’t hit anybody. Too little structure creates confusion; too much squeezes out judgment. Establish enough clarity that people know the boundaries, then give them room to act.

Shared Leadership, Psychological Safety and Recognition

Martin cites the conductorless Orpheus Chamber Orchestra as an example. Its musicians still need tempo, cadence and coordination, but leadership emerges according to the piece being performed and the expertise required at that moment. “Everyone has the potential to be the leader of the group,” he says.

Shared leadership does not absolve the formal leader. It makes the leader’s job more foundational. Martin says people need clear answers to basic questions: Why is the world better with us in it? What is our mission now? How do we get work done? How does the enterprise succeed economically? What is the leader’s promise to the people doing the work? When those questions remain fuzzy, empowerment can become abandonment.

That clarity is inseparable from psychological safety. Martin warns leaders not to assimilate newcomers too quickly. Rather than immediately teaching them “how we do things,” he recommends preserving their outsider perspective long enough for them to identify assumptions insiders have stopped noticing. “Give them 90 days to be our biggest critic,” he says.

The same logic applies to dissent. An open-door policy has little value if employees never see disagreement rewarded. Culture, Martin says, is learned through modeling. Recognition then becomes a cultural tool, not merely a reward for results. Leaders should also recognize the behaviors they want repeated: a courageous question, useful dissent, collaboration or curiosity.

Building Belief Through Progress, Failure and Humility

Confidence grows from progress, so Martin favors a “Goldilocks” approach when someone takes on something difficult: break the challenge into attainable early goals, then make the wins visible. “People benefit from low-stakes wins,” he says. Small successes, reinforced with timely positive feedback, create evidence. Evidence creates belief. And belief creates the willingness to take on something harder.

The same principle can transform failure. Martin argues that many failures feel destructive because teams never agreed on what success meant. In innovation, an experiment that disproves an assumption may still be useful. The central question becomes: were we trying to be perfect, or were we trying to learn?

Perhaps Martin’s most counterintuitive point is that leader humility can increase rather than diminish confidence. A leader who says “I don’t have all the answers” may appear to surrender authority. Martin sees something different: “the allocation of authority.” The admission invites other people to bring their expertise forward and places responsibility for finding the best idea on the group.

Asked what single intervention he would make in a typical organization, Martin points to “borrowed brilliance”—showing people examples of teams like theirs that have accomplished something significant. People need evidence that hard things are possible. His broader prescription is strikingly practical: “we need more inspiration in the world.” Not empty encouragement, but evidence-based inspiration.