I’ve been the product owner in the room when a localization program stalls, and the actual cause is almost always the same: a program spanning five markets and three internal teams, with no single person who can say yes on behalf of all of them.

What the Stall Actually Looks Like

Marketing wants a term changed for market resonance. Legal wants the same term locked for compliance reasons. Product wants it to match a UI string that shipped two versions ago. Nobody in the room has the authority to resolve that conflict, so it doesn’t get resolved. It gets escalated, or quietly decided by whoever answers the email last, and three markets ship with three different resolutions to the same question. On one program, a single untranslated legal term sat unresolved for six weeks, not because nobody had an opinion, but because four people did and none of them outranked the other three.

The One Name Test

Here’s the test I run on any stalled program: can one person in the room say yes to a cross-functional conflict without checking with anyone else first. If the honest answer takes more than one sentence, that’s the stall, and it has nothing to do with the languages on the scope sheet. Translation was never the bottleneck. Localization sits at the intersection of every team’s priorities and belongs, structurally, to none of them.

“Our Org Runs on Consensus, Not a Single Owner”

The pushback I hear most from matrixed organizations is that a single decision-maker isn’t how they operate, and forcing one in feels like it undermines how the teams are meant to collaborate. That’s a fair structural preference, and it doesn’t actually conflict with the fix. The owner doesn’t replace the conversation between marketing, legal, and product. They own the tiebreak when that conversation doesn’t converge in a reasonable window. Consensus works until it doesn’t, and a program needs a named person for the moment it doesn’t, not a permanent override of the collaboration itself.

The Fix, Plainly

Name one person. Give them actual decision rights across the teams that touch the program. Route every unresolved escalation through them instead of around them. It sounds obvious. Almost no organization has done it, because it requires someone to name a piece of control out loud and hand it over.

If your localization program has been “almost done” for longer than it should be, start by asking who can actually say yes. If the honest answer takes more than one sentence, that’s your stall.