ServiceNow SPM Optimisation

Strategic Portfolio Management optimisation is the work of making an existing portfolio forum decide better, not just faster. This guide helps a sponsor or portfolio lead find which forum decision is going wrong, test a revised rule on past cases, and decide whether optimisation is worth starting yet.

Optimising Strategic Portfolio Management starts with the decision problem, not the platform: where decision latency comes from, which work gets stopped or deferred and what that teaches, and which dashboards nobody uses. This page covers portfolio health assessment, resource allocation and capacity planning, roadmap clarity, investment decision quality, governance forums, risk and dependency analysis, strategic scoring, retrospectives, reporting and executive communication, an optimisation sprint in five steps, where effort pays off first, and when optimisation is premature.

Portfolio Health Assessment

Portfolio health is assessed by reviewing project status, budget performance, schedule performance, and risk assessments. A health dashboard shows which projects are progressing well and which need intervention. Projects with deteriorating health are identified early so corrective action can be taken.

Assessment includes review of project governance: are projects being tracked consistently? Are all projects at the same level of detail in their plans? If governance is inconsistent, portfolio metrics are unreliable.

Resource Allocation and Capacity Planning

SPM shows what resources are allocated to which projects. Optimisation identifies resource constraints: which skills are over-committed, which are under-utilised. Optimisation also identifies resource conflicts: when the same person is assigned to multiple projects without consideration of capacity.

Capacity planning uses resource data to forecast whether the current resource supply is sufficient to deliver the planned work. If demand exceeds capacity, portfolio decisions are needed: delay projects, reduce scope, add resources, or cancel projects.

Roadmap Clarity and Dependencies

The portfolio roadmap should show the sequencing of projects: which projects need to complete before others can start, what dependencies exist across projects, and what the timeline looks like. Optimisation clarifies dependencies that have been overlooked, preventing surprises when a critical dependency isn’t ready.

Investment Decision Quality

Optimisation improves decision quality by ensuring investment decisions are based on data and consistent criteria. Portfolio prioritisation should consider factors such as strategic alignment, financial return, risk, and resource requirements. Clear prioritisation criteria ensure decisions are consistent and defensible.

Portfolio Governance and Decision Forums

Portfolio governance defines how decisions are made. A portfolio steering committee should meet regularly to review portfolio status, make investment decisions, and reallocate resources as circumstances change. Optimisation ensures governance forums are effective and decision-making is timely.

Oblytech’s SPM Optimisation Services

We assess portfolio maturity and identify optimisation opportunities. We review portfolio health, resource allocation, and governance processes. Implementation includes improving portfolio dashboards and reporting, clarifying investment decision criteria, and improving portfolio governance forums. Consulting addresses how to align portfolio with strategic goals and improve execution.

Risk and Dependency Analysis

SPM should identify dependencies between projects: which projects are prerequisites for others, what resource conflicts exist, what risks could delay multiple projects. Dependency visualisation helps portfolio managers understand how projects are connected and how delays in one project ripple through the portfolio.

Strategic Alignment and Scoring

Projects should be scored based on how they align with strategic goals. Scoring models weight factors like financial return, strategic impact, and risk. Consistent scoring ensures portfolio decisions reflect strategy rather than politics or urgency.

Change Management and Governance

SPM decisions should go through appropriate governance. Changes to portfolio priorities should be reviewed by the steering committee. Investment decisions should be documented with rationale. Governance creates accountability and ensures decisions are defensible.

Lessons Learned and Portfolio Retrospectives

After projects complete, retrospectives capture lessons learned about planning accuracy, resource allocation, and risk management. Portfolio learning improves future planning. Retrospective data informs portfolio process improvements.

Portfolio Health Dashboards and Reporting

SPM dashboards provide visibility into portfolio status, showing which projects are on track, which are at risk, what resources are allocated, and what budget has been spent. Dashboards enable quick assessment of portfolio health without detailed project dives. Status reporting to executives is driven by portfolio dashboards showing aggregate metrics.

Executive Communication and Decision Support

The optimisation services include improving how portfolio data is communicated to decision-makers. Executive dashboards, portfolio reviews, and status reports should highlight key decisions needed. Clear communication ensures executives have the information needed to make strategic investment decisions.

Competitive Portfolio Analysis

SPM can include competitive analysis: what capabilities competitors have developed, what investments competitors have made. This analysis informs whether the organisation’s portfolio is sufficient to compete effectively. Portfolio decisions should be informed by competitive landscape assessment.

Portfolio Transparency and Stakeholder Engagement

Transparent communication about portfolio decisions builds trust. Stakeholders should understand why projects were selected and why others were deferred. Open communication about trade-offs and decision criteria helps stakeholders accept portfolio decisions even when their preferred projects weren’t selected.

Technology Refresh and Platform Evolution

