Written by
Argos Multilingual
Published on
14 May 2026

Shadow Localization: When Teams Translate Without You — And What to Do About It

“Shadow localization” occurs when teams within an organization begin handling their own translation and localization work outside the established localization function. This phenomenon predates AI — siloed teams have long operated independently, sometimes unaware that a centralized localization team exists — but the rise of accessible AI translation tools has accelerated it significantly. Teams that once had to submit requests, wait in queues, and build business cases for budget can now turn to tools like ChatGPT for instant results, bypassing internal processes entirely.

The instinct for localization professionals facing this situation is often to reassert control and centralize all multilingual work. However, a more effective response requires nuance. Not every instance of shadow localization is a problem to solve — some teams, like a patent department with highly specialized needs, may be perfectly well-served by their existing workflows. The key is assessing each case individually: What content is being produced? What is its lifespan and visibility? Are there quality or brand compliance risks?

When shadow localization does surface quality issues, the cleanup process becomes a strategic opportunity. Each intervention provides organizational intelligence — revealing which teams are expanding internationally, what markets they’re targeting, and where brand and quality risks exist. This intelligence, packaged and presented to leadership, repositions the localization function from a transactional translation service to a strategic advisory role with visibility across the company’s global communications.

The fundamental reframe is this: if the localization team is perceived only as “the team that translates stuff,” it will inevitably be seen as replaceable. If it is positioned as the function that provides international market intelligence, ensures cross-market brand coherence, and advises on effective multilingual communication, it becomes indispensable — and that positioning is built through helpfulness, not gatekeeping.

Key Insights

  • Shadow localization is a symptom, not the root problem. Its presence signals that something in the localization team’s setup — speed, accessibility, perceived value — is leaving internal stakeholders behind. Treating it as a diagnostic rather than a threat enables constructive response.
  • Not all shadow localization needs to be absorbed. Content tiering matters. A landing page live for 48 hours does not require the same treatment as long-lived brand assets. Localization teams should evaluate whether intervention adds genuine value or simply adds bureaucracy.
  • Cleanup work is strategic intelligence gathering. Every instance of rogue translation reveals which teams are going international, what content they’re producing, and what markets they’re targeting — organizational knowledge that no one else in the company is aggregating.
  • Influence is built through helpfulness, not policing. Teams that feel gatekept will find workarounds. Teams that receive genuine support and better outcomes will voluntarily return. The path to expanded visibility runs through service, not control.

More “Field Notes” Episodes

Explore more topics in our Field Notes series, where we break down complex localization concepts, ideas, and experiments for industry professionals. Check out our other discussions below:

 

Field Notes – Episode 11: Shadow Localization with Giulia

Stephanie Harris-Yee: Hello. I’m Stephanie, and back for another episode of Field Notes. And this time we’re actually going to be starting a new thread in Field Notes with Giulia Greco from Giulia Greco Consulting, and she’s gonna be approaching things from more of that interpersonal organizational side of things within loc programs.

So super excited to start this new series with her.

Giulia Greco: Thank you, Stephanie. This is very exciting for me, too. I’m thrilled to be participating in this new iteration of Field Notes and and grateful for the opportunity, and I think we’re gonna have some really interesting chats that hopefully can be useful to other localization professionals.

So we can take it away with our first topic.

Stephanie Harris-Yee: right, let’s do it. So this first topic is one that many of you have probably been hearing about or maybe hopefully not experiencing, but it’s something we like to call shadow localization.

So this is what happens when you’re doing your regular localization job, you have a good system in place, and all of a sudden you find out, oh, this other department has spun up their own workflows. Maybe they didn’t realize you existed. Maybe they just wanted to do their own thing. But now all of a sudden you have two separate workflows happening in the same company.

Maybe they’re doing great, maybe not. This is a situation. So AI has made translation something that anyone can do now, it seems. So you don’t really need a translation team anymore, right?

Giulia Greco: That’s what a lot of people seem to think, people that are not in the localization field, obviously many people in leadership or, other overeager folks. And sometimes I think honestly, can you blame them? The barrier to entry into translating has disappeared. But I also want to say something first, because this whole thing of shadow localization existed even before AI, at least in big companies that may have a tendency to be a little bit siloed.

There’s always like the little team that nobody knows about in an obscure part of the company doing something that kind of flies under the radar that doesn’t really interact with other teams. And they sometimes live under a rock and they just don’t know that now there is a localization team and maybe there wasn’t two years ago or five years ago when they were assembled and started doing some work and realized that they needed translations.

Maybe there wasn’t any infrastructure and no people doing this. So they took matters in their own hands. But they still kept on flying under the radar.

And this actually happened to me in my previous company with the patent team. Nobody knew about it. They were like three people. They had, easy access to procurement and legal because of the nature of what they do, clearly.

