I know a lot of Project Managers and they are all over 30 years old.

Are all project managers like that? I mean, is this about getting more experience than at least 7-8 years?

enter image description here

Or being a Project Manager is so hard? What do you think?

closed as primarily opinion-based by jmort253 Sep 11 '13 at 1:27

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Trying to find commonality between three disjoint sets. That's so hard – pramodc84 May 27 '11 at 3:43
  • I wanted to take a moment to point out that discussion questions, polling questions, and "What do you think?" type questions are generally frowned upon on the Stack Exchange network. The best questions are those that are about a specific problem that you are facing and that produce real, factual answers that can be backed up with references. Please see Good Subjective, Bad Subjective for more information on asking questions here. – jmort253 May 29 '11 at 19:55
  • @jmort253 Thanks for clarification. You are right. – Soner Gönül May 30 '11 at 9:04
up vote 19 down vote accepted

Communication is 90% of the job. The other 90% is keeping track of the bigger picture. It generally takes years of experience to see what needs to be done, make plans for it and effectively communicate that to a broad range of people involved on a project- from corporate stakeholders, customers and regulatory agencies to technical team leads and the technical implementation team.

I also tend to see a requisite degree of humility and confidence in plus 30 project managers that makes them more successful than younger pm's on larger projects.

Keep in mind, project management is more than task management and scheduling. It's hard because the project manager is accountable for the overall success of the project and whether the time and money spent was put to good use.

Most Project Managers are over thirty because you cannot really learn to be a good PM from just training but from experience. The more projects a PM has managed and the more diverse these have been, the more effective usually he/she is. You use different methodologies through the years and you certainly learn from previous mistakes. Project Management needs also strong leadership skills that usually you obtain through the years. The older you get you can also see the bigger picture so you can take better strategic decisions. Also you have dealt with a lot of different people so you are better in people management.

  • Thansk for the good answer Fay. So we can say PM = experience + leadership + good strategy right? :) Maybe more.. – Soner Gönül May 25 '11 at 5:50

I can only speak for myself on this, but I would have made a lousy project/program manager in my 20's. Why?

It wasn't a lack of attention to detail, a critical component in being a PM. It wasn't a lack of technical knowledge, I knew the products I was working with very well. It wasn't a lack of understanding of the product lifecycle, I helped create the one for the company I was at in my 20's.

It was a lack of developed people skills.

It takes a lot of intense people skills to be a really great project manager. Few people have these in their early 20's (I applaud Trevor his success). It took me until nearly 40 to learn the difference between driving a team and leading a team.

It will be interesting to see how the up and coming crop of young project manager bachelors change the face of this. My guess is they will suceed or fail based on how much emphasis their degree work put on people skills.

Best, JBC

  • 1
    I love that "It was a lack of developed people skills. " – Soner Gönül May 25 '11 at 6:12

I think the fact that most PM are more than 30 is not really related to the hardness of the task, but either because in most companies, you become PM only after you have proven yourself as operative. For example, in the IT business, you will first have to prove yourself as a valuable engineer before any hope of becoming PM. And it's caused by the increasing price due to experience: the years passing by, you become gradually to expensive for a simple operative work, and so your company will want you to switch to more managerial positions, like PM for example.

But the work itself is not so complicated: create the conditions to let your team do it's work, monitor schedules and, most important, contain pressure from above to avoid scaring your team...

  • Thanks for the answer. In your answer you say it very good "For example, in the IT business, you will first have to prove yourself as a valuable engineer before any hope of becoming PM" . That's also true. Nobody's first job is PM. Right? Maybe %5 percent. What do you think about that? – Soner Gönül May 25 '11 at 6:02
  • 1
    I agree. Most of the time, you don't begin as a PM, and you wouldn't be legitimate with your team. Imagine a team of seasoned engineers, and now comes a freshman who just finished his studies, to manage the project they are working on. This can hardly end well... – Alexis Dufrenoy May 25 '11 at 8:16

You need broad experience (technical, personal, and organizational) before most companies will give you project management duties. Competent PMs can plan and oversee a project from beginning-to-end without burning out their team, which is rarely an easy task.

Earning the respect of technical teams BEFORE you manage them also takes time. People need to believe you'll ask the right questions, help solve their problems, and understand why they make different technical decisions. Your graphic is a good illustration of why project management is "hard"--you need general expertise, not only know how to write code or create a MS Project schedule.

  • Nice answer. Like other answers and Steve Ballmer "Experience ,Experience ,Experience " in PM :)) – Soner Gönül May 25 '11 at 5:57

It's not necessarily 'harder' than any other management discipline, but since it plays off of all the others, usually you need to have some experience in another area (mgmt or tech) before you can manage a project. For most companies a project represents a strategic component, so they want they to be sure whoever's running it is going to be able to do so successfully.

But there's no age limit. I started managing projects when I was 22. The key point around this though it that it's not about age, it's about complexity. I was managing projects, but they were relatively non-complex. It was only as I gained experience that I was looked at as being competent to handle more complex projects. By 30 I was handling both projects and programs, but only because I had the experience.

  • 1
    But 30's PM Trevor is better than 22's PM Trevor right? – Soner Gönül May 25 '11 at 6:31
  • Most definitely. – Trevor K. Nelson May 25 '11 at 17:33

I think Project management is hard for two main reasons:

First you generally evolve from a technical leader role where things are globally well defined to a role where things are sometimes hazy, unclear or ambiguous. It may take you sometimes to clearly understand what to be done (or not), what are the corrects goals (official or not)… In the same times you need to give clear objectives to your team, so beginning a project is sometimes very anxiogenic.

Second, Team management is the most difficult part (See how many questions you have here). You can do bad choices (technical, process, functional) and may correct them easily if you are a good leader and are followed by your team (they may alert you, or work harder and later), but when you did Team management mistakes you may demotivate people and all can fall over. Don’t remember that you need to define goals first, and depending experience of your team, not the way to do it (All people can have good ideas). Don’t forget to listen, listen and listen…

All of us have been managing projects since we were five-years-old. The concepts are exactly the same whether you are building a replica of the solar system with your classmates or the next space vehicle working with NASA. The complexity, rigor, formality, and impacts grow. The point is, you take on projects consistent with the level of your competency and capability. This can and does happen at any age of seniority.

Age is a red herring. Most folks seem to equate years of experience with competency. The assumption is made that, if you have been managing complex projects for fifteen years, you are more competent and capable then one who has managed the same complex projects for five years. Banking on that assumption is at your detriment.

Skill, knowledge, and experience make up competency, with experience being the least reliable but upon which most folks rely.

PM of complex projects is difficult, but relying on someone's age and years of experience will not increase the likelihood of success in any reliable way.

  • Age and experience tend to be better predictors of success because most people lack the humility to learn from others' experiences. – Huperniketes Jun 5 '11 at 22:46
  • Unfortunately, that is simply not true. – David Espina Jun 6 '11 at 18:28
  • Saying so doesn't make it not so. You are espousing a belief. – Huperniketes Jun 8 '11 at 2:47
  • I know that both skill and knowledge can be measured on a performance scale and mapped to a result. Experience is the passage of time. EVERYONE is equal in experience, i.e., a 30-year PM vet is the same as the other 30-year PM vet. I know that it is safe to assume a normal distribution for a performance curve, meaning a full 50% fall less than the median. So no matter the experience, 1/2 are less than average performance. Get out a coin. – David Espina Jun 8 '11 at 17:13
  • These things are studied. I am not holding on to a non educated belief. Are you? – David Espina Jun 8 '11 at 17:14

Not the answer you're looking for? Browse other questions tagged or ask your own question.