No time to lead? Then prepare to fail

Technology projects rarely fail because the technology does not work. They fail because nobody with enough time, authority and judgment is leading them. Research cited by the Institute of Electrical and Electronics Engineers and industry publications puts the share of troubled projects at about 70 percent, and the common thread is leadership rather than code.

Imagine the monthly steering committee of a company that is replacing its core commercial platform. The project is eleven weeks late. The executive sponsor joins twenty minutes into the meeting, between two other calls, and asks for a summary. The project manager reports on tasks completed but not on decisions pending, and three of those decisions, on data ownership, on process exceptions and on who approves scope changes, have been waiting for a month. Everyone in the room is competent and busy. Nobody has the time to lead.

The cost of that scene rarely appears on a budget line. It appears in missed sales cycles, in teams that disengage, in vendors who bill for rework and in customers who experience the old system for another year. This article argues that leadership is the scarcest resource in any technology initiative, that it can be described concretely, and that executives can organize their calendars and their governance to provide it.

Why do so many technology projects fail?

Have you ever wondered why some technology projects succeed while others stall along the way? Recent research conducted by the Institute of Electrical and Electronics Engineers, the IoT Journal of Data Science and Analytics, and IoT Magazine reveals that 70 percent of technology projects fail due to poor management. The figure is consistent with what independent studies of transformation show. A McKinsey Global Survey of 1,793 participants, fielded in January 2018, found that only 16 percent said their organizations had improved performance and sustained the gains, as set out in McKinsey's study of digital transformation success.

What decides the outcome in the remaining minority? The answer lies in the leaders. Having skilled and committed people who take responsibility for coordinating and overseeing every stage, from conception to implementation and evaluation, is crucial. A McKinsey & Company report points to effective leadership as a key element for success in the digital transformation of companies, and according to the study the authors consulted, organizations with effective leaders are 70 percent more likely to achieve their transformation goals.

The McKinsey material that is publicly available points in the same direction, though with different numbers. Companies in its survey that engaged a chief digital officer were 1.6 times more likely to succeed, and nearly 70 percent of respondents said their top teams had changed during the transformation, often by adding leaders who understood digital technology. A separate 2018 McKinsey survey of 1,733 C-suite executives found that making the transformation a top priority for senior leaders made beating profit expectations 1.5 times more likely, according to McKinsey's analysis of how to improve the odds of success. The precise multiples differ by study, but the message does not. Where senior leaders own the result, projects are more likely to deliver it.

What does effective leadership of a technology project look like?

To be a good leader of a technology project is to combine a handful of qualities that are easy to name and hard to sustain. Taken together they describe the person an executive should look for, and the support that person needs from the organization.

A clear vision. A successful leader sees the ultimate goal of the project, can visualize the desired outcome and communicates it so that the team understands why the work matters. The vision acts as a beacon for decisions and actions throughout the project. It is also what differentiates an exceptional leader, because the ability to convey it with conviction generates enthusiasm and commitment, which in turn raise motivation and performance. In practice, the vision should be expressible in one sentence that a salesperson or an operator would recognize as relevant to their day.

Strategic planning. The leader must build a solid plan to reach the objectives. That means identifying tasks, allocating resources efficiently across the team and estimating the time each task requires, then setting a realistic schedule that anticipates possible delays. A detailed schedule breaks the work into smaller activities with deadlines, which makes progress easier to track and delays easier to detect early. Risk management completes the picture. Considering different scenarios and keeping a contingency plan for unforeseen events is not pessimism, it is what lets a team absorb a surprise without losing a quarter.

Decision making. During any project, decisions arrive constantly. An effective leader makes informed and timely decisions, weighing the factors involved and their implications. The word that matters in that sentence is timely. A good decision made three weeks late often costs more than an adequate decision made on the day it was needed, which is exactly what the pending items in our steering committee illustrate.

Problem solving. Projects present obstacles. The successful leader identifies problems quickly, finds effective solutions and knows how to use the strengths of the team and foster collaboration to overcome blockages efficiently. They treat a problem as shared information rather than as an individual failure.

