How do I effectively prioritize projects in a portfolio when every stakeholder claims high priority?
We are currently managing over thirty active projects, and every department head insists their initiative is the top priority for the business. What objective scoring models or frameworks can I use to rank these projects based on actual strategic value and resource availability without causing internal conflict?
2025-03-14 in Project Management by Tyler Henderson
| 14221 Views
All answers to this question.
You need to implement a Weighted Scoring Model (WSM) immediately. This takes the emotion out of the room by grading projects against pre-defined criteria like "Strategic Fit," "ROI," and "Risk." I recommend using the Pairwise Comparison method where you compare two projects at a time to determine which contributes more to the bottom line. This forces stakeholders to defend their "High" priority status against hard data. Once you have a numerical rank, it becomes much easier to explain why Project A is being deferred in favor of Project B, as the decision is backed by a transparent and repeatable scoring process.
Answered 2025-05-18 by Sarah Jenkins
Sarah, that sounds great, but how do you handle "Pet Projects" from the CEO that bypass the scoring model entirely? Is there a way to integrate executive mandates into a standardized portfolio workflow?
Answered 2025-05-22 by Mark Sullivan
-
Mark, you're spot on. In most companies, a "CEO mandate" is its own category. The best way to handle this is to create a "Strategic Bucket" for these projects. This allows you to track their resource consumption separately so the rest of your portfolio isn't penalized. It brings visibility to how much of the team's capacity is being "stolen" by these mandates, which is often a wake-up call for leadership when they see other revenue-generating projects falling behind schedule due to a lack of resources.
Commented 2025-05-25 by Robert Miller
Try using the MoSCoW method for a quick initial filter. It helps categorize projects into Must-have, Should-have, Could-have, and Won't-have, which is a great starting point for any PMO.
Answered 2025-05-28 by Jessica Albright
-
I totally agree with Jessica. MoSCoW is excellent for high-level filtering before you dive into the deep math of a weighted scoring model. It saves a lot of time during the initial planning phase.
Commented 2025-05-30 by Tyler Henderson
Write a Comment
Your email address will not be published. Required fields are marked (*)

