Top ten signs you might not be a project manager

Congratulations! You finally received that much-coveted title of Project Manager — a position you really wanted and dutifully placed on your career planning job appraisal every year. Well I may have a surprise for you. Not everyone who is titled a project manager is a project manager, just as there are professionals acting as project managers without the title.

How could this happen?

Reasons for the disconnect vary with Individuals and organizations. In the later instance, you may have a qualified developer who does not want to be a project manager because he or she is on a technical tract and fears being pigeon holed into management and kept away from technical growth and interesting problems. However, they are willing to do typical project management tasks when asked.

In the first group though are individuals with the title project manager but unfortunately

  1. Believe that management is only about numbers — how much, how many, how quickly and at what cost per item
  2. Believe that management is management, whether it is running a baseball team or developing software
  3. Think that PMBOK may be a type of bird
  4. Do not notice that no one actually reports to them
  5. Are kept away from customers and client meetings
  6. Think “risk” is a board game
  7. Consider product requirements to be large documents primarily useful as a paperweight
  8. Prefer spending time in a large, windowed office sitting behind a clean desk with a tasteful credenza that is covered with sports trophies from high school
  9. Never work nights, weekends or carry home a full briefcase
  10. Believe that Dilbert is a fairytale about a whiny employee and the Pointed Haired Boss is tragically misunderstood

If you find yourself agreeing with any of these top ten, perhaps it is time for a career change — I am sure you would do well as a car salesman.

Dealing with a micromanaging boss or client

OK – How many of you have had to deal with a boss or client who is what we call a “micromanager”?  There are successful techniques that you can apply to help deal with a boss/client that micromanages your project. First though, it helps to understand where the micromanager is coming from and what problems he or she is trying to avoid.

Behaviors of a micromanager

Micromanagers are into control. Micromanagers are afraid to delegate authority or responsibility. They want to be apprised of even the smallest details about the project. And, they need that information updated constantly (Many would prefer telepathic real time updates!). Micromanagers often want to make ALL project decisions — from the important ones, such as staffing, to the minor ones, like the placement of the white board. Their constant need for data and their tendency to require “all decisions go through them for approval” slows the team’s progress — not to mention driving you, the PM, a bit batty.

During the execution of a project, the micromanager may not limit their interaction to requests for information. They may also try to tell team members how to do their jobs (even if they have never done the job). Be aware that on the rare occassion when the micromanager appears to be delegating authority and responsibility, they are likely to take back control at the first sign of trouble.

Motivations of a micromanager

I am not saying that I agree with micromanagers, but understanding what can motivate or drive them to this behavior is the first step in dealing effectively with them. Here are some of the common motivations:

  • Micromanagement may be the only kind of management they know how to do
  • They may be insecure in their position or in their knowledge
  • They genuinely believe that the project will not succeed without their direct and constant involvement
  • Because they do not feel competent to deal with complex issues, they choose to deal with small, trivial ones where they do feel competent
  • Maybe his or her boss is micromanaging them, and you know the saying about stuff rolling downhill….

Consequences of micromanagement practices

If you have a micromanager then you will have probably experienced or observed the following:

  • Team members stop trying to improve processes and results
  • Project do not succeed as well as they might have if everyone applied more of their knowledge and experience
  • Project managers (and other project members) fail to learn lessons that help them mature as PM professionals
  • Leadership is not developed (see Project Leadership Requires Sharing Responsibility)
  • High rate of employee loss — especially the bright, talented and potential future managers
  • Increase in stress, anxiety and anger for everyone involved

Working effectively with a micromanager

Well I don’t have any magic bullets, but here are some tips you can try.

As justified as your frustration and anger may be when you have to work under a micromanager, you need to take a deep breath and make the best of the situation. Then, you need to take some actions to try to counter the effects of this behavior on the project and the team.

Anticipation of the needs of the micromanager for authority and information should be dealt with preemptively. For example, when given a task, find out as many details as possible about the micromanager’s expectations. Listen carefully and feedback your understanding of the task. Asking detailed questions may limit the number of “bring me a rock” exercises you have to go through.

Keep the lines of communication open with the micromanager – yes I know how painful this can be. You may be able to build a trusting relationship over time that allows you to provide feedback on the deleterious effect of his or her management style. At worst, you will at least be able to talk with them about how it negatively impacts the project.

