By Willian Magalhães, Localization Specialist & Conversation Designer Every Monday I had the same small problem. New content had landed over the weekend, and somebody had to turn it into tasks. Creating the tasks takes maybe five minutes. Figuring out who should get each one is what used to eat my morning. In a TMS you sometimes run into fairly complex cases, and out of the box there is often no UI to handle them comfortably. This is one of them. "Which of my translators has room for this?" sounds like a simple question, but the answer is spread across every project you have. I have used a lot of TMSs and they all have good screens. None of them had a screen for how my team works, and honestly I don't expect one to, because no product can ship a screen for every team out there. So I did what most of us do. I exported a spreadsheet, or asked an engineer to write me something with the API, or I just opened project after project and kept the whole picture in my head. I really believe your problem should be solved the way your team works, not the way your TMS happens to have UI for. And this is where Crowdin is at its best for me. There's the whole apps infrastructure to build on, plus Crowdin Copilot, which lets you run localization from a chat. And the chat builds a dynamic UI on the fly. That last part I didn't expect, so I recorded a video to test it on a setup that looks like a real company.

If you've spent any time in localization, you've probably crossed paths with LocWorld, one of the industry's longest-running conferences. And if you've been to one, odds are you've also crossed paths with Renato Beninatto. On a recent episode of The Agile Localization Podcast, host Stefan Huyghe caught up with Renato, now CEO of LocWorld after Nimdzi Insights acquired it from founders Ulrich Henes and Donna Parrish, to talk about what's changing, what's staying, and why Vancouver is about to get very interesting.

About twenty years ago, TAUS founder Jaap van der Meer predicted that translation would become a utility: something you could tap into as easily as electricity from a wall socket. That prediction has largely come true. But the version of it we're living in now is bigger than anyone expected. On a recent episode of The Agile Localization Podcast, host Stefan Huyghe spoke with Anne-Maj van der Meer, Head of Growth at TAUS, ahead of the TAUS conference in Vancouver: The Art of Mastering Intelligence-as-a-Utility. This year, the event runs alongside LocWorld as part of the first Vancouver Localization Week. Their conversation shows how the challenges facing the localization industry have changed.

When your product is used by a seven-year-old learning multiplication, a university professor running a pop quiz, and an HR manager onboarding new hires, all in the same afternoon, across 22 languages, localization stops being a translation exercise and starts being something closer to cultural choreography. That's the world Maria Saez and Gabriele Spiteri live in every day. On a recent episode of The Agile Localization Podcast, host Stefan Huyghe sat down with Kahoot!'s Localization Manager and Localization Program Manager to unpack how they keep a platform that's simultaneously an e-learning tool and a live game experience feeling native everywhere it lands.

This September, AI took on more of the work in Crowdin, and your organization's context now reaches the teams that translate outside it. Copilot runs scripts and builds apps without a developer, AI Pipeline can leave proofreaders only the ambiguous strings, one glossary and TM can cover every project, and teams that translate in their repository get the same Crowdin context.

A practitioner focused framework for deciding what to localize, when to localize it, and how to connect localization to real user tasks. Localization teams rarely have the luxury of translating everything at once. There is always more content waiting. New product features are being released. Documentation is changing. Marketing wants campaign pages translated. Support needs troubleshooting content. Product teams want the UI ready for a new market. Then comes the question: What should we localize first? It is tempting to answer that question by looking at what is ready for translation, what was translated last time, or which team is asking most urgently. That can create a translation queue, but it does not necessarily create a better localized experience. A more useful question is: Where does language create the most friction for our users?