Seeing the Business Before It Breaks.

A few weeks ago, my wife’s car got stuck in a gym carpark.

Not in a dramatic way. There was no smoke pouring out of the bonnet, no crash, no breakdown on the side of the highway. It was just stuck. A park brake actuator locked on, the car could not be moved, and something that should have been simple suddenly became a month-long problem.

By that point, the immediate safety question had almost passed. The car was not moving. No one was in danger in that moment. The more practical issue was that the car could no longer do what we needed it to do.

It had stopped being useful.

That is the part that stayed with me. The purpose of the car is not to sit safely in a carpark. The purpose of the car is to move people or things from A to B without unnecessary disruption. It needs to start, stop, steer, brake, carry what needs to be carried, use fuel or power efficiently, and get us where we need to go.

Of course it needs to be safe. Safe is not optional. Safe is foundational. Safe is permission for the car to be driven in the first place.

But safe is not the purpose of the car.

That is where my mind goes when I think about dashboards, data and leadership.

I have always thought about business dashboards in the same way I think about the dashboard in a car. There are things I want to know all the time. How fast am I going? How hard is the engine working? Is it getting hot? How much fuel do I have? These things help me make decisions while I am driving. If I am doing 70 in a 60 zone, I can ignore the speedo if I like, but I know what that means. The information is there. The consequence of ignoring it sits with me.

Then there are the warning lights. Oil. Seatbelt. Door open. Engine light. They are not there to explain the whole problem. They are there to get my attention and tell me something needs to be investigated before it becomes more serious.

Then there are the indicators that help shape how we drive. Reversing cameras, parking sensors, lane detection, school zone alerts, and that increasingly dramatic moment when the whole dash turns red because the car has decided you are about to run into something that definitely should not be run into. Some of these things are annoying. Some are brilliant. Some only matter in a specific moment. Used properly, they help you operate the car with more awareness than you could without them.

And then there is the deeper diagnostic layer. The things a mechanic can plug into when the car goes in for a service. I do not need to understand every code, reading or hidden system. I do need someone to find what needs attention, explain what matters and help me keep the car operating as intended.

That is the point. All of those indicators exist to help the car operate. They do not exist for their own sake. They exist because failure is disruptive, expensive, frustrating and, depending on the situation, potentially unsafe.

Business is not that different.

The purpose of a business is not to be safe. I say that carefully, because I believe deeply that everyone should go home from work in at least as good a condition as they arrived, and hopefully better. Safety is not secondary in importance, but it is foundational in role. It is permission to operate. It is part of the licence a business earns every day.

But the business exists to deliver an outcome, product or service to people willing to exchange money for it. It needs to produce, serve, maintain, move, supply, build, repair, respond or operate in a way that creates value.

So the better leadership question is not simply, “Are we safe?”

It is more complete than that.

Are we delivering what we exist to deliver, and are we doing it in a way that is controlled, reliable, sustainable and safe?

That is the operating question.

Back in 2010, I wrote and presented a piece of work called Leading with the Numbers. At the time, the core idea was simple: if you want to lead performance, including safety performance, you need to understand and use the numbers in the business. But the point was never the numbers themselves. The point was helping organisations deliver consistently, efficiently and without people getting hurt. It was helping leaders see where to look, what to question and where action may be needed.

I have spent much of the time since helping organisations wrestle with that same problem in different forms.

What should leaders see? What should the frontline see? Which indicators need constant attention? Which ones only matter when something is changing? Which ones tell us to stop, lift the bonnet and find out what is actually going on?

Those questions still matter because many organisations have become very good at producing information without always being as good at using it. They have reports, dashboards, monthly packs, scorecards, charts that go up and down, and tables full of numbers that can be filtered every possible way.

Some of that work is useful. Some of it helps leaders see what is happening and where they need to act. But some of it becomes reporting theatre: impressive-looking graphs, long packs of information, and a quiet assumption that because something has been counted, the business must somehow understand it.

That is not how it works.

A fuel light does not fill the tank. An oil warning does not change the oil. A dashboard does not drive the car. The value is not in the indicator itself. The value is whether the indicator helps someone understand what is happening early enough to do something useful about it.

That is the leadership test.

If a number helps a leader ask a better question, it has value. If a dashboard helps a team see where work is drifting, it has value. If a warning tells people to investigate before disruption becomes failure, it has value.

But if the information does not change the decision, the action or the conversation, then it is just more information.

And most organisations already have plenty of that.

The hard part is not collecting more. The hard part is knowing what matters, when it matters, who needs to know, and what should happen next.

That was true when I first started writing about leading with numbers.

It is still true now.

The dashboard does not drive the car. The report does not lead the business. The number does not make the decision. But the right signal, seen at the right time, can change what a leader does next.

Paul