You are accountable for an outcome you cannot see.

The project is someone else's to run. The PM sends updates. The steering committee meets. But the information reaching you has been filtered, summarised and smoothed before it arrives. By the time something is visibly wrong, it has usually been quietly wrong for a while.

This is not a failure of the project team. It is a structural problem. The people closest to the work are not always incentivised to surface bad news early. The reporting designed to keep you informed was designed by people whose primary audience is the steering committee, not the business.

The result is a particular kind of exposure. You find out late. You react rather than act. And when the outcome doesn't land, the accountability still sits with you.

How the picture gets smoothed

In any large program there are many layers between the work and the boardroom. Each layer, almost inevitably, applies some degree of interpretation to the information passing through it. The instinct to resolve ambiguity before escalating. The instinct to present problems alongside solutions. Those instincts are entirely human. Multiply them across five layers and a dozen workstreams and the picture that arrives at the top can look quite different from the reality underneath.

That is why the discomfort is so familiar: status reports say green, but something feels off. The questions you ask get confident answers that somehow don't quite add up. And you find out something has been developing for months at the point where the options to fix it have already narrowed.

Four questions that get past the summary

We do a lot of work in this space. In our experience, four questions consistently get past the smoothed summary and into what is actually happening.

Ask for a benefits tracking view. Not just schedule and cost, but whether the project is still set up to deliver what the business case promised.

Ask what the current risks look like in plain language, not a risk register. Ask which ones the team is most worried about.

Ask when the last independent review was done, and what it found.

Ask what decisions are coming up in the next 30 days that you should know about.

Well run project teams welcome these questions. Projects in trouble can err to answering them vaguely.

Four tests of your reporting

The same logic applies to the reporting system itself.

Ask when the last three escalated issues were first identified at project level. The gap tells you a lot.

Ask what would have to be true for a green project to be rated amber. If nobody answers quickly, your criteria are not clear enough.

Look at reports side by side. Consistent structure matters. But if a central function is rewriting every report into a uniform voice, you may be losing the specificity that tells you what is really going on.

Check the length. A report that takes twenty minutes to read is not a status report. If you cannot get a clear picture in two minutes, the format is working against you.

Visibility, not control

You do not need to run the project. You do need enough visibility to protect your business.

When reporting works well, the right conversations happen earlier. Problems surface while they are still manageable. And the discomfort of not quite knowing what is really going on quietly disappears.