From Dashboard Dreams to Daily Habits: A 90-Day Plan to Measure Teamwork Without Killing Trust

Claire Monroe

Welcome back to The Science of Leading. I’m Claire, and I’m here with Edwin Carrington. Today we’re talking about something that sounds kind of boring on paper, but totally changes how teams perform: the first 90 days of measuring teamwork.

Edwin Carrington

And specifically, how not to turn that into what you once called, Claire, a “spreadsheet crime scene.”

Claire Monroe

Yeah, that. So let’s start with weeks one through four. Edwin, a lot of leaders jump straight into tools and dashboards. You’re saying: slow down, define “team success” first. What does that actually look like?

Edwin Carrington

You start with this team, in this context. Not a template from another department. I’d look at three layers. First, outcomes: what results does this team need to deliver that actually matter to the business? Deadlines, quality, customer impact, revenue support—whatever is real for them. Second, operating health: can they deliver those results at a sustainable pace? Or are you relying on heroics, late nights, and quiet burnout? Third, collaboration and decision quality: are they aligned on goals, resolving disagreements productively, and making decisions that don’t fall apart two weeks later.

Claire Monroe

So not just “hit the number,” but “hit the number, without breaking people or the system, and stay on the same page while you do it.”

Edwin Carrington

Exactly. If you only measure the outcome, you can accidentally reward very fragile, even toxic performance. If you only measure the vibe, you get lovely meetings and weak delivery.

Claire Monroe

Alright, so once I’ve got that three-part definition for my team—outcomes, operating health, collaboration—what’s next? You talk a lot about a lean metric set, 6 to 10 max. What goes in there for weeks one to four?

Edwin Carrington

You want four buckets. One: delivery. That could be on‑time delivery versus deadlines, or throughput per week or sprint. Two: quality. Something like rework rate or defect rate. Three: collaboration. Blocker aging is powerful—how long do issues sit unresolved? Handoff friction is another—how often does work bounce back and forth? And four: team health. A simple pulse survey trend around clarity, support, and psychological safety.

Claire Monroe

Let me push on that pulse survey piece. Busy managers are gonna say, “We’re drowning already. Do we really have time to add more surveys?”

Edwin Carrington

If you design it badly, no, you don’t. But we’re talking five to eight questions, every two to four weeks. Things like, “I know what success looks like this week,” “Blockers get removed quickly,” “I can raise concerns without negative consequences.” That’s it. The point is to get a baseline trend, not a novel. And you only run it if you’re prepared to act on what it tells you.

Claire Monroe

Right, otherwise it’s just disappointment with extra steps. Where does something like OAD fit in at this early stage? Because we’re talking metrics, but underneath that are real people with very different behavior patterns.

Edwin Carrington

Good question. Early on, OAD is helpful as a lens—not a scorecard. When you start seeing patterns in your metrics—say, chronic handoff issues or one person becoming a bottleneck—OAD can help you understand the stable behavior traits underneath that. Are you overloaded with big-vision, low-detail profiles? Are your natural “finishers” spread too thin? That lets you interpret the data without just blaming whoever speaks the least in meetings.

Claire Monroe

So the first four weeks are basically: define success for this team, pick 6–10 metrics across delivery, quality, collaboration, and health, run that first pulse survey, and… build a dashboard. But you’re very specific that it should be simple and visible. What does that look like in practice?

Edwin Carrington

One page. Trend lines, not walls of numbers. No more than those 6–10 metrics. And each metric has an owner. Not an owner who gets punished if the number is bad, but someone who’s responsible for collecting the data, checking it’s not garbage, and bringing it to the conversation. Delivery metrics might sit with the team lead, quality with a QA or process owner, health with HR running the survey and the manager owning the response. The key is: by the end of week four, everybody knows what “good looks like,” where the numbers live, and who will keep them alive.

Claire Monroe

And we’re not trying to fix everything yet—we’re just getting a clear, honest starting line.

Edwin Carrington

Exactly. You’re building a real baseline, not a pretty dashboard for executive theater.

Claire Monroe

