What else creates lag before a localization project kicks off?
Once you receive the quote and confirm the project, the real work begins. Ideally, when creating the quote, the project manager should set up and analyze the project in such a way that work can start as soon as the final files are received and imported.
Localization engineering should be involved right from the beginning of the analysis. If projects aren’t organized this way, then some work will need to be repeated after the quote is confirmed, which makes the whole process less efficient.
There is also a period in most projects when the project has been confirmed, but localization can’t yet begin. This could
cause lag—or the downtime could be used to take care of some of the “invisible” background work that is so essential to a successful, high-quality localization project.
Once work begins, other little things can eat up time, too. For example, if you add new files to the project, you might need another quote, and the project manager will have to add the new files to the existing project
. Requests for status updates and back-and-forth emails
also nibble away at everyone’s time. It might not sound like much, but these little details can add up over the course of the project. As a seasoned pro in the games localization industry, though, Altagram has found a lot of ways to deal with this type of communication as efficiently as possible—for example by automating the process of file handling, quotation setup, and workflow with all the stakeholders, including the sales team, project managers, and localization engineers.