ServiceNow Project Portfolio Management: Roles, Responsibilities and RACI

Portfolio roles split into governance, execution and resourcing. The Portfolio Director sets strategy and governance rules, the Portfolio Manager runs intake, priorities and resources, and each Project Manager delivers one project. A RACI table then shows who is responsible, accountable, consulted and informed for each portfolio decision.

Portfolio Director: Setting Direction and Governance

The Portfolio Director (or Chief Portfolio Officer) sets portfolio strategy and governance. Responsibilities: define portfolio goals aligned to business strategy, establish portfolio evaluation criteria, charter the portfolio review board, ensure portfolio discipline (decisions stick, resource allocations hold), report portfolio status to executives. The Portfolio Director owns portfolio governance: they decide how portfolio decisions are made, who participates, what escalation process applies. They are ultimately accountable for portfolio health and value delivery. They are Responsible and Accountable for portfolio strategy, Responsible for defining governance, and Consulted on major portfolio decisions.

Portfolio Manager: Orchestrating Portfolio Delivery

The Portfolio Manager (or Chief Portfolio Manager) executes the portfolio strategy. Responsibilities: maintain the project portfolio (intake, prioritization, tracking), manage portfolio resources (allocate people across projects, resolve resource conflicts), manage portfolio budget and financial reporting, manage portfolio risks at the aggregate level, report portfolio progress to leadership. The Portfolio Manager is accountable for portfolio execution and timeliness. They are Responsible for most portfolio activities, Accountable for portfolio delivery, Informed of project status, and Consulted on resource conflicts and priority changes.

Project Manager: Delivering Individual Projects

Project Managers execute individual projects within the portfolio. Responsibilities: plan and deliver their assigned project on time and on budget, report project status to portfolio management, escalate project risks and dependencies to portfolio management, manage project scope and change control, deliver project benefits as promised. Project Managers are accountable for their project’s success. They are Responsible for project execution, Accountable for project delivery, Consulted on resource availability and dependencies with other projects, and Informed of portfolio-level changes that affect their project.

Resource Manager: Allocating and Tracking People

Resource Managers (or Resource Planners) allocate people to projects. Responsibilities: forecast resource availability for the planning period, participate in portfolio resource planning to ensure feasibility, allocate specific people to projects, track resource utilization (are people actually available as planned?), escalate resource conflicts to portfolio management, manage resource training and development so skills match project needs. Resource Managers are accountable for realistic resource plans and for resolving resource conflicts. They are Responsible for resource allocation and tracking, Accountable for resource plan feasibility, Consulted on project resource needs, and Informed of resource changes.

Business Sponsor: Funding and Benefiting from Projects

Business Sponsors (one or more per project) fund projects and benefit from their delivery. Responsibilities: approve business case and funding for their projects, define intended benefits and success criteria, participate in project governance (steering committee, reviews), assess benefits realization after project completion, escalate business risks or blockers. Sponsors are accountable for the investment decision and for benefits realization. They are Responsible for benefit definition and assessment, Accountable for ensuring value is delivered, Consulted on project priorities and trade-offs, and Informed of project progress and risks.

Portfolio Review Board: Making Prioritization Decisions

The Portfolio Review Board (or Steering Committee) meets regularly (monthly or quarterly) to make portfolio decisions. Membership typically includes: Portfolio Director or Chief Portfolio Officer, senior business leaders, IT leadership, Finance leadership. Responsibilities: evaluate new projects for portfolio inclusion, prioritize accepted projects based on criteria, resolve resource conflicts, assess portfolio health, escalate blockers to executive leadership. Board members are collectively accountable for portfolio decisions. They are Responsible for evaluation and prioritization, Accountable for decisions, Consulted on project impacts, and Informed of portfolio trends.

Portfolio Office: Supporting Portfolio Operations

The Portfolio Office (Program Management Office or PMO) provides operational support to portfolio management. Responsibilities: maintain portfolio data and reporting systems, collect and consolidate project status, prepare materials for portfolio review board meetings, escalate risks and blockers, track benefits realization, provide portfolio analysis and recommendations. The Portfolio Office is Responsible for portfolio operations, Accountable to the Portfolio Manager for accuracy and timeliness, Consulted on portfolio trends and risks, and Informed of all project changes.

Example RACI Table for PPM Decisions

Portfolio Intake (add new project to portfolio): Portfolio Director Accountable, Portfolio Manager Responsible, Portfolio Office Responsible (data entry), Business Sponsors Consulted. Portfolio Prioritization: Portfolio Review Board Accountable, Portfolio Manager Responsible (recommendation), Resource Manager Consulted. Resource Allocation: Resource Manager Responsible and Accountable, Project Manager Consulted, Portfolio Manager Informed. Project Escalation: Project Manager Responsible for escalating, Portfolio Manager Accountable for resolution, Business Sponsor Consulted.

