ServiceNow Strategic Portfolio Management: Roles, Responsibilities and RACI

Strategic Portfolio Management roles are split between deciding and doing. The Steering Committee makes the final call on which projects proceed, the Portfolio Manager proposes the priority list and monitors portfolio health, and the Business Case Lead writes the justification for each project. The Resource Planner shows whether capacity can carry the portfolio.

Strategic Portfolio Leadership Structure

Strategic Portfolio Management requires a governance structure that balances competing business needs and allocates limited resources to high-value initiatives. The Portfolio Manager owns the overall strategy and health of the portfolio; they lead portfolio planning, prioritization, and governance reviews. The Business Case Lead writes the financial justification and business context for each proposed project, translating business need into project scope. The Steering Committee—comprising CIO, business unit leaders, and financial representatives—makes portfolio-level prioritization decisions about which projects proceed. The Resource Planner forecasts resource availability and identifies constraints that limit portfolio capacity. The Project Manager executes individual projects selected by the portfolio; they report status to the Portfolio Manager, who aggregates status into portfolio-level dashboards. The Portfolio Analyst supports the Portfolio Manager by maintaining portfolio data, running portfolio models, and preparing steering committee materials.

Portfolio Decision Authority

The Portfolio Manager proposes the initial prioritized list of candidate projects, but the Steering Committee makes the final selection. This separation prevents a single person from biasing the portfolio toward their preferred initiatives. If the Portfolio Manager and Steering Committee disagree on whether a project should proceed, the Steering Committee’s decision is final; the Portfolio Manager implements the steering committee’s direction. The Business Case Lead owns the business case analysis and recommendation to proceed or defer; if the steering committee decides to defer a project that the business case owner recommends, the business case owner can escalate to the CFO for reconsideration, but typically the steering committee decision stands. The Resource Planner forecasts capacity and constraints; if forecasts show the portfolio is overcommitted, the Portfolio Manager works with the Steering Committee to defer or descope projects to fit available resources.

RACI Matrix for Portfolio Activities

The following table clarifies roles across strategic portfolio management activities:

Project Selection and Prioritization Logic

Portfolio prioritization should follow a documented framework that the Steering Committee approves annually. Common frameworks include: financial return (projects with highest ROI proceed first), risk mitigation (projects that address critical vulnerabilities proceed), strategic alignment (projects supporting corporate strategy are weighted higher), and capacity constraints (available resources limit portfolio size). The framework should be transparent so that project sponsors understand why their project was selected or deferred. If the framework allows executive discretion (overriding prioritization for strategic initiatives), document the override and rationale so that future portfolio reviews can assess whether discretionary decisions delivered expected value.

Portfolio rebalancing occurs when a high-priority project encounters cost overruns or schedule delays. The Portfolio Manager, with steering committee approval, may defer lower-priority projects to reallocate resources to the at-risk project, or may approve cost/scope tradeoffs. Rebalancing decisions should be made quickly, within a time limit the steering committee sets, to prevent project delays from cascading through the portfolio. The Steering Committee should have clear decision criteria for rebalancing, such as: projects can be deferred if they do not directly support revenue or critical risk mitigation. Document rebalancing decisions and the factors that drove them so that steering committee members can understand how portfolio decisions evolved over time and can assess the decisions’ outcomes in retrospect.

Portfolio Governance and Review Cadence

The Portfolio Manager leads monthly portfolio status reviews and quarterly steering committee meetings. Monthly reviews track project progress, identify emerging risks, and flag resource constraints. Track key portfolio metrics in monthly reviews: schedule variance (projects on time vs. delayed), budget variance (projects on budget vs. overrunning), and resource utilization (are constrained resources being used efficiently). Quarterly steering committee meetings review portfolio-level health, approve portfolio changes, and make prioritization adjustments if business conditions change. An annual portfolio planning cycle (typically August through October) solicits new project proposals, develops business cases, and presents a new prioritized portfolio to the steering committee for approval. The Steering Committee should formally approve the portfolio each fiscal year so that business unit leaders and project sponsors understand the company’s commitment to each initiative.

Turning the role chart into a list of decisions

A RACI chart answers the question of who does what. In portfolio work the more useful question is which decision each person can finish without waiting on someone else, and where the outcome of that decision is written. Start from the decisions the portfolio makes during a normal year rather than from the activities listed in a project template. Typical decisions include admitting a new request into intake, accepting or rejecting a business case, ranking a funded project against the rest of the portfolio, releasing people to a project, moving a start date, and stopping a project that no longer earns its place. Each decision needs one accountable owner and one record where the result is stored.

