Management Pitfalls

The project environment offers numerous opportunities for project managers and team members to get into trouble. Common types of management pitfalls are:

• Lack of self-control (knowing oneself)

• Activity traps

• Managing versus doing

• People versus task skills

• Ineffective communications

• Time management

• Management bottlenecks

Knowing oneself, especially one's capabilities, strengths, and weaknesses, is the first step toward successful project management. Too often, managers will assume that they are jacks-of-all-trades, will "bite off more than they can chew," and then find that insufficient time exists for training additional personnel. The following lines illustrate self-concept:

Four Men It chanced upon a winter's night Safe sheltered from the weather. The board was spread for only one, Yet four men dined together. There sat the man I meant to be In glory, spurred and booted. And close beside him, to the right The man I am reputed. The man I think myself to be His seat was occupying

15. Russell D. Archibald, Managing High-Technology Programs and Projects (New York: Wiley, 1976), p. 230.

Hard by the man I really am To hold his own was trying. And all beneath one roof we met Yet none called his fellow brother No sign of recognition passed They knew not one another.

Author unknown

Activity traps result when the means become the end, rather than the means to achieve the end. The most common activity traps are team meetings, customer-technical interchange meetings, and the development of special schedules and charts that cannot be used for customer reporting but are used to inform upper-level management of project status. Sign-off documents are another activity trap and managers must evaluate whether all this paperwork is worth the effort.

We previously defined a characteristic of poor leadership as the inability to obtain a balance between management functions and technical functions. This can easily develop into an activity trap where the individual becomes a doer rather than a manager. Unfortunately, there often exists a very fine line between managing and doing. As an example, consider a project manager who was asked by one of his technical people to make a telephone call to assist him in solving a problem. Simply making the phone call is doing work that should be done by the project team members or even the functional manager. However, if the person being called requires that someone in absolute authority be included in the conversation, then this can be considered managing instead of doing.

There are several other cases where one must become a doer in order to be an effective manager and command the loyalty and respect of subordinates. Assume a special situation where you must schedule subordinates to work overtime on holidays or weekends. By showing up at the plant during these times, just to make a brief appearance, you can create a better working atmosphere and understanding with the subordinates.

Another major pitfall is the decision to utilize either people skills or task skills. Is it better to utilize subordinates with whom you can obtain a good working relationship or to employ highly skilled people simply to get the job done? Obviously, the project manager would like nothing better than to have the best of both worlds, but this is not always possible. Consider the following situations:

• There is a task that will take three weeks to complete. John has worked for you before, but not on such a task as this. John, however, understands how to work with you. Paul is very competent but likes to work alone. He can get the job done within constraints. Should you employ people or task skills? (Would your answer change if the task were three months instead of three weeks?)

• There exist three tasks, each one requiring two months of work. Richard has the necessary people skills to handle all three tasks, but he will not be able to do so as efficiently as a technical specialist. The alternate choice is to utilize three technical specialists.

Based on the amount of information given, the author prefers task skills so as not to hinder the time or performance constraints on the project. Generally speaking, for long-

duration projects that require constant communications with the customer, it might be better to have permanently assigned employees who can perform a variety of tasks. Customers dislike seeing a steady stream of new faces.

It is often said that a good project manager must be willing to work sixty to eighty hours a week to get the job done. This might be true if he is continually fighting fires or if budgeting constraints prevent employing additional staff. The major reason, however, is the result of ineffective time management. Prime examples might include the continuous flow of paperwork, unnecessary meetings, unnecessary phone calls, and acting as a tour guide for visitors.

• To be effective, the project manager must establish time management rules and then ask himself four questions:

• What am I doing that I don't have to be doing at all?

• What am I doing that can be done better by someone else?

• What am I doing that could be done sufficiently well by someone else?

• Am I establishing the right priorities for my activities?

• Rules for time management

• Conduct a time analysis (time log)

• Plan solid blocks for important things

• Classify your activities

• Establish priorities

• Establish opportunity cost on activities

• Train your system (boss, subordinate, peers)

• Practice delegation

• Practice calculated neglect

• Practice management by exception

• Focus on opportunities—not on problems

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment