Continuous Localization – the Key to Efficient Product Globalization

持续本地化发展是高效产品全球化的关键

2021-03-25 19:25 Memsource

本文共1247个字,阅读需13分钟

阅读模式 切换至中文

Continuous Localization – the Key to Efficient Product Globalization If global growth is a key objective for your business, then localizing your products and services is a strategic concern. It’s important not just to get it right, but to do it at the right time. Particularly if you’re in the software or SaaS arena where updates usually need to be fast and frequent. But how do you achieve that on a global scale? In the past, localization work was manual, time-consuming, and complex, often involving many parties and drawn-out processes. Today, technology lets you streamline localization and follow new approaches that enable you to work more efficiently and effectively. So, you can accelerate your time to market, implement immediate improvements, and keep customers with increasingly high expectations satisfied – whatever your international reach. One such approach is continuous localization. Continuous localization keeps pace with development Continuous localization is when localization works in parallel with agile software development cycles – or indeed other product development cycles – rather than happening afterwards as a separate workflow. Without continuous localization, you’re at risk of the downsides of the waterfall product development model where each phase follows in sequence. A typical waterfall scenario is this: developers complete a development sprint and project managers package up string resources into localization kits and send them to translators. By the time translations start to come in, developers are already immersed in a different development sprint. They then need to return to the previous sprint and address questions, changes to coding, retesting of features, and so on, that have been thrown up by the localization work. This yoyoing between sprints, due to the lag in the localization workflow, can continue across multiple sprints and cause serious complexity and headaches. Continuous localization overcomes this by keeping pace with development, rather than holding it back or causing unnecessary disruption. It’s seen as best practice for creating global software and can be applied in other industries too. How to implement continuous localization To implement continuous localization, and keep it flowing as you grow, you need to establish two important structures: The right people working together in the right way. The right technologies working together in the right way. Once these are established, technology becomes a powerful enabler to localizing at the right time, at speed, and with quality, whatever your global scale. Let’s look at the people and technology elements in practice. Integrate development and localization teams To enable localization to be continuous, any disconnect between your localization and software development teams needs to be removed. There must be close collaboration. Ideally, your in-house localization team should have at least the following roles: Localization manager — to manage the whole process. Localization engineer — to implement your continuous localization workflow. Localization quality assurance manager — to oversee the quality of localization. The integration of your localization and software development teams becomes even more vital when you’re working at scale – for example, to localize thousands of strings across multiple languages and updates each day. Translators are part of the development process When you have translators working hand in hand with developers, they’re no longer passive suppliers with a separate workflow that causes disruption and delays. They’re immersed in the ongoing process. You can ensure translators gain product knowledge more quickly, understand what developers are working on, and learn which words to use in context. This symbiotic approach also enables developers to become more aware of localization issues and allows translators to provide valuable, timely feedback. For example, by highlighting inconsistencies or identifying bugs. Work with multilingual, cross-functional teams Even if it’s impractical to have translators working directly with developers, having a localization manager to keep information flowing between them is crucial. One of the benefits of continuous localization is you can allow developers to create interfaces in their first language. So you may have multiple development teams working in different languages. If that’s the case, or if you have several cross-functional teams, it would be worth having a localization champion on each team too. Choose the right localization tools If the goal for continuous localization is to ensure your teams are collaborating closely, with development and localization happening almost simultaneously, how do you achieve that at scale? How do you avoid wasting time by emailing files by hand, for example, or by batching and sending strings to translators? The answer is to automate and streamline as many steps as possible. And for that, you need the right tools – and they need to talk nicely to one another. A cloud-based TMS is key Your developers can, of course, develop their own localization software. But that takes them away from developing revenue-generating products. And, unless they’ve worked in the localization industry, it won’t have the benefit of years of localization experience and fine-tuning. It’s best, therefore, to invest in specialist localization tools, with the top priority being a powerful translation management system (TMS) that’s fully equipped for continuous localization. Ideally, it’ll be cloud-based to ensure it’s centralized, secure, and can easily scale up and down, depending on your needs. This allows your team(s) to stay in sync, however dispersed they are geographically. And you can keep tight control on costs, only paying for what you use. Look for strong integration capabilities You don’t want to be left doing a lot of the work manually, especially when you have a large and growing localization program. So ensure your TMS offers full API integration or connects easily with your other platforms such as your content management system and software development platform. Memsource’s Continuous Job feature, for example, has a great impact on efficiency and is powered by out-of-the-box connectors. When a file in a repository is updated, the corresponding job in Memsource is automatically updated within the existing project. This is particularly useful for software and app localization where updates are being made continually. Your translators can monitor when the development team adds strings and get to work localizing them straight away. Other important characteristics for your TMS To enable the best return on investment, also look for a TMS that offers features to improve the quality of localization. For example, artificial intelligence, translation memory, terminology management, and the ability to provide context to translators. And seek out features that improve efficiency such as end-to-end automation, machine translation, and an intuitive workflow for translators. Overcome potential challenges While continuous localization comes with a host of benefits, there can be challenges to overcome. For example: Maintaining consistency and accuracy – particularly if small translations are requested out of context. Pricing and managing translations – which can be tricky if you have a high volume of translators, with many working on just a few words a week. Efficient collaboration across functions – you’re likely to have product managers, designers, UX specialists, marketers, and more, involved in your processes, as well as translators and developers. Tailoring workflows – each product development workflow may be different, so you’ll need to build flexibility into your localization processes. Reap the rewards Fortunately, by investing in the right technology and getting your people and processes working in the right way, you can overcome these challenges. You can implement continuous localization successfully at scale and gain the benefits of increased focus, better quality products, faster launches, significant cost savings, and total flexibility to work around your needs.
持续本地化发展是高效产品全球化的关键 如果全球增长是业务的一个关键目标,那么本地化的产品和服务是一个战略问题。不仅是把事情做好,更要在对的时间做。尤其是在软件或SaaS领域,更新通常需要快速和频繁。但如何在全球范围内实现这一目标呢? 过去,本地化工作多是人工进行,花费时间长,程序步骤复杂。相关内容涉及到多方利益,过程会漫长。如今,技术能够简化本地化程序并遵循新的方法,从而使工作更有效率和速度。因此,您可以加快您的市场时间,实施即时的改进,并保持满足客户越来越高的期望-无论您的国际范围。其中一种方法是持续本地化。 持续本地化与发展同步 持续本地化是指本地化与敏捷软件开发周期(或者其他产品开发周期)并行工作,而不是作为一个单独的工作流在之后发生。 如果没有持续的本地化,您将面临瀑布式产品开发模型的不利因素,其中每个阶段都是按顺序进行的。一个典型的瀑布式场景是这样的:开发人员完成开发冲刺,项目经理将字符串资源打包到本地化工具包中,并将它们发送给翻译人员。当翻译开始出现时,开发人员已经沉浸在一个不同的开发冲刺中。然后,他们需要返回到之前的sprint并解决本地化工作中提出的问题、编码的更改、特性的重新测试等等。 由于本地化工作流程的滞后,这种在sprint之间的yoyoyong可能会在多个sprint之间继续,并导致严重的复杂性和头痛。持续的本地化通过与开发保持同步来克服这一点,而不是阻碍开发或造成不必要的中断。它被视为创建全球软件的最佳实践,也可以应用于其他行业。 如何实现持续本地化 要实现持续的本地化,并在增长过程中保持其流动性,您需要建立两个重要的结构: 相配的人会在一起工作 以正确的技术协同工作顺利进展。 无论您的全球规模,一旦这些都建立起来,技术将成为一个强大的使能器,在适当的时间、速度和质量进行本地化。 让我们看看实践中的人员和技术元素。 整合开发和本地化团队 为了使本地化能够连续进行,需要删除本地化团队和软件开发团队之间的任何断开连接。必须密切合作。 理想情况下,您的内部本地化团队应至少具有以下角色: 熟悉本地化管理的管理者来管理整个流程。 本地化工程师-执行持续本地化工作流程。 本地化质量监督管理者-监督本地化质量。 当您在大规模工作时,本地化和软件开发团队的集成变得更加重要—例如,跨多种语言本地化数千个字符串并每天更新。 翻译是开发过程的一部分 当你让译员与开发人员携手合作时,他们就不再是被动的供应商,有一个单独的工作流程会导致中断和延迟。他们沉浸在正在进行的过程中。您可以确保翻译人员更快地获得产品知识,了解开发人员在做什么,并了解在上下文中使用哪些词。 这种共生的方法还使开发人员能够更加了解本地化问题,并使翻译人员能够提供有价值的、及时的反馈。例如,突出显示不一致或识别错误。 与多语种、跨职能的团队进行合作 即使让翻译人员直接与开发人员合作是不切实际的,但让本地化管理人员保持他们之间的信息流动也是至关重要的。持续本地化的好处之一是您可以允许开发人员用他们的第一语言创建接口。因此,您可能有多个开发团队以不同的语言工作。如果是这样的话,或者如果你有几个跨职能的团队,那么每个团队也应该有一个本地化冠军。 选择正确的本地化工具 如果持续本地化的目标是确保您的团队紧密协作,那么开发和本地化几乎同时进行的情况下,要如何在规模上实现这一目标?如何避免浪费时间呢?例如,通过手动发送文件,或者批量发送字符串给翻译人员? 答案是尽可能地自动化和简化步骤。为此,你需要合适的工具,他们需要友好地交谈。 基于云盘的TMS是关键 当然,您的开发人员可以开发自己的本地化软件。但这使他们无法开发创收产品。而且,除非他们在本地化行业工作过,否则他很难有多年本地化经验,懂得微调的好处。 因此,最好是投资于专业的本地化工具,最重要的是一个功能强大的翻译管理系统(TMS),它为持续的本地化做好了充分的准备。理想情况下,它将是基于云的,以确保它是集中的、安全的,并且可以根据您的需要轻松地上下扩展。这允许您的团队保持同步,无论他们在地理上多么分散。而且你可以严格控制成本,只为你使用的东西付费。 寻找强大的集成能力 你不想被留下来做大量的手工工作,尤其是当你有一个大型的和不断增长的本地化程序的时候。因此,请确保您的TMS提供完整的API集成,或与其他平台(如内容管理系统和软件开发平台)轻松连接。 例如,Memsource的连续作业功能对效率有很大影响,并且由现成的连接器提供动力。更新存储库中的文件时,Memsource中相应的作业将在现有项目中自动更新。这对于不断进行更新的软件和应用程序本地化特别有用。您的翻译人员可以监视开发团队何时添加字符串,并立即开始本地化它们。 TMS的其他重要特征 为了获得最佳的投资回报,还需要寻找一款TMS,该TMS提供了提高本地化质量的功能。例如,人工智能、翻译记忆、术语管理以及为翻译人员提供上下文的能力。并寻找提高效率的功能,如端到端自动化、机器翻译和为翻译人员提供直观的工作流程。 克服潜在的挑战 虽然持续的本地化带来了很多好处,但也有一些挑战需要克服。例如: 特别是在不符合上下文要求的情况下,谨记保持一致性和准确性。 定价和管理--如果你有大量的翻译人员,很多人一周只工作几个单词,这可能会很棘手。 跨职能部门的高效协作—您可能会有产品经理、设计师、用户体验专家、营销人员等参与到您的流程中,以及翻译人员和开发人员 定制工作流程-每个产品开发工作流程可能不同,因此您需要在本地化过程中增加灵活性。 收获回报 幸运的是,通过正确的技术投资,能让您的人员和流程以正确的方式工作,就可以克服这些挑战。在规模上成功地实施连续本地化,并获得更多的关注、更高质量的产品、更快的发布、显著的成本节约以及完全灵活地满足您的需求等好处。

以上中文文本为机器翻译,存在不同程度偏差和错误,请理解并参考英文原文阅读。

阅读原文