Portfolio management includes decisions about technology refresh: when to retire old systems, when to modernise platforms, when to migrate to cloud. These decisions have long-term strategic importance and should be made through portfolio governance, not ad-hoc.

Where optimization effort pays off first

An SPM instance that is technically sound can still produce a poor portfolio. The usual symptoms are a forum that approves almost everything it is shown, projects that run for a long time after their business case has lapsed, and funding that moves to whichever sponsor is most persistent. Optimization is the work of changing those outcomes. It is different from configuration, and it should start from the decisions the forum makes rather than from the screens the platform offers.

This guidance is for the sponsor of the portfolio, the chair of the investment forum and the portfolio lead who must defend the output. It assumes the instance is live and the forum meets, but that its decisions are slow, reversed or hard to explain.

Diagnosing the decision problem before touching the platform

Start by naming the decision that is going wrong, then trace it backwards. A forum that never stops a project is a different problem from a forum that stops projects but restarts them the following month. The table maps common symptoms to the place where the investigation should begin.

Symptom in the forum	Likely root	Where to look first
Almost everything is approved	Scoring does not separate options	Whether the scoring criteria differ enough to rank two real candidates differently
Projects are never stopped	No stop criteria were agreed at approval	Whether approved projects carry an explicit review point with conditions for ending them
Stopped projects come back	Deferred work has no owner or re-entry rule	Whether deferral records keep the original business case and a named sponsor
Decisions take several cycles	Papers arrive late or incomplete	The date papers close, and whether the forum can decide with the information the paper actually contains

The point of the table is to stop the team from configuring its way out of a governance problem. A stop criterion cannot be added to a workflow if nobody has agreed what should trigger a stop.

An optimization sprint in five steps

Run optimization as a bounded piece of work with a fixed set of decisions to test, not as a general review of everything. The sequence below keeps it focused.

1. Choose one forum decision to improve, such as stop decisions or re-entry of deferred work, and write down how it is made today.
2. Pull the records for the last few cycles that touched that decision and read them, not just their totals.
3. Draft a revised rule for the decision, with its trigger, the evidence it needs, and the person who makes the call.
4. Test the rule against past cases. Ask whether the forum would have decided differently, and whether that difference is one the sponsor would have wanted.
5. Adopt the rule for one cycle, then review how the forum used it before extending it to other decisions.

Decision latency as the measure that matters most

Most portfolio dashboards report how much work is in flight. Fewer report how long decisions take. Decision latency, measured from the date a request becomes complete to the date the forum records a decision, is often the most revealing figure. Long latency often means the forum is working from incomplete papers, that its membership is too large to agree, or that decisions are being re-opened outside the meeting. Track it by request type so that a slow category is visible rather than averaged away. Keep the measure simple, because a complicated measure will be argued about instead of acted on.

Learning from stopped and deferred work

Stopping a project is a decision that should produce learning, but in many portfolios it simply disappears. The business case, the people allocated and the spend to date vanish from view. Optimization should record why a project was stopped, what was salvaged, and whether the same need is likely to return. A short closing note on each stopped item, reviewed once a quarter, gives the forum evidence about its own judgment. Over time it shows which kinds of project are consistently optimistic at approval, which is more useful than any general lesson about estimation.

Retiring the dashboards and reports nobody uses

An optimized instance often has fewer reports, not more. Each report carries a maintenance cost and a risk of showing a different number from the forum paper. Check which dashboards have been opened in the last few cycles, ask the sponsor which figures they actually quote, and retire the rest. Replacing a crowded executive page with the three figures the sponsor uses in decisions is often the most visible improvement a team can make.

When optimization is premature

Hold back if the forum has not yet agreed what it is for, if the portfolio is being restructured, or if the instance has fewer than a few complete decision cycles behind it. Optimizing a process that is about to change wastes effort and tends to lock in habits the new structure does not need. In those cases the better investment is a clear statement of the forum’s purpose and a small set of agreed rules.

Questions sponsors raise about optimization

How do we know the forum is making better decisions, not just faster ones?

Look at what happens after the decision. Check whether funded projects meet the conditions the forum set, and whether stopped projects were genuinely stopped. Speed without that follow-up can simply mean the forum is approving more quickly.

Should the scoring model be changed to fix poor decisions?

Only after the stop and re-entry rules are working. A new scoring model applied to the same unclear decisions produces new numbers that the forum still cannot act on.

Who should own the stop criteria?

The sponsor, agreed with the forum. The portfolio lead records them and checks compliance, but a stop rule that the sponsor did not set will be quietly ignored at the first difficult case.

How often should optimization be repeated?

Repeat the sprint when a decision has been revisited more than once without a clear reason, or when the forum changes membership. Continuous optimization sounds disciplined but in practice it produces constant small changes that nobody can trace.

Next step

The optimization services page describes what an optimization engagement covers for an existing instance, and the strategic portfolio management guide explains how the portfolio layers fit together.