It is 8:52 on a Thursday. Your quarterly portfolio review starts at nine.
The VP who called it has a hard stop at 9:15 because something got double-booked, which means the ninety-minute meeting you prepared for is now, in practice, a five-minute meeting with witnesses.
You have a forty-slide deck. Slide 12 has a chart nobody has ever understood, including the person who made it.
Somewhere in the back row, someone whispers:
"Can you just tell us if we're okay?"
That whisper is the whole job.
An executive rarely wants the portfolio. They want a verdict about the portfolio, plus the few things only they can fix.
If you can deliver that in five minutes, you become the person they trust when the timeline gets ugly.
So let us build that five minutes.
What five minutes actually buys you
First, define the goal, because "update" is a slippery word.
An update can mean status.
Or it can mean decisions.
Those are different meetings.
In this post, a five-minute portfolio read means one thing:
Giving an executive enough shared truth to make or confirm a decision, and nothing more.
That framing changes what belongs in the conversation.
Progress that requires no decision is context, not headline.
The migration that is quietly on track does not need airtime.
The migration that will slip unless someone reprioritizes a shared database team does, because only leadership can settle that fight.
Before you say a word, sort the portfolio into two buckets:
- No executive action: On track, or recoverable by the team without leadership intervention.
- Executive action needed: Blocked, resource-constrained, strategically misaligned, or otherwise unable to move without leadership.
Most of your portfolio will usually fall into the first bucket.
That is good news.
It is also why the whole thing fits in five minutes.
You are not narrating the healthy majority. You are pointing at the few places where leadership attention can change an outcome.
The five-minute structure
Here is a structure that tends to hold up under time pressure.
Roughly one minute each.
- The verdict. One sentence on portfolio health, backed by a number.
- Strategy fit. Are we spending time and capacity on what we said mattered?
- The decisions. The small set of issues only leadership can resolve.
- What changed. Movement since the last review, not a repeat of status.
- The ask. Restate what you want decided, confirmed, or unblocked today.
Notice what is missing.
There is no slide-by-slide tour.
There is no project you mention simply because its manager is in the room.
Fairness to your teams matters, but an executive review is not the place to distribute attention evenly.
It is the place to spend a scarce resource, leadership attention, where it can do the most good.
There is a tradeoff: you are going to leave things out.
Someone whose project gets zero seconds may feel unseen.
Handle that outside the room, in writing, so the five minutes stays focused on decisions.
A worked example
Say you run a PMO with fourteen active projects.
Here is what the five minutes might actually sound like.
Minute one: the verdict
"Eleven of fourteen projects are on track. Two are at risk and one is red. Forecast spend is about four percent over plan, driven almost entirely by the billing replacement."
That is the whole portfolio in three sentences.
When I say "at risk" here, I mean the delivery date or budget is likely to miss without intervention, not that outcomes are uncertain in some vague sense.
Define your terms once, out loud, and the room stops arguing about what the colors mean.
Minute two: strategy fit
"Sixty percent of our capacity is on the two objectives you set for the year, retention and cost to serve. The other forty percent is support, compliance, and one legacy commitment we cannot drop until Q3."
You are not apologizing for the forty percent.
Support, maintenance, and compliance work are real work.
You are showing leadership that you know where the money and capacity are going, and whether that still matches the strategy.
Minute three: the decisions
This is the heart of the review.
- "The billing replacement and the data platform both need the same two senior integration engineers in April. We can protect one date, not both. I recommend protecting billing because it directly supports the retention objective. That moves the data platform by three weeks."
- "The compliance project is red because we are waiting on a vendor contract that has been sitting in legal since March. That is not a delivery problem. It is a signature problem, and it needs your help."
- "We have a business case for a self-service portal that scores well against cost to serve, but there is no capacity to start it before June without dropping something else. I am not asking you to start it. I am asking you to confirm that it can wait."
See the pattern.
Each item identifies the real constraint, states a recommendation, and makes the tradeoff visible.
You are not handing the executive a problem.
You are handing them a decision with your homework attached.
Minute four: what changed
"Since last month, the mobile project moved from red to green after we borrowed a designer. The warehouse rollout slipped a week, but the schedule buffer absorbed it, so there is no date impact."
Movement only.
If nothing meaningful changed on a project, it does not need a sentence.
Minute five: the ask
"I need three things today: confirm billing over the data platform for April, help unstick the vendor contract this week, and confirm the portal can wait until June."
Then stop talking.
The point of minute five is not to introduce anything new.
It is to make the decisions unmistakably clear before the meeting ends.
The silence that follows is often the most useful part.
Where this approach can fail
Compression requires judgment.
When you reduce fourteen projects to a handful of sentences, you are deciding what deserves attention and what does not.
Get that filter wrong and you can steer leadership very efficiently toward the wrong problem.
One safeguard is simple: keep a written record of what you chose not to discuss so anyone can challenge the filter.
The approach also depends on trustworthy portfolio data.
A crisp executive verdict built on stale project status is worse than a messy but accurate one.
If you do not know the real state of a project, say so.
"I cannot vouch for the warehouse number this week" is a legitimate statement.
False precision is not.
This is where the underlying portfolio view matters.
Health, capacity, dependencies, strategy alignment, and recent changes need to stay current enough that the five-minute summary is a read of reality, not a monthly reconstruction exercise.
A well-maintained spreadsheet can support the same discipline.
A PPM platform should make it easier by keeping those pieces connected and reducing the amount of manual work required to understand what changed, what is competing for capacity, and where leadership attention is actually needed.
Perspective PPM can bring those signals together in an executive view with portfolio health, strategy alignment, capacity, and written summaries in one place.
The tool makes the preparation faster.
It does not make the judgment for you.
How to start this week
- Take your current portfolio list and tag every item no executive action or executive action needed. Be strict.
- For every item that needs executive action, write the constraint, your recommendation, and the tradeoff in three lines.
- Draft your one-sentence portfolio verdict with a real number in it. If you cannot, your data has a gap worth finding.
- Cut anything that requires no decision from the spoken version. Put it in a written appendix.
- Rehearse the review out loud once against a timer. Five minutes is shorter than you think.
Brief the decisions, not the deck. The rest is just paper.