In short
A review on exceptions starts from an agreed, current picture of every program and spends its time only on what moved and what needs a decision. It requires the status to be produced continuously from the tools, so that nobody assembles it by hand and nobody argues about it in the meeting.
Where does the time go in a normal review?
Into establishing facts. Program managers spend most of the week collecting updates and building slides; the meeting then walks through each one. By the time a problem is recognised there is little time left to decide what to do about it.
What does an exception review cover?
Three lists and nothing else:
- What moved this week, and what each change affects.
- Which programs are at risk against their date, and why.
- Which decisions are waiting, each with its options and reasoning.
What has to be true for this to work?
People have to trust the picture more than their own slides. That happens when the picture is read from the systems where the work is done — regression results, timing reports, tickets, supplier messages — and when every correction to it is recorded with who made it.
What changes for the program office?
The work shifts from collecting status to owning decisions. Program managers report that status assembly falls from most of the week to a short review, and steering meetings shorten because they no longer exist to pass information around.