What makes a project failed

Through rapid-results initiatives, project team members iron out kinks early and on a small scale. Rapid-results teams serve as models for subsequent teams who can roll out the initiative on a larger scale with greater confidence. The teams feel the satisfaction of delivering real value, and their company gets early payback on its investments. Traditionally, one team might analyze customers, another select the software, a third develop training programs.

Using rapid-results initiatives, a single team might be charged with increasing the revenues of one sales group in one region within four months. Vertical, rapid-results initiatives offer many benefits.

Such activities offer cost-effective economies of scale. The key is to balance vertical and horizontal, spread insights among teams, and blend all activities into an overall implementation strategy. After only three months, the teams were meeting their goals—e.

Top management extended the rapid-results process throughout the company, reinforcing it with an extensive employee communication program.

As horizontal activities continued, dozens more teams started rapid-results initiatives. Big projects fail at an astonishing rate. Whether major technology installations, postmerger integrations, or new growth strategies, these efforts consume tremendous resources over months or even years.

Yet as study after study has shown, they frequently deliver disappointing returns—by some estimates, in fact, well over half the time. And the toll they take is not just financial. These failures demoralize employees who have labored diligently to complete their share of the work.

So project teams can execute their tasks flawlessly, on time and under budget, and yet the overall project may still fail to deliver the intended results. The key is to inject into the overall plan a series of miniprojects—what we call rapid-results initiatives —each staffed with a team responsible for a version of the hoped-for overall result in miniature and each designed to deliver its result quickly.

Say, for example, your goal is to double sales revenue over two years by implementing a customer relationship management CRM system for your sales force. Using a traditional project management approach, you might have one team research and install software packages, another analyze the different ways that the company interacts with customers e-mail, telephone, and in person, for example , another develop training programs, and so forth.

So even though they may know how to enter the requisite data into the system, they refuse. But consider the way the process might unfold if the project included some rapid-results initiatives. Team members would probably draw on all the activities described above, but to succeed at their goal, the microcosm of the overall goal, they would be forced to find out what, if anything, is missing from their plans as they go forward.

The team may also discover that it needs to tackle other issues, such as how to divvy up commissions on sales resulting from cross-selling or joint-selling efforts. A project of this magnitude entails many teams working over a long period of time, and it crosses functional and organizational boundaries. They started as they had always done: A team of World Bank experts and their clients in the country in this case, Ministry of Agriculture officials spent many months in preparation—conducting surveys, analyzing data, talking to people with comparable experiences in other countries, and so on.

Based on their findings, these project strategists, designers, and planners made an educated guess about the major streams of work that would be required to reach the goal. The result of all this preparation was a multiyear project plan, a document laying out the work streams in detail. Nobody is that smart or has that clear a crystal ball. But if the World Bank had kept proceeding in the traditional way on a project of this magnitude, it would have been years before managers found out if something had been left off the plan or if the various work streams could be integrated—and thus if the project would ultimately achieve its goals.

By that time, millions of dollars would have been invested and much time potentially wasted. As it happened, the project activities proceeded on schedule, but a new minister of agriculture came on board two years in and argued that he needed to see results sooner than the plan allowed.

Over the next few months, we worked with Piccioni to help him and his clients add rapid-results initiatives to the implementation process. They launched five teams, which included not only representatives from the existing work streams but also the beneficiaries of the project, the farmers themselves.

The teams differed from traditional implementation teams in three fundamental ways. Even though one has to stay optimistic about the future, one still has to factor in problems that might arise and possible solutions to solve them. As the saying goes, failing to plan is planning to fail. Even though the plan will change, a project has to start and you should always have a clear vision of what is to be achieved.

On the other hand, over planning and trying to think of all possibilities is totally wrong. Overplanning will paralyze you and will drain the energy and flexibility required to make a project succeed. The three main reasons why projects fail are over-optimistic milestones, lack of planning, and overplanning. Equally, I have delivered projects that failed to meet some of those criteria and it has been a big success! Assessing the characteristics of each individual project allows a project manager to set goals accordingly for each element and track the status appropriately.

Then perhaps, failure will be seen as true success. So, when executing a project, keep in mind the seven common reasons why projects fail as mentioned in this blog post and try to eliminate all these mistakes from your project management lifecycle. The ideal way out is by choosing a simple project management software that helps to manage multiple projects, teams, and tasks on a single dashboard. One such software you can try out is ProProfs Project. From defining project goals to generating insightful reports, you can do it all hassle-free!

David is a Project Management expert. He has been published in Jeffbullas. As a project planning and execution expert at ProProfs, he has offered a unique outlook on improving workflows and team efficiency.

Survey Maker Create customer satisfaction survey for free. We believe software should make you happy Learn more about us. October 12, Last modified: October 5, Do you want a free Project Management? Table of Contents. Do you want a free Project Management Software? David Miller. In fact, some project management groups estimate that as many as 70 percent of projects fail. During the course of most failing projects, there is usually a point at which it is possible to save them.

In this article, you will learn how to recognize the signs that a project may be failing and how to recover. According to the Project Management Institute PMI , a project is temporary, with a defined beginning, end, scope, and resources. It is unique and works toward a singular goal.

Projects often include people who do not regularly work together. The discipline of project management concerns the application of knowledge, skills, tools, and techniques for the purpose of meeting the requirements of a project.

Organizations have long practiced project management, but it became a profession in the midth century. Today, there are several certifications for project managers. Every organization has a different definition of what constitutes a project failure. Often, it means a project is over budget, over deadline, or over schedule. It can also mean it did not satisfy stakeholders. Of course, a failure can consist of any combination of these reasons.

