Select Page


10 Ways to Sink a Project
By André Augusto Choma

Many projects face problems for multiple reasons: problems of scope, insufficient planning and bad risk assessment are frequent nightmares in any project manager’s life. The root causes of these problems are diverse, but some difficulties are common to many projects, and, for this reason, should get more attention from the project manager and his/her team. However, when fighting against these most frequent project enemies, the project manager will reinforce his/her capacity for risk response planning and increase his/her chances for success.

This article presents ten situations that can bring project failure, with the objective of alerting project managers to some key risks that are frequently ignored during project planning and execution. In a humorous manner, I’ll approach the common causes of these problems, not with the purpose of proving that only these 10 situations should command all the project manager’s attention, but to highlight that risk prevention IS the project manager’s greatest responsibility and IS the decisive factor of success. In my next article, I will offer suggested courses of action that can be taken by the project manager to face each and every one of these 10 risk situations and in this way keep the project “floating”.

To sink a project is easy! Therefore, good project managers spend their time trying to prevent their projects from “taking on water”, whilst others wait as the water rises to their necks before looking for a solution. There are risks in every part, in projects of all kinds, sizes and budgets; and if the attitude of the “crew” is not one of prevention against the risks that can sink the project, the destiny of the “ship” is certain!

Although there are many risks imaginable, there are some risks that can be common to many different kinds of projects. The occurrence of these risks is independent of the executing company, the complexity of the scope or the size of the project budget. The fact that these risks repeat themselves in many various types of projects is precisely why the project manager needs to take advantage of the lessons learned from past projects to prevent those common (but powerful) risks from damaging the project’s “hull”.

This article discusses, from here on, ten risks that can be common to any project, and that can, alone or combined, behave like real “torpedoes” (or icebergs) that can sink your project if the necessary care is not taken.

1 – Be vague: the most generic scope keeps your client away from asking for details

Be Careful! A very well defined project scope can limit you! If too well defined, it will force you, automatically, to do exactly what was requested. What’s the problem with that? If your company made a mistake in the time or cost estimates, there won’t be a way to make any adjustments in scope to compensate for the differences.

A detailed project scope will make the client constantly complain about small particulars, generating unnecessary conflicts and taking the focus away from what really matters: to finish the project! Some clients also like to reconsider the scope after signing the contract, which can cause more conflicts with the project manager. If the commercial proposal has been approved and the contract has been signed, these discussions are unnecessary. It’s the Project Technical Team who will be in charge of executing the work in the way they know best.

If a change turns out to be necessary, during execution, the project manager can slightly alter the project scope. As long as there’s no damage to the final product, with a less defined project scope, it won’t be necessary to get client approvals for each small change. The executing team is able to define what is, technically, best for the project, based on their experience.

2 – Begin the execution as soon as possible (why spend time planning if you already know that a lot of changes will happen?)

Certainly you’ve heard someone say that “the only thing that we know for sure about a project is that changes will happen”. Time after time this is confirmed, and obliges the project manager to continually make lots of changes in the project plans. Beyond that, in the last few years, it’s been possible to see a significant reduction in the amount of time given to project execution, which can push the project manager to begin execution as quickly as possible.

Since the client is waiting anxiously for the project execution to begin (to see the construction start or to see the programmers begin to write code), the project manager shouldn’t leave the client waiting. As there isn’t always enough time for planning, this phase should not delay the beginning of the project. For sure any plans you make will change, there won’t be time enough to keep them up to date, and most likely the project manager will just file the paperwork away for “future” consultation.

Updating the project plan takes away precious time from the project manager. During that time he/she should be involved in project execution or project meetings. The project manager’s efforts must be concentrated on controlling the cost and time of the project. Only in this way will there be a much more satisfied client!

3 – Focus on the team’s work – talking too much with the client will distract you

Some clients interfere significantly in the execution of the project; constantly scheduling meetings, regularly making direct contact with other involved departments without your knowledge and, most importantly, constantly requesting changes in scope. Many times, this proximity creates dangerous interference in the work. This can result, in the end, with the client overriding the power of the project manager in front of his own team! Clients that participate too much during project execution are always demanding that the project manager report to them, influence the direction of the work and undermine the agility of the project manager to make his/her day-by-day decisions.

This excessive involvement can wear down the relationship between the project manager and the client, creating unnecessary tension, and can cause many conflicts that may cause a breach in the contract. With clients who usually micro-manage, from the beginning, the project manager should define clearly the roles and responsibilities of both parts, and show that he will not accept constant interference in the work.

During project execution, the manager should concentrate his efforts on his team’s work, focusing on the execution of the tasks and staying close to his resources. He should invest his time working with his team and insuring that the client doesn’t overstep his bounds.

4 – Don’t document the changes – this will save you from discussions with the client

Adjustments are always necessary during every project. In fact, one of the few things that a project manager knows for sure is that the project will change, independent of its kind, size or resources involved. If the project manager has to put the work on hold every time a necessary change is detected; fill out a change request, then discuss the changes with his client and get his signature on many forms, the only thing that he will get are conflicts and mistrust.

If both parts are aligned on the project objectives, and agree that some adjustments are necessary, all those many forms will only be seen as a defensive behavior from the executing company. This practice will delay the necessary changes, and will take away the agility of the project execution. It will also wear down the relationship. What is expected in a project environment is a trusting relationship; so, if both parts agree that a change is needed, the project team’s time should not be wasted documenting what’s already been agreed.

Formal change requests and impact analyses usually result in cost changes for the client, which, obviously, won’t leave them happy about the project. Beyond that, all this documentation is useless at the end of the project, so don’t waste your precious time taking care of documents that won’t be used afterwards.

