Here's a pattern I've watched play out in companies of every size, in every industry, for fifteen years. A leadership team meets. They make a real decision, a good one. Everybody nods. Everybody leaves the room aligned. And then ninety days later the thing still isn't done, and nobody can quite say why.
When that happens, the instinct is to blame the plan. So they make a new plan. Same room, same nodding, same ninety days, same nothing. The plan was never the problem. The decision got made in one language and the work happens in another, and somewhere in between, the meaning fell out.
I call these translation failures, because that's what they are. Not strategy failures. Not effort failures. Nobody in these stories is lazy or stupid or hiding the ball. They're all working hard on slightly different versions of the same idea, and the gaps between those versions are where the company quietly bleeds.
The decision gets made in one language. The work happens in another. The meaning falls out in between.
One company I worked with had a project that lived on the leadership agenda for six straight months. Every meeting, it came up. Every meeting, everyone agreed it was important. Every meeting, it moved to next week. Marketing assumed the design team had it. Design assumed they were waiting on a sign-off. Leadership assumed it was already in motion. Six months. Three teams. One project that never moved an inch, and not one person who could be fairly blamed for it.
That's the tell. When something stalls and you genuinely can't find who dropped it, it usually means the handoff was never clear enough for anyone to catch. The ball wasn't dropped. It was never actually handed to anyone.
The reflex in most organizations is to fix this with more. More meetings. More documentation. More project management software. More status updates. And sometimes that helps a little, but mostly it just adds layers, and every layer is one more place for meaning to leak. You don't fix a translation problem by adding more languages to the room.
What actually closes the gap is almost embarrassingly simple, and almost nobody does it. You make one person responsible for the meaning surviving, not just the message getting sent. Someone whose actual job is to stand in the gap between strategy and execution and ask the unglamorous questions. Who owns this. By when. What does done look like. Who's waiting on what. What did each person in that meeting actually hear, because I promise you it wasn't the same thing.
That role rarely sits on an org chart. It's not a director title or a department. It's a function, and in most companies it's nobody's job, which is exactly why the gap stays open. The best operators I know are the ones who quietly do this work without being asked, and they're usually the ones everyone calls indispensable without being able to explain why.
Here's the part that matters more every year. As companies bolt on more tools, more automation, more AI, the speed goes up and the surface area for translation failure goes up right along with it. You can generate a strategy deck in four minutes now. You still can't make twelve people understand it the same way. The technology compresses the easy part and does nothing for the hard part, which was always human.
So the companies that win the next decade won't be the ones with the most technology. They'll be the ones who lose the least meaning between deciding something and doing it. That's not a software feature. That's a person, paying attention, refusing to let the room walk out with five different meetings.
If something keeps stalling and you can't find the culprit, stop looking for the lazy person. There isn't one. Look for the translation that never happened.