|
Think about your last team meeting. You laid out a plan, everyone nodded, and nobody raised a single concern. You walked out feeling good about it. That might be the problem. We usually picture a struggling team as a loud one: people snapping at each other, deadlines slipping, resumes quietly getting polished. But teams rarely fall apart that dramatically. Most crumble slowly, and the earliest warning signs tend to look like good news. Smooth meetings. Confident answers. Careful attention to detail. Then six months later half the team has checked out and three people have resigned. The trap is defining a healthy team by what's missing: no conflict, no mistakes, no reason to doubt anyone. A healthy team isn't defined by what's absent. It's defined by what's present, which means trust, candor, and productive disagreement. People can admit they're wrong, ask for help, and challenge each other to make the work better. Amy Edmondson's research on psychological safety ties exactly those behaviors to how teams learn: seeking feedback, asking for help, and talking openly about errors. When they start disappearing, a team is in trouble long before anyone says so out loud. Here are the six signs to watch for, and what to do about each one:
You don't have to fix all six this week. Pick the one you recognized fastest and start there. Each one is the same failure in a different costume: people stopped telling the truth where the whole team could hear it. And that's the real job of a leader. It isn't keeping the peace. It's creating a place where people can tell the truth early enough to do something about it. Teams rarely collapse overnight. Usually, they stop talking first. I walk through all six signs in more detail in this week's video, worth a watch if any of them sounded a little too familiar.
Here's some more resources I recommend: What Tesla's Robot Factory Teaches Us About AI: In 2017, Tesla tried to build a car factory so automated it barely needed people. The target was five thousand cars a week, but across the third quarter the line produced 260. Most people remember the comeback, yet the fix only worked because the skill was still in the building. Teams build judgment through routine, repetitive work, which is exactly the work that's easiest to automate. In my latest video, I break down what went wrong, the 1983 research that explains it, and two questions to ask before you automate anything on your team. Click here to watch. Making Teamwork Work: Most leaders can describe what a high-performing team looks like. Far fewer know how to actually build one. In my LinkedIn Learning course, I walk through the two drivers that matter most—clarity and empathy—and how they shape everything from team priorities to collaborative culture. You'll learn how to spot what's actually holding your team back, how to set priorities that stick even as things change, and how to build the kind of shared understanding that makes collaboration feel natural instead of forced. If you're ready to move your team from good to high-performing, this one's worth your time. Click here to get started.
|
Join 25,000 other leaders who receive my twice monthly tips on building high-performing teams.
You’ve probably felt both sides of this. You have an open role and a stack of applications, and somehow nobody in the stack looks ready. Meanwhile, someone you know, maybe a former colleague’s kid or a recent grad you’ve mentored, has sent out two hundred applications without landing a single interview. Both of those things are true at the same time, and the gap between them is getting wider. The numbers are stark. The Federal Reserve Bank of New York found that unemployment for college...
Think about the last time a piece of work moved between two of your teams. The deal that closed and got thrown over to delivery. The candidate who went from the recruiter to the hiring manager. The project that left design and landed in build. Somebody promised to loop you in, and what arrived was a forty-message forwarded thread and the word "thoughts?" Somewhere in that gap, something everybody knew stopped being known. Here's a question worth answering honestly: who owned that transition?...
Think about the best person on your team, and where they actually learned what they know. It almost certainly wasn't a training program. It was some stretch of tedious, repetitive work (the reports nobody read, the calls nobody wanted) that you'd automate tomorrow if the right vendor showed you the right demo. That matters, because the costliest automation mistake happening right now doesn't look like a mistake. Stanford's Digital Economy Lab tracks payroll data for roughly one in six...