Your Transformation Dashboard Is Probably Lying to You

Most transformation programmes have no shortage of reporting. RAG statuses, milestone plans, financial forecasts, risk registers and benefit profiles all roll up into a dashboard.

Yet programmes still miss deadlines, costs still rise and initiatives still jump from Green to Red without warning.

The data usually isn't wrong. The problem is that most dashboards are built to describe activity, and leaders need them to show what's likely to happen next.

What we'll cover

• The difference between reporting and control

• Why Green is often a judgement call

• The warning signs most dashboards miss

• How averages hide the risks that matter

• What a useful executive dashboard should show

Reporting and control are different things

A tidy dashboard gives a sense of order. Every programme has a colour and every risk has an owner.

Control means something else: knowing what's likely to happen, noticing when things change and stepping in early enough to make a difference.

Most dashboards lean on lagging indicators like work done, money spent and milestones hit. By the time one of those turns Red, the cause may have been there for months.

Green is often a judgement call

RAG looks objective. In practice it depends on the programme manager's judgement, and that judgement is shaped by optimism, pressure from sponsors and a natural reluctance to escalate.

Nobody needs to be dishonest for this to happen. People want their programmes to succeed and believe they can recover. If Red brings criticism instead of help, teams learn to avoid it.

The portfolio slowly fills up with programmes that are Green but fragile. We cover this in more detail in The Most Dangerous Transformation Status Is Green.

Warning signs most dashboards miss

Sudden deterioration is rarely sudden. Look out for:

• decisions left open past the point where they affect delivery

• critical roles that are vacant, shared or overstretched

• milestones ticked off with poor-quality outputs

• dependencies that are logged but not managed

• risks open for months with no real mitigation

• forecast dates slipping a little each month

• recovery plans that nobody has tested

• stakeholder confidence falling while the status stays the same

One of these on its own may not justify Red. Several together are a clear signal.

Milestones can give false comfort

Milestones feel factual. Either it's done or it isn't. But they can hide a lot:

• ten admin tasks don't make up for missing the one decision that unlocks the next phase

• a design can be produced without being agreed

• a system can go live without anyone using it

• a process can be documented without becoming how people work

• a business case can be approved on assumptions that no longer hold

The better question is whether completing a milestone made the outcome more likely.

Averages hide the risks that matter

A portfolio might report 82% of milestones on track, 90% of risks with an owner and only 8% of initiatives at Red. That looks healthy.

But the delayed 18% could sit on your most important programme. Those few Red initiatives could carry a large share of the expected benefits.

A useful dashboard shows where value, dependency and exposure are concentrated. Counting every item equally hides exactly that.

Risks and financials need a direction of travel

A risk on a register isn't necessarily a risk under control. For each big risk, ask whether it's rising, stable or falling, and whether the response is working.

Financials can mislead too. An underspend can mean delayed hiring or work that hasn't started. Benefit forecasts often stay the same long after the assumptions behind them have weakened.

Leaders should be able to see how delivery confidence, forecast cost and expected benefits relate to each other. When one changes, the others should be looked at again.

What a useful executive dashboard shows

Keep the usual measures (status, milestones, cost, risks and benefits). Then add forward-looking indicators in seven areas:

• Outcome confidence: will the initiative still deliver what justified it?

• Critical path: are the activities that really matter on track?

• Decision speed: are big decisions being made in time?

• Dependencies: are cross-programme dependencies owned and moving?

• Resources: is the capacity there for the next phase?

• Risk direction: is exposure rising or falling?

• Adoption and value: are changes being used, and do the benefits still stack up?

It's also worth tracking your surprise rate: the share of significant status changes that had no earlier warning. If it's high, your reporting isn't doing its job.

The aim isn't to stop statuses changing. Transformation is uncertain and things will move. The aim is to stop avoidable surprises.

Independent challenge matters

Programme reporting comes from the people delivering the work. Their knowledge is essential, but they're close to it. A Transformation Management Office (TMO) should test the evidence behind each status. Good questions to ask about every status:

• What has to be true for this status to stay Green?

• Which assumptions have changed since the last report?

• What does the recovery plan depend on?

• Are the decisions it needs within the programme's control?

• Do the milestones show real progress towards the outcome?

• Is the benefit case still achievable?

The aim is to make sure leadership's confidence rests on evidence.

Where the stakes are high, independent assurance can show where reported progress and reality have started to drift apart.

Frequently asked questions

What should a transformation dashboard include?

The usual status, milestone, cost, risk and benefit measures, plus forward-looking indicators: outcome confidence, critical path, decision speed, dependencies, resources, risk direction and adoption.

What are leading and lagging indicators in transformation?

Lagging indicators show what has already happened, such as milestones hit and money spent. Leading indicators help predict what will happen next, such as open decisions, resource gaps and rising risks.

Why do RAG statuses fail?

RAG relies on judgement, and that judgement is shaped by optimism and pressure. Where Red brings criticism instead of support, problems get reported late.

How do you measure the quality of programme reporting?

Track how often significant status changes arrive without earlier warning. The lower that number, the better your reporting is at spotting problems in time.

How Condor helps

We help leadership teams set up TMOs, strengthen portfolio reporting and provide independent assurance, so problems surface early enough to fix. Past work includes £150m in cost savings for clients.

If your dashboard keeps surprising you, let's talk. Get in touch

When Execution Matters, We Deliver.