From Gut Feel to Real Data: A Practical Playbook for High-Performing Teams

Claire Monroe

Welcome back, everyone. I’m Claire, and I’m here with my favorite resident sage, Edwin Carrington. Today we’re talking about team performance, but not in the “let’s do a pep talk and order pizza” way.

Edwin Carrington

No, no pizza required. We’re going to separate vibes from evidence. Because most organizations don’t actually have a “team performance” problem. They have a measurement problem.

Claire Monroe

Let’s start right there. When you say “team performance,” what do you actually mean? Because a lot of leaders still default to, “Are people working hard enough?”

Edwin Carrington

Team performance is simple to say, harder to live. It’s a team’s ability to consistently produce the outcomes it’s responsible for, at an acceptable quality level, inside real constraints—time, budget, dependencies—without burning people out. So outcomes, quality, speed, and sustainability. All four.

Claire Monroe

So that’s different from individual performance reviews, which are more, “Is this person doing their job well?” You’re asking, “Can this whole group actually produce results together?”

Edwin Carrington

Exactly. You can have a room full of high performers on paper and still have a weak team. Work gets stuck in handoffs. Decisions take forever. Conflict just…sits there. Ownership is fuzzy so nothing moves. That’s the gap between individual performance and team performance.

Claire Monroe

You also make a distinction I really like between team effectiveness, team dynamics, and team health. Can you break those down in plain language?

Edwin Carrington

Of course. Team effectiveness is, “Do we actually deliver?” So speed, quality, reliability of outcomes. Team dynamics is, “What does it feel like when we work together?” Communication patterns, how we handle conflict, how we make decisions. Team health is the sustainability layer: engagement, trust, morale, workload, psychological safety. Are people able to keep doing this without frying?

Claire Monroe

So effectiveness is results, dynamics is how we interact, health is whether we’re burning out or building something durable. And research from the big players basically says: you can measure all three, right?

Edwin Carrington

You can, and you should. The most robust studies on teams tend to land on a similar core: psychological safety, dependability, structure and clarity, a sense of meaning and impact, plus basic health indicators like engagement. Those are not fluffy ideas—they show up over and over as predictors of whether teams actually deliver.

Claire Monroe

Okay, so, if the research is pretty clear, why do so many leaders still jump to motivation talks, new tools, or a reorg when a team slips?

Edwin Carrington

Because those are visible. They feel like action. The real drivers of performance are more boring: role clarity, decision rights, how work actually flows, whether people feel safe surfacing risks early. If you’re not measuring those, you end up doing what I call performance theater—lots of motion, little change.

Claire Monroe

So let’s get practical. If I’m an HR leader or a founder in, say, a 100-person company, how do I move from theater to evidence without turning this into a giant culture project?

Edwin Carrington

You start with a very simple diagnostic. Two parts. First, a short team health survey: a few questions on psychological safety—“Can I speak up?”—dependability, clarity of goals and roles, and whether the work feels meaningful. Short enough that people actually finish it. Second, a handful of hard metrics.

Claire Monroe

These are the ones I’ve seen you use again and again. Delivery reliability, cycle time, decision latency. Walk us through those, please?

Edwin Carrington

Delivery reliability is, “Do we do what we said we’d do, when we said we’d do it?” It’s just the percentage of commitments met. Cycle time is, “How long does typical work take from start to done?” Decision latency is, “How long do important decisions sit unresolved?” Add a simple quality signal—defects or rework—and a basic team health trend.

Claire Monroe

So you’re not asking for a dashboard with 40 KPIs. You’re saying: a short survey, plus four or five numbers you can track weekly.

Edwin Carrington

That’s right. Consistent and simple beats perfect. Once you can see, for example, that decision latency is high and psychological safety is low, you stop guessing. You can say, “We don’t need another motivational talk. We need clearer decision rights and safer conversations.”

Claire Monroe

This is also where I see tools like OAD help, because they add the behavioral layer. You’ve got the survey and the metrics, but you can also see: do we have a decision-averse leadership group? Do we have a whole team of people who avoid conflict or hate structure?

Edwin Carrington

Exactly. Behavioral data gives you x‑ray vision on fit. You can see whether a manager’s natural style clashes with what the role and the team actually need. You can see collaboration preferences, stress responses, decision styles. When you layer OAD on top of the metrics, it tells you whether the problem is the system, the fit, or both.

Claire Monroe

And that’s the shift you’re arguing for: stop blaming “the team,” start measuring the system they’re in—and use data, including OAD, to see if you’ve actually set them up to perform.

