In the world of IT, projects do crash and burn.. a lot of times lately. When things go wrong, who’s to blame? Before you go on a witch hunt for the next responsible person, you ought to dig deeper for you to come up with a permanent solution. It’s never an easy job though, but doable nonetheless. While it’s better to talk about why IT projects succeed, to know why they fail can help improve the chances for many of us who are missing goals terribly. According to a recent study featured by Cio.com, 50 percent of companies had experienced IT project failure in the last 12 months. You start to wonder if there’s a shortage of project managers or skilled IT workers (or both).
Don’t Blame It on IT
Let’s set aside for a moment this tech fiasco where Obamacare is concerned. While working as a software developer helped me acquire logical and problem-solving skills, I just feel it’s totally unfair to blame it all on IT when things go wrong. Did you know that most IT project fail because of poor management? It’s very rare that failure is due to major technical hurdles. Key to the success of any undertaking is assigning the right tasks to the right people, plus, defining clear goals and responsibilities. Just because developers are working in tech doesn’t mean expecting them to behave like computers too. When leadership is lacking, programmers can get lost in a maze of confusion (not to mention, frustration).
The Constantly-Evolving Role of Project Managers
Gone are the days when managers send out orders to be followed by their minions. The role has evolved into something so dynamic that it involves human relations. It’s not only making sure that deadlines are met and everyone adhere to best practices, but project managers should also communicate and motivate their team to be their best. Still, we see many who are stuck in the old mindset that they’re not ready to implement change management, no matter how Agile they think they are. One of the biggest failure that a project manager can commit is not aligning goals between team players and stakeholders. They’re supposed to bridge the gap and create trust; instead, they are putting everyone on gridlock until everyone decides to quit and call it a long day.
Looking at the Real Problem
Because it’s easy, when IT projects fail – people will simply look at the IT department to blame. It’s not really the case. Most of the time, it’s lack of resources that contributed to the failure. As enterprises move to the cloud, we see demands in adopting more application, adding to the backlogs of the IT team. Nobody really cares how people work on it so long as it’s delivered in lightning speed. Soon, your team feels overworked and confused on what to prioritize first. While you can argue that this can be easily fixed by project managers, most often, they add to the burden by simply not admitting that there’s a problem in the first place. You can’t blame them though when they’re expected to run things to spotless perfection. Should the founders be blamed then for such unrealistic expectations? Accountability should run from top to bottom, no exceptions!
No matter, if you embrace failure as a testing ground instead of your final destination, you might just win the race to the next disruptive technology around.
**Something new is coming. Stay Tuned!