Latest / The Science of Leading / From Gut Feel to Real Data: A Practical Playbook for High-Performing Teams

Transcript

From Gut Feel to Real Data: A Practical Playbook for High-Performing Teams · The Science of Leading

• 0:00
  Welcome back, everyone.
• 0:01
  I'm Claire, and I'm here with my favorite resident sage,
• 0:04
  Edwin Carrington.
• 0:05
  Today we're talking about team performance,
• 0:07
  but not in the "let's do a pep talk and order pizza" way.
• 0:07
  No,
• 0:12
  no pizza required.
• 0:13
  We're going to separate vibes from evidence.
• 0:16
  Because most organizations don't actually have a "team performance" problem.
• 0:20
  They have a measurement problem.
• 0:20
  Let's start right there.
• 0:23
  When you say "team performance," what do you actually mean?
• 0:27
  Because a lot of leaders still default to,
• 0:29
  "Are people working hard enough?"Team performance is simple to say,
• 0:34
  harder to live.
• 0:35
  It's a team's ability to consistently produce the outcomes it's responsible
• 0:39
  for, at an acceptable quality level,
• 0:42
  inside real constraints-time, budget,
• 0:45
  dependencies-without burning people out.
• 0:47
  So outcomes, quality, speed, and sustainability.
• 0:51
  All four.
• 0:51
  So that's different from individual performance reviews,
• 0:56
  which are more, "Is this person doing their job well?" You're asking,
• 1:00
  "Can this whole group actually produce results together?"Exactly.
• 1:04
  You can have a room full of high performers on paper and still have a
• 1:08
  weak team.
• 1:08
  Work gets stuck in handoffs.
• 1:11
  Decisions take forever.
• 1:12
  Conflict just...sits there.
• 1:14
  Ownership is fuzzy so nothing moves.
• 1:17
  That's the gap between individual performance and team performance.
• 1:17
  You
• 1:22
  also make a distinction I really like between team effectiveness,
• 1:25
  team dynamics, and team health.
• 1:27
  Can you break those down in plain language?
• 1:27
  Of course.
• 1:30
  Team effectiveness is, "Do we actually deliver?" So speed,
• 1:34
  quality, reliability of outcomes.
• 1:37
  Team dynamics is, "What does it feel like when we work together?" Communication
• 1:42
  patterns, how we handle conflict,
• 1:44
  how we make decisions.
• 1:45
  Team health is the sustainability layer: engagement,
• 1:49
  trust, morale, workload, psychological safety.
• 1:53
  Are people able to keep doing this without frying?
• 1:53
  So effectiveness is
• 1:58
  results, dynamics is how we interact,
• 2:00
  health is whether we're burning out or building something durable.
• 2:03
  And research from the big players basically says: you can measure all
• 2:06
  three, right?
• 2:06
  You can, and you should.
• 2:09
  The most robust studies on teams tend to land on a similar core: psychological
• 2:15
  safety, dependability, structure and clarity,
• 2:18
  a sense of meaning and impact,
• 2:20
  plus basic health indicators like engagement.
• 2:23
  Those are not fluffy ideas-they show up over and over as predictors of
• 2:28
  whether teams actually deliver.
• 2:28
  Okay,
• 2:31
  so, if the research is pretty clear,
• 2:33
  why do so many leaders still jump to motivation talks,
• 2:36
  new tools, or a reorg when a team slips?
• 2:36
  Because those are visible.
• 2:41
  They feel like action.
• 2:43
  The real drivers of performance are more boring: role clarity,
• 2:47
  decision rights, how work actually flows,
• 2:50
  whether people feel safe surfacing risks early.
• 2:53
  If you're not measuring those,
• 2:55
  you end up doing what I call performance theater-lots of motion,
• 2:58
  little change.
• 2:58
  So let's get practical.
• 3:02
  If I'm an HR leader or a founder in,
• 3:04
  say, a 100-person company, how do I move from theater to evidence without
• 3:08
  turning this into a giant culture project?
• 3:08
  You start with a very simple
• 3:13
  diagnostic.
• 3:14
  Two parts.
• 3:15
  First, a short team health survey: a few questions on psychological safety-"Can
• 3:21
  I speak up?"-dependability, clarity of goals and roles,
• 3:25
  and whether the work feels meaningful.
• 3:27
  Short enough that people actually finish it.
• 3:30
  Second, a handful of hard metrics.
• 3:30
  These are the ones I've seen you use
• 3:35
  again and again.
• 3:36
  Delivery reliability, cycle time,
• 3:38
  decision latency.
• 3:39
  Walk us through those, please?
• 3:39
  Delivery reliability is,
• 3:43
  "Do we do what we said we'd do,
• 3:45
  when we said we'd do it?" It's just the percentage of commitments met.
• 3:49
  Cycle time is, "How long does typical work take from start to done?"
