Team success is 90% structure, not in-the-moment coaching

Executive overview

Most leaders spend their time coaching teams through daily challenges — but research shows that real-time coaching drives only 10% of team effectiveness. The other 90% is determined before the team ever gets going.

Structure — who's on the team, what they're working toward, how they'll operate — is the game itself. Coaching is just how you play it.

The 60-30-10 rule captures this: 60% of team performance is set by structure (composition, goals, tasks, norms), 30% by the launch meeting, and 10% by ongoing coaching. Most leaders have this almost exactly backwards.

Why structure beats coaching every time

• Well-structured teams benefit from good coaching and survive bad coaching with little damage.
• Poorly-structured teams are barely helped by good coaching — and devastated by bad coaching.
• Trying to coach your way out of a structural problem is like finding the optimal strategy for a rigged casino game: the house still wins.
• Fix structural problems first; coaching amplifies structure, it doesn't replace it.

Goals: the "California tomorrow" problem

• Vague goals — "delight the customer", "deliver on time" — give teams almost no basis for coordinating action.
• Goals must be specific enough that team members can stay aligned even when they're not talking to each other.
• Under-specification is the norm; leaders consistently assume people know more than they do.
• Repeating the goal — its destination, its importance, and what makes it hard — is a core leadership function throughout the life of the team, not just at kickoff.

Tasks: making progress visible

• A well-designed task is a whole piece of work: visible from start to finish, with clear outcomes and impact on an end user.
• Tasks that disappear "up the chain" with no feedback are inherently demotivating — teams lose the sense that their work matters.
• Break large tasks into smaller visible units; "read a paper" is invisible, "write a three-sentence summary of how this paper applies to our project" is not.
• Surfacing small wins — pointing them out explicitly — keeps momentum and is one of the highest-leverage uses of a leader's coaching time.

Composition: deep diversity over surface diversity

• Surface-level diversity (race, gender, age) matters largely because it's a proxy for deeper differences in knowledge, skills, and perspectives.
• Deep-level diversity — genuinely complementary expertise and viewpoints — is what creates the potential for synergy.
• Most teams are composed by availability ("who can I get?") or social comfort ("who do I get along with?"), not by what the task actually requires.
• Homophily — birds of a feather — is the default pull; if everyone on the team looks, thinks, and talks the same, that's a warning sign.
• Start from the goal and work backwards: what knowledge, skills, and perspectives does this specific task demand?

Norms: invisible rules that run the team

• Norms are what feels normal in a group — who speaks, who's quiet, how decisions get made, how fast emails get answered.
• They emerge fast and stick hard; wherever you sit in the first meeting becomes your seat for the rest of the project.
• The most consequential norms are about communication channels, information storage, decision-making, and whether it's safe to disagree or make mistakes.
• Leaders must actively shape norms rather than let them emerge by accident.

Launching well: the 30%

• Most leaders skip clearly articulating the goal at launch — they assume everyone knows why they're there.
• At the first meeting: state the goal, explain why it matters, name what will be hard, and invite questions.
• Explicitly agree on communication channels and information storage; unspoken assumptions cause conflict and exclusion.
• Set a midpoint check-in at launch — exactly halfway to the deadline. Teams are uniquely open to change at the midpoint when they feel the time pressure; use that window to revisit goals and norms.