Start From Decisions, Not From Job Titles

A RACI built from a list of job titles tends to look tidy and then fail in the first real dispute. Someone holds a title that sounds accountable, yet the decision in question is taken in a different forum. The more reliable method runs the other way. List the decisions the portfolio actually makes in a typical quarter, then assign people to each one. Titles come last, because the same title can hold very different authority in two business units.

Write the decision list as verbs with an object: approve a new initiative, move a shared engineer between two projects, stop funding for a project that has missed its gate, change the priority order inside a funded program. A decision phrased this way can be tested. Either the person named can make it, or they cannot.

Rules That Keep the Matrix Honest

• Each decision has exactly one party marked accountable. Two accountable parties means no one is.
• The accountable party is never the only person doing the work. If the project manager prepares the proposal, someone else should review it.
• Every decision names at least one party who must be consulted before it is taken, and that list is short enough that people actually answer.
• Anyone who needs to act on the outcome is informed, but being informed does not give a vote.
• A role that appears in no row of the matrix is removed from the governance model until a real decision needs it.

Building the Matrix in Four Passes

1. Collect the decisions from the last two review cycles, taken from minutes, email threads and escalations. Decisions that were made informally still need an owner.
2. Group the decisions by stage: entering the portfolio, running inside it, and leaving it. Most disputes cluster at the boundaries between stages.
3. For each decision, fill the accountable, responsible, consulted and informed columns in one sitting with the people involved, so the matrix reflects how work actually moves.
4. Test three real cases against the matrix. Pick one routine decision, one contested decision and one decision that crossed a budget boundary. If the matrix cannot settle all three without a conversation, revise it before publishing.

Where Matrices Break Down

The first breakdown happens at the seam between portfolio and resource decisions. A resource manager may hold the accountable line for allocating a specialist, while the portfolio manager is accountable for the project that needs that specialist. Name the rule for a tie: usually the portfolio decision wins, with a documented escalation when the resource manager cannot meet the commitment. Without that rule, each side will assume the other has decided. Keep the resource-side rows in a separate matrix so the two can be compared line by line.

The second breakdown is the delegated decision. A review board delegates small funding changes to the portfolio manager, then forgets to record the threshold. Put the threshold in the matrix as a condition on the row, and review it whenever the board changes its terms of reference.

The third breakdown comes with turnover. When the person named as accountable changes role, the matrix still points at the old name and the new holder inherits authority they never agreed to. Assign roles to positions with a named deputy, and check the matrix at each change of personnel. Access rights tied to those roles need the same check.

Indicators That the Matrix Is Working

• Decisions reach the agreed forum without a second round of informal lobbying.
• Escalations are about trade-offs between valid options, not about who was supposed to decide.
• New starters can find the owner of a decision by reading one row.
• Minutes of each review board can be checked against the matrix without anyone needing to explain the gap.

When a Full RACI Is Too Much

A small portfolio with one sponsor and a handful of projects does not need a detailed matrix. A short decision-rights note, covering funding, prioritization and cancellation, is enough and will be read. The full version becomes worth its effort when several business units share funding, when external partners sign off on work, or when audit asks who approved a change. Build the detail at the point it is needed rather than in advance. The questions in the requirements workshop list are a good way to find out which decisions are really in play.

Questions Teams Raise When Drafting the Matrix

Can the sponsor also be the accountable party for benefits?

Often yes, and that is a sensible arrangement when the sponsor controls the budget that the benefits depend on. Split the rows anyway. Funding approval, benefits tracking and benefits sign-off are three decisions, and the sponsor may be accountable for one and only consulted on the others.

Where does the portfolio office sit in the matrix?

Usually as responsible for recording and reporting decisions, not for making them. An office that starts deciding priorities has quietly become a governance body, and that change should be made visibly, with a board decision, rather than by drift.

What should happen when a decision needs an expert nobody listed?

Add the expert as consulted for that decision only, and record the reason. If the same expert appears in several rows, that is a signal the matrix should show them as a standing member of a forum rather than a one-off.

What triggers a review of the matrix?

Review it when the governance forum changes its terms, when a major program joins or leaves the portfolio, and when a decision is contested twice. A calendar review is less useful than those triggers because it runs whether or not anything has changed.

Next Step

A live governance forum can test a draft matrix in one sitting: bring the decisions that were contested last cycle and ask whether each row settles them.

Related guides: Project Management & Business Analysis.