ServiceNow Strategic Portfolio Management Best Practices

Strategic Portfolio Management only pays off when a few conditions hold at the same time: strategic goals are written down and shared, a governance forum with clear criteria meets on schedule, prioritisation rests on data rather than volume, the portfolio is balanced across types of work, dependencies are managed explicitly, health is measured, resources are planned honestly, risks are owned, the portfolio is reviewed and rebalanced on a cadence, and decisions are communicated. Each practice below states the reason behind it and what good looks like, followed by how to treat each as a condition rather than a slogan.

Practice 1: Define and communicate strategic goals

Before managing the portfolio, define what strategic goals you are trying to achieve. Examples: grow revenue, expand into new markets, improve customer satisfaction, reduce operational cost.

Reason: portfolio decisions must be traceable to strategy. If a project does not support a strategic goal, it should be deprioritized or deferred. Every item in the portfolio should answer “how does this help us achieve our strategy?”

What good looks like: strategic goals are documented, communicated to all stakeholders, and reviewed quarterly. Portfolio reviews explicitly evaluate projects against strategic goals.

Practice 2: Establish clear portfolio governance

Portfolio governance defines who makes decisions, what criteria they use, and how often they review. A portfolio steering committee (executive leaders, business heads, chief architect) meets monthly or quarterly to review the portfolio, approve new work, and adjust priorities.

Reason: governance ensures consistent decision-making and accountability. Without it, work decisions are made ad hoc and conflicts are resolved based on politics.

What good looks like: governance committee meets on schedule, has clear decision criteria, documents decisions, and escalates conflicts to appropriate level.

Practice 3: Use data-driven prioritization

Prioritization should be based on data and criteria, not opinion or politics. Define criteria: business value (revenue, cost savings, risk mitigation), strategic alignment, feasibility (time, cost, resources), and dependencies.

Reason: data-driven prioritization is defensible and consistent. Stakeholders understand why their project was prioritized high or low.

What good looks like: portfolio has a prioritization framework, scoring is documented, and prioritization is reviewed for consistency and bias.

Practice 4: Balance the portfolio

Portfolio should be balanced between different types of work: strategic initiatives (big transformations aligned with strategy), tactical improvements (smaller enhancements, optimizations), and maintenance (keeping systems running, paying down technical debt).

Reason: all work is needed. Pure focus on big strategic initiatives leaves the foundation neglected. Balanced portfolios deliver both transformation and stability.

What good looks like: portfolio has targets (for example, the largest share strategic, a significant proportion tactical, a modest share maintenance). Review quarterly to ensure balance.

Practice 5: Manage dependencies explicitly

When project A depends on project B, sequencing matters. If B is delayed, A is blocked. Identify all cross-project dependencies and manage them.

Reason: dependencies create risk. If not managed, projects miss dates and cascade delays through the portfolio.

What good looks like: dependency map is maintained, dependencies are reviewed in portfolio governance, prioritization considers dependencies.

Practice 6: Track portfolio health and metrics

Define portfolio health metrics: on-time delivery rate (what percentage of projects deliver on schedule), within-budget rate (what percentage stay within budget), value realisation (what percentage of promised benefits are achieved), and resource utilisation (are people assigned to projects).

Reason: metrics let you see what is working and what is not. If on-time delivery is weak, you have an execution problem. If value realisation falls short of what was promised, you have an estimation or execution problem.

What good looks like: metrics are tracked, reported monthly, and used to guide improvements in governance and execution.

Practice 7: Manage resource constraints realistically

Resource capacity limits how much work you can do. If the team is small and each project needs several people for a long stretch, only a few projects can run in parallel. Overcommitting resources leads to delay, quality issues, and burnout.

Reason: realistic resource planning prevents overload and improves delivery.

What good looks like: portfolio has a resource capacity plan, projects are resourced realistically, and resource allocation is reviewed in governance meetings.

Practice 8: Plan and manage risks

Portfolio risk includes: resource risks (people leave, expertise gaps), technical risks (unknown architecture, integration issues), business risks (market changes, priorities shift), and execution risks (estimation error, schedule slippage).

Reason: risks materialize and impact delivery. Proactive risk management surfaces issues early so you can plan mitigation.

