Adelina Karpenkova

Adelina is a Marketing Manager at CodeControl.

Why Your Tech Project Can Fail and How to Avoid the Failure

Project Management Institute claims that one out of four organization’s projects failed outright. The numbers are far from being encouraging.
With an increasingly competitive digital landscape, it’s almost impossible to predict project success and totally eliminate risks. But still, every project failure affects negatively not only your business KPIs but also your employees’ retention and motivation.
So how to reduce risks and avoid common mistakes of project management? In this article, we’ll highlight seven reasons why tech projects fail and give you some actionable tips to avoiding it.

Reason 1. Lack of communication

The gap between executives and counterparts in the product, engineering, design, and marketing often causes serious consequences.
First of all, it often happens that senior management or sponsors don’t spend much time getting involved with the project. They provide their requirements and wait for teams to produce the desired result. Not being able to ask questions or suggest changes, teams are forced to continue developing ‘blindly.’
On the other hand, tech experts are rarely sociable enough. The common belief that nobody but the IT department can understand what’s happening leads to a lack of accountability. If your tech lead can’t convey the project details to the non-tech executives, your project totally depends on a group of people within one department, which is a huge mistake.

Reason 2. The requirements aren’t communicated clearly

In the early stages of project development, everybody has own view on how everything should be done. In a perfect world, the opinion of all counterparts should be heard and taken into account.
However, in the real world, 39% of projects fail because of bad requirements. It means that business stakeholders often move forward with their requirements without getting input from employees responsible for the product.

Reason 3. A real user need isn’t solved

It has something in common with the previous parts. This time the problem concerns your relationships with customers. Requirements are often defined by an intermediary who fails to consult or involve people who will eventually use the product.
Not knowing your real customers’ needs will definitely result in a failure. So, before starting a project you need to answer one simple question: ‘Does anyone need what we are going to build?’

Reason 4. Estimating issues

Although it’s impossible to predict how much time the project will take, there are lots of serious issues that can be avoided only by taking the estimating process more seriously.
As people who actually perform the work often are rarely allowed to take part in the estimating process, the estimates often appear to be too far from reality.
Moreover, to make the project seem more attractive, estimates may be arbitrarily cut, which leads to setting unreasonable deadlines. Hurrying up to finish the project, the team may overlook or deliberately skip some crucial aspects.

Reason 5. Failure to plan

Diving into the performance without thinking is another reason for project failure. The problem is often caused by underestimating the project’s complexity (see Reason 4).
Here are the most common planning issues:
Not discussing clear roles and responsibilities.Teams follow their own schedule not first getting corresponding commitments from other members who also have to commit to the schedule.Not adding a risk or contingency buffer to the project timeline.Not breaking a large scale action plan into separate more manageable pieces.

Reason 6. No sufficient tracking

Not tracking your project, you can’t address occurring issues in the early stages. Such delays later result in other knock-on problems.
Being ready to update the schedule is crucial. With sufficient monitoring, you can notice that the project is running into difficulties and fix it without serious consequences. However, missing this moment, you’ll have to spend much more money and efforts redoing the work done.

Reason 7: Decision-making problems

Critical decisions are often made by people having little practical experience in the area. On the other hand, teams working on the project avoid making decisions no to be responsible for future consequences.
Moreover, not tracking the project (see Reason 6), stakeholders aren’t aware of the unscheduled issues and fail to make the right decisions.

How to avoid the failure

Even the best ideas fail to be successful when poorly translated into actions. I circled out 10 crucial project management tips that will help you prevent project failure:
1. Learn what your audience needs: ask your sales team for feedback, read reviews for similar projects, talk to people that are likely to use your product or service directly.
2. Take time to conduct additional market research and analyze other niche players’ experience.
3. Involve people who will actually perform the work to the estimating process.
4. Don’t make firm estimates but encapsulate the unknowns.
5. Establish effective communications between groups involved in the project.
6. Engage technical lead to provide clear and concise reports.Consider the opinion of all counterparts at the early stages of project planning.
7. Encourage executives to be involved in the project.
8. Plan beforehand: set clear roles, make sure different teams’ plans correspond, add a risk contingency, etc.
9. Always keep monitoring and analyzing intermediate results.
10. Be ready to respond to changes.
Regardless all the recommendations you can find on the Internet, hiring tech people being a non-tech person is a challenge (and I doubt whether you should accept it). If you have little experience in project management and your internal specialists are already over capacity, you can always hire remote workers. Such companies as CodeControl or Honeypot can help you hire talented freelance developers or even get assembled project team within several days.

Tags

Comments

August 20th, 2019

Great article, thank you. You can write thousands of pages on why projects fail but I will add a few more:
1- Failure to get “buy-in” from the C-suite (or executives with the right level of seniority)
2- Project taking too long to execute , making the requirements obsolete before implementation has finished (which is why Agile was invented)
3- Inaccurate estimations, running out of money before project is finished
4- Too many “chiefs” in the project , no clear chain of command

Sarah

August 21st, 2019

Everything you mentioned in the article makes sense and of these, number three is the most important to note. A need is not solved.

If a product or service is not solving a need in a more efficient manner as compared to the products and services already available, that startup is set to fail.

I remember reading an instagram post. It said: people still were able to share pictures on Facebook when Instagram wasn’t there.

Instagram made sharing pictures more fun. That’s how startups should look at their products.

August 21st, 2019

The one mistake startups do many times is being too stiff. In the beginning, one needs to be agile. There are many changes that are required on the path to development. In such a case, by sticking to that one idea that you think is “perfect” slowly kills your progress.

It was a great read. Thanks.

Topics of interest