Shifting Left: Software Localization from Design and Development with Nicolas Martinez | Motorola

Описание: In this webinar, Nicolas Martinez (Senior Localization Software Operations Specialist, Motorola) talks with Adam Asness (CEO of Lingoport) about what “shifting localization left” really means in practice. Instead of treating localization as a final step after design and development are done, they discuss how teams can bring localization into the workflow earlier—when changes are easier, faster, and cheaper.

Nico shares how Motorola works across design, engineering, and localization, where the biggest friction appears, and what helps reduce it. A big theme throughout the session is context: without it, short UI strings are easy to misunderstand, which creates quality issues and rework later. They also discuss how automation, Figma-based workflows, and AI can support teams—without slowing designers and developers down.

Main topics discussed:

What “shift left” looks like at Motorola
The biggest pain point: lack of context
Using Figma to spot layout issues early
Localization in GitHub pull requests
“Definition of Done” for localization
Where AI helps (QA, classification)
Where AI doesn’t help (translation trust)
Measuring “lack of context” as a KPI
First step: understand the dev cycle

If you’re facing challenges with internationalization or localization, you don’t have to solve them alone. Lingoport works closely with product, design, and engineering teams to help build localization into the software lifecycle early.

Whether you’re just starting to shift localization left or looking to improve existing workflows, you’re always welcome to reach out to Lingoport:

https://lingoport.com/get-a-demo/