[Claire Monroe]
Welcome to the show—Edwin, I want to start with a sentence that tends to make leaders a little uneasy: five brilliant hires can still give you a terrible team.
[Edwin Carrington]
They can, and usually for reasons that have nothing to do with talent. Talent doesn’t coordinate itself. Leaders still fall in love with individual brilliance—the standout CV, the exceptional engineer, the high-performing salesperson—and then they’re surprised when the group stalls. But teams tend to fail in quieter ways: unclear roles, messy handoffs, no clarity on who decides, and people not feeling safe enough to say, “this isn’t working.”
[Claire Monroe]
“Talent doesn’t coordinate itself” is… annoyingly accurate. Because I think a lot of founders still have this sort of movie version of team-building. You assemble a group of high performers, put them in a room, and somehow everything just clicks.
[Edwin Carrington]
Yes, and then in reality they spend most of their time trying to figure out who owns what. OAD points to something important here—hiring isn’t just about individual strength. It’s about how someone’s way of working fits the role, the team, and the environment. Performance is contextual. A strong hire in the wrong structure can look average very quickly.
[Claire Monroe]
Let’s make that concrete. Say you’ve got a startup that hires a great product lead, a strong engineering manager, a high-performing marketer, a sought-after data person, and an experienced operations lead. On paper, that’s a dream team. Where does it break?
[Edwin Carrington]
Usually very early. Product assumes they own prioritization. Engineering assumes they control feasibility and timing. Marketing builds plans on a roadmap that isn’t stable. Data is waiting for someone to define success. Operations is dealing with the fallout. And then add one more factor—conflict isn’t handled directly. So instead of clear decisions, you get more messages, more meetings, more alignment conversations, and less progress.
[Claire Monroe]
So it’s not a talent issue at all. It’s more like five capable people arriving at the same intersection with no traffic rules.
[Edwin Carrington]
That’s a good way to put it. Everyone can be competent and still collide. Leaders often see that friction and think they need more alignment. What they actually need is better design. Alignment isn’t more meetings. It’s clear decision rights, defined handoffs, and expectations for how disagreement gets surfaced early.
[Claire Monroe]
And yet the default reaction is always more meetings. The team is confused, so now there’s a Monday sync, a Thursday check-in, a cross-functional update, and maybe a retrospective because everyone’s already exhausted.
[Edwin Carrington]
Meetings can become a way to avoid structural decisions. Defining ownership has consequences. If I say you’re the decision-maker, I have to accept not being the decision-maker. If we define what “done” means, we lose the ability to hide behind ambiguity. Structure makes performance visible, and that can feel uncomfortable.
[Claire Monroe]
So when someone says, “my team isn’t clicking,” what you’re really hearing is something more specific. Roles might be unclear, handoffs might be breaking, decision-making isn’t defined, and people don’t feel safe calling that out.
[Edwin Carrington]
Exactly. “Not clicking” sounds like chemistry, but it’s usually architecture. And that matters because chemistry feels intangible. Architecture can be improved.
[Claire Monroe]
So if chemistry isn’t the answer, what actually helps? If someone’s listening to this and their team feels slow or heavy, where do they start?
[Edwin Carrington]
Start with fundamentals. Shared purpose, role clarity, trust, psychological safety, and accountability. Shared purpose means the team can clearly explain what they’re trying to achieve and why. Role clarity means people understand their responsibilities and decision boundaries. Trust means people follow through. Psychological safety means people can raise risks or admit mistakes without social cost. And accountability means commitments are visible and actually met.
[Claire Monroe]
Two of those stand out to me—interfaces and social cost. Because work doesn’t usually break inside teams, it breaks between them. And the social cost part… that’s where people hesitate. If I say the timeline is unrealistic, am I now “difficult”?
[Edwin Carrington]
That’s where most friction lives—in the seams. A practical fix is to define decision roles clearly. Not in a complex framework, just plainly. Who recommends, who decides, who contributes, who executes. Even simple clarity like that removes a surprising amount of friction.
[Claire Monroe]
And it probably saves a lot of time too. Instead of six people sitting in a meeting trying to figure out what should have been clear already.
[Edwin Carrington]
Exactly. Teams often spend significant time compensating for one missing decision owner. Another improvement is reducing unnecessary meetings. If a meeting exists because something is unclear, fix the underlying issue. If it’s just status updates, move it to writing. Use live time for decisions and trade-offs.
[Claire Monroe]
So not fewer meetings for the sake of it, but fewer meetings that exist to patch over structural gaps.
[Edwin Carrington]
Precisely. And one more simple but critical point—define what “done” means. That sounds basic, but it’s often unclear. Does “done” mean designed, approved, built, tested, or delivered? When people use the same word for different endpoints, conflict is inevitable.
[Claire Monroe]
“Done” might be one of the most misleading words in the workplace. But let me push on psychological safety, because that one gets misunderstood. Does it just mean being nice?
[Edwin Carrington]
No, and it’s important to be precise here. Psychological safety is not about comfort or lowering standards. It’s about being able to speak honestly without fear of negative consequences. Research has shown that strong teams combine high standards with high candor. People can challenge ideas, admit uncertainty, and raise concerns early.
[Claire Monroe]
So it’s not about everyone feeling comfortable—it’s about making sure the truth shows up early, before it becomes expensive.
[Edwin Carrington]
That’s a better way to think about it. Honest conversations are often uncomfortable, but they’re necessary. The key is that discomfort doesn’t turn into punishment.
[Claire Monroe]
And that connects to accountability. If people can speak up early, you avoid that situation where everyone privately sees the issue but publicly acts like everything is fine.
[Edwin Carrington]
Exactly. False harmony is costly. So instead of trying to boost morale, a manager can ask a few clear questions: what are we trying to achieve, who decides what, where do handoffs break, what does done mean, and what happens when someone raises a problem? Those answers reveal more than any motivational speech.
[Claire Monroe]
I like that this shifts the focus. It’s not about finding the perfect team—it’s about building a system where people can actually perform.
[Edwin Carrington]
That’s the core idea. Team performance isn’t something a group either has or doesn’t have. It’s designed—through structure, norms, feedback, and the signals leaders send consistently. And if leaders focused more on that, they would spend less time searching for exceptional individuals and more time creating conditions where strong work can happen reliably.
[Claire Monroe]
That’s a good place to land. Not heroes—conditions.