A leadership team came to us saying their problem was communication. Meetings ran long, decisions got made and then unmade a week later, and two directors had stopped speaking to each other outside formal sessions. The brief on the table was a workshop on communication skills.

That’s usually where organisational development actually starts: with a label that isn’t quite the problem.

A few conversations in, the pattern looked different. Nobody disagreed about strategy. What they disagreed about was who actually had the authority to make a call once it left the boardroom. One director would sign off on something in the room, someone else would quietly reverse it in a hallway conversation two days later, and the original decision would just evaporate. People had started reading the meeting invites to guess whose call was going to get overridden this time.

That’s not a communication problem. That’s a decision-rights problem wearing a communication problem’s clothes.

Once that was named, the work changed. Instead of a workshop on listening better, the team mapped out where decisions actually needed to sit, who had final say on what, and what “final” was supposed to mean once someone said it. Meetings got shorter, not because people talked less, but because there was nothing left to relitigate.

That’s what organisational development actually is. Not culture as a slogan or a values poster on the wall, but system design applied to how an organisation decides, communicates and holds people accountable. The presenting problem is data. The job is working out what it’s data about.

Most people who come to us arrive with a label already attached: communication, culture, engagement. Sometimes the label’s right. More often it’s just the nearest word available for something the organisation hasn’t been able to name yet. OD is the work of sitting with that until the real shape of it shows up, and building something that fixes what’s underneath rather than papering over the label sitting on top.