Posts Tagged ‘wrong’

Selecting the wrong project manager for Projects from POME by Gautam Koppala

Selecting the wrong project manager

Even though executives know the personal characteristics and traits that project managers should possess, and even though job descriptions are often clearly defined, management may still select the wrong person because they base their decision on the following criteria.

Maturity

Some executives consider gray hair to be a sure indication of maturity, but this is not the type of maturity needed for project management. Maturity in project management generally comes from exposure to several types of projects in a variety of project office positions. In aerospace and defense, it is possible for a project manager to manage the same type of project for ten years or more. When placed on a new project, the individual may try to force personnel and project requirements to adhere to the same policies and procedures that existed on the ten-year project. The project manager may know only one way of managing projects.

Hard-Nosed Tactics

Applying hard-nosed tactics to subordinates can be very demoralizing. Project managers must give people sufficient freedom to get the job done, without providing continuous supervision and direction. A line employee who is given “freedom” by his line manager but suddenly finds himself closely supervised by the project manager will be very unhappy.

Line managers, because of their ability to control an employee’s salary, need only one leadership style and can force the employees to adapt. The project manager, on the other hand, cannot control salaries and must have a wide variety of leadership styles. The project manager must adapt a leadership style to the project employees, whereas the reverse is true in the line organization.

Availability

Executives should not assign individuals as project managers simply because of availability. People have a tendency to cringe when you suggest that project managers be switched halfway through a project. For example, manager X is halfway through his project. Manager Y is waiting for an assignment. A new project comes up, and the executive switches managers X and Y. There are several reasons for this. The most important phase of a project is planning, and, if it is accomplished correctly, the project could conceivably run itself. Therefore, manager Y should be able to handle manager X’s project.

There are several other reasons why this switch may be necessary. The new project may have a higher priority and require a more experienced manager. Second, not all project managers are equal, especially when it comes to planning. When an executive finds a project manager who demonstrates extraordinary talents at planning, there is a natural tendency for the executive to want this project manager to plan all projects.

Technical Expertise

Executives quite often promote technical line managers without realizing the consequences. Technical specialists may not be able to divorce themselves from the technical side of the house and become project managers rather than project doers. There are also strong reasons to promote technical specialists to project managers. These people often:

Have better relationships with fellow researchers
Can prevent duplication of effort
Can foster teamwork
Have progressed up through the technical ranks
Are knowledgeable in many technical fields
Understand the meaning of profitability and general management philosophy
Are interested in training and teaching
Understand how to work with perfectionists

As described by Taylor and Watling:

It is often the case, therefore, that the Project Manager is more noted for his management technique expertise, his ability to “get on with people” than for his sheer technical prowess. However, it can be dangerous to minimize this latter talent when choosing Project Managers dependent upon project type and size. The Project Manager should preferably be an expert either in the field of the project task or a subject allied to it.

Promoting an employee to project management because of his technical expertise may be acceptable if, and only if, the project requires this expertise and technical direction, as in R&D efforts. For projects in which a “generalist” is acceptable as a project manager, there may be a great danger in assigning highly technical personnel. According to Wilemon and Cicero:

The greater the project manager’s technical expertise, the higher the propensity that he will overly involve himself in the technical details of the project.
The greater the project manager’s difficulty in delegating technical task responsibilities, the more likely it is that he will overinvolve himself in the technical details of the project. (Depending upon his expertise to do so.)
The greater the project manager’s interest in the technical details of the project, the more likely it is that he will defend the project manager’s role as one of a technical specialist.
The lower the project manager’s technical expertise, the more likely it is that he will overstress the non technical project functions (administrative functions).

Customer Orientation

Executives quite often place individuals as project managers simply to satisfy a customer request. Being able to communicate with the customer does not guarantee project success, however. If the choice of project manager is simply a concession to the customer, then the executive must insist on providing a strong supporting team.

New Exposure

