IT projects frequently fail or run over time and budget due to a complex mix of technical, organisational, and human factors. While many of these issues are not unique to IT, they are amplified in this domain due to the rapid pace of technological change, complexity of systems, and lack of maturity in IT project management compared to other engineering disciplines. This discussion explores several core reasons for IT project failure—scope issues, intangibility, stakeholder resistance, and lack of long-term experience—and examines how effective risk management can mitigate these risks.
________________________________________________________________________________________________
________________________________________________________________________________________________
Scope Creep, Ambiguity, and Overreach
One of the most cited reasons for IT project failure is scope creep—the uncontrolled expansion of project boundaries without corresponding adjustments in time, budget, or resources. This often occurs because:
-
Initial requirements are poorly defined or incomplete.
-
Stakeholders request new features mid-project.
-
Project teams underestimate the technical effort required.
Ambiguous or shifting scope can lead to missed deadlines and budget overruns. In IT, where change is easy to initiate (e.g. a small code tweak), there is a tendency to add functionality without formal controls, leading to bloat and burnout.
💡 Risk management can reduce this risk by requiring thorough requirements analysis, formal change control processes, and regular scope reviews tied to cost-benefit assessments.
Intangibility: Difficulty in Visualising and Measuring Progress
Unlike civil engineering projects where progress is visible (e.g. foundations laid, walls built), IT project deliverables are often intangible until late in the development process. This leads to several issues:
-
Stakeholders struggle to conceptualise what is being built.
-
Testing and usability problems are discovered late.
-
Progress may be overestimated, masking deeper issues.
This intangibility also makes it harder to measure outcomes against expectations until the end, at which point correction is costly.
💡 Risk management practices, such as regular demonstrations, prototypes, and user feedback loops (e.g. Agile sprints), can help surface problems early and reduce surprises at go-live.
Stakeholder Resistance: Cultural and Organisational Barriers
IT projects often involve changes to how people work—automating processes, centralising data, or eliminating roles. As such, they encounter resistance from stakeholders, including:
-
End users who fear job loss or increased scrutiny.
-
Managers who feel disempowered by automation.
-
Teams that prefer legacy systems they are familiar with.
This resistance can manifest as non-cooperation, delays, or sabotage, especially when change is imposed without adequate consultation or communication.
💡 Risk management can identify potential resistance early. Change management strategies—such as stakeholder mapping, communications planning, and user training—should be embedded in project risk registers.
Lack of Long-Term Experience in IT Project Delivery
Compared to construction or manufacturing, IT project management is a relatively young discipline, and suffers from:
-
Inconsistent use of formal methodologies.
-
Inadequate understanding of software development lifecycle (SDLC).
-
Underestimation of complexity, especially in integration and data migration.
IT professionals may be technically strong but lack experience in estimating effort, managing vendors, or aligning projects with strategic goals. This lack of maturity leads to naïve optimism, under-planning, and failure to anticipate known risks.
💡 Risk management frameworks (like PRINCE2, PMBOK, or ISO 31000) bring structure, discipline, and historical data to improve forecasting and resource planning.
________________________________________________________________________________________________
Sign Up Here:
________________________________________________________________________________________________
How Effective Risk Management Helps
Risk management is an ongoing cycle of the identification, evaluation and mitigation of risks.
A disciplined approach to risk management can significantly reduce the likelihood and impact of IT project failures:
|
Risk Management Activity |
Contribution to Success |
|---|---|
|
Risk identification |
Early recognition of likely problem areas (e.g. integration risks, stakeholder resistance). You can use tools like a PESTLE or SWOT analysis to identify key risks |
|
Risk analysis |
Prioritisation of effort based on an assessment of likelihood and impact. Part of this assessment will depend on understanding your appetite for risk. |
|
Mitigation planning |
Proactive steps to reduce likelihood (e.g. vendor due diligence, scope lock-in). You can find out more about different types of risk mitigation here. |
|
Contingency planning |
Backup plans for when things go wrong (e.g. rollback strategies). |
|
Monitoring and control |
Ongoing oversight to adjust plans as new risks emerge. |
When integrated with best practice, user-centred design, and change management, risk management helps anticipate failure points, aligns expectations, and builds in realistic buffers for uncertainty in any IT project.
Conclusion
IT projects are vulnerable to failure due to factors like scope volatility, the intangibility of deliverables, stakeholder resistance, and a lack of accumulated project wisdom in many organisations. These issues can be addressed through structured and mature risk management practices that help anticipate, plan for, and respond to threats. In an environment where complexity is the norm, risk management is not an administrative overhead—it is a critical success factor.
________________________________________________________________________________________________
Gain the practical skills you need to identify and manage risk with this five-star rated training course.
Available in person, online or in-house the focus on practical skills and unique post-course support you get by learning with us will ensure you and your organisation can tackle this key governance activity with confidence.
________________________________________________________________________________________________