Latest / The Science of Leading / Team Dynamics Assessments: A Practical Playbook for Better Team Performance

Transcript

Team Dynamics Assessments: A Practical Playbook for Better Team Performance · The Science of Leading

• 0:00
  Welcome back to The Science of Leading.
• 0:01
  I'm Claire, and I'm here with Edwin Carrington.
• 0:04
  Today we're getting really practical about team dynamics assessments-what
• 0:07
  they actually are, and how to make them something more than a colorful
• 0:11
  report that everybody forgets about.
• 0:11
  Glad to be here,
• 0:14
  Claire.
• 0:15
  And I like how you framed that,
• 0:16
  because most assessments die in a folder somewhere.
• 0:16
  Yeah.
• 0:20
  So let's start at the very top.
• 0:21
  You use this distinction a lot: team performance versus team dynamics.
• 0:26
  Can you unpack that in plain language?
• 0:26
  Sure.
• 0:29
  Performance is what the team delivers-output,
• 0:32
  quality, speed, customer outcomes.
• 0:35
  Dynamics are how they produce that performance-how they communicate,
• 0:40
  decide, handle conflict, and correct course when things go wrong.
• 0:44
  Performance is the scoreboard.
• 0:46
  Dynamics are the operating system under the hood.
• 0:46
  And that ties to the
• 0:50
  research, right?
• 0:51
  Google's work on effective teams,
• 0:52
  Project Aristotle... they basically found that the environment matters
• 0:56
  more than having a few superstars.
• 0:56
  Exactly.
• 0:59
  Google kept seeing the same conditions on strong teams: psychological
• 1:04
  safety, dependability, structure and clarity,
• 1:07
  a sense of meaning and impact.
• 1:09
  It wasn't "we hired the smartest people." It was "we built a system where
• 1:14
  smart people can actually work together." And Gallup's engagement research
• 1:19
  points the same way: when the environment is strong,
• 1:22
  you see better profitability, productivity,
• 1:24
  and lower turnover.
• 1:24
  So when we say "team dynamics assessment," we're not
• 1:28
  talking about a vibe check.
• 1:28
  No.
• 1:31
  A team dynamics assessment is a structured way to measure how the team
• 1:35
  functions day to day, not just what it produces.
• 1:38
  Usually that's a questionnaire plus a process.
• 1:42
  People respond to statements like,
• 1:44
  "We can raise concerns without negative consequences," or "Decisions
• 1:49
  are clear and stick," and then you turn those responses into a practical
• 1:54
  map of how the team is actually operating.
• 1:54
  Let's list the core dimensions,
• 1:58
  so folks can sanity-check what they're using.
• 2:00
  I'm thinking: trust, psychological safety,
• 2:03
  clarity, decision-making, accountability,
• 2:06
  communication... what else would you add?
• 2:06
  That's the heart of it.
• 2:11
  I'd bundle a few more inside those: cohesion and trust-do people feel
• 2:16
  connected enough to coordinate fast?
• 2:18
  Role clarity-do they know what "good" looks like and who owns what?
• 2:22
  And conflict patterns-do disagreements get resolved or just recycled?
• 2:22
  And
• 2:28
  you like this phrase, "making the operating system visible." What do you
• 2:31
  mean by that?
• 2:31
  Most teams fail not because they lack talent,
• 2:35
  but because they lack a shared operating system.
• 2:38
  How decisions get made, how conflict gets handled,
• 2:42
  how information moves, whether it's safe to tell the truth before something
• 2:46
  breaks.
• 2:47
  A good assessment makes that system visible.
• 2:50
  You're diagnosing the system, not blaming individuals or personalities.
• 2:50
  So,
• 2:55
  if I'm a skeptical line manager listening right now,
• 2:58
  I might be thinking, "Okay, psychological safety sounds soft.
• 3:01
  How does that actually tie to risk?"Amy Edmondson's work is helpful here.
• 3:06
  Psychological safety is not "being nice." It's a shared belief that you
• 3:10
  can take interpersonal risks-speak up,
• 3:13
  admit a mistake, challenge an idea-without being punished.
• 3:17
  When that's weak, you get silent risk: people sit on concerns until the
• 3:22
  damage is expensive.