Claire Monroe

Alright, so we’ve got a clearer picture of what to measure. Let’s talk about what “good” actually looks like. When you walk into a high-performing team, what do you notice?

Edwin Carrington

The first thing is very unglamorous: work moves. Decisions don’t sit. Handoffs don’t stall. People keep commitments. You see dependability—if someone says, “I’ll have it by Thursday,” it usually shows up by Thursday at an acceptable quality level.

Claire Monroe

There’s also a kind of…cleanliness to the way they operate. Goals and roles aren’t fuzzy. People know why the team exists, what success looks like, and who owns what slice of it.

Edwin Carrington

That’s structure and clarity. High-performing teams don’t leave ownership to chance. They define who decides, who executes, what “done” means. That reduces friction and conflict before it starts. Then there’s psychological safety and trust—you’ll hear people raise uncomfortable truths early, not at the end when everything’s on fire.

Claire Monroe

So you might hear someone say, “Hey, we’re over-committing this sprint,” or, “This requirement doesn’t make sense,” and it’s normal, not career suicide.

Edwin Carrington

Exactly. And when those issues are raised, the system turns them into action. That’s a key marker. In the better studies on team trust, high-performing teams aren’t “nice”—they’re proactive about tension, they keep each other in the loop, they resolve issues before they rot.

Claire Monroe

You’ve also talked about the human capability side—curiosity, resilience, connected teaming, different ways of thinking. How do those fit into this picture?

Edwin Carrington

Those capabilities are like fuel. Curiosity means people question old assumptions instead of just pushing harder. Connected teaming is the ability to coordinate across functions. Resilience keeps the team steady when things change. Divergent thinking lets people see multiple options instead of defaulting to the obvious one. But those only show up consistently when the basics—clarity, trust, governance—are in place.

Claire Monroe

So, human capabilities are powerful, but they’re amplified or suppressed by the manager and the system. A strong manager with clear decision rules and a good operating rhythm kind of “turns up the volume” on those capabilities.

Edwin Carrington

That’s right. A good manager makes it safe to be curious, uses structure so divergent ideas actually get tested, and protects the team’s resilience by managing workload. And governance—who decides what, how fast—is what stops cross-functional teams from drowning in ambiguity.

Claire Monroe

Let’s make this really concrete. If I’m looking across my organization, what observable traits tell me, “This is one of our best teams”?

Edwin Carrington

You’d see: they hit the majority of their commitments without drama. Their cycle times are shorter than peers. Decisions in their world move quickly. When you ask them about goals and roles, they give consistent answers. In meetings, you hear disagreement early and resolution by the end, not the same debate every week. And their engagement and turnover look better over time, not worse.

Claire Monroe

And if you compare that to a struggling team, you’d probably see slow decisions, vague ownership, a lot of rework, and people quietly checking out.

Edwin Carrington

Exactly. The differences sound simple—dependability, clarity, safety, trust—but they add up. And here’s where OAD becomes very practical for HR and founders. Once you know which teams are your best, you can look under the hood behaviorally.

Claire Monroe

Yeah, you can ask: what’s actually true about the people and the roles on those teams? Do we have managers whose natural style fits the role? Do we have the right mix of drivers—some people who love structure, some who challenge it, some who bring calm under pressure?

Edwin Carrington

And you can compare that to struggling teams. Maybe your weakest team has a manager whose natural tendencies are highly controlling in a role that needs delegation, or very conflict-avoidant in a space that needs hard trade-offs weekly. With OAD, you’re not guessing. You see where role demands and natural style are misaligned.

Claire Monroe

I’ve seen companies use it to staff project teams, too—putting the naturally detail-oriented folks in critical handoff roles, pairing them with people who push decisions forward, and avoiding those teams where everyone wants to brainstorm and nobody wants to finish.

Edwin Carrington

That’s right. You’re not looking for “better people.” You’re designing better combinations and clearer conditions. The research tells you which conditions matter. Your metrics tell you which teams are actually performing. Behavioral data from OAD helps you replicate the wins and spot manager risk early, instead of waiting for burnout or attrition to show up in a dashboard.

Claire Monroe

So high-performing teams are not a mystery. They’re a pattern you can observe, measure, and then intentionally recreate—with the right structure, the right manager habits, and the right behavioral mix.

Claire Monroe

Alright, let’s get into the “do this next month” part. You talk a lot about running boring, powerful experiments instead of announcing big initiatives. What does that loop actually look like?

Edwin Carrington