Provide the level of detail and frequency of project information they ask for, but add information on why and how. You may be helping to train the micromanager at the same time increasing their trust in you. Take the initiative to set up meetings and phone calls before they ask.

Give credit to the micromanager when it is due and reward them verbally when they stop micromanaging for a minute.

Don’t let them “push your buttons”.  Keep your cool and remember that you are doing the job and keep reminding them that you can handle the tasks.

So have you had encounters like this?  What tricks and techniques have you used?

Go with your gut — cautiously

On the popular TV show NCIS, the team leader (Mark Harmon) is frequently heard exhorting his staff to “go with your gut” (for the women readers I guess you call this female intuition!). The lesson he is sharing with the team is that your intuition, as opposed to decisions based solely on analytics, may give you the best answer when you need to make a decision quickly.

Experts in neuroscience talk about intuition as a type of pattern matching. A new situation reminds you of a previous situation and its outcome. For example, given enough experience in selecting subcontractors, hiring coders, picking a winning stock or getting burned in a relationship, you develop a sense of when to move forward and when to walk away. Learning to listen to your instincts can save you time and trouble. Have you had the experience of meeting someone and knowing in the first few minutes that they were an expert in their field—or that they were “trouble”?

Let me call your attention to a recent Harvard Business Review Blog titled, “Learn to Trust Your Gut”. This is a well-written, if somewhat simplistic, view of listening to your inner voice when you believe a poor or even dangerous course of action is proposed.  When your inner voice speaks, the author suggests that, “If you think that doing things another way would make a material difference, talk to your boss (or customer or client). Why do we do it this way? Would you be open to different ways? What would be the payoff and the risk? Can we experiment with an alternative? Would it be worth doing some further analysis?” I agree this is an internal conversation worth having.

However …

Equally interesting to me in the blog post is comparing the author’s suggestions with comments from readers. Many commenters said — in different words and ways — “hogwash”. The gist of their negative reaction is that authority figures do not want to be questioned. They believe that following your gut, applying the principle that it is easier to get forgiveness than permission, or arguing for a different course of action than the one proposed by senior management is career limiting.  (If this is true, Steve Jobs should have not been very successful!)

So, why the disconnect?

I suggest that first you should ask yourself, “Whose decision is it?” As a project or team manager, if the final decision is yours, collect data and also tune in to your instinct. You will make a better decision when you take advantage of analytical and intuitive analysis.

In an alternate case, when your opinion is solicited before an action is taken by senior decision makers, I think you should give the questioner both facts and your intuitive assessment. For example, “I believe that XYZ Corporation brings useful skills and contacts to our proposal team. However, in conference with them, they only presented their approach and did not ask questions about our solution or the customer’s needs. I am concerned that they will have difficulty working in our cooperative environment.”

Finally, consider the situation, when as a project manager or team member you are told the decision and given your tasking. You “know” that the proposed activity is doomed to failure and you have an idea of a different, and more likely successful, way to achieve the stated goal. Here is where the situation becomes a bit sticky. What is the most effective way to share your insight and impact the action plan?

  • Before saying anything, reflect on your motives. Are you often the first person in any meeting who points out problems? Is your intuition telling you to avoid any change or only the proposed one? Are you reacting to the proposal or to the person making it?
  • Assuming, after your self-assessment, you conclude that your motives are pure and untainted by cognitive biases, then organize your thoughts and recommendations as talking points that demonstrate your appreciation of the decision maker’s priorities.
  • Unless asked directly for your opinion, it will be more effective to offer your comments and suggestions in a private face-to-face meeting than to confront the presenter publically.
  • If you are having difficulty putting words to your intuitive feelings, try talking it over with someone you trust and respect. Listen to their questions and feedback and allow it to help you organize your thoughts before talking with the decision maker.
  • Wait a day to let your cognitive analytical and intuitive thoughts coalesce before presenting your thoughts. Sleeping-on-it, like your grandmother said, helps. (Got a tough decision to make? Research suggests you’re best off just sleeping on it and Research: You make better decisions using intuition and Incubating Decisions).

If you have complementary or contradictory thoughts, please share.

Follow

Get every new post delivered to your Inbox.

Join 393 other followers