• 3:24
  Problems surface late, decisions drag out,
• 3:27
  high performers carry the load until they leave.
• 3:30
  Those are hard performance outcomes,
• 3:33
  not moods.
• 3:33
  So the assessment is really an early warning system.
• 3:37
  Performance might look fine... right up until it isn't.
• 3:40
  But the dynamics-the safety, the clarity,
• 3:43
  the accountability-those frictions show up earlier.
• 3:43
  That's right.
• 3:47
  The assessment helps you answer three questions: what do we protect,
• 3:52
  what do we fix, and what do we stop pretending is "just personality"
• 3:56
  when it's actually a system problem.
• 3:56
  Okay,
• 3:59
  so we've defined the why and the what.
• 4:01
  Next we'll get into how to actually design and run one of these without
• 4:04
  turning it into a blame game or a survey nobody trusts.
• 4:04
  Alright,
• 4:08
  let's get practical.
• 4:09
  If I'm HR, or I'm a founder, and I wanna run a team dynamics assessment
• 4:13
  that people actually believe in,
• 4:14
  where do I start?
• 4:14
  Start before the survey.
• 4:17
  Step one is defining business goals.
• 4:20
  What are you trying to improve that an operations-minded leader would
• 4:23
  care about?
• 4:24
  For example: reduce cross-functional friction that's slowing launches,
• 4:29
  improve decision speed without sacrificing quality,
• 4:32
  reduce rework from unclear ownership,
• 4:35
  or stabilize a team after a re-org.
• 4:35
  So not "team building."Exactly.
• 4:41
  If the goal is "team building," you get fuzzy,
• 4:44
  feel-good outcomes.
• 4:46
  Tie it to speed, quality, customer escalations-something concrete.
• 4:50
  Then step two is picking outcomes and baselines.
• 4:54
  Decide what you'll track alongside the assessment: cycle time,
• 4:58
  defect rates, escalation volume,
• 5:00
  regrettable turnover.
• 5:01
  If you don't set a baseline date,
• 5:03
  you can't credibly say you improved anything.
• 5:03
  Okay,
• 5:07
  then tools.
• 5:08
  There are a million surveys out there.
• 5:10
  How do you choose one without getting lost in marketing?
• 5:10
  You look for
• 5:14
  three things.
• 5:15
  One: it measures behaviors and conditions,
• 5:18
  not moods.
• 5:19
  Items like, "We raise issues early," "Handoffs are clear," "Commitments
• 5:24
  are followed through." Two: it produces team-level reporting with safe
• 5:29
  aggregation, not individual scorecards.
• 5:32
  And three: the output is actionable-clear strengths,
• 5:36
  constraints, and suggested moves,
• 5:38
  not just labels or color wheels.
• 5:38
  And what about privacy and anonymity?
• 5:42
  Because as soon as people think they can be identified,
• 5:45
  they go into polite-lie mode.
• 5:45
  Yes.
• 5:48
  You need to lock that in up front.
• 5:50
  Minimum standards: results reported at team level,
• 5:53
  an anonymity threshold for any subgroup views,
• 5:56
  and clear rules on who sees what.
• 5:58
  You tell people explicitly, "Your individual responses won't be shown.
• 6:03
  We'll only look at patterns, and here's exactly who will see the team
• 6:07
  report." If you can't explain it in a paragraph,
• 6:10
  it's too complicated.
• 6:10
  Let's talk onboarding language.
• 6:14
  What should leaders actually say when they roll this out?
• 6:14
  Something like:
• 6:19
  "We're doing this now because launches are slower than they should be,
• 6:22
  and I don't think that's a talent problem,
• 6:24
  I think it's a system problem.
• 6:26
  The survey will take about 10 minutes.
• 6:28
  It's anonymous at the individual level.
• 6:31
  HR and I will see team-level patterns,
• 6:34
  not who said what.
• 6:35
  We'll share the results with you and agree on 2-3 changes we'll actually
• 6:39
  make." Simple, concrete, time-bound.
• 6:39
  You also like including a little open
• 6:44
  text, right?
• 6:45
  But not so much that you create essay fatigue.
• 6:45
  Two to four prompts is
• 6:49
  plenty.
• 6:49
  For example: "What slows this team down most?" "What should we do more
