Voices on Project Management

By Sree Rao, PMP, PgMP, PMI-ACP

Over the past 18 months, Big Tech companies have let go of several program- and product-adjacent roles, as companies double-down on AI efficiency. One of the roles that is heavily impacted is the TPM (technical program manager) role.

To stay relevant in this changing landscape, here are some do’s and don’ts based on my experience—and my mentors’ suggestions. While I specifically talk about TPMs in this blog post, most of these are relevant to program managers, as well.

Do’s:

• 1. Run a pre-mortem for your career. Yes, you heard that right. Similar to how we run pre-mortem for our programs to identify failure points, do a pre-mortem for your career. Analyze how big of a risk it is for your role to be replaced. Identify what you can do if that happens. Do you have an option to pursue a different career? Are there any skillsets that you can acquire to stay ahead of the competition?
• 2. Become product-fluent, not just process-fluent. Earlier in my career as a TPM, I used to get consistent feedback that I should understand all the requirements. Based on that feedback, I started focusing a lot more on product requirements. That made a lot of difference in how I managed the programs. I spent a lot more time not only understanding the requirements, but also playtesting the product, identifying bugs and making suggestions. As you become more senior, building that product knowledge is a must. Dedicate time to build that knowledge.
• 3. Dig into the technical stack. One of my mentors said that he spends four hours every weekend reading up on the technical documents so that he can keep up with the team’s work. While not everyone can spend time over weekends for this, it is important to carve out the time to understand the architecture, the trade-offs, and the technical debt lurking under the hood. This will help you gain more credibility with your team.
• 4. Leverage AI tools to automate the busywork. Status reporting, risk tracking, analyzing data and even meeting notes…use artificial intelligence to help. Free up your time for higher-value work, and show your team you’re always looking for ways to work smarter.
• 5. Be proactive and stay ahead of risks. TPMs who thrive are those who bring order to chaos. Proactively surface ambiguities, clarify priorities, and communicate relentlessly. Anticipate blockers, dependencies, and resource gaps before they become emergencies. Your ability to foresee and mitigate risks is what sets you apart.

Dont’s:

• 1. Don’t just be a meeting scheduler. I have heard that “TPMs are glorified admins.” If you’re only booking rooms and sending invites, you’re not adding strategic value. There have been several times where people ask me to schedule meetings even though I don’t even need to be in that meeting. I have politely started pushing back on this. When asked to schedule a meeting, you can say: “I typically schedule meetings where I drive the agenda. In this case, I am not driving the agenda. Happy to do it this time.”
• 2. Don’t just be a paper pusher. Status reports and documentation are important, but they’re not your whole job. Focus on driving outcomes, not just tracking them. Additionally, ensure that status docs drive decisions.
• 3. Don’t just be a reminder service. Following up on action items, tasks and tickets is one of our job responsibilities. However, that should not be our biggest contribution. Figure out ways to reduce the number of manual follow-ups. Example: Create a tracker with all the action items and set up a recurring placeholder calendar invite (daily, weekly, etc., depending on the need) with a link to the tracker.
• 4. Don’t just be an event organizer. Planning offsites and other team events is fine, but it’s not your core value. Be the person who drives programs forward, not just the one who plans the party.
• 5. Don’t wait for direction. TPMs who sit back and wait for other people to tell them what they need to do are the first to go. As mentioned in the Do’s section above, be proactive!

Key takeaways

We should prioritize deepening our technical skills, understanding our product, and relentlessly demonstrating our impact—or risk being left behind. The best TPMs are those who bring clarity, leadership, and technical insight to the table every single day.

In the comments let me know the Do’s and Don’ts that resonated with you. Also let the community know your suggestions!

By Sree Rao, PMP, PgMP, PMI-ACP

“Begin with the end in mind” is one of the recommendations from The 7 Habits of Highly Effective People by Stephen Covey. Extending that to program management, “Begin with exit criteria” should be one of the habits of an effective program manager.

Exit criteria are the specific conditions that must be met before a program/project can be considered complete. Defining exit criteria is one of the most critical aspects of ensuring a successful product, feature or project launch.

Exit criteria depend on the type of the program. For example, construction projects would have different criteria from software programs. My experience is in software development, and so the examples and insights I share in this post are about software programs.

I will discuss the importance of defining exit criteria and share some tips on how to create effective ones.

Importance of Exit Criteria

Exit criteria are a set of predefined conditions that serve as the benchmark for determining whether a feature is ready to be deployed to meet user needs and quality standards. Exit criteria can be set at various phases of a program, like going from the quality assurance phase to user acceptance testing.

