Customizing translations for organizations and teams

Customizing translations for organizations and teams

Businesses have specialized translations needs and preferences. How can we translate with nuance and respect to branding, subject matter and preference?Nothing should be lost in translation — even for international, multi-cultural, and multi-disciplinary teams.

Role: Sr. Product designer

Team: 1 Product Manager, 1 Developer, 1 Designer

+Lots of stakeholders

Adoption for the glossary — a key translation customization feature — was still lagging

Adoption for the glossary — a key translation customization feature — was still lagging

Pains plagued different users at different times throughout the journey. Those who were involved in onboarding or who had language were not actual end users of the product.

There were many opportunities to tackle. I knew there were too many gaps in the user journey, and we needed to improve the experience across the entire journey. However, leadership wanted to invest by creating glossaries from previous translation data that companies might have

The MVP, largely dictated by scoping, was a miss

The MVP, largely dictated by scoping, was a miss

Users struggled to format their upload data and were confused by the instructions. There was too much information on one page and weren't sure what to focus on first

I split up the flow into more steps, and to accommodate more file types & language combinations

I split up the flow into more steps, and to accommodate more file types & language combinations

Original landing page

Re-design

Providing more focus for each task at hand

Contributing an upload component for the design system

What's next?

What's next?

  • Evaluate usability & default criteria for review process

  • Enable multiple users to participate in the process — we learned that different users can be involved in the upload process than the review process

  • Add product entry points for this feature

  • Improve downstream capabilities (like glossary merge)