Seven Patterns That Kill Projects

Picture this: Your team is great. You've got capable people. Everyone's committed to making this work. When people ask for specifics about how certain things will get done, you find yourself giving reassurances... "We'll figure it out," "Our team always comes through," "We've handled tough projects before." And you believe it. Your people are resilient. They'll make it happen.

But you're also getting questions you can't quite answer. How exactly will this integration work? What's the backup plan if the timeline slips? Who's actually going to do this work? The answers feel fuzzy, but you're confident the details will sort themselves out. They always do. Your team will step up. That's what they do.

What's actually happening: You're operating on faith instead of planning. The belief that "it'll all work out" has replaced the hard work of figuring out how it'll work out. Your team isn't asking for reassurance... they're asking for information, clarity, and realistic plans. But instead of specifics, they keep getting platitudes. The leadership optimism isn't grounded in anything concrete. It's blind faith masquerading as confidence.

Why this kills projects: Eventually, "we'll figure it out" runs into reality. Your capable people can't make up for lack of planning, unclear roles, or impossible timelines just by working harder. When the project struggles, leadership is genuinely shocked. You believed in your people... and they did step up. But no amount of effort can compensate for fundamentally unrealistic expectations.

Picture this: Some people weren't thrilled when the decision was made. They raised concerns early on, but leadership moved forward anyway. Now they've accepted their assignments. They're not arguing anymore. They show up to meetings, they listen, they take notes. But something feels off.

The work doesn't quite get done on time. Or it gets done, but barely... just enough to technically complete the task. When you follow up, you get reasonable explanations: priorities shifted, something urgent came up, they needed clarification but didn't want to bother anyone. You know these people aren't excited about the project, but they're professionals. They said they'd do it.

Progress feels slower than it should be. You find yourself having to follow up multiple times on things people already agreed to handle. It's frustrating, but you can't quite call it resistance. They're doing what you asked... sort of.

What's actually happening: People have reasons not to want this to succeed. Maybe they've seen initiatives fade away before and don't believe this one will stick. Maybe they still fundamentally disagree with the direction and think time will prove them right. Or maybe they're scared... scared this change eliminates their role, diminishes their value, makes them replaceable. When people believe a project threatens their livelihood, it's human nature not to help it succeed. So they comply on the surface while doing the minimum beneath it. Waiting. Stalling. Protecting themselves.

Why this kills projects: Work happens to the letter of what was asked, but not the spirit. Momentum bleeds away slowly. By the time you realize it's not just "busy people" or "competing priorities"... it's passive resistance rooted in fear, disagreement, or skepticism... you've lost months. Trust is damaged. And the people who were waiting you out feel validated that they were right not to commit.

Picture this: You greenlit this project. You picked someone to lead it... someone capable who knows the business. You made it clear this is important and they have your support. You tell them to come to you if they need anything.

But you're busy. You've got a lot on your plate. You trust the project leader to handle things. When they bring you decisions, you often tell them to make the call... they're closer to it than you are. When they mention resources are tight or there are conflicts, you encourage them to work it out. You don't want to get pulled into every detail.

Lately though, things don't seem right. The timeline is slipping. People seem frustrated. You're hearing that resources keep getting pulled back. When you ask about it, you get reasonable explanations, but you're starting to wonder if something bigger is going on.

What's actually happening: Saying this project is important isn't the same as actively protecting it. The project needs you clearing obstacles before they become crises. It needs you protecting resources when operations tries to reclaim them. It needs you making decisions and ensuring they stick. It needs you resolving conflicts that the project leader can't resolve on their own. Your "come to me if you need anything" approach puts the burden on them to fight their way to you... when what they actually need is you providing air cover without being asked.

Why this kills projects: Without you actively protecting the project, other executives don't prioritize it. Resources get pulled away. Decisions get delayed or ignored. Conflicts drag on. The project leader is working hard but losing battles they can't win without your authority. By the time you realize the project needed more than your verbal support, months are gone and momentum is lost.

Picture this: The project got approved. People were assigned to make it happen. It was assumed they'd be able to make time to work on it alongside their regular jobs. That's how things work around here. When something important needs to get done, our people make it happen.

But now the timeline is slipping. The work is taking way longer than anyone expected. When you ask why, you hear about people being overwhelmed, competing priorities, things falling through the cracks. You're frustrated. Why is this taking so long? These are capable people.

