DJ has supplied some very erudite advice that I am sure we can all learn from. However, I have faced a number of situations where "following the well established procedures" would never have produced a positive result. DJ freely admits that not all procedures are sensible or good. Well, then sometimes they simply have to be changed. Those who like an easy life won't do it and those with a vested interest definitely won't do it! So who will do it? What DJ describes is learning to live within and how to use the "system", ie. what can be safely ignored.
If the system is flawed, should we just gnash our teeth, count to ten and get on with it or show some mettle and set about changing the system for the betterment of all? This may sound somewhat altruistic but sometimes it just has to be done. After all personal future and the future of the organization might just depend upon it.
Will you skin your knuckles in the process? Darn right you will. Will you risk your job in the process? Quite possibly. Will you be thanked for making things better? Don’t count on it. Then why would we ever want to do it? Quite simply, if nobody did it then how would things ever get better? At times, frankly, I would much rather expend some energy in trying to improve the “system” than waste that energy trying to get around it with the attendant frustrations.
Rarely do the people at the top of the organization see how broken it is. PM's are often in a position to see the good and the bad because they have to interact with pretty much all parts of the organization. The PM's responsibility is to get the "job" done and sometimes this requires an "it is easier to get forgiven than get permission" attitude. I definitely do not recommend charging through the organization like a "bull in a china shop" either. As DJ rightly points out there is no substitute for experience.
Something that was not touched upon is the importance of the support of your team. Without that you are dead anyway regardless of the system. You will gain great respect from them by tackling those “procedures/issues” which frustrate them and do something about it. You will get the opposite if, in their eyes, you appear to excuse yourself on the basis that "the problem is insurmountable and the system is the system".
In my opinion the PM position is primary one of a Leader who uses just sufficient knowledge (too much knowledge or use of it makes you dangerous – “don’t keep a dog and bark yourself”) in the technology to communicate effectively with the team, the organization and the client. That is not to say that a PM does not need to be very familiar with the best practices of professional Project Management such as defined by the PMI for example, but it is primarily a “people” job. I have seen many projects and PM’s fail because they either didn’t understand that or lacked the necessary people skills.
My 2c worth!
Graham Jones
President, VANTUG