Insight

When a green status report needs a second look

Milestones can be on schedule while the assumptions underneath a programme quietly move.

Insight

When a green status report needs a second look

Milestones can be on schedule while the assumptions underneath a programme quietly move.

Insight

When a green status report needs a second look

Milestones can be on schedule while the assumptions underneath a programme quietly move.

Advisers discussing technology and business decisions
Advisers discussing technology and business decisions

Published

Published

A programme report is a view of delivery, not delivery itself. Its colour depends on the measures, thresholds and assumptions behind it. When those assumptions change without a corresponding change in the report, a sponsor can receive reassurance at the very moment a closer look would be useful.


Separate activity from progress

Workshops completed, people assigned and tasks closed are useful operational measures. They do not necessarily show how much usable capability has been delivered. A more informative discussion connects activity to accepted scope, quality and the effort still needed to complete the job.


Test the original baseline

An independent review can start with three straightforward questions: was the original estimate reasonable, what has actually been delivered, and what does the remaining scope imply for time and cost? The purpose is not to replace the delivery team’s judgement. It is to give the sponsor another basis for deciding where support, challenge or a change of direction is needed.

The most useful warning is one that arrives while there are still options. Ask what evidence would cause the team to change its forecast, then make sure that evidence appears in the next report.