Sunday, 10 January 2010 00:00

Fire the Bastards... and Other Conflict Resolution Techniques

Rate this item
(0 votes)

Conflict resolution is a major part of recovering red projects. The solutions range from firing the bastards to analyzing where the sources of conflicts are and determining a more friendly way to resolve them. I have to admit, when stepping into a project where the estimate at completion is a couple million dollars over the budget, everyone is pointing fingers, and the customer is screaming the supplier is in default, replacing people is sometimes the best option. So much so, my kids occasionally refer to me as 'hatch.'

Case Study: Removing Team Members

In some severe conditions, people may need to be removed. Contrary to common belief, this can have a very positive effect. At one client, nearly two-thirds of the team was going to be laid off in a work force reduction scheduled in a few weeks. All laid-off workers would be given a severance package. However, one individual refused to do requested work and was being non-professional, dishonest and exhibiting behavior destructive to the team. He had been warned of his negativism and was finally recommended for termination—a week prior to the layoff. There was a lot of hesitation since he was on the list for the layoff. The issue was pushed based on the reasoning that letting him go would show the remaining team that management was intolerable of his toxic behavior and would take action. Eventually management gave in and terminated the person. After the layoff, many of the remaining team members commented and thanked the recovery manager for showing fairness and stopping the insanity. They saw the action as positive and as a sign of being able to trust management. Sensible action and control was being applied to the situation.

Do not get me wrong, there are times when termination is the route. Waste no time in releasing destructive team members. The team performs better, not because they are scared that they are next, rather that they are pleased to see some leadership that is stopping the insanity.

Strategic or Tactical

There are more subtle forms of conflict and kinder methods of resolution. Some so subtle the project sponsor is unable to see the conflict and needs help understanding the core problem. For instance, a few years ago I was assigned to a project and had a very difficult time getting people to understand the project was ill defined. The customer's documentation clearly stated the goal of the project was to assess the problems with an existing tool and "stop the bleeding." A tactical solution was a good approach since they were hesitant to invest money in something they may throw away in a few years. Even though this project was listed as tactical, the budget was $1.8 million. The year prior, a similar project was proposed with a budget of only $800,000. Further investigation uncovered statements in the proposal documentation saying, "fifty percent of the code would be reusable." (I am still wondering how they planned to test this.) These seemed a little incongruous with an "extremely tactical project," so I escalated it to the Project Sponsor. Here I ran into something unexpected. The newly assigned sponsor had not been part of the original definition. He put project scope at the top of the triple constraints. The sponsor gets what the sponsor wants, they have the budget.

Tactical Strategic
$800,000 $1.2 Million
Existing Programming Platform New Programming Platform
Stop the Bleeding 50% reusable code
  1. Cost
  2. Timeline
  3. Scope
  1. Scope
  2. Timeline
  3. Cost
Figure 1. Showing the Conflicts

I shook my head and moved on to initial design meetings. Here the architect defined a solution that entailed moving the system, rather than fixing the existing one, to a different platform and enhancing the product to provide the base functionality. In doing this, multiple tasks were added to the activity list. One, titled "Refactor Struts to JSF," looked as if it was stepping way outside the tactical definition. To help me out, the schedule stretched out and the required budget suddenly jumped $400,000. That did it, this was just wrong.

I put the data that I had into a simple table (Figure 1) to present to executive management. I am sure that the nearly 25% increase in budget caught their attention first, but rest of the data allowed them to draw their own conclusions on the how the project's intent had shifted. Within the course of a couple days, the project sponsor had an epiphany and the project was drastically scaled back.

Evaporating Clouds

Critical chain advocates approach the problem from a very different angle—the evaporating cloud. They actively look for the conflict and focus on the problem's root cause. For instance, let's take the following conflicting opinions:

Evaporating Cloud
Figure 2. Evaporating Cloud
  1. Letting the team talk to the customer will cause scope creep;
  2. To gather requirements the team must talk to the customer.

The problem is diagrammed to show the need, translate customer needs into a product, and the resulting logic to get to this result. Figure 2 illustrates this simple case. Boiling the conflict down into two diametrically opposed statements, the analyst can arrive at the conflict and work on the root cause. The theory says at core of the conflict is an incorrect business assumption. In this case, the errant thought may be that the project team will increase scope or an intermediate analyst will be unable to get the correct definition. Proper education and leadership will avert the conflicting concerns. The critical chain team would look for the incorrect assumptions and work at resolving them.

Of course if you fail to resolve it this way, just fire the bastards. (You know I am kidding, right?)

Read 8074 times

Related items

  • Filling Execution Gaps: Building Success-Focused Organizations

    Executives define vision, strategy, and goals to advance the business. Projects enable companies to meet those goals. Between strategy and projects, there is a lot of work to be done—work that lays the foundation for project and operational success. Through experience and research, six common gaps exist in organizations that inhibit project success—absence of common understanding, disengaged executive sponsors, misalignment with goals, poor change management, ineffective governance, and lackluster leadership.

  • Get Recognized as a Leader: Four Core Leadership Actions

    Leaders make decisions. This requires a core set of actions to gather the best information, hear out the concerns of others, and making a decision that everyone will follow—even if they do not necessarily agree with the decision. This session covers the four core leadership actions (listening, dialog and discussion, selling a vision, and elimination of blame) that are critical in your journey as a leader. We discuss and practice these actions in small role-playing groups.

  • Build Your Leadership Style: Six Leadership Strategies

    As project managers, you need to change your leadership style based on the situation. The need for a situational style is more important in project management than in nearly any other business position. Commanding the six core strategies—directive, expert, consensus, engaging, coaching, and affiliative—allows you to build the style most appropriate for the conditions surrounding the project.

  • Develop Your Inner Leader: Nine Leadership Traits

    One cornerstone of leadership is our personality traits. Project managers need to develop and hone nine core traits—accountability, ethics, inspiration, decisiveness, awareness, empathy, confidence, focus, and humility—to ensure they can lead our diverse workforces. This track session is a deep dive into these traits using a roundtable discussion format—the audience voices there opinion of what the trait is and the presenter moderates the discussion and gives guidance on what that means in a business setting.

  • Extreme Leadership: A Matter of Life and Death

    Leadership is a journey. Events in our personal and professional lives shape us as leaders. In a heartbeat, how we lead and its impact can change our lives, those of our loved ones, and the people around us. The most trying of these events come in our personal lives. Personal events, such as serious illness or death of a loved one, are high-stress, emotional situations where we must be leaders with little or no authority. A skill that is also indispensable in the office, for instance, when working for a difficult boss, being fired, or any number of other circumstances where we have little or no control. These “leadership passages” shape us as leaders. Understanding how these situations affect our leadership strategies, traits, and actions that make up our leadership style, helps us overcome seemly insurmountable challenges.

Leave a comment

Filling Execution Gaps

Available Worldwide

Filling Exectution Gaps cover

Filling Execution Gaps is available worldwide. Below are some options.

 

PG DirectLogo
Limited Time Price $20.99
Amazon logo
Book or Kindle
Flag of the United States Canadian Flag Flag of the United Kingdom Irish Flag Deutsche Flagge
Drapeau Français Bandiera Italiana PRC flag
Japanese flag
Bandera de España
Flag of India
Bandera de México
Bandeira do Brasil
Flag of Australia
Vlag van Nederland
DeG Press Logo
Barnes and Noble Logo
Books a Million Logo
Booktopia Logo
Worldwide: Many other
book sellers worldwide.

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

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Sitemap