• 6:54
  of, less of, start, stop?" "Where do you feel least clear?" And you tell
• 7:00
  people up front: we'll use these as themes,
• 7:02
  not as quotes pinned to individuals.
• 7:02
  What about demographics and behavior
• 7:06
  tools like OAD?
• 7:07
  Leaders love slicing the data,
• 7:09
  but that's where trust can evaporate.
• 7:09
  Right.
• 7:12
  Optional demographics are fine if you follow two rules: don't collect
• 7:17
  anything you won't actually use,
• 7:19
  and don't break anonymity.
• 7:20
  So no tiny subgroups.
• 7:23
  And personality or behavioral tools,
• 7:25
  like an OAD-style survey, can be powerful context-helping you understand
• 7:31
  how people naturally communicate or respond under pressure.
• 7:34
  But they must never be used as a hunt for "who's the problem." You're
• 7:39
  looking for patterns like, "We've staffed a highly detail-oriented team
• 7:43
  into a role that needs fast, cross-functional decision-making," not,
• 7:47
  "This one person is difficult."So clean data collection is: clear purpose,
• 7:52
  short behavior-focused questionnaire,
• 7:54
  a couple of open questions, strong anonymity rules,
• 7:57
  and no segmentation that lets people play "guess who."Exactly.
• 8:01
  Do that, and you've earned the right to look at the results.
• 8:05
  Skip it, and you're just measuring how scared people are.
• 8:05
  Alright,
• 8:09
  the survey's done, the dashboard is pretty... now what?
• 8:11
  How do we go from data to decisions?
• 8:11
  You start by looking for patterns,
• 8:15
  not perfection.
• 8:16
  First cut: team-level averages across dimensions like trust,
• 8:21
  clarity, accountability, communication,
• 8:24
  conflict.
• 8:25
  Identify top strengths, biggest constraints,
• 8:28
  and a few risks to watch.
• 8:28
  Can you define those three buckets quickly?
• 8:28
  Strengths
• 8:34
  are high scores with low variance-stable assets you should protect.
• 8:38
  Constraints are low scores in areas that directly slow execution-those
• 8:43
  are your bottlenecks.
• 8:44
  Risks may not be the absolute lowest scores,
• 8:47
  but they're things like psychological safety,
• 8:49
  decision clarity, accountability,
• 8:51
  conflict avoidance-conditions that,
• 8:54
  if weak, tend to show up in later performance problems.
• 8:54
  And then there's
• 8:58
  the fun one: leader-team gaps.
• 9:00
  Where the manager thinks something's great and the team is like,
• 9:03
  "Uh, no."Yes.
• 9:05
  When leaders rate an area higher than the team,
• 9:08
  that often means they're seeing intent and the team is feeling impact.
• 9:12
  Use that as a hypothesis, not a verdict.
• 9:15
  In the results meeting, you might say,
• 9:17
  "The data shows I think our decision-making is clearer than you do.
• 9:21
  What are you experiencing that I'm not seeing?" And then you listen.
• 9:21
  You
• 9:26
  also look for high-variance items,
• 9:27
  right?
• 9:28
  Not just low scores.
• 9:28
  Exactly.
• 9:30
  High variance means inconsistent norms.
• 9:33
  Some people think something is fine,
• 9:36
  others think it's broken.
• 9:37
  That often points to differences by location,
• 9:40
  tenure, or role.
• 9:41
  Instead of saying, "Who's wrong?",
• 9:43
  you ask, "What's happening that makes people experience this so
• 9:43
  differently?"Okay,
• 9:49
  now prioritization.
• 9:50
  Because this is where leaders blow it-they pick ten focus areas.
• 9:50
  Most
• 9:55
  teams can only work on two or three things at once.
• 9:57
  Use a simple filter: impact on performance,
• 10:01
  leverage across workflows, feasibility in 30-60 days,
• 10:05
  and whether progress here will build trust in the process.
• 10:08
  Typical top priorities: decision rights,
• 10:11
  role clarity, feedback and conflict hygiene,
• 10:14
  and basic accountability routines.
• 10:14
  Give me a concrete example.
• 10:19
  Let's say the data shows slow decisions and lots of revisiting.
