Portfolio and program are not interchangeable. Mixing them wastes time and confuses decision rights. Here’s how I separate them in practice.
Portfolio governance
- Purpose: pick the right work. Align investments to strategy and capacity.
- Cadence: quarterly prioritization, monthly health checks.
- Artifacts: business cases, prioritization model, funding tranches, benefits map.
- Decisions: start/stop/defer, funding shifts, sequencing.
Program control
- Purpose: deliver the chosen work. Coordinate scope, schedule, risk across projects.
- Cadence: weekly cross-workstream syncs, biweekly steering.
- Artifacts: integrated plan, RAID, decision/change logs, readiness gates.
- Decisions: trade-offs inside the program; scope/schedule adjustments within portfolio guardrails.
Avoid overlap
- Keep portfolio forums out of delivery detail; keep program forums out of strategic reprioritization.
- Use a shared risk/issue register only for items that cross the boundary (funding, policy, major dependencies).
- One escalation path: program -> sponsor -> portfolio board.
Clean lines speed decisions. Know which hat you’re wearing—and make it clear to everyone else.