Okay, so we’ve survived weeks one through four. We’ve got a definition of team success, a lean metric set, a simple dashboard, some pulse data. Now weeks five to eight is where this lives or dies, right? Because this is where you either build habits or the dashboard starts collecting dust.

Edwin Carrington

That’s right. The heart of this phase is a weekly, 15‑minute metrics review. Short on purpose. You answer three questions: what moved, what’s stuck, and what one decision do we need this week.

Claire Monroe

Fifteen minutes sounds almost… too short. Why not an hour-long deep dive?

Edwin Carrington

Because if you need an hour every week, your system is too complicated. The metrics are there to surface where the conversation is needed, not to become the conversation. In those 15 minutes, you glance at delivery, quality, collaboration, and health. If something’s off—say blocker aging is spiking—you decide: who’s going to dig into that, and what will we try before next week.

Claire Monroe

So this is “steering the ship,” not rebuilding the engine in every meeting. Where do deeper conversations happen then? You mention structured one on ones, retrospectives, psychological safety checks… how do those layer in without overwhelming people?

Edwin Carrington

You don’t add three new rituals at once. Start by tightening what you already have. Turn existing one on ones into better diagnostic time. Ask a few consistent questions: What’s slowing you down? Where is the team not on the same page? What decision are we avoiding? Then capture themes—no gossip. Retrospectives you can run monthly. Look at the metrics and ask: what improved, what got worse, what blocked us most, what one change will we test next month.

Claire Monroe

And the psychological safety checks—are those just part of the pulse survey, or are you watching behavior in meetings too?

Edwin Carrington

Both. Pulse questions like “I can raise opposing opinions without negative consequences” give you the trend. Then someone—often a team lead or HR partner—pays attention in meetings. Who speaks, who stays quiet? Do we actually follow through on decisions, or do the same issues keep resurfacing? If the scores drop and you see people disengaging, that’s a real signal, not a vibe.

Claire Monroe

I can hear some listeners worrying this starts to feel like surveillance. Weekly metrics reviews, observers in meetings… How do you keep this from turning into “we’re watching you” instead of “we’re supporting you”?

Edwin Carrington

You’re very explicit about the goal. You tell the team: we’re measuring to make better decisions, reduce friction, and keep performance sustainable. We’re not scorekeeping individuals off these charts. You look at themes, not who said what on Tuesday morning. And if you bring in tools like OAD, you use them to understand behavior patterns, not to label people as the problem. For example, OAD might show you that your team is heavy on independent, fast-paced profiles and light on patience and detail. That explains why blockers pile up or why rework is high. The response is redesigning roles and support, not shaming individuals.

Claire Monroe

That’s a really important distinction. Let’s talk about experiments, because this is my favorite part of weeks five to eight. You’re not launching a big “transformation,” you’re running little tests, like a two‑week experiment to reduce meetings or clean up handoffs. How specific do these need to be?

Edwin Carrington

Very specific. One change, one owner, one short time window, and one or two metrics that you expect to move. For example: “For the next three weeks, we cut recurring meetings by 20 percent and tighten agendas. We’ll watch throughput, blocker aging, and the pulse question on clarity.” Or: “We add explicit handoff criteria—what ‘done’ means before passing work—and see what happens to rework rate and first‑pass acceptance.”

Claire Monroe

And if nothing changes?

Edwin Carrington

Then you’ve learned that that lever doesn’t move this system, or you didn’t apply it consistently. Both are useful. The worst outcome isn’t a failed experiment. It’s no experiment at all—just more pressure and more status reports.

Claire Monroe

So weeks five to eight are all about rhythm and learning: a quick weekly review, better conversations in one on ones and retros, and small experiments that give you proof, not just opinions.

Edwin Carrington

Exactly. You’re teaching the team to treat metrics as a flashlight, not a weapon.

Claire Monroe

Alright, let’s bring it home with weeks nine to twelve. At this point, we’ve been measuring and experimenting long enough that we actually have trends—eight to twelve weeks of them. What should leaders be looking for now?

Edwin Carrington

You’re looking at three buckets again: what improved, what’s stable but not good enough, and what’s getting worse. And you look across delivery, quality, collaboration, and health together. For example, maybe on‑time delivery improved, but defect rate and pulse scores about sustainable pace got worse. That tells you you’re buying speed with quality and stress.

