ServiceNow SPM Health Check

What an SPM Health Check Covers

An SPM Health Check is a comprehensive assessment of your Strategic Portfolio Management deployment, examining demand management, portfolio prioritization, resource management, and project delivery. We evaluate whether SPM is enabling effective work prioritization, resource optimization, and delivery of strategic initiatives. The health check identifies gaps where SPM capabilities exist but are not being used effectively, recommends improvements to increase adoption and value, and validates that SPM is supporting your business strategy.

Demand Management Assessment

We review your demand intake process: are requests for work flowing through a structured demand management process, or are decisions being made outside the platform based on informal influence. We assess whether demand is being categorized correctly (project, ongoing operational work, problem-solving) so that different types of work are prioritized appropriately. We evaluate whether demand records contain enough information to make informed prioritization decisions. We identify whether all key demand sources—business units, IT operations, compliance—are routing requests through demand management.

Portfolio Prioritization and Capacity Planning

We evaluate your prioritization process: are projects ranked against clear strategic criteria, or are funding and staffing driven by organizational politics. We assess whether you have visibility of capacity—do you know how many resources you have available and how they are allocated across projects. We review whether you are operating above capacity (committing to more work than resources can deliver), which leads to overwork, delays, and poor quality. We identify prioritization and capacity management improvements.

Resource Management Effectiveness

We assess whether resource needs are being accurately estimated for projects, whether resource allocation is driving realistic delivery timelines, and whether resources are being utilized effectively. We identify whether key skill gaps exist and whether resource strategies address them. We evaluate whether resources are being shifted between projects realistically based on business priority.

Recommendations

The health check produces a detailed report with findings and recommendations prioritized by value and effort. Quick wins—process improvements requiring minimal configuration changes with high impact—are recommended first. Larger initiatives requiring organizational change or process design work are planned in phases. The report helps you build an SPM improvement roadmap.

Portfolio Data Quality and Accuracy

The health check evaluates quality of project and demand data in your portfolio: are project estimates accurate, are resource allocations realistic, is status reporting truthful or are projects consistently over-optimistic about progress. Accurate portfolio data is prerequisite for effective portfolio management. Garbage in, garbage out applies to SPM as much as any system. We assess data quality and identify improvements to increase reliability of portfolio planning.

Prioritization Process Effectiveness

The health check evaluates your prioritization process: are projects ranked consistently against clear criteria, are decisions made objectively or driven by political influence, do prioritization decisions align with business strategy, are priorities re-evaluated when business conditions change. Effective prioritization ensures you are doing the right work and not wasting resources on low-value initiatives.

Delivery Performance and Variance Analysis

The health check examines delivery performance: do projects complete on time and within budget, what causes variances from estimates, are estimates improving over time or consistently poor. This analysis identifies process improvements, training needs, or capacity gaps that, when addressed, improve delivery predictability and success rates.

Strategic Alignment and Business Planning

SPM should align work portfolio with business strategy. The health check evaluates whether projects and demand being prioritized actually support strategic objectives or are misaligned tactical work consuming resources. Strategic alignment ensures limited resources are focused on initiatives that matter most to the business. This alignment should be explicit and visible, not left to assumption or hope.

Resource Utilization and Capacity Analysis

SPM provides visibility into resource utilization: how many projects are each resource assigned to, how is their time being allocated, are they overallocated or underutilized. This visibility enables better resource management. Overallocated resources lead to poor quality work, missed deadlines, and staff burnout. Underutilized resources might be reassigned or trained on new skills. Resource analytics informs staffing decisions—whether to hire, train, or reorganize teams.

Change Management and Organizational Adoption

SPM implementations often require organizational change. Demand management processes must be followed rather than bypassed through political influence. Portfolio decisions must be accepted even when unpopular. Change management helps staff understand and adopt new practices. Training on portfolio management helps staff understand how to use the system. Communication from leadership about why portfolio management matters builds support for the changes.

Is a portfolio review the right move this quarter?

A health check makes sense when the portfolio numbers stop matching the decisions people actually make. The steering committee approves a project, the project shows as green in the portfolio view, and then the delivery team says the work has not started because nobody was allocated. Or the demand queue keeps growing while the approved list stays flat. Those gaps are the signals that justify a review. A review does not fix them by itself. It shows which part of the chain is broken so the fix lands with the right owner.

This guidance is written for the SPM program owner, the portfolio office lead and the finance partner who signs off the budget view. It assumes the SPM application is live and that at least one planning cycle has run on it. If the platform has never been used for a real decision, a health check will mostly measure how much data entry has happened, and a short adoption review is the better first step.

Reading the portfolio for signs that its data is not telling the truth

