Who Is Responsible When IT Projects Fail?
Why Digital Transformation Success Depends More on Organizational Maturity and Collaboration Than on Technology Alone
Imagine a large organization launching a business intelligence (BI) implementation project.
The contract has been signed, the contractor selected, the infrastructure put in place, and the IT team has spent months designing and implementing management dashboards.
Yet a year later, the project has still not achieved its intended results.
The finance department fails to provide the required information on time. The human resources department uses different definitions for certain performance indicators. Operational departments disagree about data accuracy, and some managers still prefer to receive their reports in Excel spreadsheets.
Eventually, the project falls behind schedule, and a familiar question arises during a senior management meeting:
“Why has the IT department failed to deliver the expected results?”
And attention usually turns to the IT manager.
But were all the factors determining the project's success really under the IT manager's control?
Could the IT manager have resolved conflicting definitions across organizational departments single-handedly? Compelled managers to use the dashboards? Guaranteed the quality of data generated by other departments? Or overcome employees' resistance to change?
These questions lead us to one of the most important realities of IT management:
IT projects may be implemented within the IT department, but many can succeed only through organization-wide collaboration and maturity.
When We Label an Organizational Project an IT Project
One of the most common mistakes organizations make is classifying projects solely according to the technology they involve.
Because a project involves software, databases, servers, or artificial intelligence, responsibility for it is naturally assigned to the IT department.
In reality, however, many of these projects extend far beyond technology.
For example, implementing an enterprise resource planning (ERP) system is not simply a matter of installing and configuring software. It also requires reviewing business processes, defining responsibilities, standardizing information, and changing how work is performed.
A business intelligence (BI) project involves more than building dashboards. Its success depends on organizational agreement about performance indicator definitions, data quality, and decision-making processes.
Similarly, an artificial intelligence (AI) project is not merely about choosing a model and developing algorithms. It requires reliable data, a clear understanding of the business problem, collaboration among specialists from different disciplines, and organizational readiness to use the results.
Therefore, many projects that appear to be IT initiatives are, in fact, organizational transformation projects enabled by technology.
This distinction is critically important.
If we misunderstand the true nature of a project, we are likely to define its governance structure, responsibilities, resources, and even success criteria incorrectly.
The IT Manager Is Responsible, but Not for Everything
Emphasizing organizational responsibility does not mean that IT managers bear no responsibility when projects fail.
On the contrary, the IT manager is one of the key contributors to project success and must be accountable for decisions and actions within their authority and responsibilities.
Selecting an appropriate architecture, assessing technical requirements, managing infrastructure, ensuring information security, integrating systems, overseeing contractors' technical performance, managing technology risks, and providing transparent project progress reports are among the essential responsibilities of this role.
The IT manager must also understand the organization's actual needs, communicate technical limitations, correct unrealistic expectations, and report project risks to senior management before they develop into crises.
However, an IT manager cannot reasonably be expected to independently reform every organizational process, resolve all management disputes, establish data ownership across departments, or transform employees' work culture.
Responsibility must be aligned with authority.
If an organization expects its IT manager to successfully deliver an organization-wide project, it must also provide the necessary authority, management support, and mechanisms for involving other departments.
Otherwise, the organization is holding a manager accountable for outcomes that depend on factors beyond their control.
Senior Management: An Irreplaceable Driving Force
In major IT projects, senior management support is not an added advantage. It is one of the fundamental prerequisites for success.
The CEO and senior executives play a role that no contractor, software solution, or IT manager can fully replace.
They can establish the project as an organizational priority, assign departmental responsibilities, resolve cross-functional conflicts, and allocate the resources required for implementation.
However, genuine senior management support goes beyond signing a project initiation document or approving its budget.
Support becomes meaningful when senior executives remain actively involved throughout implementation.
When two departments disagree about data ownership, there must be a clearly designated decision-making authority.
When a middle manager refuses to cooperate, an accountability mechanism must be in place.
When implementation requires changing a long-established process, senior management must support the necessary change.
And when the project enters its operational phase, senior executives must use its outputs themselves.
Consider an organization that has invested substantially in business intelligence, while its CEO continues to request management reports exclusively in traditional formats.
What message does this send to other managers?
Unsurprisingly, many of them may see little reason to change their established working practices.
Senior management does more than sponsor a project. Its behavior and decisions determine how seriously the project is taken throughout the organization.
Resistance to Change: A Barrier That Technology Purchases Cannot Remove
Many IT projects encounter difficulties during adoption and actual use, even when their technical design is sound.
Employees may feel uneasy about changing familiar ways of working.
Middle managers may believe that a new system will introduce greater transparency into their departments' performance.
Some individuals may even perceive new technology as a threat to their positions or authority.
Such resistance is not always the result of deliberate opposition.
Sometimes users have not received adequate training, have not been involved in designing the solution, or do not yet understand what problem the new technology will solve for them.
In other cases, unsuccessful experiences with previous projects have undermined employees' confidence in new initiatives.
Therefore, resistance to change cannot be overcome simply by issuing directives or requiring users to adopt a system.
Organizations need a structured approach to change management.
Users must be involved at the appropriate stages of the project, their concerns must be heard, they must receive relevant training, and they need to see how the change benefits their daily work.
At the same time, senior management must establish clear expectations and support necessary changes to ensure that departmental resistance does not undermine broader organizational objectives.
Technology can be purchased, but acceptance of technology must be cultivated within the organization.
Organizational Maturity: The Missing Link in Many Projects
Two organizations may purchase the same software, work with the same contractor, and allocate nearly identical budgets, yet achieve entirely different outcomes.
Why?
One important explanation is the difference in their levels of organizational maturity.
An organization with well-defined processes, clear responsibilities, reliable data, a collaborative culture, and coherent decision-making mechanisms is generally better prepared to implement complex projects.
By contrast, an organization whose processes depend heavily on individuals, whose information is fragmented across departments, and whose decisions rely on informal arrangements may face serious difficulties even when implementing a relatively simple system.
In this context, organizational maturity does not mean having a larger administrative structure or more policies and procedures.
Rather, it refers to an organization's ability to make coordinated decisions, execute reliable processes, embrace change, and learn from results.
For example, before launching a business intelligence project, the organization should establish who is responsible for defining management performance indicators.
Before implementing an ERP system, its core business processes and the responsibilities of their owners should be clearly defined.
And before adopting artificial intelligence on a large scale, the organization must address data quality, accountability for decisions, and human oversight of AI-generated outputs.
Advanced technology cannot, by itself, compensate for fundamental weaknesses in organizational management and processes.
In many cases, new technology does not conceal existing problems. Instead, it makes them more visible.
Artificial Intelligence Projects: Where Organization-Wide Collaboration Becomes Even More Critical
The importance of organizational maturity and collaboration becomes even more evident in artificial intelligence projects.
Imagine a manufacturing company deciding to use AI to predict equipment failures.
The IT department can provide the necessary computing infrastructure, connectivity, security, and technical environment.
An AI specialist team can design and develop the analytical models.
But can these two groups achieve success on their own?
Certainly not.
The maintenance department must provide equipment failure data, maintenance records, and information about operating conditions.
The production department must explain operational constraints and the actual conditions under which the equipment is used.
Technical specialists must participate in interpreting the data and evaluating the model's predictions.
Senior management must also determine how the project's outputs will be incorporated into decision-making and maintenance planning.
If the data is incomplete, operational specialists do not trust the model's predictions, or no process has been established for using those predictions, even a technically sophisticated model may fail to generate meaningful operational value.
The same principle applies to enterprise AI projects, intelligent automation, predictive analytics, and decision-support systems.
AI success depends not only on the intelligence of the model, but also on the organization's readiness to use that intelligence effectively.
Business Intelligence: When Disagreement Over a Single Number Brings a Project to a Halt
In BI projects, some of the most significant challenges arise outside the programming environment.
Imagine a project to develop a dashboard displaying the liquidity position of companies within a holding group.
The finance department of one company uses a particular definition of liquidity.
Another company calculates certain components differently.
In one subsidiary, information is recorded with delays, while in another, data is extracted from several different systems.
Under these circumstances, the IT team is not dealing with a purely technical problem.
Before designing the dashboard, the organization must agree on indicator definitions, authoritative data sources, responsibility for validating data, and update frequencies.
Achieving this agreement requires collaboration among finance, planning, IT, and senior management.
Without such agreement, the technical team may build a dashboard that accurately reflects the data it receives, yet managers may continue to dispute the validity of its figures.
Ultimately, the organization may conclude that the business intelligence system is not performing adequately.
In reality, however, the underlying problem may be the absence of effective data governance and shared organizational definitions.
Business intelligence creates value when the organization reaches agreement on the meaning of information before attempting to integrate its systems.
Why Are Some Projects Set Up to Fail from the Beginning?
Not all project failures occur during implementation.
Sometimes a project is exposed to the risk of failure through poor decisions made before the first line of code is written or the first piece of equipment is purchased.
For example, an organization may decide to adopt a technology simply because it has succeeded elsewhere, without adequately understanding its own needs.
Or a major project may be approved without assigning a clearly identified business owner.
In some cases, the budget covers software and equipment purchases, while the resources required for training, process improvement, data cleansing, and post-implementation support are overlooked.
In other cases, project objectives are defined so broadly that there are no clear criteria for determining success.
Expressions such as “making the organization smarter,” “improving productivity,” or “digital transformation” do not, by themselves, constitute measurable objectives.
The organization must specify which problem the project is intended to solve, what improvements it should deliver, and how its success will be measured.
Furthermore, contractor selection should not be based solely on price or technical promises.
The suitability of the proposed solution, the contractor's delivery capabilities, knowledge transfer, security requirements, and long-term maintenance costs must all be considered.
In other words, effective project management begins with understanding the problem, not with signing the contract.
How Should Responsibility for Project Success Be Shared?
In organization-wide projects, responsibilities should be clearly assigned before implementation begins.
Senior management should assume responsibility for organizational sponsorship and support, while removing cross-functional barriers.
The IT department should be responsible for technical architecture, security, integration, and technical oversight of implementation.
Business departments should define their requirements, provide reliable data, improve their processes, and participate in testing and accepting project deliverables.
Project management should coordinate activities, schedules, resources, dependencies, and risks.
External contractors or implementation partners must also be accountable for fulfilling their contractual obligations and meeting agreed quality requirements.
In major projects, an executive sponsor, a clearly identified business owner, and an active steering committee can play important roles in coordinating these responsibilities.
The essential point is that these responsibilities must not merely be documented. They must also be accepted and fulfilled in practice.
| Stakeholder | Primary Responsibility |
|---|---|
| Senior Management | Setting priorities, providing executive support, allocating resources, and resolving conflicts |
| IT Manager | Technical leadership, security, architecture, integration, and technology risk management |
| Business Unit Managers | Ownership of requirements, processes, data, and acceptance of outcomes |
| Employees and Users | Participating in design, testing, training, and effective use |
| Project Manager | Coordinating implementation, monitoring progress, and resolving obstacles |
| Contractor | Fulfilling contractual obligations, ensuring delivery quality, and transferring knowledge as agreed |
This allocation of responsibilities helps organizations identify the actual causes of problems rather than immediately searching for someone to blame.
Has the Organization Assessed Its Readiness Before Starting the Project?
This brings us to a fundamental question:
How can an organization planning a major digital transformation, business intelligence, or artificial intelligence project determine whether it is ready for the transformation?
Does its IT infrastructure have sufficient capacity?
Are information security and risk management at an acceptable level?
Can its existing systems be integrated?
Are its IT processes adequately documented and reliable?
Is its IT strategy aligned with the organization's broader objectives?
Do senior executives support the project?
Are employees and users prepared to embrace change?
Does the organization have the necessary specialist expertise and management structure for implementation and ongoing operation?
The answers to these questions should not depend solely on managers' personal perceptions or fragmented departmental reports.
The organization needs a structured, evidence-based, and multidimensional understanding of its current state.
Its technical infrastructure may be in good condition, while weaknesses in governance, processes, or user engagement threaten project success.
Conversely, an organization may be well prepared from a management perspective but face infrastructure or security limitations that prevent reliable implementation.
Readiness for transformation is not merely IT readiness. It combines technical, managerial, human, and organizational preparedness.
Feedora: Assessing IT Beyond Equipment and Systems
One of Feedora's primary objectives is to provide a more comprehensive understanding of an organization's IT environment.
Under this approach, assessment is not limited to examining servers, networks, equipment, or software.
Feedora evaluates the state of IT from several complementary perspectives.
Its technical assessment covers areas such as IT governance, information security, infrastructure, IT service management, information systems, digital transformation, and intelligent technologies.
This assessment can help identify strengths, weaknesses, risks, and maturity levels across different IT domains.
However, understanding the technical environment alone is not sufficient.
For this reason, Feedora also incorporates nontechnical and managerial information and assessments alongside its technical evaluation to develop a more complete picture of the organization's circumstances.
These complementary perspectives address matters such as workforce structure, IT management and strategy, and other relevant organizational information.
Feedora also collects feedback from users and employees about IT services, making it possible to examine the actual experiences of those who use these services.
This is particularly important because an IT department may perform well against technical indicators while users across the organization continue to experience significant difficulties.
Conversely, some problems that initially appear to be IT-related may actually originate in weak organizational processes, insufficient management coordination, or unclear expectations.
The value of Feedora's multidimensional approach lies in extending assessment beyond equipment and systems by bringing technical, managerial, and user-experience perspectives together.
An IT assessment, of course, is not a substitute for a comprehensive evaluation of organizational culture or change readiness across every business function. Nevertheless, it can provide important evidence and indicators for identifying barriers to the success of technology-enabled projects.
From Understanding the Current State to Making Informed Decisions
Imagine a holding group planning to implement business intelligence or artificial intelligence projects across several subsidiaries.
Would it make sense to establish an identical implementation plan for every company without first understanding their current circumstances?
One company may be more prepared in terms of infrastructure, information systems, data management, and human resources.
Another may first need to improve its management processes or upgrade its infrastructure.
In yet another company, the primary obstacle may be a lack of alignment between IT strategy and business priorities.
Feedora's assessment results can help holding company management better understand differences among subsidiaries, identify significant risks, and make more informed decisions about prioritizing corrective actions.
Comparing assessment results across different periods can also help track changes and improvements within each company.
Subsequently, corrective measures and action plans can be defined and recorded based on assessment findings, creating a clearer path for organizational improvement.
Under this approach, assessment is not merely a scoring exercise. It becomes an important input into decisions about organizational readiness, investment priorities, and the actions required before pursuing digital transformation.
Conclusion: Identify the Barriers Instead of Searching for Someone to Blame
When an IT project fails, asking who was responsible is an important question.
However, if the question is asked solely to identify an individual to hold accountable, the organization may overlook the most valuable lessons from the failure.
We should examine whether the project was properly defined from the outset.
Did senior management provide effective support?
Did organizational departments accept their responsibilities?
Were users adequately prepared for change?
Did the organization's infrastructure and processes demonstrate sufficient maturity?
And did the IT manager have the authority and resources needed to fulfill their responsibilities?
The answers may reveal that some responsibility rested with IT management, some stemmed from senior management decisions, and some arose from structural and process-related weaknesses within the organization.
Successful IT projects depend on cooperation among all these elements.
An IT manager cannot transform an organization single-handedly, just as senior management cannot achieve successful digital transformation without a capable IT department.
Particularly in artificial intelligence, business intelligence, and digital transformation projects, success requires technology, management, processes, and people to move in the same direction.
Through its multidimensional assessment of the IT environment, examination of managerial factors, and collection of user feedback, Feedora helps organizations gain a clearer understanding of their capabilities, weaknesses, and risks before launching major projects or while implementing them.
Because timely identification of barriers, sound decision-making, and adequate organizational preparation can reduce the likelihood of many failures before they occur.
And perhaps, at the next meeting where a project is facing difficulties, instead of immediately asking:
“Why couldn't the IT manager deliver the project?”
We should first ask:
“Have we, as an organization, created the conditions necessary for this project to succeed?”
Feedora | From Assessment and Understanding to Action Planning