Home / Leadership / Popular Opinion Says Project Managers Lack Basic Skills

Popular Opinion Says Project Managers Lack Basic Skills

What’s the most common mistake that project managers make? The responses of 78 professionals who answered that question through my LinkedIn poll surprised me. I expected, maybe idealistically, that miscalculating project risks would top the list. However, after categorizing the responses according to the nine PMBOK knowledge areas (integration, scope, time, cost, risk, HR, quality, communications, and procurement), the tally was that communications and quality management cause 48% of the most common project manager mistakes. Add scope management and the total became 65%. (Click here to see the analysis and responses.) This is good and bad news. The bad news is that project managers appear to lack basic skills like communications, quality and scope management or technical know-how. However, the good news is that the right training can remedy these deficiencies.


A common response was that project managers lack technical expertise. 22% of poll respondents cited it as a major source of serious project manager mistakes. It makes sense: Would anyone expect a project manager who successfully builds bridges to competently deliver a complex software project? Would it be a surprise if a project manager who deploys large-scale fiber optics networks failed when restructuring an accounting-system for a multi-national corporation? Neil H., a software expert from the UK, said that “the role of a PM is a collision of several very differing disciplines, and quite often a PM is hired (by less than technical leaders/managers etc. who have no ability to judge whether they are suitable or not) for their administrative abilities way over their technical knowhow or understanding”. Silvio B., a video engineer from Italy commented that “some PMs lack or underestimate the knowledge of everyday work”. David M., Operations Manager from the US, added that the responsibility to identify the project manager’s level of expertise lies with the boss and that it is hard to find a PM that has “the charisma of a salesman and the analytical skill set of an engineer.” Organizations often choose between training a skilled project manager with technical expertise and training a technical expert to become a project manager. There are countless factors that influence the best choice, but a successful decision should mitigate the gaps with the appropriate training to create knowledge and skills.


To state the obvious: project managers require project management expertise. 23% of responses cited project communications errors as a major source of serious project manager mistakes. Darlene S. a Project Coordinator from Canada said that a common error is “assuming instead of confirming that communications are clear to all the project team and/or stakeholders”. Seamus O., a Director from Ireland, says that “it is important to spend the time early on with the stakeholders to get their buy in.” A lack of communications and buy-in is a common thread through the responses. Scope management is the next-largest project manager failure. According to the poll, 18% of serious mistakes originate from scope assumptions, lost focus, and scope creep. There is no PMBOK knowledge area that was not a source of big project manager mistakes, even though budgeting and procurement were the least blamed.


However an organization decides to bridge the knowledge gap, it is critical to provide the right training to create job skills. Adrian D., a project management Fellow from the UK emphasized the point. He said: “They had all been on the basic courses and knew what they should have done.” Ineffectual training can provides poor return on investment, particularly if it creates false confidence rather than real skill. For example, a project manager who memorized formulas to calculate earned value may have no idea how to use them to mitigate a budget overrun on a real project. On the other hand, on-the-job training is usually very effective because a project manager learns while solving project problems with immediate feedback from a mentor. In this example, a project manager may not know the textbook-definition of “schedule float” but practice the concept to calculate the critical path and to avoid schedule mistakes.


Assuming that the opinion of 78 professionals accurately reflects reality, then the solution to big project manager mistakes can be solved with diligent training. Imagine if the most common sources of mistakes were risk and uncertainty–it would be difficult to change it. Luckily, good professional development programs with on-the-job training and formal classroom education could improve project manager performance. To end with a famous quote: “If you think training is expensive, try ignorance!”

About RolandHoffmann

Roland Hoffmann is a 20 year veteran who has led a wide spectrum of projects, ranging from colossal to miniscule, from IT to construction, and from Europe to Asia and the Americas. He decided to convey his two decades of experience through Hoffmann Conseho’s project management courses, and founded the company in 2007. www.conseho.com

Check Also


Stakeholders – from confrontation to engagement

Project stakeholders can be helpful, obstructionist and almost anything in between – but for most …


  1. I am thankful for this article. It is so rare to get honest feedback about Project Management. The thing that escapes me is I am technically incline with well over 10 years of Senior PM experience and my profile is posted accordingly. However I have little success in finding employers who will respond to my online applications and resumes.

  2. Thank you Richard for the valuable information. I can say I am not surprised. Socially and culturally we have seen a trend over the last decade of a decrease in basic social skills, inability to have a range of communication styles or even appropriate basic communication. This doesn’t just apply to PM’s but has become a part of our culture. I worked as a PM and needed to communicate with a range of individuals; board members, stakeholders, developers, business analysts, business departments influenced by the projects being completed, the sales force and trainers. Each group was different and needed to be communicated with differently. Each group had different concerns that needed to be validated and addressed. People don’t want to hear, this is the direction of the company and too bad if you don’t like it. They want to feel a sense of collaboration, that they have a say in how their workflow is developed. Empowering individuals has been proven to improve results.


Leave a Reply

Your email address will not be published. Required fields are marked *