The planning gap
The board meets on a cadence. Change arrives every week.
PMI’s Standard for Portfolio Management sets out portfolio governance: who decides what gets funded, what starts, what pauses and what stops. The structure is sound. The pressure comes from timing. A new mandate lands, a program slips a phase, a shared platform team is pulled into an incident, and by the time the board meets, the pack describes a portfolio that no longer exists. The first half hour goes on agreeing what is true.
Capacity and capability management asks a simple question: can the people we have deliver the work we have approved, in the order we approved it? In many organizations the answer still lives in a spreadsheet that one person understands, and it rarely counts the day job. Operations and service work take their share every period, so a plan that ignores them is overloaded before it starts.
The hardest moments come at phase gates and in programs. A gate can judge the project in front of it, but the real question is about everything else: who builds the next phase, what has to wait, whether the budget still holds. In a program, one slipped project can delay a dependent platform, a process change and the first benefits, and leave a shared team double-booked across programs.