Claire Monroe

So you’re connecting the dots instead of celebrating one green number and ignoring two red ones. How do you decide which metrics to keep and which to drop at this stage?

Edwin Carrington

Simple test: did this metric change a decision in the last two months? If not, it’s probably vanity. You keep the ones that actually provoke action—like reducing blocker aging, clarifying ownership, or changing how you staff the team. You also refine definitions. If “on‑time” has meant five different things, you standardize it. If “rework” is fuzzy, you tighten what counts.

Claire Monroe

Can you give a quick example of a vanity metric that sounds impressive but doesn’t really help?

Edwin Carrington

Hours logged is a classic. It tells you who’s in the tool, not who’s creating value. Another is counting meetings or messages without asking whether decisions are actually being made. Those numbers can look very active while progress is stalled.

Claire Monroe

This is also where I imagine OAD can help you “tune” the system, not just the metrics. Like, you’ve got data that says handoffs are still messy, or conflict keeps resurfacing. How do you use behavior insight here without making it personal?

Edwin Carrington

You use it to design the team, not to diagnose character. If the data shows chronic conflict around priorities, and OAD reveals you have several highly assertive, big‑picture profiles and very few people wired for detail and follow‑through, that explains the pattern. You can then adjust roles, add a more detail‑oriented hire, or pair people differently. The message is, “We’re aligning work with strengths,” not “You’re wrong as a person.”

Claire Monroe

I like that. Okay, last big decision in weeks nine to twelve: how far do you scale this system? More teams, more metrics… or resist the impulse to add complexity. What do you tell leaders here?

Edwin Carrington

First, protect trust. If the team feels the system is fair and useful, don’t jeopardize that by suddenly turning it into surveillance. Stay focused on team‑level signals unless roles are very stable and there’s strong trust in how individual data will be used. Second, only expand if the basics are working: metrics are accurate, reviewed weekly, and driving experiments. If that’s not true, don’t scale the mess.

Claire Monroe

So maybe you roll it to one or two more teams, or you add a single new metric where you see a blind spot, but you’re not trying to build a giant enterprise cockpit overnight.

Edwin Carrington

Exactly. A good measurement system is boring, stable, and effective. You keep it lean enough that people actually use it. And you keep reiterating: the purpose is better decisions, sustainable performance, and healthier collaboration—not catching individuals out.

Claire Monroe

Before we wrap, I wanna connect this back to something practical for listeners who are about to start this 90‑day journey. If they’re nervous about misreading the data, or blaming the wrong things, where does a tool like OAD really de‑risk the process?

Edwin Carrington

It helps you see the human patterns behind the charts. When your metrics say, “We miss deadlines when priorities shift,” or “Rework spikes on cross‑team projects,” OAD can show you how people naturally approach pace, detail, and conflict. Instead of guessing, you see, “Ah, we’ve put three highly independent profiles on something that actually needs tight coordination,” or, “We’re light on people who enjoy structure.” That makes your interventions sharper and much fairer.

Claire Monroe

So you’re not just tuning the metrics; you’re tuning the team design to support those metrics.

Edwin Carrington

Exactly.

Claire Monroe

Alright, let’s land this. If you remember nothing else from today: in 90 days, you can build a simple, trustworthy system to measure teamwork—define success for your specific team, pick a lean set of metrics, turn them into weekly habits and honest conversations, then tune and protect the system so it serves people, not the other way around.

Edwin Carrington

And give yourself permission to keep it simple. Depth comes from consistent use, not from more charts.

Claire Monroe

If you wanna de‑risk those first 90 days and really understand the behavior patterns behind your delivery and collaboration metrics, you can test OAD for free at OAD.ai. It’s a practical way to see how your team is wired before you redesign roles, experiments, or expectations around teamwork. Edwin, thanks as always for the wisdom.

Edwin Carrington

Thank you, Claire. Always a pleasure.

Claire Monroe

And thanks to all of you for listening to The Science of Leading. We’ll be back with more on building healthier, higher‑performing teams. Until then, take care of yourselves—and your data. Bye, Edwin.

Edwin Carrington

Goodbye, Claire.