Sunday, 29 May 2011 00:00

Passionately Dispassionate

Rate this item
(1 Vote)

People routinely ask me the question, "What do you do when you find yourself on a project that is a hopeless failure?" It was raised again a few weeks ago in a Focus.com roundtable and then last week in an interview with Andy Kaufman. It only matters if the executives above the project are ignorant to how dire the situation is. It is tricky, trying to convince someone that they have a problem when they refuse to acknowledge the obvious—a tough and politically dangerous sell. The general consensus is "dust of the résumé." However, there is a logical approach to the problem—be logical.

 

Optimism, Negativism, and Realism

The three "-isms"—optimism, negativism, and realism—must be conquered. The situation is difficult. Optimism is the trait people commonly attribute team players. Blindly promoting how successful a project will be drowns the cries of the realist. Report it as you see it and you run the risk of sounding negative. Management overlooks the pragmatist setting themselves up to be errantly led down a rose laden, but thorny, path. Management has neither the time nor inclination to suss out whether the realist is being objective or confrontational. Therefore, it is incumbent on realist to sell his or her assets. This is a slow process of analyzing, predicting, mitigating, and reporting. In time, people see the value and gravitate toward the realist for comprehensive assessment.

Dispassionate And Committed

The predicament is passion. In the corporate world, passion, zeal, and enthusiasm are virtues. They also beget evangelists, zealots, and bigots—the antithesis objectivity. Brushing aside risk pre-destines operations to devastation from unmitigated menaces and inadequate contingencies. Management hires a hero to ride in for the rescue. Our culture adores heroes, teams are envious, and companies lose.

Dispassionate and committed is the answer—commitment to success and dispassion of the answer. Finding the data that substantiates or refutes solutions to issues will lead you to finding the answer. Presenting management with a concern accompanied with a mitigation or solution is critical to running a successful project. This is the single most important trait for any project manager and is essential to fixing failing projects. There is no place for reaction. Every action must be well conceived and fact based.

Want to read more?

Projects take more than managers, they need leaders. Leading is a special set of skills that one needs to hone and develop. We have numerous white papers on the topic. One, Transforming Project Managers Into Project Leaders talks specifically about what a PM must do to become a leader.

Patience Grasshopper

Will the analytical approach make you the instant hero? No. On the contrary, it can make you a pariah. If you want instant fame, this is not your job. Patiently pointing out the hurdles and developing solutions is difficult work. It is far from the ostentatious white knight galloping in on his stead to solve the project's ills.

Recently, I described how I discuss PMOs with customers:

I ask them to tell me what a PMO is. I listen to their attempts to assign traits. "It provides governance," "It monitors projects, measuring their progress consistently so we can compare two dissimilar projects," "It makes sure projects are following the right process," and so forth. Trying to get them to realize that these are solutions, I reframe the question, "What does the acronym mean?" In harmony, I get "project," "program," and "portfolio" followed by "management office." Those three P's define wildly different scope. After people look at themselves for a few moments, I ask, "If we have trouble agreeing on the 'P', then maybe it will help to know what problem you are trying to solve." [...] Eventually someone gets to the point, "Our customer does not like what we are building for them." Now, that is a problem.

People first have to come to the realization that they are asking the wrong question. It is senseless to go against their perception of reality. They must go through the process of discovery and you are their guide. It is the subtlest form of leadership.

Have A Plan

When you find yourself in any situation where you can clearly see the answer and management has not come to that same conclusion, facts are your only way out. Provide a concise description of each problem and the ways to solve them. Remove yourself from the fray scuffling in a religious war over which solution is better and resort to reality. Be the honest broker, never taking sides. Ensure everyone is aware of the solution's strengths and weaknesses. Eventually you will be seen as the real savior of the project. If your case is contrary, resort to rule one—dust off the résumé.

Read 10163 times

Related items

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • The Executive-Project Manager Gap

    It was such an innocuous question, "Working on an article; what is the biggest problem you see with project governance at orgs? Can you comment?" Can I comment? Really? That is like cheese to a mouse. Where could I start—bureaucracy, draconian process, poor executive sponsorship, disengaged leaders? Plenty of fodder, because they all lead to project failure. I fired off, "Creating an over bureaucratic morass stifling innovation & implementing process instead of cultivating leaders." Then the maelstrom started and it went directly to the gap between the executives and projects managers. Naomi Caietti, Robert Kelly and I had a great conversation. Most of the thread is below.

  • Disband Your PMO

    After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.

  • The Catch-22 of Organizational Change Management

    "Kotter, ADKAR, or CAP which methodology should we be using to build our approach to improving project adoption?" I hear this question repeatedly from people trying to implement an organizational change management (OCM) program. The problem is that is the wrong question. Take a perfunctory peek at any of the models and you will see that in the quest for an answer people have mistakenly jumped over the first few steps and they head down the road of failure. It is a Catch-22; unless you already have an OCM process in place, you will most likely fail at implementing it. Putting one in place, however, is a change—one of the most difficult cultural transformations your company will undertake. As a result, people jump to the solution stage, which is well down the change management process path (which, they did not know, ironically, since there was no procedure in place).

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

Sitemap