5 – Exceed the client’s expectations: add extras to the project scope

Nowadays clients expect much more from you and your company. The competition is strong and you must make good use of this opportunity to earn the client’s trust. Therefore, some additions to the project scope can help you further impress your client, earning their confidence and guaranteeing future work.

These additions, big or small, must be in accordance with the wishes of the client. This will increase your cost to some extent and will, therefore, reduce the project’s profitability. However, this difference will surely be compensated for by future opportunities created as a result of this current project. To surprise the client and exceed their expectations isn’t an easy task, and will require a lot of creativity from the project manager.

As well, it will be necessary to convince your boss or bosses that the extra work is necessary and important, even if it is not part of the contracted baseline. The most important thing, at this moment, is to keep your team inside of the client’s site and to hold the competitors back. In the future, new contracts will be signed, and the lost profit will be recovered.

6 – Risk Management? Counting on your luck is the only way out!

Problems happen in all projects, even if the team has preventive action plans in place. By definition, risks are uncertain events (PMI, 2004) whose occurrence can impact the project objectives. Since the occurrence of these risks is uncertain, and the final impact is often unknown, why waste hours and hours trying to predict the future?

Even using advanced technological tools, futurology exercises or meetings using crystal balls, the majority of the time the risks occur at random, and little can be done by the project team to change this situation. The best thing to do, from the beginning of the project, is to stay focused on the execution and try to finish the tasks as soon as possible. Keep the team alert and prepared to take action to solve the problems as they happen.

Every project faces problems, and these problems can ruin the project if adequate care is not taken. The project manager and his team must be alert and solve the problems as they arise. Long planning meetings trying to predict what will happen have little effect when the time comes to deal with the risks that can happen in the future.

7 – Giving attention to quality matters most only in the final stage of the project; after all, what really counts is the ‘finished product’

Companies usually have complex quality rules, standards, forms, processes and procedures that must be followed; but if you really try to follow all the existing rules, the project will never be completed! It’s impossible to do all the tasks according to all the required processes, and many hours of the team will be consumed in endless and unproductive meetings about standards, quality plans and internal audits.

It is certain that the project’s product quality is essential, and is something that the project manager has to worry about. It is important that this quality control be rigorous only at the end of the project, to ensure that the client receives a product free from defects. The final tests are necessary, and at this time the project manager should mobilize his team to guarantee that the product meets all the pre-defined requirements.

It’s worthless to worry so much about Quality documentation that you risk loosing focus on the final product picture. What the client will notice when he receives the product is its final appearance; and if you loose time at the beginning of the project with standards, rules and forms, your product may not reach the hands of the client as early as you needed.

8 – Avoid bureaucracy – filling forms is a waste of time! This documentation will only fill up the archives!

As explained in the previous topic, nowadays companies have many different document types, processes and procedure verification forms that must be filled out throughout the project life cycle, proving that you are in compliance with the company’s rules and standards. This paperwork includes, for example:

  • Quality standards and process verification forms;
  • Project management process forms;
  • Project plan and quality plan templates;
  • WBS and schedule templates;
  • Forms for validating / changing the scope;
  • Checklists for cost and man-hour estimates;
  • Contract templates.

During the execution of a big project, hundreds (or even thousands) of hours of the project manager and all the stakeholders are spent filling out, evaluating, changing and forwarding the many different kinds of forms that there are. Just imagine the benefit for the project if all these hours were used in the execution of the project activities! Avoid losing all this precious time filling out papers that won’t in the end be useful to the project results; your company’s archives will thank you!

9 – Make the team work hard to avoid delays – overtime is essential to keep the team focused

All projects are practically BORN behind schedule! The deadline seems unachievable and the last days become a real torture! To avoid delaying the project, the team must always be “on”, that is, to keep on top of the schedule. The project manager must control all his team’s tasks to guarantee that all their efforts are being applied effectively to the project.

Overtime can often help the project manager keep the team’s dedicated spirit going the whole time, and not just during the most critical stages. This way, the project manager can keep the team’s commitment, motivation and attention to the scheduled tasks, all under his control. Projects are temporary endeavors (PMI, 2004) and, therefore, require extra energy from the team to succeed. A good project manager can get this “something else” from his/her team during the development of the project. He/she must begin to pressure the team right away, from the beginning of the project, even though there isn’t a need for overtime in the early stages. The team must know the project manager’s time expectations, and those who aren’t willing to contribute to finish the project on time, probably will have to be replaced.

10 – Get rid of the paperwork after the project close out! Past information will only take up too much space in your office!

By the time the project ends, boxes and boxes of papers and documents have accumulated in the project manager’s office, besides all the electronic files spread throughout the company’s network. Considering this historical documentation important, the project manager often decides to keep the entire project archive. This just chokes up the company’s store room. Nobody will use this material, not the same team, and not even other professionals in the company. Why keep useless material?

If a new project is beginning, all those documents will only confuse the life of the project manager. What are we doing with all this stuff? Why send it into the company’s archives, when we know that these boxes will only collect dust until someone decides to get rid of them? Wouldn’t it be better, faster and cheaper just to immediately get rid of all those, apparently worthless, piles of paper?

Andre Augusto Choma, PMP – Brazil (

André is a qualified Civil Engineer, with post graduation studies in Construction Management. His professional experience encompasses Industry Construction, Government and IT Projects, consulting (including strategic planning and portfolio management) and training.

André is a Project Analyst at IPA (Independent Project Analysis) Latin America, Brazil, and the author of “How to Manage Construction Contracts With Contractors” (, and has been a speaker in many Project Management Conferences around the world.

Recommended PM App

Recommended PM App