Getting Started with Globalization in ServiceNow: Tools, Tips, and a Live Demo

[Sharon_Barnes]

Globalization is no longer optional for enterprise platforms. With only about 20% of the world speaking English, organizations need to deliver experiences that work across languages, regions, and cultures. 

In this session, the ServiceNow team walk through how globalization is built into the platform and how you can take advantage of it to support your users worldwide. 

Why Globalization Matters 

Historically, enterprise software has been built primarily for English-speaking users. Today, non-English speakers make up the majority of internet users, meaning that organizations must rethink how they design and deliver digital experiences. 

ServiceNow approaches globalization as a foundational capability tied closely to accessibility ensuring its users can work effectively regardless of language or region. 

The Layers of Globalization 

No globalization strategy would be successful without considering three core components. 

1. Internationalization (i18n) 
   Generalizing products so that it can handle multiple languages and cultural conventions without the need for redesign, for example date and currency formats.  
2. Localization (L10n) 
   Converting software or products from one language into another. ServiceNow offers 25 languages out of the box. 
3. Translation (t9n) 
   The act of translating text from one language into another. 

Common Challenges Teams Face 

Many teams only think about localization when a need arises, for example when entering a new market or acquiring another company. These events lead to questions such as: 

• What needs to be translated?  

• Which tools should we use?  

• How do we maintain translations over time?  

A key takeaway: localization is never “done.” It’s an ongoing process that requires the right tools and workflows. 

Localization Workspace: Your Control Center 

Localization Workspace is the central tool for managing translations in ServiceNow. Built on Localization Framework, it helps automate and scale translation efforts. 

Key setup tips include: 

Translation Preferences 
Define whether content should go through machine translation, vendors, or a mixture of both methods. 

Translation Workflows 
Customize workflows for approvals, reviews, and publishing based on language or content type. 

Language Groups 
Bundle commonly used languages together to speed up repeat translation requests. 

Language Asset Management (New) 
Manage glossaries to ensure consistency and quality across translations. 

Demo: Translating a Portal in Minutes 

One of the highlights of the session was a live demo showing how to translate an Employee Center portal from English to Japanese in just a few minutes. 

Using Localization Workspace, the process includes: 

• Selecting content to translate  

• Choosing the target language  

• Reviewing cost estimates  

• Selecting machine translation as the translation method to be used  

• Publishing the translated content  

Automation + Flexibility 

ServiceNow doesn’t lock you into a single approach. You can: 

• Use machine translation for speed  

• Integrate with external vendors via APIs  

• Build custom workflows for compliance or quality control  

This flexibility allows organizations to balance cost, speed, and accuracy. 

Final Thoughts 

Globalization in ServiceNow is powerful. With the right configuration, you can: 

• Deliver consistent multilingual experiences  

• Reduce manual translation effort  

• Scale across regions with confidence  

If you’re just getting started, Localization Workspace is the best place to begin.