Anyone who has sat through steering committees knows the moment. The slides go by, the progress percentages appear, the status lights are green or amber. Then, at the break, the project manager tells a different story, more nuanced, more worried. Nobody lied. Yet the committee has just spent an hour on figures that their own authors only half believe.
In our article on the main challenges in project management, we mentioned the lack of visibility and coordination. Steering committee indicators are often its most visible form, and its most costly.
Where the figures come from
Consider how a progress percentage is produced in most organisations. The day before the committee, the project manager is asked to update their table. They go through their work packages, form an opinion, and turn that opinion into a number. Sixty per cent, say. They do their best, but they do it from memory, quickly, with the background question of what that number is going to set off.
An amber light raises questions you do not yet have answers to. A figure that goes backwards from one week to the next looks suspicious. So the project manager rounds towards what can be defended. Management, for its part, prefers stable indicators. Everyone has good reasons, and together they produce smooth figures that slowly drift away from reality.
The price of the gap
The gap costs almost nothing at the time. It costs a lot later. A delay visible three weeks out can be handled with modest adjustments. The same delay discovered three months out forces painful trade-offs: pushing back a contractual milestone, taking resources from another project, dropping part of the scope.
It also costs trust. When everyone knows the figures are approximate, people stop looking at them, and the committee becomes a presentation ritual rather than a place where decisions are made.
Henry's perspective: observe rather than declare
The Henry team draws a very useful distinction in its article The steering committee where everyone knows the numbers are wrong: the difference between declared and observed progress. The first is an opinion turned into a percentage for the meeting. The second is derived from what the teams have actually done: actions completed, time spent, remaining work re-estimated as you go.
An observed figure is often less flattering. It is also far more useful, because it carries neither the caution nor the optimism of the person producing it. And it requires no extra work: it follows from work already recorded, provided the teams really track their tasks where the information is consolidated.
A second article on the same blog, The metrics you watch because they exist, takes the thought further: an indicator is only worth the decision it makes possible.
What you can do right now
- For each indicator presented, ask where it comes from: an observation, or an estimate made for the meeting.
- Replace the progress percentage with remaining work, re-estimated by the people doing it. It is harder to round off and more telling for decisions.
- Accept that an indicator moves. A light that turns amber early is good news: it leaves time to act.
- Spend committee time on decisions rather than on commenting the figures. Reliable figures do not need lengthy commentary.
A useful steering committee is not one where everything is green. It is one where problems are found early enough to be fixed.