A clear mandate to get it done no matter what. And one day, I guess one of them talked to somebody else in the company and found out that there was a localization team that was providing translations to the entire company except for them. And they were like we have a contract for translations with an LSP. So they called me. I sat down. I had a chat. And I found out that the LSP was a reputable one. I found out about their volumes. I asked them, do you think you want to come on board and have my team handle your work? Or is this something that you are okay continuing with the way you are? And they were we don’t really know what we don’t know.

And what I realized was that they could probably benefit from being onboarded to my LSP because I said, you can benefit from volume discounts. At this point, you get under the umbrella of our general contract and SLAs, but you can still manage the whole pipeline on your own. Because I think they wanted to maintain independence and the ability of just do things the way they had always done them.

Everything worked out. It became a question of can you get a better price if you hop on our bus with this LSP with whom we have a big contract, versus keep going as a small thing with your own LSP?

And that’s what they did. I put them in touch directly with my LSP, and I said, “They’re on their own. I don’t need to take this on. God knows we have enough work as it is. I’m not looking for more work for me and my team.” And they were happy, and then it just became an addendum to our regular contract with the negotiated rates and everything, and Bob’s your uncle.

Everybody was happy. And this was pre-AI days. So this is just to say that it can happen. It was happening even before. But now it has a bit of a different flavor. Now it’s like teams who are like, “Oh man, I used to have to go through the localization team and having to fight for budget and make a business case

and now I can just go to ChatGPT and get it translated immediately and move by myself and look like the hero who’s shipping stuff, and I don’t have to deal with those annoying localization people who are telling me that quality is na, na or tell me that I have to get in line because there’s more important things in the queue first.

So this is what I mean when I say, can you blame them? The reality is that for a lot of teams there is a queue.

Stephanie Harris-Yee: Yeah.

Giulia Greco: Translation is not immediate when you’re going through a localization team, and sometimes localization people get too hung up on the consistency and the quality conversation without realizing that is of absolutely no interest and no consequence to their interlocutor.

And I think that’s a conversation that we need to have, because if there is shadow localization in your org right now, this is a signal that maybe something needs to change so that it doesn’t become more widespread, and eventually you end up appearing as irrelevant and not needed. That’s the number one thing.

Stephanie Harris-Yee: It sounds like things can come in two ways. So one, like you mentioned in your previous company, where they actually realize that, oh, there’s a localization department now, and they’ll come to you. And then other cases where, you’ll go out and you’ll say, “Wait, this suddenly popped up out of nowhere.

Here’s this thing that’s happening.” And either can, sometimes it’ll be working well, sometimes it won’t. What does happen if you come across one of those situations where you’ve found someone, they’ve made this whole system, and it’s a mess?

Giulia Greco: Yeah. So this is the other way exactly to your point. You usually find out in two ways that there’s shadow localization, either because somebody contacts you out of the blue and says, “Hey, I didn’t know you guys existed. We’ve been doing translations for a while,” like that patent team that I just mentioned.

Otherwise, you just accidentally, randomly run into some content in the wild, as I like to call it, like translations in the wild. You’re like, “Wait a minute. What is this? Did we do this?”

This doesn’t look like something that we did.” And usually it’s stuff that attracts your attention because, to my previous point, the quality’s not there.

And so it’s harder to surface, but it does happen quite a bit, and it did happen to me and my team quite a bit. It’s harder to get to the bottom of it, and it’s honestly way more concerning ’cause it is that other aspect of teams who maybe they never came to you, but maybe they did.

They tried a few times and the process felt either too slow for their timeline or somehow it didn’t satisfy their needs, and so they ended up building a workaround, and they have no reason to stop unless you give them a reason to stop. So when that happens if you’re able to get to the bottom of it and find the team or the person responsible for this what I did in the past was just reach out and say, “Hey, we noticed that you did these translations.

Can you tell me more about it? I come from the localization team, so I’m interested in everything multilingual, and I’m curious as to how you guys got this done. Also, just FYI, we noticed that language XYZ has some significant mistakes.” There’s been other instances where other teams have done localization through a third-party vendor.

And so they sell a turnkey type of project where they include translation and make it sounded like it’s gonna be so easy, you don’t have to worry about a thing. And, people that are already overworked and under-resourced are like, “Yeah, okay. Sure. Sounds good.” They’ll take care of it.

But then they get a little doubt, and so they may say yes, fully knowing that there is an internal localization team, and then they’ll go to the localization team and say, “Hey, can you check this? My vendor did it, and we wanna make sure that they did it correctly.”

And I hated that because that’s basically you’re getting called in as the cleanup crew, basically. Having said that, it’s annoying, but it is an incredible opportunity, just like it’s a good opportunity when you find the shadow localization in the wild. Because either way, if you are able to establish a connection or if they come to you asking to check, this is your opportunity to run a diagnostic and demonstrate your value.

And the review usually uncovers problems because of course it does, because there was no style guide. There was no terminology adherence. There were no branded terms. And so usually you can find quite a bit that needs to be changed. So you do it, you fix it, you go back, and you’re like, ” We’ve done the cleanup. It was quite significant, and here’s why.