By establishing these criteria early in the development process, teams can ensure that everyone involved in the project shares a common understanding of what leads to a successful outcome. This alignment helps prevent misunderstandings or miscommunications that could lead to program delays.

Clear exit criteria also promote accountability among team members. When each person knows exactly what is expected of them in terms of deliverables and quality standards, they can work more efficiently.

Additionally, having well-defined exit criteria allows teams to track progress more accurately and identify potential issues earlier in the development cycle, making it easier to course correct if necessary.

Creating Effective Exit Criteria

Determining the exit criteria depends on the type of program and the goals of the program. If it is a new feature development, then the exit criteria would be dependent on the success criteria for that feature. If it is a program to reduce bugs across the team, exit criteria would be different.

The best way to come up with exit criteria would be to think about what success would look like for that feature and then create exit criteria accordingly.

Here is how to create effective exit criteria:

• Collaborate with stakeholders: Involve key stakeholders such as product managers, designers, engineers, data scientists and testers when defining exit criteria. This ensures that diverse perspectives are taken into account and that the criteria reflect the needs of all parties involved. Once you set the criteria, ensure you get signoff from all the key stakeholders.
• Focus on user needs: Exit criteria should prioritize user satisfaction and the fulfillment of their requirements. Consider what features and functionality users expect from the product and make sure these are reflected in your exit criteria.
• Set measurable criteria: Define criteria that can be objectively measured and verified. For example, instead of saying "the feature should perform well," specify that "the page should load within three seconds for 95% of the users."
• Balance quality and time constraints: Exit criteria should strike a balance between ensuring high quality and meeting project deadlines. While you can set a criterion that there should be zero open bugs, in reality it might not be possible. Hence, establish criteria that accept a certain level of imperfection while still meeting user needs and business objectives.
• Regularly review and update criteria: As the project progresses, reassess your exit criteria to ensure they remain relevant and achievable. Don’t wait until the end to measure and evaluate.

Best Practices for Setting Exit Criteria

It is crucial that the exit criteria are both realistic and measurable. This means that they should be achievable within the given timeframe and resources, and there should be a straightforward method to measure whether each criterion has been met. Use S.M.A.R.T goals (specific, measurable, achievable, realistic, timebound) for exit criteria as well.

• Use prior data and metrics: If you already have prior data, then use that to guide your exit criteria. If you do not have prior data, then look for benchmarks within your industry to figure out what constitutes a good score.
• Prioritize: Prioritize your exit criteria based on their importance and impact on the program's success. Similarly, identify the likelihood of achieving that exit criteria.
• Limit the number of exit criteria: While the number of criteria depends on the complexity of the program, don’t create too many and cause analysis paralysis. It is more important to focus on creating a clear and comprehensive set of criteria that aligns with the program's objectives, rather than trying to hit a specific number.

Here are some sample exit criteria for a software user experience-related program. I intentionally kept it very generic:

Conclusion

Defining exit criteria is an important aspect of managing a successful program launch. I ran some programs without aligning on exit criteria at the beginning of the program and had to scramble toward the end, which caused a lot of stress—and in some cases program delays as well.

By setting clear, measurable and collaborative criteria, you can ensure that your team is aligned and working toward a common goal. Remember that exit criteria should prioritize user needs; balance quality and time constraints; and be regularly reviewed and updated throughout the development process. By following these guidelines, you can significantly increase the likelihood of a smooth and successful program launch.

By Sree Rao, PMP, PgMP, PMI-ACP

We are almost at the end of 2023! As I take a moment to reflect on this wild ride of a year, here are three key lessons I learned that I wanted to share with you all.

1. Embrace change: Projects are like a box of chocolates…you never know which ones might get canceled.
As program managers, we are no strangers to change. Yet some types of changes are easier to deal with than others. 2023 has been a turbulent year for me with multiple project cancellations right before releasing them to production.

It was super demotivating. But as technology continues to evolve, customer needs shift and market trends change, it's essential to stay flexible and change course as strategy demands. If you ever have to deal with such a situation, rather than feeling demotivated you should embrace it as an opportunity for growth and learning. By doing so, you'll be better equipped to lead your team through the ups and downs.

One of my mentors gave this perspective, which has helped me immensely: “We get paid to do the work without promises that the features/projects will be released to production. So as long as you get paid and you are continuing to learn, do your best work and leave the rest.”

2. About pursuing your passion: Stop comparing yourself to others.
You might have heard this advice from several people: If you pursue your passion, your work will be more enjoyable. For the longest time, I have been beating myself up because I don’t have any passions (unless binge watching TV counts as a passion? :)). I personally do not find this advice to be practical, so I made peace with the realization that it is important to be content with myself rather than compare myself to others who are “pursuing their passion.”

What I realized is that we can pursue our interests in other ways and means instead of completely switching careers or trying to turn hobbies into a living. We can pursue our passions/interests in small ways like finding opportunities in the domain that we are interested in. As an example, if your hobby is photography and photo editing, perhaps you could continue being a program manager but find a job in a company that specializes in photo editing software like Adobe.

Find the domain or area that brings you joy—whether it's event management, innovation or team building—and find opportunities in that domain. When you enjoy what you do, everyone benefits—not just your own well-being, but also your program's success.

3. Attitude of gratitude: The secret ingredient to well-being, in both your professional and personal life!
Last but not least is cultivating an attitude of gratitude. Sure, there are always things that could have gone better (like projects not getting canceled), but be grateful for what we have.

As a program manager, we have the privilege of working with talented team members who contribute their skills and expertise to our projects. Rather than thinking “they are doing their job,” make it a point to express gratitude toward them regularly. A simple "thank you" or acknowledgement can go a long way in building positive relationships within your team
and fostering a supportive work environment. Additionally, practicing gratitude can help reduce stress and improve overall well-being.

By embracing these three lessons, you'll be better equipped to navigate the challenges of program management in 2024 and beyond. Remember, as a program manager, our role goes beyond managing projects; it's about leading people, fostering collaboration and driving impactful results.

As we bid farewell to another year, I want to express my heartfelt gratitude to each and every one of you for your thoughtful comments and engagement. (A special shoutout to our editor Cameron for inspiring me to write and for shaping my musings a better way). Wishing you all a blessed 2024!

By Sree Rao, PMP, PgMP, PMI-ACP

During my initial phases as a technical program manager, I was heavily focused on the execution of programs and didn’t bother much with strategy. As I gained more experience, I realized the importance of understanding strategy and how it can uplevel us as program managers.

Based on my experience, there is a common misconception that TPMs only play a role in program execution once a strategy has been determined. Strategy plays a crucial role in determining the success of any program, so in this post I will discuss why being plugged into strategy is essential for TPMs.

Strategy vs Plan: Understanding the Differences
Before diving into the importance of strategic management, it's important to understand the difference between “strategy” and “plan.” Strategic management involves the formulation and implementation of long-term plans to achieve organizational goals. Simply put, strategy is the what and why, while a plan is the how.

What is Strategic Management?
Strategic management is a vast topic—there are even master’s programs that delve into it in detail (I will not be able to do that kind of justice to it in this post). A high-level summary is that it refers to the process of defining an organization's mission, vision and overall direction, as well as making decisions on how to allocate resources to achieve those goals. It involves analyzing the internal and external environment—identifying strengths, weaknesses, opportunities and threats (SWOT analysis), and developing strategies to address them.

One of the key benefits of strategic management is its ability to provide a clear roadmap for achieving project/program goals. Strategy involves conducting market research, analyzing competitive landscapes, identifying customer needs, and developing long-term plans that align with business objectives. By having a well-defined strategy in place, we can ensure that our projects are focused on delivering value to stakeholders—while also contributing toward the organization's overall success.

Product managers usually create the strategy, but TPMs play a significant part in putting it into action.

Why is Strategic Management Important for TPMs?

1. It forces you to focus on the long term, not just the short term. I have worked with teams that did not have product managers. These teams were identifying and executing on features that would benefit in the short term, but were not necessarily thinking about the long term. This has served us well when the customer base was small, but was not sustainable when the customer base began to grow. This is where TPMs can be force multipliers—by understanding the fundamentals of strategic management, TPMs can help ensure the teams are set up for long-term success.
2. You can track KPIs/benefits over time. As TPMs, we not only should be tracking program/project key performance indicators, but also track if we are achieving the benefits we set out to achieve with the program. This includes monitoring metrics/KPIs well after the programs have been implemented. This involves setting clear targets and KPIs, regularly monitoring progress toward these goals, and making adjustments as necessary based on the data we collect. By having a well-defined strategy in place that includes specific milestones and metrics, we can ensure that our projects are aligned with broader business objectives. This also provides us with valuable insights into how to improve performance over time.
3. It aligns efforts with goals. As the saying goes, “Ideas are a dime a dozen.” In companies that foster a bottom-up culture, we often receive an abundance of project and feature ideas from team members. By understanding the organization's overall strategy, TPMs can help prioritize these ideas based on their alignment with the company's goals. This ensures that resources are used efficiently and avoids confusion about what to focus on.
4. It provides a framework for decision-making. A well-defined strategy provides a framework for decision-making throughout the project/program lifecycle. This involves analyzing various options and their potential outcomes before making a decision, as well as regularly reviewing the strategy to ensure that it remains relevant in light of changing market conditions or customer needs. By taking a more deliberate approach toward decision-making, we can minimize the risk of costly mistakes while also ensuring that our projects are aligned with broader business objectives.
5. It provides data-driven insights. As TPMs, we have access to a wealth of data about the project's progress. By providing data-driven insights into the program's performance—and how we are tracking toward achieving goals—we can help inform strategic decisions and ensure that resources are being used effectively.

