In my current program, I have two Project Managers whose primary stakeholders have completely opposite priorities for our shared database upgrade. One wants speed, the other wants maximum security. As a Program Manager, how do I handle this without alienating one of the project teams? Is there a specific PgMP technique for "Stakeholder Diversity" management?
3 answers
Stakeholder Engagement is one of the most weighted domains on the PgMP exam. In a real-world scenario I faced in late 2024, I used a "Stakeholder Map" to visualize the power/interest grid across the entire program, not just per project. You have to move the conversation up to the "Program Objective" level. If the program’s primary goal is security-led (like a bank migration), then the security stakeholder wins, but you must find a "secondary benefit" for the speed-focused stakeholder to keep them engaged. It's about finding the common ground in the Business Case.
Do you have a formal "Stakeholder Engagement Plan" at the program level, or are you relying on the individual project plans? Sometimes a unified communication strategy can help bridge the gap before the conflict turns into a project delay.
Remember that stakeholders are "engaged," not "managed." It’s a subtle shift in the SPM that emphasizes two-way communication over top-down control.
That’s a very important distinction, Mary. Engaging them means they feel part of the solution, which naturally reduces conflict.
Charles, we currently have separate plans, which I now realize is part of the problem. It’s creating silos. Kimberly, the idea of a "Program-level Stakeholder Map" is exactly what’s missing. I need to show both stakeholders how their individual project goals contribute to the larger enterprise value. I’ll start drafting a unified engagement plan this week to bring everyone into the same room and align them with the program’s North Star.