Monday, 14 December 2009 00:00

The Honest Broker

Rate this item
(0 votes)

Objectivity is paramount. Above all Recovery Managers need to be honest brokers. They must look at every situation (before they become issues) and determine a fair and equitable approach. Allegiance to any party on the project is certain failure. Why? Recovery Managers are mediators in a negotiation process. Only fair and objective treatment of the project team, suppliers and customer will allow the recovery manager to reach an acceptable recovery goal.

A Negotiation Process

Yes, negotiation. To resolve the issue, negotiation is the primary non-technical skill required. Recovery Managers need to be in the center of a project looking honestly at both the supplier's and customer's interests in the project. They need to objectively assess the problems and conflicts and provide fair and equitable resolutions. Fact-based nonpartisan decisions will win the project participants' respect and enlist cooperation.

Case Study: The Stockholm Syndrome

Shortly into an audit, on what would turn out to be a very difficult recovery, I was working remotely from the team at the customer's site. The Project Manager entered my office and declared, "We are concerned you are experiencing the Stockholm Syndrome." Being unfamiliar with the term, I asked for clarification. The PM explained it was named after an episode that occurred in Stockholm in the 1970s when armed robbers took bank workers captive. The hostages began to identify with and grow sympathetic toward their captors.

To say the least, I was surprised that uncovering facts about the project would meet with such an analogy vilifying the customer and me. It revealed the degree of animosity in the project.

The real problem was that I was treating the customer fairly, listening to their grievances and about to uncover issues with the PM. These issues included the PM's unwillingness to address customer issues, inability to resolve problems in the project team and lack of communication with the customer, to name only three of the major problems on the project.

This is a difficult task. Being human, opinions form quickly. People like to please others and being objective in a highly partisan environment is exhausting. Recovery Managers, however, need to be agnostic. It is critical the solution is viewed as being objective and devoid of bias. Without this, the solution will be unacceptable to a large portion of the stakeholders and the Recovery Manager's job will be impossible.

Too many times the organization paying for the recovery wants the Recovery Manager's allegiance. This might seem reasonable, but partisan Recovery Managers will be unable to achieve concessions from other groups when issues arise. This will lead to more difficulties in trying to implement a solution and executing the new plan.

This is the reason enough for the Recovery Manager to report to the Steering Committee. Their duty, being a mixture of suppliers and customers, is to focus on a successful project, as opposed to laying blame or having one group edge out another.

Separate Agendas

When people have a separate agenda inside the project, friction always arises. These may be people pushing for a specific solution, trying to promote a product, service or themselves. An honest broker must meet these situations openly and honestly by asking the Steering Committee for direction. It should be a topic of discussion in meetings. A stated direction to use a product or service is not a hidden agenda. If the team is unaware of the direction, then perception is as bad as if it were reality. People should follow the direction or be removed from the project.

How About the Project Manager?

Sit back, think about this. Help me understand how this is any different from how any Project Manager (not to mention a leader) should act. The Project Manager needs to have this same objectivity. When dealing in facts, many of the common project level problems (scope creep, communication breakdowns, risk control and so forth) never become big issues. In fact, objectivity provides the Project Manager with the tools to address the big killers of projects—senior management's ineffective involvement and lack of direction. Cold, hard facts are very powerful and the most effective tool to thwart management's inaction. Reread this article and replace the 'Recovery Manager' with 'Project Manager' and you will see that everything still applies.

Read 3527 times

Related items

  • Process Mapping

    Process is at the core of any business. It makes work predictable, repeatable, and transferable. Without it we cannot scale our businesses. However, process can be a bane to making progress. Processes that work for a $10 million company have difficulties supporting a $30 million company. Trying to scale them to a $300 million company will not only fail but not address the issues that larger companies have that were never dreamt of in a smaller organization. Processes need to be discarded, revamped, and built—all of that without creating an overburdening bureaucracy.

    Anytime you need to go someplace, you first have to know where you are. Processes are never static and your company's current state is probably far from where you think it is. Hence, the first step is mapping out you company's current state followed by defining the future state. This is more than a logical map of the process; it must also include physical maps. Whether your process is solely to provide a service (say, website development) or physical (say, manufacturing) there are logistical issues that complicate the process flow. Without fully understanding those nuances, future state processes will not reach the desired efficiencies.

    For more information about process mapping fill out the form to the left and we will get in touch with you.

  • 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.

  • Tales of an Expert Witness: Sex, Lies, and Video Tape (Part II)

    Trust relationships, certifications, and standards sound like such a safe harbor. These sound like such great words in a proposal or statement of work. How could you possibly go wrong building a trusted relationship with a customer by committing to follow a standard? In fact, this can burn you… in court.

    No one ever starts a project with the goal of ending up in court. In fact, litigation may never cross your mind; after all, you have built a trusted partner relationship. Taking a few cautionary steps, however, will make your life easier if you end up in that ill-fated litigious position. Your best chances for success come long before you enter the courtroom—even before the project starts.

  • Comparing Organizational Change Management Models

    A few weeks ago, I set out to write a post on the comparison of various organizational change management (OCM) methodologies and realized that would be a disservice to my readers. It would simply drag you down the path of implementation while failing to focus you on building the foundation. The pressure was too much and I have relented to numerous requests on making that comparison. The caveat is that juxtaposing these models is not comparing different varieties of oranges or even apples and oranges; we are surely comparing the peel to the fruit they contain. Hence, comparing methodologies like Kotter's model (the peel), Prosci's ADKAR (the core), and General Electric's Change Acceleration Process (the whole fruit) need a different approach.

  • 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.

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