Someone mentioned a new job title to me recently that they predict will come to fruition over the next few years – a Chief Conversation Officer. My first thought (after the initial giggle) was that I’d quite happily put my hand up for that one.
I honestly don’t think every organization needs another person in the C-suite, but I do think we’re massively underestimating how much conversation matters, especially with everything changing as fast as it is right now.
Think about what’s going on in most companies at the moment. There’s huge investment in AI, teams are being restructured, and the way work gets done is shifting under people’s feet. Employees are getting emails about transformation strategies, sitting through town halls, finishing their training modules and being told what the future’s going to look like. There’s no shortage of communication, but I keep wondering how much actual conversation is happening alongside it. How often do people get the chance to ask what all of this means for their job, push back on a decision they don’t understand, or explain why something that looks brilliant on a strategy slide falls apart on a Thursday afternoon? Communicating with people and having a conversation with them are two very different things.
Telling people isn’t the same as them understanding
I spent 11 years building and leading teams in Data and AI, and one of the first things I learned (usually the hard way) was that saying something doesn’t mean people heard it the way you meant it. I’d walk out of a leadership meeting convinced we were all on the same page, then find out a week later that three people had taken the same decision three completely different ways. Nobody was being awkward, they honestly thought they’d understood.
Now scale that up to an organization where thousands of people are being asked to change how they work. Leadership announces a new AI strategy, managers get briefed, and employees get a presentation on the tools, the benefits and the rollout timeline. As far as the organization is concerned, the message is out and the job’s done. Then someone asks which part of their workload they’re supposed to drop to make time for experimenting, or two department heads realize they both think they own a process that now runs across both teams. You can’t sort those out with another email. They need people sitting down together, hearing each other out and making a decision.
More messages won’t give people clarity
I think we often mistake the volume of communication for the amount of clarity people actually have. A company can have brilliant internal comms, regular leadership updates and a channel for everything, and people can still feel uncomfortable asking a hard question or disagreeing with what they’re being told. None of that guarantees leaders are listening either.
There’s a real difference between asking your team whether they understand the strategy and asking them what isn’t making sense, where they’re getting stuck and what you might be missing. That second conversation can get uncomfortable pretty quickly. Someone might tell you your priorities aren’t realistic, that two departments are pulling against each other, or that the shiny new tool is creating extra work somewhere you can’t see. Surely that’s exactly what a leader needs to know, though?
Those conversations do have to go somewhere. There’s not much point inviting people to speak up if nothing changes afterwards. Someone has to listen, spot where a decision is needed and make sure it actually gets followed through, otherwise you’ve just built another place for people to vent.
So what would a Chief Conversation Officer actually do?
I don’t think the job would be getting everyone to talk more, since most organizations have more than enough (too many) meetings already. The way I see it, it’d be someone whose job is making sure the conversations that matter are actually happening. That might mean checking whether a leadership team is really aligned rather than taking silence as agreement, or getting department heads in a room when their responsibilities overlap and neither of them has the full picture. It might mean helping managers be honest with their teams about how roles are changing, including the bits they don’t know yet. It would also mean recognizing when the problem isn’t communication at all, but a decision leadership hasn’t made yet. Not every problem can be talked away, and sometimes people know exactly what’s wrong and are just waiting for someone with the authority to do something about it.
I’d still put my hand up
Something I see all the time in my coaching and advisory work is how much time and energy people spend working around the conversations they don’t want to have. Managers dodge the difficult discussions, senior leaders hold back from admitting they don’t have all the answers, and departments carry on in their silos because challenging each other feels politically risky. Meanwhile decisions stall and people fill the gaps with their own assumptions. AI didn’t create any of this, but it’s making it a lot harder to ignore.
To be fair, I don’t think every organization needs a Chief Conversation Officer. These are skills the whole leadership team should be building. What the title does do is raise a good question about who’s actually taking responsibility for making sure the right conversations happen.
This is a big part of the work I do with leaders, and it’s some of the work I enjoy most. So if Chief Conversation Officer ever becomes a real job, my hand’s going up. Until then, I’ll keep saying it: we don’t need more communication, we need better conversations. If there’s one your leadership team keeps putting off, message me this week and we’ll work out how to have it.