The ability to motivate and guide. A good leader maintains a positive working environment, recognizes individual and collective achievements, supports professional growth and aligns everyone around the objectives. This is not about enthusiasm in speeches. It is about making sure each person understands how their contribution connects to the result.

Effective communication. Clear communication is a critical skill. The leader conveys information accurately and concisely and also listens to the needs and concerns of the team. Communication fosters collaboration, prevents misunderstandings and makes problem solving smoother. Power skills of this kind are not soft. The Project Management Institute reported that, among organizations that prioritize them, 72 percent of projects met business goals, with communication, problem solving, collaborative leadership and strategic thinking singled out as the most critical, according to the PMI Pulse of the Profession 2023.

What does weak project leadership look like in different industries?

The symptoms differ by sector, but the diagnosis is usually the same. Three illustrative scenarios show how the absence of leadership time appears in practice.

Imagine a manufacturer replacing its planning software. The vendor delivers on schedule, but production planners keep using spreadsheets because nobody resolved how the new system would handle rush orders. The sponsor, a plant director, assumed the IT team would settle it. IT assumed operations would. The system is live, yet the benefits are not, and a year later the company concludes that the software was the problem.

Imagine a retail bank modernizing its customer onboarding. Compliance, product and digital teams each hold part of the process, and each has a legitimate reason to ask for changes. Without a leader who has the authority to arbitrate, the scope grows with every meeting. The launch date moves twice, the team works evenings, and when the product finally reaches customers it carries compromises that nobody chose deliberately.

Imagine a distributor adopting a CRM and a customer portal at the same time. The regional managers are enthusiastic in kickoff and absent afterwards, because their quarter is demanding. Adoption depends on the sales representatives, who copy what their managers do, and their managers are not using the tool. In each case the technology was adequate. What was missing was a leader with enough time, authority and credibility to resolve the open questions and to model the new way of working.

Six disciplines that keep a project on course

Leadership qualities need to be translated into habits, and six disciplines recur in projects that deliver. The first is setting clear and realistic goals. Goals should be specific, measurable, achievable, relevant and time-bound, and they must be communicated so that everyone understands what is expected. A goal such as "improve the customer experience" is an aspiration. "Reduce the time to resolve a service request from five days to two by the end of the third quarter" is a goal a team can plan around.

The second discipline is proper planning. That means taking the time to break major tasks into smaller steps, set realistic deadlines, consider the resources needed and keep a contingency plan for unforeseen events. Teams that skip this stage tend to discover its value around the middle of the project, when the cost of correcting course is highest.

The third is efficient resource allocation. Assess the skills and capabilities of the team, distribute responsibilities fairly and account for the material and technological resources the project needs. A frequent mistake is to assign the most capable people to a project in addition to their regular duties, which guarantees that neither receives their best attention.

The fourth is constant monitoring of progress. Establish milestones, conduct periodic evaluations and use project management tools to keep an up-to-date record of tasks completed, deadlines met and emerging problems. Monitoring is not a reporting ritual. It is the means of seeing decisions that are waiting and risks that are growing while there is still time to act.

The fifth is fostering collaboration and support. A working environment where team members feel comfortable sharing ideas, asking questions and exchanging information produces better solutions and earlier warnings. Open communication and recognition sustain motivation and commitment over the many months a significant project requires.

The sixth is flexibility. Projects involve unexpected changes and challenges, and the team must be ready to adapt. Anticipating obstacles and developing contingency plans keeps the project on track, but adaptability is what ensures that the plan serves the objective rather than the other way around. For a broader view of how these disciplines fit into a transformation, see 6 Steps That Bring Your Business Closer to Digital Transformation.

What happens when leaders are always putting out fires?

While these disciplines are useful, in the world of technology projects it is common to find ourselves constantly putting out fires. Emergencies, unexpected problems and interruptions divert attention and consume time and resources, and the project leader is usually the first person to be pulled away. The danger is an endless cycle of problem solving in which the urgent always displaces the important and nothing moves forward.

