|
When a project drags to the very last minute—again—it's tempting to assume your team just doesn't care enough to start early. But that instinct is almost always wrong, and acting on it tends to make things worse. Procrastination isn't really about laziness. The research points somewhere more useful: it's about stress. When a task feels important, ambiguous, or high-stakes, our brains generate a negative emotional response—and because we're wired to avoid negative emotions, we avoid the task that triggers them. That single insight reframes everything. A team that keeps stalling usually isn't unmotivated. They're working without a clear picture of what's expected, what "done" looks like, or whether they're even heading the right direction. When people don't know those things, they stall. That's not a character flaw. It's a structural problem, and structural problems have structural fixes. The fix most managers reach for is the one that backfires. Checking in more, layering on deadlines, building in fake early due dates, quietly tightening the grip—it all feels responsible, but the research on micromanagement is consistent: it produces lower morale, higher turnover, and less output, not more. The behavior meant to speed your team up is the very thing slowing them down. What works instead is quieter and more deliberate, and it comes down to five moves:
None of this requires becoming the boss nobody wants to work for. It just requires treating procrastination as the stress signal it actually is, and building the structure that lets your best people do their best work. If you want the full breakdown—including the exact questions to ask in your next one-on-one—I put it all together in this week's video.
Here's some more resources I recommend: Align your team to what actually matters: Most team dysfunction isn't a people problem—it's an alignment problem. When individual incentives drift from organizational goals, everyone loses. In my LinkedIn Learning course, I walk you through how to connect your team's purpose to the broader mission, set goals that actually align with strategic priorities, and keep everything on track through regular, impactful huddles. Check it out here. Three things great teams have in common: After years of studying high-performing teams, the research keeps pointing to the same three fundamentals: shared understanding, shared trust, and shared purpose. Employees on positive teams are 2.3 times more likely to be highly engaged. That's not a rounding error—that's the difference between a team that delivers and one that barely gets by. I filmed a full keynote speech on exactly this. Research, examples, practical tools, and a few stories about group projects gone wrong that will feel uncomfortably familiar. Watch the full talk here.
|
Join 25,000 other leaders who receive my twice monthly tips on building high-performing teams.
You've probably got a dashboard somewhere that says things are fine. Few problems reported, most metrics green. Here's an uncomfortable thought: that might not mean you have few problems. It might mean you have a team that learned not to report them. That's the real lesson buried inside one of the most famous business turnarounds of the last twenty years—and it's not the one that gets taught. In December 2009, Domino's did something almost no company ever does. They bought national TV time to...
You know the type. They announce a bold new priority in the all-hands meeting with zero warning. Two weeks later, it's a completely different priority. They run on urgency, change, and a little chaos — sometimes a lot of it. When you were an individual contributor, that kind of leader was mostly a problem for happy hour. Once you became a manager, their chaos became your job. You're now the buffer between the noise at the top and the people counting on you to help them do good work — whether...
Most advice on managing teams assumes everyone works for you full-time, in the same building, on the same schedule. That assumption hasn't been true for years. Your team probably includes a freelance designer juggling two other clients, a fractional product manager who vanishes after Monday's standup, or a part-time engineer with more experience than half your full-time staff. Leading a team like this isn't just "regular management, but smaller." The rules actually change. Here's the core...