How to run a status review that ends in decisions
Many steering committees spend an hour hearing each program say Green, then leave without deciding anything. This guide sets out a 45-minute agenda that spends the time where it matters and ends every discussion with a decision that someone owns.
By the Tarivra team · · 6 min read
Why status reviews drift
- Every program gets the same airtime, so the troubled ones get too little.
- Updates are read aloud from slides everyone could have read beforehand.
- Discussion ends with 'let's keep an eye on it' instead of a decision.
- Nobody checks at the next review whether last time's decisions were carried out.
Before the meeting
- Send a one-page view a day ahead: each program's reported status beside the status the work supports.
- Mark the programs where the two disagree, or where a target date has moved since the last review. Those are the agenda.
- Ask each of those program owners for one line: what they need from the committee.
- Include last review's decisions, with owner, due date and whether each is done.
A 45-minute agenda
- 5 minutes: last review's decisions. Done, late or not started, and what happens to the late ones.
- 25 minutes: the flagged programs only, about 8 minutes each. The owner states the ask; the committee decides.
- 10 minutes: dates. Which programs moved a target date, and whether downstream programs are affected.
- 5 minutes: read back every decision with its owner and due date.
Programs that are Green and supported by the evidence are not discussed. That is the reward for honest status.
What counts as a decision
A decision changes something: scope, people, money, a date or a dependency. Each one needs four things:
- What was decided, in one sentence.
- One owner, a person rather than a team.
- A due date.
- Where it will be tracked: ideally as an item in the team's own tool, so follow-through is visible where the work happens.
'Monitor closely' and 'take offline' are not decisions. If the committee cannot decide yet, decide what information is needed, from whom and by when.
After the meeting
- Record the decisions the same day and send them to the owners.
- Create each as a work item in the team's tool, linked to the program.
- Review them at the start of the next meeting, before any new discussion.
- Track how many decisions close on time. Over a quarter, that number says more about governance than any status report.
Where Tarivra fits
Tarivra prepares the pre-read automatically, ranking the programs where reported status and evidence disagree, and records each decision with an owner and due date, writing it back to Jira, Azure DevOps, ServiceNow, GitHub or GitLab and closing it when the work is done.
Questions
How long should a status review be?
For a portfolio of 10 to 30 programs, 45 minutes is usually enough when only the flagged programs are discussed and the rest is read beforehand.
Which programs should be discussed?
Those whose reported status disagrees with the evidence, those whose target date moved, and those whose owner needs a decision. Programs that are Green and supported by the evidence can be skipped.
How do we make sure decisions are carried out?
Give each an owner, a due date and a work item in the team's tool, and review them first at the next meeting.