A failed project can be demoralizing for the people who worked on it, especially if they did not see it coming. It can be a blow to your ego or self-esteem to be the leader of a failing project, but it is a big lesson learned as far as what to do or what not to do next time. Smartsheet is a cloud-based platform that allows teams and organizations to plan, manage, and report on projects, helping you move faster and achieve more.

See Smartsheet in action. Watch a free demo. It is often difficult to pinpoint why a project fails. Sometimes, there is a trigger event, but failure usually happens after many problems surface. The main causes of project failure are inadequate planning, insufficient resources, and deficient leadership and governance. Through his company eCameron , he is often the person that companies bring in to help them salvage their failing projects.

To extend the metaphor, there is usually a lot of blood, and the first step is to stop the bleeding. Then, you figure out what to do next. He uses a similar process for projects, controlling the obvious problems and then looking for what caused them. As mentioned above, there are three main root causes of project failure: inadequate planning, insufficient resources, and deficient leadership and governance. Inadequate risk management.

He notes that executives often do not have project management experience and do not understand everything that goes into completing a project. Planning is what happens before work on a project begins and is often where projects begin to fail. When beginning a project, many managers keep a triangle in mind. PMI refers to this concept as the iron triangle. The iron triangle highlights the constraints of project management that impact quality: scope, time, and cost. When a project begins, a manager tries to keep the triangle as equilateral as possible.

As a project progresses, changes in one constraint impact the others, and it is up to the manager to make trades between constraints. One big problem with planning often involves the scope of the project. Scope has a way of changing or creeping, and when it does, it often means more money, time, and people.

Unclear goals, objectives, and deliverables can lead to scope changes. The project can also be too complex or too oversimplified to fit into its initial scope. He explains that, by definition, scope creep is uncontrolled change to a project. Along with the changes in scope, bad estimates about time and resources can cause problems for project managers. Inaccurately estimating the time necessary for a project leads first to the unrealistic commitment of time and people, and ultimately, to project failure.

Differing expectations can also lead to project failure. Project planners sometimes have different views about the quality and standards a project should have. When these contradictory views compete, the schedule and the budget can take priority over quality, practically guaranteeing the defeat of a project.

Problems and setbacks are inevitable in almost any project, and neglecting to plan for them can cause a project to fail. It is impossible to predict everything that could possibly happen, which is why it is crucial to have a contingency plan in place in case some parts of the project take extra time or cost more than originally planned. Poor planning is one key reason projects fail, but issues with resources can also lead to failed projects. Picking the wrong people or not having enough people to work on a project can lead to failure.

Finding warm bodies to put on a project instead of waiting for the correct personnel can mean people lack the expertise they need to do the job. Involving the client in the process of selecting qualified staff can help you avoid a gap in proficiency. The [senior] leaders might not have an understanding of how things get done. Because projects often involve people who do not usually work together, team issues frequently arise.

Projects can fail because of something a team did poorly or failed to do, and interpersonal issues and friction can put a team in turmoil. Coordination and communication — both among team members and from project leaders — can be a deciding factor between success and failure.

Leaders often do not clarify roles and responsibilities for individual team members, which leads to confusion. Project managers think in terms of scope, schedule, and budget, while executives think about value and the bottom line. The terminology can differ greatly. In turn, these sentiments can translate into an absence of accountability and a poor attitude. Training is vital. Getting everyone who is involved in the project to understand the skills they will need is necessary for the project to be successful.

When looking at training requirements, project managers often overlook the potential for technology problems or the need for task-specific equipment. Unrealistic estimates regarding both budgets and personnel can also cause failures. Planners often cut the former and the latter to make a project seem more attractive to either management or a client.

Not allocating enough time to complete a project is another way to end up with shoddy work. Hofmeyer suggests having a senior leader kick off a project by conceding that leadership does not have all of the answers — this approach encourages critical thinking and discourages passive resistance among team members.

Hofmeyer also recommends keeping an eye on cultural differences within project groups. For instance, some people are brought up to always say yes and be positive, even when things are not going well.

They will not speak up to raise a red flag. In addition to projects failing because of planning and resources, they also fail because of poor leadership and governance. Because of this phenomenon, new items become part of the scope, teams do not have enough time, budget overruns occur, and projects fail.

Poor leadership does not necessarily indicate you have a poor project manager — it can also be an indication of an unsupported project culture, bad executive leadership, or an absence of consensus among stakeholders. Arriving without a plan to turn the failure around is unlikely to be well received. In general, the conversation regarding project failure should be had face to face. If you cannot arrange a meeting in person with stakeholders then you should try and arrange a video call.

Email messages leave too much space for misinterpretation of the facts and communicating failure in this way is unprofessional. Be prepared for your client to respond in a worried or angry manner. Hopefully, once you have finished sharing the information and explained the plan going forwards, relations will improve. It is crucial to be honest about what has happened.

Accept responsibility if necessary and use your leadership skills to explain what will happen next. Above all else, remain professional throughout the conversation and stick to the facts. The reality is that we all make mistakes and projects rarely run completely smoothly. The important thing is to learn from the mistakes and make yourself a better project manager going forwards. Here are the important things to remember if your project has failed:.

Really it should start with an agreement on the scope at the start of the project and then change control from that point forward. Trying to recover once you have overspent is going to be a difficult negotiation. Try getting some of your senior managers involved. Your email address will not be published. Save my name, email, and website in this browser for the next time I comment.

This site uses Akismet to reduce spam. Learn how your comment data is processed. Home Courses. Step 1.