Latest / The Science of Leading / Why Brilliant Hires Still Become Bad Teams

Transcript

Why Brilliant Hires Still Become Bad Teams · The Science of Leading

• 0:00
  Welcome to the show-Edwin, I want to start with a sentence that tends
• 0:04
  to make leaders a little uneasy: five brilliant hires can still give you
• 0:09
  a terrible team.
• 0:09
  They can, and usually for reasons that have nothing to
• 0:13
  do with talent.
• 0:14
  Talent doesn't coordinate itself.
• 0:17
  Leaders still fall in love with individual brilliance-the standout CV,
• 0:22
  the exceptional engineer, the high-performing salesperson-and then
• 0:22
  they're
• 0:26
  surprised when the group stalls.
• 0:28
  But teams tend to fail in quieter ways: unclear roles,
• 0:32
  messy handoffs, no clarity on who decides,
• 0:35
  and people not feeling safe enough to say,
• 0:37
  "this isn't working.""Talent doesn't coordinate itself" is... annoyingly
• 0:42
  accurate.
• 0:43
  Because I think a lot of founders still have this sort of movie version
• 0:46
  of team-building.
• 0:47
  You assemble a group of high performers,
• 0:49
  put them in a room, and somehow everything just clicks.
• 0:49
  Yes,
• 0:53
  and then in reality they spend most of their time trying to figure out
• 0:57
  who owns what.
• 0:58
  OAD points to something important here-hiring isn't just about individual
• 1:03
  strength.
• 1:04
  It's about how someone's way of working fits the role,
• 1:07
  the team, and the environment.
• 1:09
  Performance is contextual.
• 1:11
  A strong hire in the wrong structure can look average very quickly.
• 1:11
  Let's
• 1:16
  make that concrete.
• 1:17
  Say you've got a startup that hires a great product lead,
• 1:19
  a strong engineering manager, a high-performing marketer,
• 1:22
  a sought-after data person, and an experienced operations lead.
• 1:25
  On paper, that's a dream team.
• 1:27
  Where does it break?
• 1:27
  Usually very early.
• 1:30
  Product assumes they own prioritization.
• 1:33
  Engineering assumes they control feasibility and timing.
• 1:36
  Marketing builds plans on a roadmap that isn't stable.
• 1:40
  Data is waiting for someone to define success.
• 1:43
  Operations is dealing with the fallout.
• 1:46
  And then add one more factor-conflict isn't handled directly.
• 1:51
  So instead of clear decisions,
• 1:53
  you get more messages, more meetings,
• 1:55
  more alignment conversations, and less progress.
• 1:55
  So it's not a talent
• 1:58
  issue at all.
• 1:59
  It's more like five capable people arriving at the same intersection
• 2:03
  with no traffic rules.
• 2:03
  That's a good way to put it.
• 2:06
  Everyone can be competent and still collide.
• 2:08
  Leaders often see that friction and think they need more alignment.
• 2:12
  What they actually need is better design.
• 2:15
  Alignment isn't more meetings.
• 2:17
  It's clear decision rights, defined handoffs,
• 2:20
  and expectations for how disagreement gets surfaced early.
• 2:20
  And yet the
• 2:24
  default reaction is always more meetings.
• 2:26
  The team is confused, so now there's a Monday sync,
• 2:29
  a Thursday check-in, a cross-functional update,
• 2:31
  and maybe a retrospective because everyone's already exhausted.
• 2:31
  Meetings
• 2:36
  can become a way to avoid structural decisions.
• 2:39
  Defining ownership has consequences.
• 2:41
  If I say you're the decision-maker,
• 2:44
  I have to accept not being the decision-maker.
• 2:46
  If we define what "done" means,
• 2:49
  we lose the ability to hide behind ambiguity.
• 2:52
  Structure makes performance visible,
• 2:54
  and that can feel uncomfortable.
• 2:54
  So when someone says,
• 2:58
  "my team isn't clicking," what you're really hearing is something more
• 3:01
  specific.
• 3:01
  Roles might be unclear, handoffs might be breaking,
• 3:05
  decision-making isn't defined,
• 3:07
  and people don't feel safe calling that out.
• 3:07
  Exactly.
• 3:10
  "Not clicking" sounds like chemistry,
• 3:13
  but it's usually architecture.
• 3:15
  And that matters because chemistry feels intangible.
• 3:18
  Architecture can be improved.
• 3:18
  So if chemistry isn't the answer,
• 3:23
  what actually helps?
• 3:24
  If someone's listening to this and their team feels slow or heavy,
