The case for conversations
A podcast interviewer asked me recently: "What makes conversations so special? Why aren't existing tools enough?"
It's a fair challenge. Organisations already invest heavily in listening to themselves. Think audits, reporting systems, metrics, dashboards. That infrastructure exists. So what is it that conversations can do that the rest of that apparatus can't?
My answer starts with a line from my book: organisations that can't hear themselves, can't improve themselves. The tools above are all attempts to hear. But they were built to capture what is already known, already named, already legible to the system. A form field can only receive what fits inside it. A dashboard can only display what someone decided to measure.
Conversation reaches somewhere else entirely. Conversations can:
Catch the unnamed, the unease, the hunch, the "that's weird." Formal systems can only capture what already has a category. But a lot of what matters in organisations doesn't have a category yet. It's the feeling a technician has that something is off, the leading hand that’s running past a contractor because time isn’t quite enough, the quiet worry that never becomes a report because nobody is quite sure how to name it. Conversation is the only mechanism that can reach something before it's been labelled.
Carry context: the meaning that travels with the message. A conversation preserves what a form field destroys: tone, hesitation, the detail someone adds almost as an afterthought, the thing said with eyes down rather than straight ahead. When you strip experience down to a data point, you get the what without the richness of where it’s coming from. Without that, data is difficult to understand.
Work in real time. Conversations are always on, not episodic. Audits happen quarterly. Surveys go out annually. Slow-moving risk doesn't wait for the review cycle. A conversation can happen the moment someone notices something worth noticing, which means it can catch what every scheduled mechanism is structurally too late to see.
Cross boundaries. As a genuine exchange between frontline and leadership, they have the potential to translate worlds, not just information. Most organisations have channels for information to travel upward. Few have conditions for it to arrive intact. A conversation between someone doing the work and someone making decisions about it doesn't just transfer facts, but transfers the weight of the experience. That's different in kind, not just degree.
Surface what's unspeakable. Some things don't travel through official channels because people have learned, accurately, that it isn't safe to send them. A genuine conversation, one where curiosity is real and the response to honesty is not punishment, can reach what the reporting system never will. Not because the system is broken, but because no system creates the conditions that trust creates. People do that.
Challenge identity. A person saying an uncomfortable truth is harder to dismiss than a data point. Organisations develop stories about themselves: we have a strong safety culture, our people speak up, we learn from incidents. Data can be reinterpreted to protect those stories. A person sitting across from you, telling you what it's actually like, is harder to explain away. Conversations can shift the story an organisation tells about itself in ways that a report rarely does.
Close the loop. Conversation is inherently two-way. Reporting is not. When someone files a report, the exchange often ends there, unfortunately. When someone speaks honestly and is genuinely heard, an implicit commitment is made: this will be responded to. That accountability, the expectation that hearing leads to something, is part of what makes people willing to speak in the first place. Remove it, and the channel goes quiet.
Build the muscle. Organisations that talk honestly get better at it. Conversation is a practice, not a system. It develops through use, atrophies through neglect, and compounds over time. An organisation that invests in genuine dialogue doesn't just get better information, but builds the capacity to keep getting it. That's a different kind of organisational asset than any tool on a dashboard.
The list above is an argument for taking seriously what organisations are losing when the conversations they have are scripted, performative, or never happen at all.
Every audit, dashboard, and reporting system was built to solve a real problem. But they were built to capture what is already known, already named, already legible to the system. Conversations have the potential to reach and capture what the system hasn't learned to see yet.
And in most organisations, that’s where risk lives.
Daniel