A PMO meeting covers many programs in little time. This agenda opens on portfolio risk and change, and Husn fills each program's status so the meeting reads, not recites.
Two programs depend on the same platform team, which is now overcommitted and slipping both.
Risk
A program moved from amber to red this week after a key milestone missed, with no escalation raised.
Changed
A decision needed from this PMO meeting has been pending across two prior sessions.
Watch
Across 8 programs - 2 cross program risks - 1 needs escalation
The problem
PMO meeting agenda
A PMO meeting has to cover a whole portfolio in an hour, so each program gets a few minutes of verbal status from whoever owns it. Without a written read ahead of time, the meeting becomes a round robin of updates, and the cross program risks that the PMO exists to catch get lost between programs.
Covering every program in one meeting means each manager recites status, and the hour vanishes into updates.
Risk that spans two programs is invisible in a per program round robin, because no single owner sees both sides.
Pulling status from every program by hand before the PMO meets is a job nobody has time to finish.
Why this gets hard at scale
Why PMO meetings struggle to scale
01
The more programs in the portfolio, the less time each gets, so the meeting skims and the real issues stay buried.
02
Cross program dependencies and drift only show up when you read across programs, which a sequence of solo updates never does.
03
Gathering a current read on every program each week is a coordination cost that grows with the portfolio.
How Husn helps
Step 01Husn reads Jira, Slack, and docs across programs and fills each line of the agenda, so the PMO knows what changed before the meeting starts.
Step 02It surfaces risk and drift that cross program lines, the kind no single program owner would raise alone.
Step 03The whole agenda arrives filled and current, so the meeting opens on what needs attention instead of touring status.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01Portfolio change and risk, the cross program view at the top.
02Program status, a current read on each program in the portfolio.
03Cross program dependencies, the shared teams and handoffs at risk.
04Escalations, which programs need a decision raised this cycle.
05Decisions for the PMO, the calls this meeting exists to make.
06Actions and owners, what was committed and whether it moved.
Connect your stack and Husn will fill your PMO agenda across every program in about fifteen minutes, so the room knows what changed before the meeting starts.