August 28th, 2005 by A.J.
Wondering whether you have what it takes to be a project manager? Here are ten signs that you’re never going to make it to the top of the project hill.
I see it everyday — talented programmers, system technicians and project engineers being promoted to project manager. You may very well be a skillful, seasoned engineer, but parlaying that talent to project management is hard to do. And your first project is how you’ll be judged.
The most important step you can take toward becoming a project manager is to get your name on the list - or, more to the point, not to get your name crossed off the list. Speak to your boss, peers, and managers so the word gets out that you want to be a project manager. Besides my own experience, I’ve spoken with CEOs, executive recruiters, and other consultants, who consider the merits of prospective PM’s. You need to heed their advice and follow their tips in getting yourself ready for that first project.
Now to be honest, one black mark from this list - or even more - won’t necessarily ban you from the project manager position for life; all of these “ten sure signs” can be addressed, in time, if you’re willing to invest the effort. You might also argue that a number of my signs conflict with each other. Should you stand up to the boss, or should you tone down the ego? Should you get more involved with operations, or should you lighten up on the tech certifications? Finding the right mix of skills for your career is a lifelong pursuit; here’s a good milepost to see where you stand.
1. You Really are Still a Technician
There’s more to being a PM than getting the code right, configuring an operating system or designing a data center. IT technicians, however skillful, can’t rise to the top without practical management experience. Good project managers have always been strategists and goal-seekers, no matter the size of the project. Only a technician would fixate on the latest hardware and software while ignoring day-to-day PM issues like schedule, costs and team resources. Remember, from a business point of view, a technician is a necessary expense, not a vital asset.
2. You Can’t Handle Project Politics
When a company has many capable techies, one of the things that allow one to rise to the PM spot is the ability to manage the politics of the business and the project. A winning PM possesses the “executive presence” to juggle the concerns of project constituents - the stakeholders, company management, accounting departments, programming managers, infrastructure engineers, clients, vendors, subcontractors, and employees - without being skewed one way or another.
Executive management has to trust the numbers and the project manager. That means more than simply managing the project downward, a PM must also “manage upward,” presenting facts and ideas to company executives and boards of directors. On occasion this might mean standing up to a CEO. A project manager who decides to play it on the safe side, or is outmaneuvered because of a lack of political savvy, will likely find himself or herself in a weaker position the next time around. Too many managers pay homage to their bosses rather than engaging them. The PM needs to be able to argue a point with the stakeholders or executive management and not shrink away the next time they meet. They form a team bonded partly by respect and trust, and partly by chemistry and other intangibles.
(To be continued in a day or two)