We have all been in that meeting. The CEO describes the organisation, explains the problems and sets out the priorities. And you, in operations, listen and think: ‘I have no idea which company this guy is talking about!’
The disconnect starts long before that meeting. Information passes through several layers of filters and biases. Problems are summarised several times and, in the end, what arrives is a very attractive, fairly orderly presentation of a false reality.
It is Instagram vs reality, but in senior management.
Nobody has to lie. All it takes is a detail lost at each step, a problem softened or something left out because it does not fit neatly into the presentation. And if the boss also struggles to accept being challenged, the team quickly learns what to tell them. And, above all, what to leave out.
More reports do not always mean better understanding
We can have more information than ever and understand less and less about how our own company works.
Dashboards show what is happening. To understand why and how, we often need to talk to the people getting the work done: where a process gets stuck, which decisions nobody is making and which problems they have spent months patching up with plasters and a couple of staples.
From the top, we see the result. We do not always see everything someone has had to do to achieve it.
That is where I find the ‘five whys’ useful for leadership, not just for analysing a technical problem. Continuing to ask questions helps us get to decisions, incentives and responsibilities that do not appear in the first explanation. It is not about forcing everything back to a single cause or turning the conversation into an interrogation.
A routine for reconnecting with operations
The proposal is simple: sit down regularly with operational teams and review a few things that are working and a few that are not.
We could do this every fifteen days or once a month, with two things going well and three going badly, or the other way round. What matters is that they are specific and that the conversation does not become another presentation for management.
Asking why helps us examine the logic behind things:
- Why did we make this decision?
- Why are we incentivising that behaviour?
- Why is this problem still unresolved?
Asking how helps us understand the reality of the operation:
- How exactly did it happen?
- How was the decision made about what to do first?
- How is the team managing to get the work done?
There is nothing magical about the number five. The aim is to look beyond the first answer and check our understanding, rather than work through a list of questions.
Listening without defending ourselves
The difficult part begins when the answer makes us uncomfortable.
Staying with the conversation without justifying ourselves. Without looking for someone to blame. Without offering a solution before we have understood the problem. Including when we discover that one of our own decisions is behind what is now not working.
This conversation can help us see broken processes, unclear responsibilities and efforts that remain invisible more clearly. But asking is not enough: if we identify a problem and nobody then decides what to do about it, the next conversation will also lose its value.
This is not about the CEO directing every task. It is about understanding the organisation they are making decisions about, and ensuring that the people responsible can resolve the issues within their remit.
Dashboards help. None can replace a conversation done well.
Because we can ask for honesty over and over again. But if people have to defend themselves every time they tell us something uncomfortable, the next meeting will be much calmer. And probably a lot less useful.