Before any formal review, a program owner can learn a great deal from three exports: the list of approved projects compared with the projects that have time booked against them, the demand records still sitting in an early state long after they were raised, and the projects whose percent complete has not moved across several status updates. Each export is quick to produce from the demand management and project records. A project approved long ago with no time logged is often a decision that was never really made. A demand record that has aged in intake is often a request nobody owns.

The discipline is to look for patterns rather than single records. One stale project is housekeeping. Many stale projects sharing one manager point to someone who approves work in meetings and never updates the platform, and that is a conversation about process, not a configuration change.

Where the failure usually sits

Health problems in SPM cluster in a few places, and each calls for a different remedy. The table is a starting point for deciding where to look first.

What the reports show	Most likely cause	First thing to check
Approved projects with no people allocated	Resource requests are not raised at the point of approval	Who owns the step that creates resource demand, and whether it is part of the approval itself
Demand backlog grows while approvals stay flat	Intake is open but evaluation has no fixed forum	Whether a named forum meets on a set cadence and sees the full queue, not a filtered one
Every status update reads on track	Status is optional, or nobody challenges it after entry	Whether a status change ever leads to a question from the reviewer
Budget totals disagree with finance	Two sources of cost, and neither is treated as authoritative	Which system holds actual spend, and whether SPM imports it or someone retypes it

None of these rows is about a missing feature. The platform often already holds the data. The problem is that nobody is accountable for entering it, reviewing it, or acting when it looks wrong. Resource-side symptoms in particular are easier to read once you have checked how resource management is wired into approval, not just whether it is switched on.

A review sequence that stays short enough to finish

A health check can drift into a long exercise that ends in a slide deck nobody reads. A short, ordered sequence protects the timeline and keeps the findings usable.

1. Write down the decision the review is meant to inform, such as whether to re-baseline the portfolio, change the intake forum, or defer a platform change. Put it on the first page.
2. Pull the three exports described above for the last complete cycle, and agree which findings are facts and which are interpretations of those facts.
3. Interview the people who create records, the people who approve them, and the people who depend on the output. Ask each group what they would stop doing if the portfolio view were wrong.
4. Group findings by owner rather than by module. A finding that belongs to the portfolio office is handled differently from one that belongs to the platform team.
5. Rank fixes by how much they change a decision against how little they cost to make. Changing who must update status before a forum meets often beats building a new report.
6. Give each fix an owner and a review date, and agree in advance how the next review will show whether the fix worked.

Situations where a review would waste effort

There are situations where the honest answer is to skip the review. If no governance forum exists, a health check will only produce a list of failures with nobody with authority to act on them. Build the forum first and review the portfolio after it has made a few real decisions. If the organization is about to restructure its technology function, the portfolio structure you assess today may be gone soon, and it is usually better to design the new structure and assess that. And if the sponsor has already decided to change the platform, a health check becomes a justification exercise. Ask the sponsor which of these applies before any work starts, because the answer changes what the report should say.

Turning findings into an improvement sequence that people will follow

The most useful output of a review is a short list of changes the people in the room agree to make before the next forum. Long roadmaps often lose momentum quickly. A better format is one page with the top findings, the owner of each fix, and one indicator that tells you whether the fix took effect. For a demand-heavy portfolio that measure is often the share of requests reaching a decision within one cycle. For a resource-constrained portfolio it is how many approved projects have named people allocated by the day work is due to start. Before choosing the resource measure, check the capacity planning signals guide, since the signal picked will shape what the team watches. Pick measures the platform can produce without manual counting, or the measure can decay once the reviewers leave the room.

Questions program owners ask before committing to a review

Can we run the review ourselves, or do we need an outside party?

Internal staff who know the approval history can run the first pass. An outside reviewer adds value when the program owner is also the person whose decisions are under examination, because findings about political prioritization are hard to deliver from inside the same reporting line. The question is independence, not technical skill.

What if the data is so poor that every finding looks like a data problem?

Then the review should say so plainly and recommend a narrow clean-up of the active portfolio only, leaving closed history alone. Cleaning old closed projects rarely changes a decision, and it consumes the time that should go to open work.

Should demand health and project health be reviewed together?

Review them in sequence. Demand health tells you whether the right work is entering the system. Project health tells you whether approved work is delivering. Mixing them hides which problem sits upstream, and the upstream problem usually causes the downstream one.

How do we stop the findings being read as a verdict on one team?

Present findings as properties of the process. A stale project is a fact about how status is requested, not about the person who owns it. Agree the framing with the sponsor before the report circulates, and keep individual names out of the summary page.

Next step

If the portfolio numbers no longer match the decisions being made, a short scoping conversation is the quickest way to decide whether a full health check is worth the effort. Once the findings are agreed, the SPM optimization service covers the platform changes that follow.