The world has changed. This is why? Smartsheet transforms your work.

Why are so many IT projects failing? IBM estimates that only 40% IT projects reach their budget, schedule, or quality goals. It is important to question why projects fail. It is possible to learn from past failures and avoid repeating the mistakes. It is better to not make the same mistakes as another person. Learn from five of my biggest project failures.
Seven years ago, I was a project manager. I learned everything about project management through the mistakes of others. I made mistakes in estimates, forgot to ask clients key questions during kickoff meetings, hesitated saying no, and answered questions reactively, before I checked with my team. I made all the rookie mistakes that can lead to embarrassing moments when I realize I was wrong.
Even though I don’t have any direct memories of project management mistakes or other obvious errors, there are still many lessons to learn from each project. It is not always as easy as it seems, even when things go wrong. Despite my many years of experience as a project manager, I have seen many projects fail spectacularly. I learn a lot from them and can use it to improve my next project.
Why do projects fail so often?
Hence, projects often fail. Here are five of the biggest mistakes I made in project management, and the lessons that I learned.
#1. #1.
This is a problem that remote developers and designers have to deal with. Although I have spoken about this before, I have been guilty of it many times. It is a human instinct to not draw attention to yourself when things go wrong. This is counterintuitive to the very nature of project management, but poor communication is often what causes projects to fail.
I must admit that it was difficult to notify clients about the status of their project due to the fact that they had a difficult client and a tight deadline. This is especially true for projects that have been quiet for a few weeks or days. This is also the most vulnerable time in your project timeline. It is crucial to maintain and foster trust with clients in your web project manager. It’s easy to lose trust. This lesson was hard for me to learn several times too many.
Lesson learned:
When I have to deliver hard news to a client I often ask myself if it is better to do it now than wait until it’s too late. It’s better if you do it now and take action. You’ll be happy you did.
#2. #2.
My teammate and me were working together on a very complex project last winter. He suggested that we use a new plugin to create a portfolio section on a client’s site. Although the slider used a different framework than we normally use, it looked and performed better than the one we had. Although I was initially skeptical due to the strict timeline and the specific design direction of the slider, I was eventually convinced by its promise of better functionality for the client and our development team. Although we hadn’t discussed upgrading our standard toolkit, the timing was perfect and it was a chance to see the new plugin in action.
The end is probably clear: the slider was both expensive and time-consuming. The slider didn’t support the key feature we needed after installation. It also didn’t support responsive sizing or part.