The project management profession is not new. It has been a mainstream profession across virtually all industries for decades now, and yet project managers continue to be created part way through their careers. When functional managers have career discussions with business analysts, testers, developers, etc., they will often hear that the staff member wants to get into project management, but rarely do you find an undergraduate who wants to be a PM when he or she enters the workforce.
This is logical: Successful project managers have an understanding of their environment that you can’t get except through experience. Anyone can be taught the basic skills that a PM needs, but project management is more than a collection of tools and techniques. It is an art, not a science, and in order to put their own style into their management a PM needs a certain degree of organizational and emotional maturity as well as superior soft skills.
This is recognized throughout the world, across multiple industries--people need to evolve into project management. Why then is it that so many organizations think that the evolution stops with project managers, that the career stops there? While it is good for the ego to think of the PM as the top of the food chain, it is clearly not the case. So why do organizations not continue down the path that they have started?
From project management to?
First off, let me say that there are plenty of opportunities for project managers to have successful careers within project management, and there is absolutely nothing wrong with that. There will always be multi-year, huge dollar initiatives that can give the PM the kind of challenge that few will ever experience, but these are the exceptions.
What happens to the 99 percent of PMs who will never have those opportunities? Some will move into PMO leadership and related disciplines--project control, audit, etc. Others will contribute to project management methodology and process. However, many will either resign themselves to remain as project managers long after the thrill has passed (often on a contract basis) or will drift away from the profession entirely.
A project is a wonderful thing--it is a business in microcosm. Today, organizations are proudly claiming to be project based businesses, effectively saying that they are a collection of projects that together form the collective company. By extension, therefore, the project manager can be compared with a business unit head. And when you start to delve more deeply into that comparison, it makes a lot of sense.
Consider the challenges that a project manager faces on a day to day basis:
· Management of the project team--ensuring that the right people are doing the right things at the right time
· Management of the project budget--hard dollars, soft dollars, resources, etc.
· Issue resolution--the PM is the first person that the team will turn to when problems occur
· Communication--the cornerstone of any project manager. If a PM cannot communicate effectively with different audiences and different media, using different styles to suit the situation, then he or she will be destined to fail.
·
I could go on, but I think the point is made. The challenges of a project manager are no different from the challenges of a functional manager, business unit head or CEO. Sure the numbers are generally bigger for the CEO than for the PM, and the specifics of the tasks/roles being managed are different, but the discipline is the same.
To me the career path is obvious. If an individual is being groomed for top management, then at some point in their careers they need to be project managers. To be more PM-centric about it, if a successful PM has the inclination to move into functional management (and particularly if they wish to move into executive management), then they will probably be very successful.
Recognizing the talent and making it happen
I am not suggesting that every PM will make a great CEO, and many will have no interest in taking that path. What I am saying is that a project manager will provide very good insight into the way that they would run a business unit by the way they manage projects.
It is for each individual company to decide what personal attributes they value in their executives; it will be impacted by the style of the company, the values that they embrace, the industry that they are in, etc. However there are certain traits that PMs will demonstrate that will help indicate their suitability and readiness for the next level.
The future executive will probably be a practical PM, using their process and methodology skills as a support, but recognizing the need to apply them to individual scenarios. They will be proactive, seeking out problems long before they become major issues and trying to head them off. This type of PM will be a comfortable communicator at all levels of the organization, will understand the perspectives of each of the people in their project and will seek to motivate them based on their own individual needs.
This all sounds remarkably obvious--I’m describing an ideal real world project manager in many people’s eyes. But if it is so obvious, why is it not happening other than as the exception? Part of the answer is that there are wonderful future executives in all disciplines--project management doesn’t have the monopoly, but it’s more than that. The connection is not being made that projects are so similar to the business that the skills are easily transferable (or at least can easily be evolved).
So how do you groom a PM to take on a leadership role? The piece that is most typically missing in the PM’s experience is the strategic elements around project drivers. The perception in many organizations is still that a project starts the day that the requirements are delivered, or at best when the business case is approved.
It is important to ensure that PMs have an opportunity to become part of the decision-making process that leads to the approval of a project. Initially they may be consumers of the information rather than contributors to the process, but this insight into the true business drivers behind the project is invaluable; it will guide a project manager when making decisions far downstream in the project.
Additionally, it won’t take long for the PM to start contributing to the discussion. After all, they are the people who work with the project teams day in and day out, they have an understanding of what can be accomplished and generally don’t have a politically motivated agenda to influence them. This is true whether the PM has aspirations to progress or not.
Conclusion
There is no silver bullet that will identify the perfect leader and point them the right way to get them to the top, nor should leaders be considered from just one part of an organization. The successful organizations will look for top talent wherever it can be found and look for ways to leverage that talent.
All I am suggesting is that PMs have many of the skills that are sought out in the business leaders of today (and tomorrow), but sometimes organizations need some help in realizing that the skills are transferable beyond projects and (ultimately) into the boardroom.
If you are a PM with aspirations to go further, think about the skills that you have, think about how they can be adapted to other roles and think about where you need to develop further skills. If you are a business leader, take a good look at your project managers--you may be pleasantly surprised.
Andy Jordan has 16 years of experience covering practical project management, project methodology development and delivery, and PMO leadership in both Europe and North America. He is currently a Senior Consultant with R3D Information and Technology Consultants in Toronto. Andy welcomes comment and debate on his articles and can be reached at andy.jordan@r3d.com.