The way out is to chart a course and focus on good communication. Reserve fixed time each week for the decisions only the leader can make. Agree in advance which problems the team can solve without escalation and which require the sponsor. Keep a visible list of open decisions with owners and dates, and review it at every meeting before reviewing tasks. This turns firefighting into a managed flow, and it signals to the organization that the project has the sponsor's attention. The same principle appears in the digital transformation office as a driver of cultural change, where a small permanent team gives leaders the capacity to govern rather than react.

What this means for the C-level

For the chief executive, the question to ask of every major technology initiative is who owns the result, and how many hours per week that person has available. An initiative with a sponsor who cannot attend decision meetings has a leadership gap regardless of the quality of the vendor or the plan. Naming a business owner, not only a technical one, and protecting that person's time is the cheapest risk mitigation available.

For the chief financial officer, the practical lever is stage-gated funding tied to decisions and outcomes rather than to elapsed time. Releasing budget when milestones and adoption indicators are met makes leadership visible, because it creates a recurring moment in which someone must account for the state of the project. It also gives early warning of the cost of delay, which in many companies shows up first as rework and extended vendor contracts.

For the chief commercial and customer officers, the point is to convert and to retain. Commercial teams experience every poorly led project as lost selling time, inconsistent data and tools that customers notice. Asking that front-line leaders participate in design and testing, and that their goals include adoption, aligns leadership of the project with leadership of the customer relationship.

How to start next Monday

An experienced consultant would begin with a thirty-minute conversation with the person leading your most important technology initiative. Ask three questions. What decisions are waiting on you or on someone above you? How many hours this week were available for this project? What would you stop doing if you could? The answers usually reveal more than the status report.

Next, list the open decisions, name an owner for each and set a date. Place that list at the top of the next steering meeting. Within a few weeks you will see which decisions are repeatedly postponed, and those are the places where governance or authority is missing. Finally, review whether the sponsor's calendar reflects the project's importance. If it does not, either the calendar or the priority needs to change, and it is better to decide which than to let the project decide for you.

As you move forward, keep an open and flexible mindset. Even with meticulous planning, challenges will arise, and creative solutions often come from the team when leaders create space for them. The success of a project depends largely on leadership and management skills, a clear vision, sound strategic planning and the ability to make informed decisions.

How ICX Consulting helps

ICX Consulting is a commercial strategy and customer experience firm based in Miami, working with companies in the United States and Latin America. In technology and transformation programs we act as the independent layer that aligns business owners, IT and vendors around outcomes, using the ICX Transformation Framework to define scope, decisions, governance and adoption before the build begins. Our change management practice works with sponsors and managers so that leadership behavior supports the new way of working, and our transformation roadmap service turns ambition into sequenced, funded initiatives with clear owners.

If you want a structured starting point, use the ICX Transformation Framework Toolkit to map responsibilities, decisions and milestones for your next initiative, and see our practical guide to the step-by-step roadmap to implement digital transformation.

Frequently asked questions

Why do technology projects fail?

Most fail for organizational reasons rather than technical ones. Typical causes are unclear ownership, decisions that wait for weeks, sponsors without time, scope that grows without arbitration and teams that are not prepared for the change. Technology problems exist, but they are usually solved quickly when leadership is engaged.

What makes a good technology project leader?

A good leader combines a clear vision, realistic planning, timely decision making, problem solving, the ability to motivate a team and effective communication. Equally important are authority and time. A capable person without the mandate to arbitrate or the hours to dedicate cannot lead, however skilled.

How much time should an executive sponsor dedicate?

There is no universal figure, but the sponsor should be reachable for the decisions only they can make and present at the recurring steering meetings. A practical test is whether any decision has waited more than a week for the sponsor. If so, the sponsor's availability is a project risk to be managed.

How can leaders avoid constantly firefighting?

Reserve fixed weekly time for decisions, define which problems the team can resolve without escalation, and keep a visible list of open decisions with owners and dates. Review that list before reviewing tasks. This keeps urgent issues from displacing the important ones that determine whether the project delivers.

If a critical initiative in your company is running late or depends on a handful of overloaded people, an outside view can help separate leadership gaps from technical ones. Talk to an ICX consultant through our contact page and we will help you decide where leadership time should go before the next milestone slips.