Localization was never a translation project. We just spent years managing it like one. I think this is one of the biggest mindset shifts happening in our industry right now.
Localization is changing. It is no longer something that happens quietly after a product, campaign, or piece of content has already been created. It is increasingly becoming part of conversations about product experience, international growth, customer experience, brand, SEO, conversion, accessibility, technology, and, of course, AI.
When the business starts looking at localization differently, localization professionals need to look at their own roles differently too.
I want to walk you through my experience of how my position within localization shifted from being primarily project-focused to becoming much more program-focused and how that shift dramatically increased the value I could bring to my team.
Localization on the table
I remember the exact type of meeting. A marketing manager or a tech lead on the other side of the call, and me, the project manager on the LSP side, walking them through timelines, word counts, and delivery dates. They wanted one thing: a text translated and delivered on time.
That was it. They didn’t know what a KPI for multilingual content could look like. They didn’t know localization could affect conversion, retention, or how a market perceived their brand. They just needed the words to arrive, in the right language, before the deadline.
I worked that seat for years, across tech, retail, beauty, and communications accounts. To be clear, I still see that client today. The one who treats localization as a checkbox at the end of a launch, not a decision made alongside it. That hasn’t disappeared.
However something else has been happening in parallel, and it’s the biggest shift I’ve witnessed in this industry: localization is increasingly on the table.
Not always valued the way it should be? Meh, but still on the table. Discussed. Planned for, at least a little, instead of bolted on after everything else was decided.
I don’t think that’s my personal win. It’s a win for the whole chain of people who do this work: translators, LSPs, in-house localization teams, because it means the value we’ve been trying to demonstrate for years is finally landing somewhere.
From deliverable to product
That expansion asked something of me in return. It required me to expand too: my skill set, my perspective, the questions I knew how to ask.
The biggest mental shift was learning to see localization as a product, not a result. A result is something that happens at the end of a process, evaluated once, then forgotten.
A product has a lifecycle. It has users. It gets iterated on. Someone owns its direction, not just its delivery. Once I started seeing localization that way, I couldn’t go back to managing it as a series of isolated handoffs.
“Localization is no longer just the result at the end of a content pipeline. It is becoming a product in itself.” Luana Santos, Localization & Global Content Strategist
That reframe is what pushed me from pure project management into program management, and I think this distinction gets flattened a lot in our industry, so it’s worth spelling out.
Project management vs. program management
Project management is focused on successfully delivering a defined piece of work. It has a defined start, a defined end, and a concrete deliverable.
In localization, that might mean taking a campaign from intake to delivery across 15 languages, coordinating linguists and reviewers, managing timelines and dependencies, handling changes, monitoring quality, and making sure the content reaches the client when it is supposed to.
There is a clear beginning, a defined scope, and an expected outcome. You are asking: How do we deliver this successfully?
Program management doesn’t have a single deliverable — it has an outcome, sustained over time, made up of many interrelated projects.
In localization, instead of asking how to deliver one project, you start asking why the workflow exists in its current form, where it is breaking, what can be standardized, what can be automated, where humans add the most value, which metrics matter, and how localization can better support the company’s goals.
You are asking: How do we make the entire system work better?
“The difference, in one line: a project manager delivers a thing on time. A program manager makes sure the right things are happening at all.” Luana Santos
For example, a Project Manager might notice that every UX localization request requires several manual handoffs between Jira, the TMS, reviewers, and the product team, and will manage those handoffs carefully to make sure the current project succeeds.
A program manager sees the pattern and asks: why are we doing these handoffs manually every time?
That can lead to redesigning the intake process, connecting Jira with the TMS, introducing automated translation using existing translation memories and glossaries, creating structured review workflows, implementing automated quality checks, building dashboards, and defining KPIs that show whether the new process is actually improving things.
The big shift
Making that shift changed what I brought to the table. I stopped being the person who shows up once the content is ready to be translated, and started being someone who sits earlier in the conversation: advising on scope, on quality trade-offs, on where to invest review time, on how this quarter’s launches connect to the next one.
I wasn’t managing a task anymore. I was managing a strategy, and localization was finally being treated as part of it.
That is the mindset shift I think localization needs more of.
Not simply “How can AI translate faster?” but “How can we redesign localization so that humans, technology, and the business work better together?”
Because localization is no longer just the result at the end of a content pipeline. It is becoming a product in itself.
Who’s building it in-house
Perhaps the most tangible sign that this shift is real is what we’re seeing on the other side of the table. Companies like Spotify, Google, Apple, and Notion are building their own localization structures, growing internal teams, and taking greater ownership of how their products and brands show up around the world.
When I started my career, I simply didn’t see many of these opportunities for myself. Localization careers felt much more concentrated on the LSP side, while the client side often meant being the person requesting or approving the work. Today, that ownership is shifting, and so are the career opportunities that come with it.
For me, that’s one of the most exciting outcomes of localization becoming a product: the value, the responsibility, and the opportunity are no longer sitting only with the LSP. They are moving closer to the people building the product, shaping the brand, and ultimately owning the relationship with the user. I honestly think that’s a fantastic shift for our industry.
Where this leaves the work
Have you seen your localization role shift from project execution toward program ownership?
Are you already treating localization as a product inside your organization, or are you still fighting to get localization a seat at the table in the first place?
What are you seeing? I’d genuinely love to compare notes with the people living through this shift every day.
Luana Santos is a localization & global content strategist working across globalization, product, and UX localization, with a focus on AI-automated workflows and quality at scale. She is based in Spain.
Visit Human-in-the-Loc to subscribe to her free weekly newsletter exploring the evolving role of humans in localization, AI-powered workflows, and global content ops.
