As in many other technical disciplines, it’s a frequent career path for engineers — almost required — to move from on from pure technical work (design, analysis, number-crunching, etc.) onto project management.
A long time ago as an undergrad in civil engineering, my course concentration was in construction project management. I learned the crunchy part, the technical part of the work: cost estimates, budgets, schedules, systems analysis, the critical path method, all that good stuff. But it turns out I didn’t learn, at the time, elements that in modern practice are considered part of a project manager’s job.
It’s hardly surprising; to this day, a majority of technical professionals learn project management on the job, through trial and error — lots of costly errors. There are a lot of human, non-technical skills and tasks involved, the so-called soft skills: leadership, people management, client contact, networking, proposal preparation, finding new projects, keeping clients happy.
In truth, many of us take years to even start realizing that some of these are indeed part of project management! For example, we keep hoping for the day the marketing personnel will learn to prepare proposals entirely without our help, without stealing our valuable technical time.
Consultants, you see, live and die by their “billable” (or “chargeable”) time: how many hours in a day do we spend working on something that advances a specific project and therefore can be charged to that client’s account? How many hours in a day do we manage to get our salary covered by project work rather than to overhead? Every employee in a consulting firm is acutely conscious of that percentage and every hour she has to spend on finding new work — networking, looking for leads, writing proposals, etc. — is an hour not spent on a chargeable project.
But it turns out it IS part of project management, as is keeping the client happy and informed, nursing bruised egos on a team, riding herd on sub-consultants, or negotiating with other project managers for common resources. Yet most of us have to learn these skills by observation or by self-directed learning.
I spent 21 years out of school before finding a company where everyone, without exception, is sent for formal training before being given projects to manage. Even though by now I had done a lot of the self-teaching, I still learned valuable information on not only setting up a project right to minimize the risk of problems, but also — something usually neglected — on getting the project out of trouble when things go awry.
In addition, this company uses a coaching system in which every project has an assistant project manager to help with management tasks, ensure redundancy in case the PM is unavailable, and provide mentorship in learning the ropes. We have tools, we have support, we have a safety net.
The wonder, really, is that I spent so long and worked at so many companies without receiving the training or support. In these places, you got technical training fairly easily, but you only received PM training as (a) a sort of accolade or pat on the back if you were doing well, or (b) a corrective measure if you were doing poorly but they still needed to keep you in the position.
Imagine that! These companies all chose to let their professionals learn by making mistakes on their clients’ projects rather than get them trained, because of the training costs or because they were too busy putting out fires rather than planning ahead. What a waste.