What good looks like: each major project has a risk register, risks are reviewed in governance, and mitigation plans are in place for high-impact risks.

Practice 9: Regular review and rebalancing

Portfolio is not static. Business priorities change, projects get delayed, new opportunities emerge. Review the portfolio quarterly: what should we start, what should we stop, what should we defer, what has changed in our context?

Reason: static portfolio alignment degrades over time. Regular review keeps portfolio aligned with current strategy and reality.

What good looks like: portfolio review is scheduled, has documented decisions, and includes all stakeholders.

Practice 10: Communicate portfolio decisions

Stakeholders need to understand what is in the portfolio, what was prioritized high/low, and why. Communication prevents confusion, reduces politics, and builds buy-in.

Reason: transparency about decisions is trust-building. When stakeholders understand the criteria and reasoning, they accept decisions even if disappointed.

What good looks like: portfolio decisions are communicated in writing (dashboard, report, presentation), rationale is explained, and feedback channel exists for questions.

Treating each practice as a condition, not a slogan

Portfolio practices are easy to agree with and hard to keep. Every organization accepts that strategy should drive priorities, and very few can say on a given Tuesday which active project would be stopped first if the budget fell. The useful way to read a practice is as a set of conditions that must already be true for it to work, plus a visible sign that it is working. The table gives that reading for five of the commonest practices.

Keeping prioritization honest under pressure

Prioritization often fails in the week a senior sponsor asks for something new. The portfolio was agreed, the scores were recorded, and then a request arrives with no score and a deadline. The practice that holds is a simple rule: new work enters the same intake as everything else, and the trade-off is shown next to it. If the new item goes ahead, the item it displaces is named and its owner is told in the same message. Contested roadmaps can be read alongside the strategic roadmap prioritization post. Treat any single split as a starting hypothesis. The right mix depends on how much technical debt the organization carries, how exposed it is to a single system failing, and how much change the business can absorb in a year. What the portfolio should show is that the mix was chosen deliberately, with a named decision maker, and that the mix is reviewed when the conditions behind it change.

Dependencies as a standing item, not an afterthought

Dependencies are rarely the reason a project is proposed, so they are the first thing left out of the intake. The practice that works is to make dependency fields required at the point a project is approved, and to put dependency review on the agenda of every portfolio meeting. A short list of items with a blocked status, each with the owner of the blocking item named, is often enough to keep the conversation specific.

A review cadence that changes decisions

1. Begin each review with the items whose status changed since the last one, not with the full list.
2. Give each item a recorded decision: continue, change scope, re-sequence or stop. A review that ends with no recorded decisions has not reviewed anything.
3. Check the capacity view before approving any new work, so that the portfolio is not promised more than the people in it can deliver.
4. Publish the decision log to the people who funded or delivered the items, within the same working day where possible.

When a practice is not working

A practice that is not producing its sign should be dropped or redesigned rather than repeated harder. Quarterly reviews that never change a decision are a common example. The fix is often to shorten the review, narrow its scope to the items with changed status, and track how many decisions it produces. If the number stays at zero for several cycles, the problem is the inputs, and the work belongs in the data, not in the meeting. The portfolio KPI guide covers measures that can show whether the inputs have improved.

Which practice should we start with?

Start with the one that has the weakest condition. For many organizations that is the goals statement, because every later practice depends on it. If the goals are not written down, the rest of the practices have nothing to measure against. Where the portfolio also has to be run as a set of platform services, the platform governance charter post covers who decides on platform matters, which is a related question once goals have owners attached.

Do these practices apply to a small portfolio?

Yes, but at a smaller scale. A portfolio of a handful of items does not need a formal committee or a monthly board. It does need written goals, a recorded decision on each item and a single place where status is kept current. Scale the forum to the number of decisions, not to an idea of what a mature organization should look like.

How do we know a practice has become a ritual?

When the meeting happens, the pack is produced, and the decisions column is empty or repeats last cycle. Put this question to attendees: which decision did the review change in the last cycle? If nobody can, the practice has become a ritual and needs redesigning.

Who should own the practices?

The portfolio lead owns the process and the sponsor owns the decisions. Mixing those roles means the people who run the meetings are also the ones who decide what the meetings produce, and the decisions tend to drift toward whatever is easiest to record.