02 operators on consoleSanju Zachariah, Sherif Koussa
Q&ACIO-260602
IT portfolios often become bloated with conflicting priorities that drain resources and blur strategic focus. This article presents expert-tested approaches for portfolio governance that creates clear alignment between IT initiatives and business objectives. Learn practical methods for prioritizing work through triage principles and managing technical exceptions to keep your portfolio lean and purposeful.
Good day,
When there is work to do than we can handle the only way to stay focused is to treat your IT projects like a triage system, not a wish list.
First I make sure every request is tied to a problem that affects how we work. Like delays in getting paid patients waiting too long or staff wasting time. If it doesn't help with one of those things it doesn't get done. This alone cuts down on requests by half.
Second we prioritize work based on how much it will hurt if we don't do it not how money we might make. For example fixing a problem that delays billing and hurts our cash flow is more important than creating an app for patients even if the app seems like a good idea.
The one rule that stakeholders actually followed was simple: no new project can start without identifying what other project will be put on hold. It sounds basic. It changes how people behave. Suddenly every request is a trade-off not just something new to add.
Some people might disagree,. Saying "yes but later" is often worse than saying "no now". It clogs up the system with promises that might not be kept.
If you want everyone to be, on the page make sure everyone can see how much work we can handle and make them choose what to do every time. Also IT portfolio is the list of projects. In this list we prioritize based on business value. We use IT portfolio to manage and prioritize IT projects.
If you decide to use this quote, I'd love to stay connected! Feel free to reach me at sanjuzachariah@portiva.com and info@portiva.com
When requests exceed capacity, focus improves when the portfolio is managed like an attack surface. Every addition creates another place where coordination, oversight, and failure can spread. The strongest portfolios are not the ones doing the most, but the ones carrying the least avoidable complexity. I have worked with teams that regained control by asking one uncomfortable question for every request, does this reduce future exceptions, escalations, or trust erosion, or does it create more of them.
The governance rule that people actually followed was a quarterly exception budget. Only a fixed number of off cycle requests could enter, regardless of seniority. That rule worked because it made urgency scarce. Once exceptions had a cost, stakeholders became far more disciplined about what truly deserved priority.
Cost of delay gives a single yardstick to rank work across value streams. Estimate the money, risk, and customer impact lost for each week a change waits. Combine that with size to find the fastest path to value using a simple score.
Start with rough grades to avoid analysis traps, then refine with real data from sales, support, and finance. Recheck the numbers often so urgent items do not hide behind old guesses. Put cost of delay into your planning cycle now to speed value delivery.
Every backlog item should map to a clear OKR so that intent and impact stay visible. Define key results in numbers that show customer and business value, then link epics and features to them. Use a simple alignment score to sort items that support the same objective.
Build dashboards that roll up delivery progress to OKR progress, not just to output. Hold quarterly reviews to add, drop, or adjust items based on movement of key results. Start tying work to OKRs today to keep the backlog focused on outcomes, not activity.
Capacity should be set by strategic themes and near, next, and later horizons. Give steady space to growth, resilience, and debt reduction so short term fire drills do not crowd out long term health. Limit work in progress in each theme to improve flow and finish rates.
Shift small amounts each quarter as new signals come in, but keep the overall mix stable. Use clear theme charters so teams know how to spend their slice. Set these capacity guards now to align delivery with strategy.
Benefits must be tracked after release to prove value and guide the next choice. Define leading and lagging signs of success before starting the work. Compare actuals to the target often and make the gap plain to leaders and teams.
Set rules for when to pivot, pause, or stop so weak bets do not drain scarce funds. Redirect people and money to winners to grow impact over time. Launch a simple benefits review cadence now to keep the portfolio sharp.
Funding should follow products with stable teams, not one off projects. A rolling budget lets a team plan, build, learn, and improve without pause. Guardrails such as spend caps, simple business cases, and value checks keep discipline without heavy gates.
Oversight then looks at outcomes and customer use, not percent complete charts. This model raises speed and reduces handoffs while staying in control. Move to product based funding with clear guardrails today to unlock flow.