Conclusion
Strategic management is a crucial aspect of any successful technical program management effort. By participating in strategy sessions and influencing decision-making throughout the program lifecycle, we can ensure that our efforts align with broader business objectives, minimize the risk of costly mistakes, and provide valuable insights for continuous improvement over time.

Disclaimer: My experience has been only in the tech industry, and I am not sure if this is prevalent in other industries. I would love to know if you have experienced something similar.

As program managers, we have to deal with various conflicts in the workplace. The book Think Again: The Power of Knowing What You Don't Know by Adam Grant calls out valuable insights into distinguishing between task conflicts and relationship conflicts—and this proves useful in reaching effective resolutions.

According to Grant, task conflict refers to disagreements or differences of opinion that arise between team members regarding the tasks they are working on. On the other hand, relationship conflict refers to personal disagreements or clashes between team members that are not related to the tasks they are working on. Relationship conflict could be due to power struggles, personality conflicts or prior conflicts leading to mistrust.

Task Conflict
Task conflict is encouraged as it promotes creativity, critical thinking and innovation. Some examples of task conflicts are: differing opinions on how to design the user experience for a particular product, or the technical architecture for implementing a system.

By having diverse opinions and having team members debate various options, we get an exploration of ideas and solutions. Task conflict often stimulates healthy debate and increases team motivation, as team members feel that their input is valued. Grant states that some organizations build challenge networks (groups of thoughtful critics) into their cultures to stir up task conflict. If your team does not have task conflicts, it might be a sign of lack of trust or other underlying issues.

While task conflict is beneficial, it is important to manage it properly. As program managers, we can play a crucial role in resolving task conflict by implementing the following strategies:

• Clearly define roles and responsibilities of program members. Use tools like RACI.
• Encourage open communication and active listening amongst your team members.
• Maintain focus on the task. Clearly identify the outcome that you are expecting. Team members should focus on finding the best possible solution, and it should not be about winning arguments or proving others wrong.
• Identify points of agreement and points of contention. This will help team members gain consensus easily.
• Use one of the three facilitating techniques (or any technique that you already have in your repertoire) mentioned in my prior blog post, ‘How to Foster Effective Group Decision Making,’ to gain consensus on points of contention.

Relationship Conflict
While task conflict can be beneficial to team dynamics, relationship conflict is detrimental. According to Grant, if task conflict is not managed properly, it can easily escalate into relationship conflict.  Relationship conflicts at work will lead to negative emotions and decreased productivity.

Occasionally, relationship conflict can manifest as task conflict. If you notice that the same individuals have recurring task conflicts even when it is not necessary, it should signal that there are some underlying relationship issues.

I have noticed this a few times with a few of my team members—and upon further investigation, I was able to find that the individuals in question had relationship conflict.

Here are a few tips for dealing with relationship conflicts:

• Set ground rules on how team members should conduct themselves, which includes acceptable behavior and procedures for handling conflict. You can add them as part of your program charter.
• Similar to how open communication and active listening is important for resolving task conflicts, it is important to resolve relationship conflicts as well.
• Identify the root cause of the conflict by talking to the team members involved in the conflict in a one-on-one setting. Avoid taking sides or showing favoritism.
• Resolving relationship conflicts requires handling people’s emotions. Sometimes this results in heated arguments and personal attacks. If you are comfortable facilitating discussions to resolve relationship conflict, go for it. I personally do not try to get into solving team member’s relationship conflicts, as these need to be handled sensitively and might require manager or HR intervention.

While it is not possible to avoid relationship conflict completely at work, you can minimize them. One way to keep relationship conflicts to a minimum is by creating professional boundaries at work and not oversharing your personal information. Getting too involved in others’ personal issues or oversharing your personal information can create unnecessary emotional investment and conflict.

I have had my share of conflicts as well—and wondered why I felt uncomfortable dealing with some conflicts versus others. This insight about task versus relationship conflict helped me figure out the reason why. 

In conclusion, I can attest to the importance of understanding the differences between task and relationship conflict. While task conflict can be constructive if managed properly, relationship conflict is often detrimental. By understanding these differences, we can better manage conflicts and create a more positive, productive environment for everyone involved.

What strategies have you found to be most effective in resolving conflicts? Leave your ideas in the comments below!