Charts drawn up as a list of activities tend to hide the gaps, and the governance model shows how to frame each decision. “Monitor portfolio health” sounds like one job, but it is really several decisions: whether to raise a risk, whether to ask for a re-plan, and whether to move money. Each of those has a different owner in many organizations, and only the decision-level view shows where two people think they hold the same call.

A sequence for building the chart from the platform outward

1. List every decision the portfolio committee and its managers take, written as a verb and an object, such as “defer a funded project” or “approve a change to budget”.
2. For each decision, name one accountable owner. If you can only write two names, the decision has not been designed yet, and the chart should say so rather than list both.
3. Identify the record where the decision is written, such as the demand, the project or the portfolio plan, and confirm which role is able to edit that record at the moment the decision is taken.
4. Mark who must be consulted before the decision and who only needs to be told afterwards. Keep the consulted group short, because a long consultation list is a common reason an approval sits unanswered.
5. Map each role in the chart to a platform role or group that exists in the instance. Record any role without a platform counterpart as a gap to close before go-live.
6. Walk one real request from intake to funding through the chart, and note every point where someone would have to ask who decides. Each question you write down is a row the chart is missing.

Where the chart fails once people use it

Many role charts look sound on paper and break in the first live cycle. The table below lists the failure patterns that appear most often and the change that often fixes each one. Adding a new role is seldom the answer. What usually helps is a clearer owner, a named delegate or a rule about which record carries the decision.

The dual-hatted sponsor is one of the most common of these, and it is seldom deliberate. A business leader with three initiatives in the portfolio knows those initiatives best, so the scores drift upward without anyone intending it. A declared conflict, shown next to the score, is often enough for the committee to discount the figure properly. The same pattern shows up among the common setup mistakes in portfolio builds, where it tends to surface only after the first ranking run.

Questions to settle before the first committee meeting

• Who can stop a project that is already funded, and what evidence must they attach to that decision?
• Who may change a project’s budget without returning to the committee, and up to what kind of change?
• Who owns the intake queue on the days the portfolio manager is unavailable?
• Which decisions can be taken by email and recorded afterwards, and which must be taken in a meeting with minutes?
• Which person has the authority to reopen a decision the committee has already closed?

Triage ownership deserves the same care. Groups that already route work well tend to do it through rules written in the platform, and for how routing rules are kept visible over time, see the notes on assignment group governance.

When the answers differ from the chart, update the chart first. The committee will act on what it says in the room, so the written version has to match that.

Keeping the chart current as people change roles

A role chart goes out of date faster than the platform configuration does. When a director moves to another business unit, the projects they sponsored keep their name until someone edits them, and the next steering pack quietly reports the wrong accountability. Link the review of the chart to job changes in your own organization rather than only to a calendar date. A simple test is to check that every active project still has a sponsor who works in the business unit that asked for it.

Teams that already run a wider review of how decisions are made on the platform often fold this check into that cycle. Pick the ten projects with the largest funding, confirm each one has a sponsor, a scorer and a funding approver who all still hold those roles, and fix any mismatch before the next ranking run.

Can the portfolio manager also approve funding?

In smaller portfolios this combination is common, and it can work when the amounts are modest and the committee reviews a summary afterwards. As the sums grow, separate the two. The person who orders the portfolio is otherwise judging their own recommendation, and an auditor will ask who checked it.

Should project managers sit on the steering committee?

Often not as voting members. A project manager brings delivery facts into the room, but a committee made up mainly of delivery leads tends to protect the work it already runs. Invite them for the items they own, and let them leave once those items are decided.

Who keeps the decision log?

The portfolio manager or the portfolio analyst is a usual owner. The important rule is that each entry is written when the decision is made, by the person who made it, and not rebuilt from memory for the next steering pack.

What happens when the committee cannot agree?

Record the question, the options on the table and the person who must settle it, and set a date for the matter to return. An unresolved item that stays on the agenda without an owner is often an accountability gap, not a hard discussion, and treating it as the second kind of problem keeps it open for months.

Next step

If your role chart has rows that no one can explain, it can be reviewed decision by decision, matching each one to a platform role, before anything is configured. For a wider view, the project portfolio governance guide covers this ground.