• 3:27
  where do they start?
• 3:27
  Start with fundamentals.
• 3:30
  Shared purpose, role clarity, trust,
• 3:32
  psychological safety, and accountability.
• 3:34
  Shared purpose means the team can clearly explain what they're trying
• 3:38
  to achieve and why.
• 3:39
  Role clarity means people understand their responsibilities and decision
• 3:44
  boundaries.
• 3:44
  Trust means people follow through.
• 3:46
  Psychological safety means people can raise risks or admit mistakes without
• 3:51
  social cost.
• 3:52
  And accountability means commitments are visible and actually met.
• 3:52
  Two
• 3:57
  of those stand out to me-interfaces and social cost.
• 4:00
  Because work doesn't usually break inside teams,
• 4:02
  it breaks between them.
• 4:03
  And the social cost part... that's where people hesitate.
• 4:07
  If I say the timeline is unrealistic,
• 4:09
  am I now "difficult"?That's where most friction lives-in the seams.
• 4:14
  A practical fix is to define decision roles clearly.
• 4:18
  Not in a complex framework, just plainly.
• 4:21
  Who recommends, who decides, who contributes,
• 4:24
  who executes.
• 4:25
  Even simple clarity like that removes a surprising amount of friction.
• 4:25
  And
• 4:30
  it probably saves a lot of time too.
• 4:32
  Instead of six people sitting in a meeting trying to figure out what
• 4:35
  should have been clear already.
• 4:35
  Exactly.
• 4:37
  Teams often spend significant time compensating for one missing decision
• 4:42
  owner.
• 4:42
  Another improvement is reducing unnecessary meetings.
• 4:45
  If a meeting exists because something is unclear,
• 4:48
  fix the underlying issue.
• 4:50
  If it's just status updates, move it to writing.
• 4:53
  Use live time for decisions and trade-offs.
• 4:53
  So not fewer meetings for
• 4:59
  the sake of it, but fewer meetings that exist to patch over structural
• 5:02
  gaps.
• 5:02
  Precisely.
• 5:04
  And one more simple but critical point-define what "done" means.
• 5:09
  That sounds basic, but it's often unclear.
• 5:11
  Does "done" mean designed, approved,
• 5:14
  built, tested, or delivered?
• 5:16
  When people use the same word for different endpoints,
• 5:19
  conflict is inevitable."Done" might be one of the most misleading words
• 5:23
  in the workplace.
• 5:24
  But let me push on psychological safety,
• 5:26
  because that one gets misunderstood.
• 5:28
  Does it just mean being nice?
• 5:28
  No,
• 5:31
  and it's important to be precise here.
• 5:33
  Psychological safety is not about comfort or lowering standards.
• 5:36
  It's about being able to speak honestly without fear of negative consequences.
• 5:41
  Research has shown that strong teams combine high standards with high
• 5:45
  candor.
• 5:45
  People can challenge ideas, admit uncertainty,
• 5:49
  and raise concerns early.
• 5:49
  So it's not about everyone feeling comfortable-it's
• 5:53
  about making sure the truth shows up early,
• 5:55
  before it becomes expensive.
• 5:55
  That's a better way to think about it.
• 5:59
  Honest conversations are often uncomfortable,
• 6:02
  but they're necessary.
• 6:04
  The key is that discomfort doesn't turn into punishment.
• 6:04
  And that connects
• 6:08
  to accountability.
• 6:09
  If people can speak up early, you avoid that situation where everyone
• 6:13
  privately sees the issue but publicly acts like everything is fine.
• 6:13
  Exactly.
• 6:18
  False harmony is costly.
• 6:20
  So instead of trying to boost morale,
• 6:23
  a manager can ask a few clear questions: what are we trying to achieve,
• 6:27
  who decides what, where do handoffs break,
• 6:31
  what does done mean, and what happens when someone raises a problem?
• 6:35
  Those answers reveal more than any motivational speech.
• 6:35
  I like that this
• 6:40
  shifts the focus.
• 6:41
  It's not about finding the perfect team-it's about building a system
• 6:45
  where people can actually perform.
• 6:45
  That's the core idea.
• 6:48
  Team performance isn't something a group either has or doesn't have.
• 6:52
  It's designed-through structure,
• 6:54
  norms, feedback, and the signals leaders send consistently.
• 6:58
  And if leaders focused more on that,
• 7:01
  they would spend less time searching for exceptional individuals and
• 7:05
  more time creating conditions where strong work can happen reliably.
• 7:05
  That's
• 7:10
  a good place to land.
• 7:11
  Not heroes-conditions.