Your transformation doesn’t need another status report.
When a transformation starts to drift, the instinct is almost always to add more reporting. New dashboards appear. Governance meetings multiply. Everything becomes green, amber or red. And somehow the work still does not move.
01
Seeing the problem is not the same as fixing it.
Leaders obviously need an honest view of delivery, risk and dependencies. The problem starts when describing an issue becomes a substitute for resolving it. I have seen beautifully produced packs carry the same blocker for months without ever naming who can remove it.
It creates a strange kind of comfort. Everybody can see the problem, so it feels managed. It is not managed. It is just being reported very consistently.
02
A useful meeting should change something.
My test for governance is simple: did it help the organisation make the next important decision? If the meeting only collected updates, it took time away from delivery without changing the outcome.
Useful governance makes the trade-off explicit, names the person who owns the decision and records what happens next. Everything else is supporting detail.
- What decision is required?
- Who is accountable for making it?
- What evidence is genuinely missing?
- What happens if the organisation waits another month?
03
Make the operating rhythm simpler.
The best transformation environments I have worked in were still complex. They were simply easier to act inside. Teams knew the priorities, leaders understood the cost of waiting and issues reached the people who could resolve them quickly.
A dashboard can support that rhythm. It cannot create it. If the transformation is stuck, start with the decisions and the accountabilities. The reporting can catch up afterwards.