LocDiscussion reposted this
Localization Has Always Been A Context Problem...Who Owns Context In Your Process? Ian Cowley, Technical Writer at Salto feels context is even more relevant today than it was a few years ago. While we can now translate a string in seconds, we still need to first understand what that string means, where it appears, who will read it, and what the user is trying to accomplish. "AI needs that context as well. So it's even more important in this day and age." The role of technical writers is evolving. They're no longer just documenting products. They are increasingly responsible for building and preserving the context that everyone else depends on, from developers and designers to translators and AI systems. Where does context live in your organization today? According to Ian, technical writers are becoming "more of a context engineer" and I think that's an accurate description of where many teams are heading. That also explains why he feels so strongly about having a single source of truth for strings. "There always should be one unique source of truth... Having multiple versions of strings is unmanageable." When context lives in five different places, neither people nor AI know which version to trust. How many sources of truth does your team have today? It’s amazing how little attention we sometimes give to the plumbing behind localization. Ian walked through the GitHub integration his team uses with Crowdin. A developer adds new strings, they flow automatically into Crowdin, translators are notified, translations return through a pull request, and the team can review everything before merging. What piece of localization "plumbing" has had the biggest impact in your organization? It sounds simple, but it fundamentally changes the workflow. The repetitive work disappears, feedback stays attached to the strings, and everyone is working from the same source. That kind of automation has probably done more to improve day-to-day localization than many of the AI announcements we've seen over the past two years. Successful AI adoption in localization depends less on choosing the right model and more on creating the right context around it. If the context is poor, AI simply gets the wrong answer faster. If the context is rich, structured, and connected to the source of truth, both humans and AI produce better work. Isn't that one of the most important lessons for localization teams right now?