From Gut Feel to Data: Using Teamwork Self‑Assessments to Build Stronger Teams

Why Your Team Doesn’t Have a “Teamwork Problem”—It Has a Visibility Problem

Claire Monroe: So, Edwin, I keep hearing managers say, “My team has a teamwork problem.” But when you and I were prepping, you pushed back on that. You said it’s usually a visibility problem. What do you mean by that?

Edwin Carrington: Most teams aren’t falling apart because people suddenly forgot how to be adults. What’s really happening is that different people experience the same team completely differently… and nobody can see those differences. One person thinks communication is clear, another feels totally in the dark. One thinks decisions are decisive, another experiences them as chaotic. Without visibility into those gaps, it all gets labeled as “bad teamwork.”

Claire Monroe: Right, and then it shows up as missed deadlines, messy meetings, uneven contributions… but nobody can quite explain why. It’s just this vague frustration.

Edwin Carrington: Exactly. And that’s where a teamwork self‑assessment comes in. It’s basically a structured set of questions where people rate specific behaviors: how communication works, how they collaborate, how the team makes decisions. It’s behavior‑focused and time‑anchored—usually the last four to eight weeks—so you’re not asking, “Are you a good team player?” You’re asking, “What actually happened recently?”

Claire Monroe: So it’s not a personality test, and it’s not some secret performance scorecard.

Edwin Carrington: That’s an important distinction. It’s not a verdict on who you are, and it shouldn’t be a hidden performance rating. The goal is to see patterns that either help or quietly block the team’s progress. Things like: Do we clarify next steps? Do we listen before we argue? Do we surface problems early or wait until the last minute?

Claire Monroe: Let me play the manager for a second. I’m busy, my team’s under pressure. Why should I spend time on a questionnaire instead of “just fixing the problem” in a meeting?

Edwin Carrington: Because that meeting usually turns into opinions competing with other opinions. The loudest person wins. A short, well‑run self‑assessment gives you structured input from everyone—quiet voices included. You start to see, for example, that communication looks fine to leadership but confusing to the frontline. Or that collaboration is strong inside the team but falls apart at handoffs with another group.

Claire Monroe: So instead of, “We’re bad at teamwork,” you get, “Our listening is decent, but our decision‑making process is inconsistent, and that’s where we’re losing time.”

Edwin Carrington: Exactly. And once you can name that, you can coach it. Now you can prioritize: “Over the next month, we’re going to tighten how we make and document decisions,” instead of trying to fix everything at once. Plus, those same dimensions—communication, collaboration, flexibility, leadership—map directly to business outcomes: fewer dropped balls, less rework, faster alignment on goals.

Claire Monroe: I like that you’re tying it back to outcomes. This isn’t about everyone feeling warm and fuzzy in meetings. It’s about making teamwork visible enough that you can actually improve execution.

Edwin Carrington: That’s the business case. Visibility turns vague frustration into specific patterns. Once you can see the patterns, you can change the behaviors. And when behaviors improve, performance usually follows.

Claire Monroe: Alright, so in this episode we’re really talking about that bridge: from invisible dynamics to actionable patterns. In the next part, we’ll get into how to design a self‑assessment that people actually trust—and don’t roll their eyes at.

Designing a Teamwork Self‑Assessment You Can Trust (Without Spooking People)

Claire Monroe: Okay, Edwin, let’s say I’m sold. I want to run a teamwork self‑assessment with my team. Where do I start without making it feel like homework… or surveillance?

Edwin Carrington: Good instincts. The structure matters a lot. A practical design uses five to seven sections: communication, listening, collaboration, flexibility or adaptability, decision making, leadership or coaching, and often a section on problem solving and innovation. Each section has a handful of clear, behavioral items—so maybe 25 to 40 statements in total.

Claire Monroe: And the scale is that classic one-to-five agreement scale, right?

Edwin Carrington: Yes, a simple five‑point Likert scale works very well: strongly disagree up to strongly agree. The key is clarity. For example, “In team discussions, expectations and next steps are stated clearly,” or, “Team members ask clarifying questions before disagreeing.” Short, observable, and anchored in recent behavior.

Claire Monroe: You also like adding a few scenarios, which I thought was interesting.

Edwin Carrington: Scenarios help people answer based on how the team really behaves under pressure, not just how they see themselves. So you might ask, “A deadline is at risk because a dependency is late. What happens next in your team?” Or, “Two team members disagree on approach. How does the team reach a decision?” Two to four of those is plenty.

Claire Monroe: Let’s talk rollout, because this is where people get nervous. Anonymous or identified?

Edwin Carrington: For development, anonymous is usually better. You aggregate results at the team level, you don’t share individual scores. That encourages honesty and reduces defensiveness. If you ever decide to use identified responses—for coaching, for example—you have to be very explicit: who can see the data, what it will be used for, and what it will not be used for.