The loop is very simple. One: pick a performance gap—late delivery, constant rework, slow decisions, rising burnout risk. Two: tie it to one main driver—clarity, trust, decisions, or communication. Three: define one or two specific behavior changes. Four: track one leading and one lagging metric for 2–4 weeks. That’s it.

Claire Monroe

Let’s walk through examples, because I know people listening are already thinking, “Okay, but what does that actually look like on Monday?” Start with decisions, since that’s such a common pain point.

Edwin Carrington

Decision-latency experiment. Performance gap: important decisions take too long. Driver: decision-making and clarity of ownership. Behavior change: every decision above a certain impact level has a named decision owner and a deadline—say 48 hours—to make the call once input is gathered. Metrics: leading indicator is median decision latency, lagging is delivery reliability on key projects. Run that for three weeks and see if work moves faster.

Claire Monroe

So really tangible: “I own this decision, I’ll make it by Thursday,” instead of decisions floating in email threads for weeks.

Edwin Carrington

Exactly. Another one is a role-clarity experiment. Gap: work falls through the cracks and people step on each other’s toes. Driver: clarity. Behavior change: for one project, you create a simple RACI for key deliverables and a one-line “definition of done” for each. Metrics: leading indicator is the number of unclear ownership escalations; lagging is rework rate or missed handoffs.

Claire Monroe

What about communication, especially with hybrid or distributed teams?

Edwin Carrington

Async-communication experiment. Gap: people feel out of the loop, meetings are bloated, and surprises keep popping up. Driver: communication. Behavior change: you standardize a daily or twice-weekly async update with a simple template—what I completed, what’s next, what’s blocked, what decisions I need. Metrics: leading is the number of blockers identified early; lagging could be cycle time or the frequency of last-minute fire drills.

Claire Monroe

You’ve mentioned light governance around these experiments, so it doesn’t become bureaucracy. What does “just enough” governance look like?

Edwin Carrington

Three things. One owner per experiment—often the manager or a project lead. A short weekly review where the team looks at the one leading and one lagging metric and decides whether to continue, adjust, or stop. And an escalation path—if a blocker sits for more than, say, 48 hours, it automatically escalates to a named leader. At the end of 2–4 weeks, you run a quick retrospective: what helped, what didn’t, what do we keep.

Claire Monroe

And I want to bring OAD back in here, because it can even help you choose which experiment to run, right? If the behavioral data shows your manager is naturally conflict-avoidant, maybe you don’t start with a trust-and-conflict experiment that depends entirely on their personal comfort level.

Edwin Carrington

Exactly. OAD can show you, for example, that your leadership trio is heavily cautious and consensus-oriented. In that case, a decision-speed experiment might need more structural support—clear rules and timeboxes—rather than just asking everyone to “decide faster.” Or if your team skews highly independent and low on structure, a role-clarity experiment will feel uncomfortable at first, and you can plan for that.

Claire Monroe

So behavioral data lets you de‑risk these small experiments. You’re not surprised when a particular change feels hard for a particular manager, because you already know their natural style and stress responses.

Edwin Carrington

That’s right. Instead of saying, “They’re resisting,” you can say, “This is a stretch for how they’re wired—how do we support it?” That’s a very different conversation. And when you combine that with simple metrics—delivery reliability, cycle time, decision latency, rework, team health trends—you can see, within a month, whether a change is actually working.

Claire Monroe

I like how all of this avoids performance theater. No giant culture initiative, no vague promises. Just: diagnose, pick one driver, change one or two behaviors, measure, repeat.

Edwin Carrington

Exactly. It’s not glamorous, but it’s how you build a high-performing environment over time. You’re treating team performance like an operating problem, not a motivational one.

Claire Monroe

Alright, let’s land this. For everyone listening—HR leaders, founders, people managers—if you want to move from gut feel to evidence in how you hire, design teams, and lead, you need both sides: simple performance metrics and real insight into how your people naturally work.

Edwin Carrington

And that’s where I’d invite you to try OAD. Use it to see role fit, decision styles, collaboration preferences, and manager risk before it shows up as burnout or attrition. Then pair that with the small experiments we’ve talked about today.

Claire Monroe

If you want to move from gut feel to evidence in how you hire, design teams, and lead, test OAD for free at OAD.ai. No drama, no performance theater—just practical data you can use next month.

Edwin Carrington

Claire, as always, a pleasure.

Claire Monroe

Same here, Edwin. And thanks to all of you for listening. We’ll be back with more ways to build teams that actually work. Take care, everyone.