What's actually happening: Nobody really understood how much effort this would take. People were assigned work without much discussion about capacity. Maybe there's a weekly project meeting on everyone's calendar and that's about it. But the work requires way more than that. People are trying to fit project work into the margins of their regular jobs. Context switching is killing productivity. When operational work and project work compete, operational work always wins because that's what keeps things running.

Why this kills projects: Your people are doing their best with an impossible situation. Project work happens in whatever time is left over... which isn't much. Quality suffers. Timelines slip. People burn out or start quietly disengaging because the project feels like extra work with no relief from their regular responsibilities. Your project leader can't fix this because the problem isn't management... it's that the work was never realistically resourced in the first place.

Picture this: The project has a deadline. Maybe it's tied to fiscal year end, a customer commitment, a board presentation, or avoiding another year of licensing costs. The date matters. Everyone knows it. It's not negotiable.

But things aren't going according to plan. The work is taking longer than expected. Issues keep popping up. People seem stressed. Tired. Things feel urgent all the time. But the deadline is the deadline. Your people will make it happen. They always do.

What's actually happening: The timeline is fixed. The work is the work. The team is the team. Something has to give. But the scope hasn't changed, nobody's been freed up or added, and the deadline isn't moving. So your people are trying to make up the difference through sheer effort. They're working nights and weekends because they're loyal and they want this to succeed. But effort can't solve a math problem. Quality is being sacrificed. Mistakes are compounding. The harder everyone pushes, the worse it gets.

Why this kills projects: Something in that equation has to adjust. Without adding capacity, reducing scope, or moving the timeline, you're just burning out your most loyal people. Quality craters. Mistakes pile up. Your best people start quietly looking for exits. When you finally hit the wall, the project is in worse shape than if you'd made the hard trade-offs months earlier.

Picture this: You asked someone to lead this project. Someone capable who knows the business. You made it clear they're accountable for delivery. Their name is on it. You're counting on them.

But things aren't moving as fast as you expected. Decisions seem to take forever. When you ask why, you hear about needing to build consensus or get alignment. Resources that were supposed to be dedicated keep getting pulled back into operations. When you ask your project leader about it, they mention conflicts or obstacles, but you're not sure why they can't just... handle it.

Sometimes you wonder if they're strong enough for the role. They seem to escalate a lot of things that feel like they should be able to resolve on their own. You find yourself thinking they need to be more decisive, more assertive...to take ownership.

What's actually happening: Your project leader is fighting battles they can't win. Everything is a negotiation. They're competing for resources with people who outrank them. They're trying to coordinate across departments that don't have to listen to them. When tasks slip or quality is poor, they have no authority to push back. Maybe you announced them in the role but haven't visibly backed them since. Or maybe their authority was never made clear to the organization. Either way, there are no consequences when people ignore them. Even trained project managers can struggle without formal authority. But leading cross-functional change is radically different from leading within your own area. Technical expertise doesn't translate to organizational influence.

Why this kills projects: Without real authority and your visible backing, every day is a battle your project leader loses. Resources get reclaimed. Decisions get overridden. Work slips with no accountability. Your capable person burns out trying to negotiate their way through obstacles that require executive authority to remove. The project stalls. And when it fails, you'll wonder why they couldn't lead effectively... when the reality is, you never gave them the organizational power or protection to do so.

Picture this: You set up oversight for this project. There's a steering committee with the right people. Regular meetings. Updates get shared. Issues get discussed. It looks like proper oversight.

But somehow, the same issues keep showing up meeting after meeting. Decisions that need to be made... who's ultimately accountable, how conflicts get resolved, what happens when deadlines slip... those don't seem to get decided. People give updates. Everyone nods. The meeting ends. Then next time, it's the same conversation.

You're starting to notice attendance dropping off. Or people showing up but clearly distracted. Nothing ever seems to get resolved. No one's driving. When deliverables slip, there are no consequences. It's starting to feel like everyone's just going through the motions.

What's actually happening: The oversight structure exists on paper, but nobody's actually steering. Meetings are information-sharing, not decision-making. The hard questions... who's really in charge, what gets prioritized when resources are tight, what happens when people don't deliver... those never get answered. No one wants to be the person making tough calls. So issues get discussed, acknowledged, and tabled. Again and again. The oversight you set up has become a charade. Everyone shows up, but nothing of substance happens.

Why this kills projects: Problems that require executive decisions just sit there, unresolved. The project has no real direction because no one at the top is actually steering. Accountability doesn't exist because there are no consequences. The team watches this happen and loses faith. By the time you realize the oversight structure is theater, months are gone and the project is adrift.