Executives run the risk of project failure if an individual is appointed project manager simply to gain exposure to project management. An executive of a utility company wanted to rotate his line personnel into project management for twelve to eighteen months and then return them to the line organization where they would be more well-rounded individuals and better understand the working relationship between project management and line management. There are two major problems with this. First, the individual may become technically obsolete after eighteen months in project management. Second, and more important, individuals who get a taste of project management will generally not want to return to the line organization.

Company Exposure

The mere fact that individuals have worked in a variety of divisions does not guarantee that they will make good project managers. Their working in a variety of divisions may indicate that they couldn’t hold any one job. In that case, they have reached their true level of incompetency, and putting them into project management will only maximize the damage they can do to the company. Some executives contend that the best way to train a project manager is by rotation through the various functional disciplines for two weeks to a month in each organization. Other executives maintain that this is useless because the individual cannot learn anything in so short a period of time.

Finally, there are three special points to consider:

Individuals should not be promoted to project management simply because they are at the top of their pay grade.
Project managers should be promoted and paid based on performance, not on the number of people supervised.
It is not necessary for the project manager to be the highest ranking or salaried individual on the project team with the rationale that sufficient “clout” is needed.

POME Case- Study

Setting High Departmental Standards as a New Manager — Case Problem: ‘‘The Bitter Beginning”

Overview

While having lunch in the company cafeteria, Jack, the general credit manager and a twelve-year veteran, couldn’t wait to tell his friend, Marv, a sales representative, about the new controller’s first divisional management meeting.

‘‘You wouldn’t believe what the new guy said,” Jack said angrily. ‘‘Let me see if I can recall some of his ‘pearls of wisdom.’

‘‘The new boss said, ‘Okay, you guys, now that I’m in charge, let’s get one thing clear. I’ve checked you out, and just by looking at you, I can tell my sources weren’t too far off. So you won’t be pulling the wool over my eyes like you did with my predecessor—who, by the way, is a good friend of mine. I want to tell you about yourselves.

‘‘ ‘Your past record is a disgrace, demonstrating indifference to the company’s needs, as well as a lack of interest in our division. In fact, it seems to me that all you’ve been demonstrating around here has been laziness, avoidance of work and, in some cases, just plain stupidity.’ ”

‘‘Jack, you’ve got to be kidding,” Marv interrupted. ‘‘You’re putting me on!”

‘‘No, I’m not, Marv,” Jack replied. ‘‘But wait, it gets better. The new controller also said, ‘I’ve been brought in to whip this group into shape. This is how I’m going to do it.

‘‘ ‘First, although I don’t expect good performance from any of you, I’d better get it, or else. Second, if you don’t perform satisfactorily, you’re going to be in for some big trouble. And, third, if, by some stroke of luck, you manage to succeed in improving this division’s performance, don’t look to me for any ‘‘thank you’s”—you’ll only be doing what you’re getting paid for.’ ”

‘‘Well, Jack,” said Marv, ‘‘it seems as though hard times are ahead for you and the rest of your division. Tolerate this guy as long as you have to; but if I were you, I’d start looking around for a new opportunity. I just don’t see how you can come out winning.”

Case Analysis

It is difficult to imagine any employee winning with a manager like the new controller. Even if Jack and his colleagues try to improve the division’s performance, they probably won’t make much headway with their new boss, since he already is convinced that they are losers and has no confidence in their ability to turn the division around.

In addition, he has refused to offer his management staff any incentive for working harder, informing them that they will receive no recognition for improved performance.

Solution:

The initial expectations and attitudes communicated by a new manager to a department can be extremely important in setting the direction for the staff. To help start off your new relationship with employees in a positive and productive manner, consider the following action tools:

During your initial staff meeting, create a positive mood and share your vision for teamwork and top results.
Explain your goals for the department and share preliminary guidelines for successful operations.
Explain your high standards and expectations of top performance and dedication to quality.
Inform your staff that top efforts and significant contributions to the department will be recognized.
Let your staff know that you are there to support and encourage them.

Gautam Koppala,

POME Author

More “project Management” Articles