Project Management

Please login or join to subscribe to this thread

Best PM Lesson Learned/Bit of Wisdom

linkedin twitter facebook   Agile   Lessons Learned   PMO   Utility  
avatar
Jon Fedor Project Manager, Cloud Connected Services| Rockwell Automation Cleveland Heights, Oh, United States
Hi there, Everyone!

I'm new on the PM scene, a recently minted PMP, and looking to learn from people who've already been walking the path. I'd love to know the top, best thing you've learned experientially during your career as a PM.

One thing piece of wisdom/caution/inspiration/concrete advice, etc.

I'd love to hear from you all and benefit from you all.

Thanks so much, in advance!

Jon
Sort By:
< 1 2 >
avatar
Jon Fedor Project Manager, Cloud Connected Services| Rockwell Automation Cleveland Heights, Oh, United States
Apr 15, 2017 9:14 PM
Replying to Griselda Friss de Kereki
...
hi Johathan and welcome to the team,

I'd say there are lots of best practices and lessons that we get learn along the way; and also lots of quotes of wisdom that help as well. Let me highlight some that I think have been very useful to me:

* Build an environment of trust, not only with your team, but also with your stakeholders. And this implies many things:

- for your team, they shouldn't feel afraid of highlighting issues, concerns or risks that they foresee. It's much better to know when you are about to hit a wall, than hit it with your eyes closed. On team meetings I always asks them: is there anything you feel we are missing or doing wrong? do you foresee any risk on this? should we be concerned about anything?
if it is not possible for them to meet a dead line, let them tell you and explain, and then see all of you together what can be done. If there is a mistake (from anyone, you included), acknowledge it, don't focus on culprits, learn from it, and try NOT to make the same error again, as i say to my teams / students, let's make sure all our mistakes are original, never a repeated one! :)

- recognize good work when done, take care of your team.

- don't be afraid of raising risks or flags, and make sure your team is aligned too. The same that applies to you and your team, applies to the business and stakeholders. Personally, when raising a risk I also try to share a mitigation or contingency plan as well, so that they are aware "we anticipate that this may happen" and "we are doing this to try to avoid it" or "we'll do that in case it happens". Personally I feel more comfortable with that approach that keeping risks in mistery (no to "scare people" and them give them a nice shockdown with the issue).

- relatd to the previous one, don't be afraid with highlighting an issue when it has happened. I try to also present the solution or paths we are analysing to fix it as well, when presenting the issue (at least, that way you are conveying the message "this happened, but we are already working to have it fixed and we are taking this steps") so that diminishes "nervousy" regarding the situation. Obviously, you'll have to keep in mind what is the best way to convey the situation to each stakeholder (shall I call this person on the phone, speak to him/her beforehand, shall i call out for a meeting with all and announce there, send a mail, etc). In this kind of situations is particularly where your stakeholder analysis pays off.

On quotes, I really like this one from Walt Disney: "“Of all the things I’ve done, the most vital is coordinating the talents of those who work for us and pointing them towards a certain goal.” 

I know this was a long response. Hope it helps and that you enjoy your career on Project Management.

Regards,
Griselda
Thanks for the good words, Griselda. The people-oriented nature of project management is a huge attraction to the job for me. Just about everything you touched on involves or relates to dealing with human brothers and sisters; I love that.

I really appreciated your encouragement to take care of the team especially when good work is done!
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Jonathan, Welcome and Congratulations.

Transparency. Don't hide things. Be up front, honest, there to help shepherd the team and stakeholders through the process.
...
1 reply by Jon Fedor
Apr 17, 2017 11:35 AM
Jon Fedor
...
Appreciate that, Andrew; thanks!

Shepherding a team/stakeholders through the process is a huge responsibility. Your encouragement around transparency is really good and goes a long way in making the process more concrete and successful; thanks!
avatar
Jon Fedor Project Manager, Cloud Connected Services| Rockwell Automation Cleveland Heights, Oh, United States
Apr 17, 2017 10:32 AM
Replying to Drew Craig
...
Jonathan, Welcome and Congratulations.

Transparency. Don't hide things. Be up front, honest, there to help shepherd the team and stakeholders through the process.
Appreciate that, Andrew; thanks!

Shepherding a team/stakeholders through the process is a huge responsibility. Your encouragement around transparency is really good and goes a long way in making the process more concrete and successful; thanks!
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
One thing? This might not be the most important thing to know, but it's easy to forget so worth listing here:

Don't wait until the end of the project to hold lessons learned. Get feedback at the end of each phase and apply relevant lessons learned to the next phase.
...
1 reply by Jon Fedor
Apr 17, 2017 3:31 PM
Jon Fedor
...
So true, "one thing" is a totally unreasonable request but it's resulting in some excellent suggestions.

Great words! I was just searching around for templates for lessons learned today because this is a huge area of improvement for me and our PMO, in general. Really need to start capturing lessons learned much better.

Thanks for the wisdom!
avatar
Jon Fedor Project Manager, Cloud Connected Services| Rockwell Automation Cleveland Heights, Oh, United States
Apr 17, 2017 12:14 PM
Replying to Aaron Porter
...
One thing? This might not be the most important thing to know, but it's easy to forget so worth listing here:

Don't wait until the end of the project to hold lessons learned. Get feedback at the end of each phase and apply relevant lessons learned to the next phase.
So true, "one thing" is a totally unreasonable request but it's resulting in some excellent suggestions.

Great words! I was just searching around for templates for lessons learned today because this is a huge area of improvement for me and our PMO, in general. Really need to start capturing lessons learned much better.

Thanks for the wisdom!
avatar
Deepesh Rammoorthy ICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood Service Tarneit, Vic, Australia
Welcome Jonathan . My pearls of wisdom

1) Project Manager is a facilitator. They might come from an Architecture or Analysis Background but once they have worn the PM hat, they should let the members with specific roles in the project do their job and trust the outcomes.

2) Project Manager must be politely persistent. Must always have a friendly and empathetic attitude but at the same time must always be at the Triple Constraints of time , scope and cost like a blood hound .

3) Must always maintain a good rapport with the Sponsor and always escalate if tolerances are being exceeded

4) Always be on the lookout for risks

5) Always promote knowledge sharing and collaboration among your team members. Never forget to acknowledge good work.

6) Try face to face meetings with the stakeholders as much as possible. know that Body language is the most effective way to communicate.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I am not bound to please thee with my answer."

- William Shakespeare

ADVERTISEMENT

Sponsors