"Cut them loose"

Summary: People are the most important asset of any project, team, or company. Good people working together, sharing a common vision and motivated to achieve common goals, will bring success to any venture.

People are the most important asset of any project, team, or company. Good people working together, sharing a common vision and motivated to achieve common goals, will bring success to any venture. Conversely, the presence of conflicting personal goals and agendas contributes significantly to many IT failures.

Failures can arise when team members emphasize personal agendas with higher priority than shared project goals. In starker terms, when personal goals and ambitions undermine or damage a project, there's a big problem. When senior managers engage in this behavior, the situation becomes intolerable.

Eric Benhamou, networking industry pioneer, describes how he responded to undermining executives while CEO at 3Com. From an excellent interview conducted by Sramana Mitra (emphasis below was added):

The two founders of Palm, Jeff Hawkins and Donna Dubinski, were in my office explaining to me why I really should not buy Palm and that I should just spin it out. They preferred to be autonomous.

They decided to part ways; it was an abrupt separation. At the time I felt good about it because I did not think that they were going to be serious players inside the company, they would only help themselves but not me. Usually when you go through a fickle situation, you have to find out who is on the boat with you rowing, and they were not rowing on my account.

What a great description of the problem and solution. No matter how valuable someone might be, regardless of their great talent and vision, if they undermine your project, cut them loose.

Topic: CXO

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

14 comments
Log in or register to join the discussion
  • Undermine your project?

    Pretty subjective, I think if a person is tasked appropriately and has well defined objectives - they wouldn't be able to "Undermine the project" as it is put. The big issue is that project managers don't know how to leverage the talent on the project team, and haven't established good milestones to look to for success. bleh...
    BreakFix
    • So what

      Let me be clear about something: when someone on my team is actively trying to undermine the project, I want them out. There's a big difference between someone who is lacking in skill or experience, and a person who is sabotaging a project.

      This is a judgment call, of course, but my personal tolerance for sabotage is low.
      mkrigsman@...
  • Where do they go?

    So you're a project manager in a big corporation and you have a couple duds weighing your project down. So you kick them off your project. Where do they go?

    This is a major issue in a matrix organization.
    Erik Engbrecht
    • Who cares where they go?

      Yes, duds are a problem. People who don't have the chops to get the work done, are lazy, etc., are definitely an issue. But that's not what I'm referring to. I'm talking about people who are actively undermining the project because of personal agendas.

      Who cares where they go? People on my team who undermine and sabotage the project are history. Where they go is their problem.
      mkrigsman@...
      • The company paying them

        In many large companies it's very hard to terminate an employee, but in many cases relatively easy to remove a person from a project. A project manager that blithely ignores that fact is in essence ignoring the success of the organization in order to increase of his individual project.

        "Huh?" you may say. Terminating an employee is hard. You need to document why. You need to give them a chance to change. This isn't a matter of "right" or "fair." It's a matter of avoiding lawsuits.

        Ok, so you say that's not the point. The point is people who undermine the project. How do you define that? What if really you are clueless and the person undermining the project is the only one knowledgeable or brave enough to attempt to bring sanity to it?

        Let's look at your quote from the interview:
        "They decided to part ways; it was an abrupt separation. At the time I felt good about it because I did not think that they were going to be serious players inside the company, they would only help themselves but not me. Usually when you go through a fickle situation, you have to find out who is on the boat with you rowing, and they were not rowing on my account."

        Notice the use of words such as "me" and "my." This is a sign of strong personal identification with the project/company, so strong that the personal identification transcends the team/project/company. People like this define "undermining the project" as "not yielding to my authority."

        Such project managers burn millions of dollars to accomplish nothing - sometimes even to do harm beyond vaporzing cash - and are far more common than individuals who genuinely attempt to undermine efforts.
        Erik Engbrecht
        • I don't buy that

          Unfortunately, determining who is undermining a project is not an exact science. Again, I'm not talking about people who have problems accomplishing what they need to, I'm referring to those who deliberately try to sabotage the project due to personal interests.

          While I certainly understand your point, when I come across the really bad ones, the people who actively do things to undermine the project goals, I find a way to cut them loose from the project. Sure, let them go to another project or department, but get them away from me.

          Regarding your point about who defines what is "right", it's definitely a judgment call. If the project manager is experienced enough, he or she should be able to make that call in an objective, thoughtful manner. If the project manager doesn't have the experience to make the call, then I'd recommend they seek assistance. In that case, they probably have more problems than one rogue team member.
          mkrigsman@...
          • What makes a "rogue?" (NT)

            .
            Erik Engbrecht
          • Iin this context..

            A rogue is someone acting out the behaviors I described: playing out their own agenda with higher priority than the shared goals, to the detriment of the project. How do you define a rogue?
            mkrigsman@...
          • Similar to my definition, but not the same...

            I would describe it as:
            Playing out their own agenda with higher priority than the shared goals, to the detriment of the business.

            You could argue that it's the job of executives or middle management to make sure projects are aligned with the business, and the job of project managers to ensure team members are aligned with projects.

            Upward communications are, by neccessity, at relatively high levels of detail. The problem is the fissures between business objectives and project objectives typically become apparent at the lower levels of the project. The project manager often sees the publication of these fissures as a direct threat to his ability to execute his project, especially in environments where funding is incrementally released or otherwise closely watched.

            It's extremely common for the project manager to have strong disagreements with team members about what constitutes an important enough fissure to communicate upwards, especially when those fissures indicate that a project should be killed or substantially altered in scope instead of simply rebaselined.

            In these situations, "doing what's right" for the team members often involves effectively sabotaging the project by making issues known to project sponsors.

            To make matters worse, project managers often have their own agendas as well. For example, project managers are often measured based on the size of projects they have managed. Consequently, suggestions to "do a pilot" or "build a prototype" for risky systems instead of simply deploying or building them threaten to change a project from something big to something small - from a resume builder to an embarassment.
            Erik Engbrecht
          • bad phrase

            Where I said "high levels of detail" I meant "at a high level," meaning details are omitted rather than included.
            Erik Engbrecht
  • Find and keep the good ones

    Right facts, odd conclusion: "fire the ones not rowing with you".

    I'd rather state: "Find and keep good people" or "Make them row with you".
    rmuliana
    • Nice theory

      But, how do you "make" people with strong negative agendas row with you?
      mkrigsman@...
      • Good question

        I'm not sure. But I guess this kind of people is kinda selfish. So, what we have to do is to give them a strong personal reason (maybe a $$$ bonus?) to row in the same direction as us, as they probably would never row _with_ us. But, personally, I'd rather fire these people, they are really a disease on our projects.

        However, I believe most of the people is not so negative, just not motivated in the right direction. :)

        But, as always, I can be plain wrong...
        rmuliana
        • I don't think money works

          Personally, I think it's an issue of individual character. An honest person remains so, whether he/she is paid or not. I agree that most people are not so negative, but I was really talking about the more extreme cases. To use your words, those people really are a "disease on the project." I think we agree on the basic points here.
          mkrigsman@...