"Project Managers" are inevitable. Love them or hate them, but if you are in a project, you have to accept them. They are Omnipresent in any project. They intervene too much on technical things without much knowledge. They create unrealistic targets and nonsensical methods of achieving them. And they invariably fail to acknowledge the individual hard work. Are they of any use?

In a recent online survey by amplicate.com, 51% of the participants expressed hate for project managers and project management. Look around yourself in your office, the scenario is probably the same. So what are the reasons that make people hate their project managers? DWBIConcepts delved deeper into this question and found out top 5 reasons about why project managers are hated.

Remember, all project managers are not hated! So, following reasons off course don’t apply to them.

1. Project managers are lazy

Generally project managers are not answerable to their subordinates. They are self-paced and semi autocratic. These allowances provide them the opportunity to spend time lazily. Many project managers spend more time surfing internet than evaluating the performances of his/her subordinates.

The cure for their laziness is pro-activeness which can help them spend quality time in office.

2. Project Managers snatch other people’s credit

I know of a project manager “Harry” (name changed), who used to receive work from client and assign the work to his subordinate “John” and once John finished the work and sent Harry an email, Harry used to copy the contents of John’s mail and reply back to the client. Since Harry never “forwarded” John’s mail directly to client – so client was always oblivion to the actual person (John) doing their work. Client always used to send appreciation mail to Harry only and John was never accredited for the work he did.

The advice for the would-be project managers here is to remain conscious about the individual contributions and give them their due credit whenever possible.

3. Project managers are reluctant to listen to new idea

There is no one-size-fit-all solution when it comes to project management. Just because a specific idea worked in your earlier project, doesn’t mean that will work in your next project also. Everybody is good at something or other. Everybody has some idea. Not all of them are good. But some of them are. So be flexible and open to new ideas.

Listen carefully what others have to say and if you have to discard them, give proper reasons.

4. Project Managers fail to do realistic planning

Proper planning makes thing easy. What do you think is the main difference between a NASA space project and a service industry IT project? The project members in that NASA project are the same kind of engineers that you have in your project. May be many of them passed from the same graduate school. The same set of people who made one project a marvelous success, fail miserably in some other project. There is nothing wrong with those people. But there is something wrong with the leader leading that set of people. A NASA project succeeds because of a meticulous and realistic planning whereas the other project slogs.

Create a detail plan and follow it closely.

5. Project Managers don't know the technology well

Don’t let new tools and technologies outsmart you. Technology space is ever changing. Try to keep pace with that.

Install the software and tools that are being used in your project in your laptop. Play with them. Know what their features are and what their limitations are. Read blogs on them. Start your own blog and write something interesting in that in a regular basis. Be a savvy. Otherwise you will be fooled by your own people.


Have a question on this subject?

Ask questions to our expert community members and clear your doubts. Asking question or engaging in technical discussion is both easy and rewarding.

Are you on Twitter?

Start following us. This way we will always keep you updated with what's happening in Data Analytics community. We won't spam you. Promise.

  • A road-map on Testing in Data Warehouse

    Testing in data warehouse projects are till date a less explored area. However, if not done properly, this can be a major reason for data warehousing project failures - especially in user acceptance phase. Given here a mind-map that will help a...

  • What is Data Warehousing?

    A data warehouse is a repository of an organization's electronically stored data. Data warehouses are designed to facilitate reporting and analysis.

  • OLTP and OLAP

    OLTP stands for On-line Transaction Processing and OLAP stands for On-line Analytical Processing. We may have heard these definition many times. But do we really understand the difference between them. Let's explore further on these two kinds of...

  • Top 5 Challenges of Data Warehousing

    Data warehousing projects are one of its kinds. All data warehousing projects do not pose same challenges and not all of them are complex but they are always different. This article illustrates the top 5 challenges that often plague modern data...

  • Enterprise Data Warehouse Data Reconciliation Methodology

    An enterprise data warehouse often fetches records from several disparate systems and store them centrally in an enterprise-wide warehouse. But what is the guarantee that the...

  • What is a data warehouse - A 101 guide to modern data warehousing

    This article discusses data warehousing from a holistic standpoint and quickly touches upon all the relevant concepts that one needs to know. Start here if you do not know where to start from.

  • Decision Support System (DSS)

    Decision Support System (DSS) is a class of information systems (including but not limited to computerized systems) that support business and organizational decision-making activities. A properly designed DSS is an interactive software-based system...

  • Top 10 things you must know before designing a data warehouse

    This paper outlines some of the most important (and equally neglected) things that one must consider before and during the design phase of a data warehouse. In our experience, we have seen data warehouse designers often miss out on these items...

  • Business Intelligence

    In a 1958 article, IBM researcher Hans Peter Luhn used the term business intelligence. He defined intelligence as: "the ability to apprehend the interrelationships of presented facts in such a way as to guide action towards a desired goal."

  • Data Retention and Purging in a Data Warehouse

    By the typical definition of data warehouse, we expect the data warehouse to be non-volatile in nature for its entire design life time. As long as it remain operation, all data loaded in the data warehouse should remain there for the purpose of...