o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o- -o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o
Software projects fail because of people -- not processes. After more than 20 years of working on software projects, the most consistent culprit isn't the technology or the timeline. It's the human factor. Specifically: a lack of empathy, a lack of planning, and a lack of communication.
Why Do Software Projects Fail?
There's one fundamental reason many software projects fail -- because we're all human. And that's more than a trite saying.
No matter how hard we try, we aren't perfect robots creating perfect products. We're people trying our best to help other people have better experiences. It's usually our attempts to hide those imperfections that gets us into the most trouble.
We try to focus on the business and what makes sense to the bottom line. We pour money and resources into projects and set hard deadlines meant to keep us on track and in scope. We assume that if we establish the right process, everything will fall into place.
In this series of blog posts, we're taking a deeper look at three human reasons software projects fail.
What Are the 3 Human Reasons Software Projects Fail?
1. Lack of Empathy
There's a reason we start every Drawbackwards project with research. It establishes empathy as a core focus of the end product.
If you don't know what your users, stakeholders, and teammates need, you'll have a hard time knowing when you've been successful. Empathy isn't a nice-to-have -- it's the foundation everything else is built on.
2. Lack of Planning
Every project needs time, staff, and budget. Every project also needs the flexibility to scale up or down to find the right balance of all those things.
You can't do that without planning and allowing for adjustments along the way. Rigid plans that can't bend tend to break -- and they take the project with them.
3. Lack of Communication
The most human factor of them all is also the trickiest to master. The key is finding the right way to make sure everybody is on the same page as priorities change.
Misalignment doesn't always announce itself. It builds quietly, and by the time it's visible, a lot of damage has already been done.
How Do You Actually Fix These Problems?
Our goal with these posts isn't to show you how to avoid these mistakes. Rather, we want to show you how to lean in with empathy.
By acknowledging the challenges the people in front of -- and behind -- your software projects face, you can better set them up for success.
That's the through-line across all three of these reasons: people. When you keep people at the center of how you plan, communicate, and build, projects have a much better chance of going the distance.
FAQ
Why do most software projects fail? Most software projects fail because of human factors, not technical ones. The three most common causes are lack of empathy for users and stakeholders, lack of flexible planning, and poor communication across the team.
What does empathy have to do with software project success? Empathy helps teams understand what users, stakeholders, and teammates actually need. Without it, there's no clear definition of success -- and it's very hard to hit a target you haven't defined.
How does poor communication cause software projects to fail? Poor communication leads to misalignment on priorities, assumptions that go unchecked, and decisions made without the right people in the room. By the time the problem surfaces, it's usually expensive to fix.
What kind of planning do software projects need? Good planning isn't just about setting timelines and budgets. It also means building in flexibility to scale resources up or down as the project evolves. Plans that can't adapt tend to collapse.
Is this a problem with process or with people? Mostly people -- but in the best possible way. The goal isn't to engineer the human element out of software projects. It's to lean into it, acknowledge the challenges people face, and build processes that support them rather than ignore them.
Get Educated