• 3:55
  Decision latency is, "How long do important decisions sit unresolved?"
• 4:00
  Add a simple quality signal-defects or rework-and a basic team health
• 4:05
  trend.
• 4:05
  So you're not asking for a dashboard with 40 KPIs.
• 4:08
  You're saying: a short survey,
• 4:10
  plus four or five numbers you can track weekly.
• 4:10
  That's right.
• 4:14
  Consistent and simple beats perfect.
• 4:17
  Once you can see, for example,
• 4:18
  that decision latency is high and psychological safety is low,
• 4:22
  you stop guessing.
• 4:23
  You can say, "We don't need another motivational talk.
• 4:27
  We need clearer decision rights and safer conversations."This is also
• 4:31
  where I see tools like OAD help,
• 4:33
  because they add the behavioral layer.
• 4:35
  You've got the survey and the metrics,
• 4:37
  but you can also see: do we have a decision-averse leadership group?
• 4:41
  Do we have a whole team of people who avoid conflict or hate structure?
• 4:41
  Exactly.
• 4:46
  Behavioral data gives you x‑ray vision on fit.
• 4:50
  You can see whether a manager's natural style clashes with what the role
• 4:54
  and the team actually need.
• 4:56
  You can see collaboration preferences,
• 4:58
  stress responses, decision styles.
• 5:01
  When you layer OAD on top of the metrics,
• 5:04
  it tells you whether the problem is the system,
• 5:07
  the fit, or both.
• 5:07
  And that's the shift you're arguing for: stop blaming
• 5:11
  "the team," start measuring the system they're in-and use data,
• 5:15
  including OAD, to see if you've actually set them up to perform.
• 5:15
  Alright,
• 5:19
  so we've got a clearer picture of what to measure.
• 5:21
  Let's talk about what "good" actually looks like.
• 5:23
  When you walk into a high-performing team,
• 5:26
  what do you notice?
• 5:26
  The first thing is very unglamorous: work moves.
• 5:31
  Decisions don't sit.
• 5:32
  Handoffs don't stall.
• 5:34
  People keep commitments.
• 5:36
  You see dependability-if someone says,
• 5:39
  "I'll have it by Thursday," it usually shows up by Thursday at an acceptable
• 5:43
  quality level.
• 5:43
  There's also a kind of...cleanliness to the way they operate.
• 5:48
  Goals and roles aren't fuzzy.
• 5:49
  People know why the team exists,
• 5:51
  what success looks like, and who owns what slice of it.
• 5:51
  That's structure
• 5:55
  and clarity.
• 5:56
  High-performing teams don't leave ownership to chance.
• 5:59
  They define who decides, who executes,
• 6:02
  what "done" means.
• 6:03
  That reduces friction and conflict before it starts.
• 6:07
  Then there's psychological safety and trust-you'll hear people raise
• 6:11
  uncomfortable truths early, not at the end when everything's on fire.
• 6:11
  So
• 6:16
  you might hear someone say, "Hey,
• 6:17
  we're over-committing this sprint," or,
• 6:20
  "This requirement doesn't make sense," and it's normal,
• 6:22
  not career suicide.
• 6:22
  Exactly.
• 6:25
  And when those issues are raised,
• 6:27
  the system turns them into action.
• 6:29
  That's a key marker.
• 6:31
  In the better studies on team trust,
• 6:33
  high-performing teams aren't "nice"-they're proactive about tension,
• 6:37
  they keep each other in the loop,
• 6:39
  they resolve issues before they rot.
• 6:39
  You've also talked about the human
• 6:43
  capability side-curiosity, resilience,
• 6:46
  connected teaming, different ways of thinking.
• 6:48
  How do those fit into this picture?
• 6:48
  Those capabilities are like fuel.
• 6:53
  Curiosity means people question old assumptions instead of just pushing
• 6:57
  harder.
• 6:57
  Connected teaming is the ability to coordinate across functions.
• 7:02
  Resilience keeps the team steady when things change.
• 7:05
  Divergent thinking lets people see multiple options instead of defaulting
• 7:10
  to the obvious one.
• 7:11
  But those only show up consistently when the basics-clarity,
• 7:15
  trust, governance-are in place.
• 7:15
  So,
• 7:18
  human capabilities are powerful,
• 7:20
  but they're amplified or suppressed by the manager and the system.
• 7:23
  A strong manager with clear decision rules and a good operating rhythm
• 7:27
  kind of "turns up the volume" on those capabilities.
• 7:27
  That's right.
• 7:31
  A good manager makes it safe to be curious,
• 7:34
  uses structure so divergent ideas actually get tested,
• 7:38
  and protects the team's resilience by managing workload.
• 7:42
  And governance-who decides what,
• 7:45
  how fast-is what stops cross-functional teams from drowning in ambiguity.
