3.3 KiB
Portfolio Management
Duration: 30--40 minutes
Definition
Portfolio management manages multiple projects as a collection competing for the same organizational resources.
Project management asks:
How do we deliver this project?
Portfolio management asks:
Which projects should we be doing, in what order, and with what capacity?
Simple Mental Model
Projects compete with each other. The portfolio makes the trade-offs visible.
How It Works
A portfolio should answer:
- What is active?
- What is queued?
- What is on hold?
- What is the priority?
- Who owns it?
- What is the health?
- What is the next milestone?
- Where is capacity constrained?
Useful portfolio states:
- Proposed
- Approved / queued
- Active
- On hold
- Closing
- Closed
Approved does not need to mean active.
A portfolio review asks:
- Which projects changed health?
- Which milestones slipped?
- Which need intervention?
- What new work is proposed?
- Do we have capacity?
- What should pause or remain queued?
- Are priorities still aligned?
The portfolio is not a giant task board.
Example
Your board has 16 projects and 12 appear active. Capacity review shows the team can reliably support six major initiatives while handling operations.
The portfolio decision is not "work faster." It is to choose the active six, queue the others, and make the trade-off explicit.
How It Fits Into the Bigger Picture
Prioritization decides relative importance. [[Capacity and WIP]] determines how much can be active. Project Health identifies where intervention is needed. Portfolio management combines them.
My Company / Real-World Context
Your Monday board is already attempting to be a portfolio. It has projects, priority, owner, status, and timelines.
The eventual goal is for it to answer:
What needs my attention?
rather than merely:
What projects exist?
CTO Perspective
Portfolio management is a major shift from execution to organizational leadership. Every project approval consumes people, money, and attention that cannot simultaneously be used elsewhere.
Every project approval is a resource-allocation decision.
Questions to Ask
- Why are we doing this?
- What is its priority relative to others?
- Do we have capacity to start?
- What will it displace?
- How many projects are active?
- Which are Yellow/Red?
- Where are bottlenecks?
- Which projects should pause or stop?
- What should start next?
Meeting Scenario
Situation: Leadership approves another initiative and asks when your team can begin.
Possible response:
I'll add it to the portfolio and assess it against current priorities and capacity. If it must start immediately, I'll show which existing commitment would need to move so we can make that trade-off explicitly.
Key Takeaways
- Portfolio management manages projects as a competing collection.
- Approved does not mean active.
- Queued and on-hold states are healthy.
- Portfolio views focus on management information, not task detail.
- Priority, capacity, WIP, and health come together here.
- Starting new work should expose what it displaces.
Related Concepts
- Prioritization
- Capacity and WIP
- Project Health
- Status Reporting
- Ownership and Delegation