Categories: Best Practices, Lessons Learned
By Sree Rao, PMP, PgMP, PMI-ACP
From rookie mistakes to hard-won victories, my decade-plus journey as a program manager has been full of lessons. Here are the ones that stuck with me the most. As you ring in 2023, I hope these lessons will help you on your PM journey.
1. Don’t get too caught up in processes and labels. In my early career as a PM, I was stuck on implementing agile methodologies like scrum, Kanban etc. With experience, I have come to realize that it is important to figure out a process that works in the team-specific context rather than sticking to the labels of agile versus waterfall.
What is effective for one team might or might not work for another team. We get better engagement and buy-in if we involve the team in setting up processes and make the changes that the team recommends. It is important to rely on the collective wisdom of the team.
2. Don’t try to control the outcome of meetings. I place a high value on clear agendas and sticking to them in meetings. However, there have been occasions where my meetings did not go as planned. At first, this upset me, but I eventually came to understand that it is our responsibility to be prepared (and we cannot always control meeting outcomes). It is important to read the room and adapt meetings as needed.
3. Don’t overload yourself. During the early stages of my career, I was hesitant to decline additional work, even if my workload was already overwhelming. I was afraid of not meeting expectations.
However, it is important to be aware of your own limitations and feel empowered to say “no” when necessary. While we may not always have a choice, it is important to carefully consider how much work you can realistically handle. Is it better to do a good job with what you already have on your plate, or lower the quality of your work by taking on more?
Constantly being overburdened with work can prevent you from having the time and energy to identify opportunities for personal and team growth.
4. Don’t be a default meeting scheduler. There is a misconception that it is a PM’s job to schedule meetings, and as such I have often been asked to schedule meetings and take notes. However, this is not the primary focus of a PM role. To better manage my workload and prioritize, I have learned to say “no” to scheduling meetings unless I am driving the agenda or have a significant interest or stake in the meeting outcome.
While I may make exceptions in certain cases (such as when I need to expedite something), I have learned to be more selective about the meetings that I agree to schedule.
5. Identify single points of failure (SPOF) for projects and their mitigations. As a Technical Program Manager in the tech industry, I have often managed projects where only one engineer is assigned to a project. This is a big risk, as that engineer is now a SPOF for the project.
Whenever possible, it is advisable to request that at least two engineers share the workload of any deadline-sensitive, critical projects to reduce the risk of unanticipated personal emergencies or other risks. Apart from reducing the risk, this also helps with improving team morale as the engineers have someone else to bounce ideas off—and share the workload.
6. Put things in writing. It is important to document commitments or decisions made during your hallway or informal conversations in writing for future reference. Putting things in writing often leads to more careful consideration and follow-through from your team members.
Personally, I have learned the hard way to always get things in writing to avoid any misunderstandings or miscommunications later.
7. Encourage proof-of-concept development. If your team is stuck in analysis paralysis, or if you are trying out a new technology, get management buy-in to spend time creating a proof of concept or a prototype. This can help to quickly demonstrate the potential of the technology or approach and facilitate faster decision making.
8. Include key stakeholders in reviewing status reports before they are published. Early in my PM career, I gave more importance to adhering to timelines than to aligning with key stakeholders. One time, I marked a project as red (behind plan) in a report without first discussing it with the manager of the team that was running behind. That manager was unavailable, and I did not want to delay publishing the status report.
I went ahead and published the report without reviewing it with him. This had unexpected negative consequences, including the manager having to explain the red status to multiple members of the leadership team.
Since then, I have been more careful about how I report project statuses. Before turning a project status red, it is important to consider possible mitigation plans and to review the status with all relevant cross-functional team members and their management. This may slow down the process, but it ensures that all key stakeholders are aware and aligned on the status.
9. Identify projects/programs to cancel. Deciding to cancel a project or program can be challenging, especially if a lot of time and resources have been invested. However, it is important to consider whether the project is still delivering the value that was expected.
Don't let the sunk-cost fallacy (the tendency to continue investing in something simply because of the resources that have already been spent) influence your decision making. It's better to cancel a project and move on to higher-value projects rather than continuing to invest in something that is no longer worthwhile.
10. Be cautious about reporting program status as green/on track. In my experience, it is rare for all the projects in a program to be on track. If you do encounter a situation where all the projects seem to be progressing as per the plan, it’s important to carefully assess the situation and verify that thorough risk analysis has been done.
While there are several other valuable lessons I've learned, I've distilled my most valuable lessons into these top 10 nuggets of wisdom. Project management veterans, what valuable insights have you gained throughout your career? Share your nuggets of wisdom in the comments section below!