Claire Monroe: So no twelve‑paragraph policy nobody reads. Just clear, plain language.

Edwin Carrington: Exactly. And a few other design choices matter. Give a realistic time estimate—eight to twelve minutes—and put it at the top. Ask everyone to think about the last four to eight weeks of work. And keep conditions consistent: same instructions, same time window, same scale for everyone.

Claire Monroe: What are the fastest ways to screw this up? I feel like that’s what managers really want to know.

Edwin Carrington: Three big pitfalls. First, making it feel like homework—too long, too abstract, or full of jargon. People rush through and the data is noise. Second, mixing evaluation with development. If people suspect it’s secretly tied to performance ratings, honesty disappears. Third, running it once, sharing nothing, and never following up. That teaches everyone that surveys don’t matter.

Claire Monroe: Yeah, the “black hole survey.” People answer, nothing happens, trust goes down.

Edwin Carrington: Right. A good self‑assessment is short, clear, and followed by action. And if, later on, you want to go beyond self‑report, you can complement it with structured tools—things like psychometric assessments—to reduce bias. But the starting point is simple: ask about real behaviors, protect psychological safety, and commit to doing something with what you learn.

Claire Monroe: So design it like you respect people’s time and intelligence. Then we can focus on the hard part: turning those scores into better teamwork.

From Scores to Behavior Change—Turning Results into 4–6 Weeks of Better Teamwork

Claire Monroe: Alright, we’ve run the assessment, we’ve got the data. I’m a manager staring at a dashboard: communication 3.4, collaboration 2.8, decision making 3.9, and some overall teamwork score. What do I actually do with this?

Edwin Carrington: Step one is to read it the right way. Don’t obsess over the single overall score. Start with the subscales—the averages for each dimension. Those tell you where the real leverage is. Then use a simple rubric. For example: scores above 4.1 are “strong and consistent,” 3.1 to 4.0 are “solid with improvement areas,” 2.1 to 3.0 are “inconsistent,” and below that is “high risk.”

Claire Monroe: So in my example, collaboration at 2.8 is in that “inconsistent, probably hurting us” zone.

Edwin Carrington: Exactly. Next, you translate that into what people actually see and feel. Low collaboration often shows up as missed handoffs, uneven workload, or projects that stall unless someone chases constantly. Weak communication looks like people leaving meetings unsure about owners and deadlines. Weak decision making shows up as rework and revisiting the same decision three times.

Claire Monroe: I like that because managers can literally look at their week and go, “Oh, that’s why we keep redoing the same slide deck.”

Edwin Carrington: That’s the goal. Then you convert those insights into very focused actions. At the team level, pick one or two behaviors for the next four to six weeks. For low collaboration, you might say, “In every meeting, we’ll end by naming owners, due dates, and what ‘done’ looks like for shared tasks.” Or, “We’ll set simple handoff rules between teams.”

Claire Monroe: And at the individual level?

Edwin Carrington: You can give each person a short summary: top two strengths, top one or two growth areas, and one “start” and one “stop” behavior for this week. For example, “Start: summarize next steps in chat after meetings. Stop: assuming others know your priorities without saying them.” Keep it behavioral, not about personality.

Claire Monroe: So you’re not telling someone, “You’re not collaborative.” You’re saying, “For the next month, confirm owners and deadlines before you leave the room.”

Edwin Carrington: Precisely. Then you wrap this in a simple improvement cycle. First, share results in a safe, transparent way—team‑level themes, not a wall of numbers. Second, agree on two or three small experiments tied to those themes. Third, run them consistently for four to six weeks. Finally, reassess with the same questionnaire and see what shifted.

Claire Monroe: And if things aren’t moving, that might be the moment to add more objective data—like a structured assessment—to understand how people’s natural styles are interacting with the team’s habits.

Edwin Carrington: Yes, that can help separate “can’t” from “won’t” and reduce some of the bias in how we interpret behavior. But the engine is still the same: make teamwork visible, pick specific behaviors, practice them, and check back.

Claire Monroe: So if I boil it down for anyone listening: your team probably doesn’t have a mysterious teamwork problem. You’ve got blind spots. A short, honest self‑assessment makes those visible, you pick a couple of concrete habits to work on, you run them for a month or so, and then you see what changed.

Edwin Carrington: And you repeat. That rhythm—measure, act, learn—is how culture actually changes, one behavior at a time.

Claire Monroe: Edwin, this was great. Thanks for walking through the practical side, not just the theory.

Edwin Carrington: Always a pleasure, Claire. These are the conversations I wish more teams were having.

Claire Monroe: Alright, we’ll wrap it there. If you’re listening and thinking about trying this with your own team, start small, be clear about why you’re doing it, and commit to at least one change afterward. Edwin, thanks again—and we’ll see all of you in the next episode.