And, next time, feel free to just call us. We can do this for you, and it will be done correctly from the get-go.” And that starts the conversation as to this is how you contact us. You basically use this as an opportunity to onboard a new team.

Stephanie Harris-Yee: Yeah. So is that usually the answer then, to try to draw them back in and bring it back under the localization team as much as possible? Or is that just a case-by-case thing?

Giulia Greco: I

think it’s a case-by-case thing. And that’s why I wanted to start this whole conversation with the patent team, because in that case, I didn’t bring them under my umbrella. You don’t always wanna bring it under it, and this is a little bit uncomfortable ’cause I think it’s in localization circles, there’s this idea that no, everything has to go through you and centralizing it, not in terms of org, but in terms of all the work needs to flow through you.

It’s considered the right thing to do, and I’m like maybe not. Maybe not in every situation. Not everything needs the full localization treatment. And so unless you are incredibly nimble as a team you can accommodate very different ways of working very quickly, suddenly.

Because a team that’s doing stuff on their own on the side because it’s faster, because they want it immediately, and because maybe they’re just translating a landing page that literally will stay online for 48 hours. We had a lot of those in my previous companies, like in-country teams that were organizing in real life events in various markets and needed just to throw a landing page up for registration with some information, and then it would come down after a week.

Do I really need to get hung up on it needs to be done 100% correctly, or can they just write it on their own? In some cases, it wasn’t even localization. It would just get completely created in the local languages from scratch, published, and it’s fine. So it’s more a question of thinking about in tiers, thinking about what is this content?

What is its longevity? What is it supposed to be doing? There are things that obviously you wanna be in the driver’s seat. But it goes back to like quality tiers that needs to reflect content tiering, right? But it’s the same situation. The patent team has something very specific.

They know exactly how it needs to be done better than any localization professional on the localization team. They already have a situation where they’re getting their needs fulfilled.

Do we need to get involved? Not really. There were no complaints. There were no quality issues. It was done to compliance.

It was done the way it was supposed to be doing. Fine, get it done.

Stephanie Harris-Yee: Yeah.

Giulia Greco: then you gotta ask yourself, why is it happening, i’ve always taken any type of initiative like this and any complaint as a flag that something in our setup is not working. Something in our setup is leaving someone behind, and we need to figure out how to not leave them behind because otherwise they will find a way that is a different way.

Stephanie Harris-Yee: So it sounds like there’s a couple of different situations. You respond to them on a case by case. How do you take all of these different things? So some you’re cleaning up messes, sometimes you’re just giving a little bit of advice. How do you organize your response so that at the end of the day, you’re ending up with a little bit more influence and more visibility than what with you started with?

Giulia Greco: Yeah, great question. So it is by reframing what your function is. If your localization team is positioned as that team that translates stuff, then of course everyone thinks that they can replace you with ChatGPT or any other AI tool. But if you’re positioned as the team that has strategic advice and a strategic point of view on international markets, that ensures that international experiences are coherent, they’re on brand, and they’re effective.

Like a team that has like international intelligence that can be deployed and help you being better at what you’re trying to do, that’s a completely different value proposition that AI can’t replicate on its own. Every time you clean up someone else’s messes you’re collecting intelligence. You’re learning which teams are going international that you didn’t know of, what content they’re producing, what markets they’re targeting, and that’s important organizational knowledge that you should have as a localization professional because you can take that to your own leadership and say, “There are X number of teams across the company doing translation work outside our function and our systems.

Here’s the quality risk and here’s what I propose.” You’re not going to your leadership to throw them under the bus and complain. You’re complaining that they are being bypassed. You’re going to them as a strategic move to present a strategic picture that you can see and nobody else is seeing. So it’s an advantage.

So the goal is not to control everything. It is to be the person in the company that understands the full picture of how your organization communicates across markets and across languages and across cultures.

That is the definition of influence. And ironically, you will get there faster if you help people, no matter what happened and how they came to you, than by gatekeeping them or policing them. Nobody likes to be policed.

Stephanie Harris-Yee: Yeah,

yeah. Okay. If you had to give someone one thing that you’d want them to take away from this chat, what would it be?

Giulia Greco: It would be that if someone in your company is localizing without you, don’t panic and don’t get territorial. Get curious instead, and use this as an opportunity to figure out what’s happening. Clean up what needs to be cleaned up, be helpful, and use what you learn in this process to make your function definitely more visible and more essential.

Yeah, I think that shadow localization is a symptom not the problem necessarily, and it tells you how your function is perceived. So it’s a data point. Use it as a data point, and then use it to expand your influence.

Stephanie Harris-Yee: Okay. Thank you, Giulia, and I’m excited to continue this series. So yeah, we’ll talk more next time.

Giulia Greco: So am I. Thank you so much.

What to read next...