• 7:45
  Let's
• 7:51
  make this really concrete.
• 7:52
  If I'm looking across my organization,
• 7:54
  what observable traits tell me,
• 7:56
  "This is one of our best teams"?You'd see: they hit the majority of their
• 8:01
  commitments without drama.
• 8:02
  Their cycle times are shorter than peers.
• 8:05
  Decisions in their world move quickly.
• 8:07
  When you ask them about goals and roles,
• 8:10
  they give consistent answers.
• 8:12
  In meetings, you hear disagreement early and resolution by the end,
• 8:15
  not the same debate every week.
• 8:17
  And their engagement and turnover look better over time,
• 8:20
  not worse.
• 8:20
  And if you compare that to a struggling team,
• 8:24
  you'd probably see slow decisions,
• 8:25
  vague ownership, a lot of rework,
• 8:28
  and people quietly checking out.
• 8:28
  Exactly.
• 8:30
  The differences sound simple-dependability,
• 8:33
  clarity, safety, trust-but they add up.
• 8:37
  And here's where OAD becomes very practical for HR and founders.
• 8:41
  Once you know which teams are your best,
• 8:43
  you can look under the hood behaviorally.
• 8:43
  Yeah,
• 8:47
  you can ask: what's actually true about the people and the roles on those
• 8:50
  teams?
• 8:51
  Do we have managers whose natural style fits the role?
• 8:54
  Do we have the right mix of drivers-some people who love structure,
• 8:58
  some who challenge it, some who bring calm under pressure?
• 8:58
  And you can
• 9:02
  compare that to struggling teams.
• 9:04
  Maybe your weakest team has a manager whose natural tendencies are highly
• 9:08
  controlling in a role that needs delegation,
• 9:10
  or very conflict-avoidant in a space that needs hard trade-offs weekly.
• 9:14
  With OAD, you're not guessing.
• 9:17
  You see where role demands and natural style are misaligned.
• 9:17
  I've seen
• 9:22
  companies use it to staff project teams,
• 9:24
  too-putting the naturally detail-oriented folks in critical handoff roles,
• 9:28
  pairing them with people who push decisions forward,
• 9:31
  and avoiding those teams where everyone wants to brainstorm and nobody
• 9:34
  wants to finish.
• 9:34
  That's right.
• 9:36
  You're not looking for "better people." You're designing better combinations
• 9:41
  and clearer conditions.
• 9:42
  The research tells you which conditions matter.
• 9:45
  Your metrics tell you which teams are actually performing.
• 9:48
  Behavioral data from OAD helps you replicate the wins and spot manager
• 9:53
  risk early, instead of waiting for burnout or attrition to show up in
• 9:57
  a dashboard.
• 9:57
  So high-performing teams are not a mystery.
• 10:01
  They're a pattern you can observe,
• 10:03
  measure, and then intentionally recreate-with the right structure,
• 10:06
  the right manager habits, and the right behavioral mix.
• 10:06
  Alright,
• 10:11
  let's get into the "do this next month" part.
• 10:13
  You talk a lot about running boring,
• 10:15
  powerful experiments instead of announcing big initiatives.
• 10:18
  What does that loop actually look like?
• 10:18
  The loop is very simple.
• 10:22
  One: pick a performance gap-late delivery,
• 10:26
  constant rework, slow decisions,
• 10:29
  rising burnout risk.
• 10:30
  Two: tie it to one main driver-clarity,
• 10:35
  trust, decisions, or communication.
• 10:38
  Three: define one or two specific behavior changes.
• 10:42
  Four: track one leading and one lagging metric for 2-4 weeks.
• 10:47
  That's it.
• 10:47
  Let's walk through examples,
• 10:50
  because I know people listening are already thinking,
• 10:52
  "Okay, but what does that actually look like on Monday?" Start with decisions,
• 10:57
  since that's such a common pain point.
• 10:57
  Decision-latency experiment.
• 11:01
  Performance gap: important decisions take too long.
• 11:05
  Driver: decision-making and clarity of ownership.
• 11:09
  Behavior change: every decision above a certain impact level has a named
• 11:14
  decision owner and a deadline-say 48 hours-to make the call once input
• 11:19
  is gathered.
• 11:19
  Metrics: leading indicator is median decision latency,
• 11:24
  lagging is delivery reliability on key projects.
• 11:27
  Run that for three weeks and see if work moves faster.
• 11:27
  So really tangible:
• 11:32
  "I own this decision, I'll make it by Thursday," instead of decisions
• 11:35
  floating in email threads for weeks.
• 11:35
  Exactly.
• 11:38
  Another one is a role-clarity experiment.
• 11:41
  Gap: work falls through the cracks and people step on each other's toes.
• 11:46
  Driver: clarity.
• 11:48
  Behavior change: for one project,
