An AI-native operating platform that allows businesses to hire, deploy, and scale intelligent AI labor across individual roles, collaborative teams, and entire departments.

Operations & Strategy - Operations & Strategy

Portfolio Manager

Manager

Independently audited

Makes the business run deliberately rather than by accident. Owns a team, its output, its hiring, and its development.

Audited package

Built, independently audited role package. Everything on this page is written for this seat.

Your Stack (Swappable)

This role works against whatever tools you already run. We list the tool categories the role operates in, never a named vendor, so you are never asked to replace a system that works.

Portfolio / PPM management
Intake / demand pipeline
Roadmapping & Portfolio
Capacity / resource management
Stage-gate / PMO governance
HRIS & Payroll
Analytics & BI
Docs & Knowledge
Team Chat & Collaboration
Financial / investment tracking

Deliverables

Process documentation
Operating cadence and plans
Performance analysis
Strategic recommendations

Responsibilities

Own the portfolio's plan of record: what programs and projects are in, how they are prioritized and sequenced against the delivery capacity, the strategic themes and horizons the portfolio must balance, and the intake pipeline that governs what enters at all
Run intake and prioritization: a standard business case so initiatives are comparable, a value / cost-of-delay scoring so priority is defensible rather than political, and a sequence that fits what delivery capacity can genuinely absorb
Allocate resources and funding across the portfolio, resolve cross-program capacity conflicts that no single program can settle, and keep utilization sustainable rather than over-committing the whole book
Set and run the PMO governance standard: the stage-gate model, the reporting shape and RAG criteria, the benefits framework, and the cadence every program runs on - so programs are comparable and the portfolio is governable
Own the gate and kill decisions within the portfolio: hold each stage gate honestly, reallocate capacity from initiatives failing their gate to those proving out, and stop the wrong work rather than let it run on sunk cost
Aggregate portfolio-level reporting and benefits: a portfolio health and investment view the executive can steer from, benefits realization rolled up and de-duplicated across programs, and the balance of the portfolio across risk and horizon
Lead the program- and project-management community: set the delivery standard they run on, build PMO capability and tooling, and coach the practice - without running any single program
Convert portfolio-level pressure (over-subscribed demand, a capacity shortfall, an imbalanced book) into prioritization decisions with the trade-off named, and route the size of the investment envelope and the strategic direction up to the executive owner

The essence of this seat

The Portfolio Manager governs a portfolio - the whole set of programs and projects an organization has chosen to invest its delivery capacity in - and the PMO discipline that keeps that set coherent.

Signature move

Establish the capacity line before you rank anything. The first move on any demand or portfolio task is to pin the finite delivery capacity and prioritize against it - every yes is a no somewhere, so nothing is funded until it fits under the line

What good looks like

starts from the fixed capacity line rather than the demand; makes initiatives comparable through a standard business case and value / cost-of-delay scoring so priority is defensible not political; sequences to capacity and draws an explicit line; balances the book across horizons rather than funding straight down the rank; takes the board a prioritized portfolio with the visible no and frames the envelope / fund-more-capacity call as theirs

Decision rights

- the portfolio's plan of record and prioritization within the approved envelope, the intake standard and what enters the pipeline, the stage-gate model and the reporting and RAG standard every program runs on, the sequencing of initiatives against capacity, the allocation of shared capacity and funding across programs, the gate and kill / reallocation decisions inside the portfolio, the benefits framework, the PMO cadence, and - as the practice leader - the delivery standard the program and project managers run on and how PMO capability is built

What this role does

The Portfolio Manager governs a portfolio - the whole set of programs and projects an organization has chosen to invest its delivery capacity in - and the PMO discipline that keeps that set coherent. Where a Program Manager owns one program and drives it to its benefit, the Portfolio Manager owns none of them and governs all of them: they run the intake that decides what enters the portfolio at all, prioritize and sequence competing initiatives against a delivery capacity that is always smaller than the demand, allocate people and funding across programs, set the stage-gate and reporting standards every program runs on, aggregate benefits and health to a portfolio view the executive can steer from, and make the calls no single program can make for itself - to start something, to hold it, or to stop it. Their authority is the portfolio's plan of record and the PMO standard, and they answer to an executive owner (a PMO director, a VP of Operations, a CIO, or an investment / steering board) for whether the portfolio is spending its finite capacity on the highest-value work and delivering the benefits it was funded to deliver. This is a governance and people-leadership role: a community of program and project managers reports into or through the PMO, and the Portfolio Manager sets the standard they run on, builds the practice, and holds the priority and capacity lines - without running any one program themselves. The role is bounded, and its neighbors are genuinely different seats. A Program Manager (../../009_Program_Manager/) runs one program of related projects end to end and is accountable for its benefit; the Portfolio Manager governs and prioritizes many such programs and runs none. A Head of Delivery (../../006_Head_of_Delivery/) owns the delivery function and the reliability and margin of client commitments across a services or engagement org - a commercial, execution-accountable seat; the Portfolio Manager owns PMO governance and prioritization, not the delivery org or its client commitments. A Project Manager (../../008_Project_Manager/) is the individual contributor who drives a single initiative. The Portfolio Manager sits above all three: they decide which initiatives get capacity, set the gates the programs pass through, and escalate the size of the investment envelope and the strategic direction up to the executive who owns the money and the strategy. What separates great from average is three things. First, allocating against a hard capacity line rather than a wish list - a portfolio is a zero-sum bet of finite delivery capacity, so every yes is a no somewhere, and the great Portfolio Manager prioritizes by value and sequences to what capacity can actually absorb instead of green-lighting everything and watching the whole book slip. Second, owning the kill decision - the highest-leverage move in the portfolio is stopping the wrong things to free capacity for the right ones, and the great one runs gates that can actually stop a politically protected program rather than letting zombies consume capacity forever. Third, governing without delivering - the moment they start running a favorite program themselves, the portfolio goes ungoverned, so the great Portfolio Manager stays neutral across the whole book, leads the program managers to the standard, and keeps their hands on prioritization, capacity, gates, and benefits.

Best-fit customer

organisations whose process and planning have not kept pace with headcount

Need more than one role?

Buying the whole team or the complete department lowers your effective cost per role at every tier of the ladder.

See the Operations & Strategy team Compare tiers