• 10:19
  You'd
• 10:23
  frame it like this: "Finding: Our decisions are unclear and often revisited.
• 10:27
  Operational cost: delays, rework,
• 10:30
  and escalation loops.
• 10:32
  Behavior change: one named decision owner per decision,
• 10:35
  with a deadline.
• 10:36
  Mechanism: we'll keep a simple decision log and add a 15-minute weekly
• 10:41
  review.
• 10:42
  Metric: time from issue raised to decision made." That connects the
• 10:42
  intervention
• 10:48
  directly to cycle time and rework.
• 10:48
  I like how boring that is.
• 10:52
  It's not a workshop; it's a new habit.
• 10:52
  Exactly.
• 10:55
  Other boring but powerful moves: setting meeting norms where every decision
• 11:00
  has a written owner and next step; creating a one-page ownership map for
• 11:04
  cross-functional work; adding a 10-15 minute commitments review to the
• 11:09
  weekly meeting; agreeing what "good conflict" looks like and how to escalate
• 11:13
  when you're stuck.
• 11:13
  Alright, implementation plan.
• 11:16
  Walk us through a simple version leaders can copy.
• 11:16
  Step one: leader-led
• 11:21
  results session.
• 11:22
  You bring the team together and say,
• 11:24
  "Here's what we measured, here's what we heard: two strengths,
• 11:28
  two constraints, one risk.
• 11:30
  We're not here to find culprits; we're here to fix the system." Then
• 11:34
  you validate: "Where do you see this in our week?
• 11:37
  What's the cost when it happens?"So you don't jump straight to solutions.
• 11:41
  You let people anchor it in real work.
• 11:41
  Right.
• 11:44
  Step two: pick the top 2-3 moves and assign owners,
• 11:48
  timelines, and simple metrics.
• 11:50
  One named owner per action, a 30-60 day window,
• 11:55
  and either a business metric-like reduced rework,
• 11:58
  faster decisions-or a clear behavior signal,
• 12:01
  like "every meeting ends with written decisions." Step three: monthly
• 12:06
  progress reviews.
• 12:07
  Add 15-20 minutes to an existing leadership or team meeting: what did
• 12:12
  we complete, what changed, what's still in the way,
• 12:15
  what's next.
• 12:15
  And then a reassessment cadence?
• 12:15
  Yes.
• 12:19
  For stable teams, re-run the full dynamics assessment every 12 months.
• 12:24
  For teams in heavy change-new leader,
• 12:26
  re-org, rapid growth-every 6 months.
• 12:29
  In between, do short quarterly pulse checks focused only on those top
• 12:34
  few priorities: "Are decisions clearer than last quarter?" "Are blockers
• 12:38
  raised earlier?" Three to eight items,
• 12:40
  max.
• 12:40
  So you're basically building a loop: assess,
• 12:44
  act, review, pulse, repeat.
• 12:46
  And over time, you're not managing "culture," you're managing the operating
• 12:50
  system.
• 12:50
  Exactly.
• 12:52
  And when leaders do this consistently,
• 12:55
  they stop reacting to surprises and start steering with data that actually
• 12:59
  reflects how the team works.
• 12:59
  Edwin,
• 13:02
  this has been really grounding.
• 13:03
  We covered the difference between dynamics and performance,
• 13:07
  how to design a high-trust assessment,
• 13:09
  and how to turn the results into boring,
• 13:11
  reliable habits that move the needle.
• 13:11
  Always a pleasure,
• 13:14
  Claire.
• 13:14
  If you're listening and thinking,
• 13:17
  "We need this, but simple," maybe pick one team,
• 13:21
  one outcome, and run a lightweight version of what we described.
• 13:24
  See what you learn.
• 13:25
  And if you want to see what a data-driven team dynamics assessment looks
• 13:29
  like in practice, you can go to OAD.
• 13:29
  ai and test OAD for free with one
• 13:36
  of your own roles or teams-so you're not guessing,
• 13:38
  you're comparing decisions with real behavioral data.
• 13:41
  We'll keep digging into tools like this in future episodes.
• 13:45
  Edwin, thanks again.
• 13:46
  And thanks to all of you for joining us on The Science of Leading.
• 13:49
  We'll see you next time.