• 11:51
  you create a simple RACI for key deliverables and a one-line "definition
• 11:56
  of done" for each.
• 11:57
  Metrics: leading indicator is the number of unclear ownership escalations;
• 12:03
  lagging is rework rate or missed handoffs.
• 12:03
  What about communication,
• 12:08
  especially with hybrid or distributed teams?
• 12:08
  Async-communication experiment.
• 12:13
  Gap: people feel out of the loop,
• 12:15
  meetings are bloated, and surprises keep popping up.
• 12:18
  Driver: communication.
• 12:21
  Behavior change: you standardize a daily or twice-weekly async update
• 12:27
  with a simple template-what I completed,
• 12:29
  what's next, what's blocked, what decisions I need.
• 12:33
  Metrics: leading is the number of blockers identified early; lagging
• 12:39
  could be cycle time or the frequency of last-minute fire drills.
• 12:39
  You've
• 12:43
  mentioned light governance around these experiments,
• 12:45
  so it doesn't become bureaucracy.
• 12:47
  What does "just enough" governance look like?
• 12:47
  Three things.
• 12:50
  One owner per experiment-often the manager or a project lead.
• 12:55
  A short weekly review where the team looks at the one leading and one
• 12:59
  lagging metric and decides whether to continue,
• 13:02
  adjust, or stop.
• 13:04
  And an escalation path-if a blocker sits for more than,
• 13:08
  say, 48 hours, it automatically escalates to a named leader.
• 13:12
  At the end of 2-4 weeks, you run a quick retrospective: what helped,
• 13:17
  what didn't, what do we keep.
• 13:17
  And I want to bring OAD back in here,
• 13:21
  because it can even help you choose which experiment to run,
• 13:24
  right?
• 13:25
  If the behavioral data shows your manager is naturally conflict-avoidant,
• 13:29
  maybe you don't start with a trust-and-conflict experiment that depends
• 13:33
  entirely on their personal comfort level.
• 13:33
  Exactly.
• 13:36
  OAD can show you, for example,
• 13:39
  that your leadership trio is heavily cautious and consensus-oriented.
• 13:43
  In that case, a decision-speed experiment might need more structural
• 13:47
  support-clear rules and timeboxes-rather than just asking everyone to
• 13:51
  "decide faster." Or if your team skews highly independent and low on structure,
• 13:57
  a role-clarity experiment will feel uncomfortable at first,
• 14:00
  and you can plan for that.
• 14:00
  So behavioral data lets you de‑risk these small
• 14:05
  experiments.
• 14:06
  You're not surprised when a particular change feels hard for a particular
• 14:10
  manager, because you already know their natural style and stress responses.
• 14:10
  That's
• 14:15
  right.
• 14:15
  Instead of saying, "They're resisting," you can say,
• 14:18
  "This is a stretch for how they're wired-how do we support it?" That's
• 14:23
  a very different conversation.
• 14:24
  And when you combine that with simple metrics-delivery reliability,
• 14:29
  cycle time, decision latency, rework,
• 14:32
  team health trends-you can see,
• 14:34
  within a month, whether a change is actually working.
• 14:34
  I like how all of
• 14:38
  this avoids performance theater.
• 14:40
  No giant culture initiative, no vague promises.
• 14:43
  Just: diagnose, pick one driver,
• 14:46
  change one or two behaviors, measure,
• 14:48
  repeat.
• 14:48
  Exactly.
• 14:50
  It's not glamorous, but it's how you build a high-performing environment
• 14:55
  over time.
• 14:55
  You're treating team performance like an operating problem,
• 14:58
  not a motivational one.
• 14:58
  Alright,
• 15:01
  let's land this.
• 15:02
  For everyone listening-HR leaders,
• 15:04
  founders, people managers-if you want to move from gut feel to evidence
• 15:08
  in how you hire, design teams, and lead,
• 15:11
  you need both sides: simple performance metrics and real insight into
• 15:15
  how your people naturally work.
• 15:15
  And that's where I'd invite you to try
• 15:19
  OAD.
• 15:20
  Use it to see role fit, decision styles,
• 15:24
  collaboration preferences, and manager risk before it shows up as burnout
• 15:28
  or attrition.
• 15:29
  Then pair that with the small experiments we've talked about today.
• 15:29
  If
• 15:34
  you want to move from gut feel to evidence in how you hire,
• 15:37
  design teams, and lead, test OAD for free at OAD.
• 15:37
  ai.
• 15:41
  No drama, no performance theater-just practical data you can use next
• 15:45
  month.
• 15:45
  Claire, as always, a pleasure.
• 15:45
  Same here,
• 15:48
  Edwin.
• 15:48
  And thanks to all of you for listening.
• 15:50
  We'll be back with more ways to build teams that actually work.
• 15:53
  Take care, everyone.