Global Design


Workday aims to ensure that users can comfortably and intuitively use our products regardless of cultural background, language, or location; and that we not only adhere to global best practices, but create innovative ways to improve global functionality and create inclusive experiences.


Workday’s approach to Globalization recognizes that the needs of all our users are not the same and that there are variations by region, language, national culture, local culture, industry and size of organization. Elements and functionality which are seemingly inconsequential to a U.S.-based user may be fundamental to users from other cultures.

We follow global best practices to meet regional customer needs. The technical practices we leverage include the:

  • International Organization for Standardization (ISO), which standardizes products and processes, including those for software development.
  • International Components for Unicode for Java (ICU4J), which provides a set of libraries that help software perform on all platforms.
  • Common Locale Data Repository (CLDR), which provides data to help software support different languages and locales.

We partner with our global customers to understand their pain points, needs, and motivations and solicit feedback on our designs. We aim to conduct foundational research and usability testing with users of varied cultural backgrounds and in different regions in order to ensure that our products and experiences meet a wide variety of needs.

Understanding Global Users

Technology is neither neutral nor static; it is used differently by different communities and it is shaped by the culture of those who create it. To have an effective global approach, we cannot design from just one perspective. We incorporate tools and processes to be as inclusive as possible in how we develop product and design experiences.


At Workday, we continuously examine what cultural biases may make their way into the technology, and we consider the needs of a broad range of communities when designing technology. Based on our experiences conducting user research to inform a globally relevant product, we have a few recommendations:

  • Consider cultural, linguistic, and national differences early on in the product roadmap.

    Cross-cultural research should influence all product roadmapsit is a must-have. Trying to accommodate the needs of global customers later on or retrofitting your product to other markets and communities is much harder and costlier than considering these factors to start off with. Build cross-cultural research into the product and design planning process wherever possible.

  • Leverage cross-cultural research to tap into previously unknown areas for innovation.

    Research can reveal untapped opportunities and unmet needs that are especially pronounced in one context and not yet fully understood in another. For example, when considering the needs of cultures which are less oriented toward an individualist mindset and are more group-oriented, we might discover opportunities for helping all users succeed as teams.

  • Be aware that cross-cultural user research is complex and requires careful planning to be successful.

    Try to find partners within your organization or outside it who have experience working cross-culturally.

Content and Visual Considerations

Users around the globe will have different interpretations of the information in the product, how that information is represented, and how they can interact with the product. When designing for a global product, keep in mind that users have different cultural frames of reference which can influence the following:

  • Perception of icons, their symbolism, and their meaning
  • Perception of color and the connotations specific to different colors
  • Preference for and comfort with the quantity of information on the page
  • Effectiveness of message hierarchyreaders of other languages are used to different text structures (such as headings, subheadings, styling of text, and more) which may influence how they skim and scan, and also how language is organized
  • Perception of voice and tonewords need to be chosen purposefully with a global audience in mind. For more on language, see the Translations article.

When conducting research, listen for the language participants use in order to inform choices in terminology that will appear in the product. The words participants use can provide insight into their mental model and what terms will make sense to them.

Interaction Considerations

  • Input methods: Every language may have a different keyboard setup and input methods across varying devices.
  • Demographics: Understanding the demographics of users may determine how they interact with the software service.
  • Field Placement and Order: Different cultures and languages require different fields and in specific orders. For example:
    • In Japanese, the postcode should appear before all other address fields.
    • In Spanish, names need to display the Paternal Surname first, followed by the Maternal Surname.


We translate the product into over 30 languages and offer over 80 different locales. Further, the combination of localization and translation produces over 2,000 unique user experiences. For example, a user may be a German expatriate, working in New York for an Israeli company, so she may choose to have her interface display localized to the U.S. in the Hebrew language.

Users have several controls related to how things will be formatted and displayed within Workday:

  • Language: Controls the language itself
  • Locale: Controls the locale setting, like date and currency formats
  • Preferred Currency: Displays the users preferred currency

With over 20 million users in over 160 countries and with over half those users coming from outside of the U.S., Workday aims to deliver a culturally and linguistically inclusive user experience to our customers.


As Workday designs and acquires new technologies, we need to consider how to ensure these can be translated and made accessible for the global market.

We have several checklists that teams can use to ensure products are global-ready:

  • i18n, Internationalization: The adapting of software to meet regional and cultural standards for technical and functional requirements
  • l10n, Localization: Translation and support of the software application and documentation in various languages
  • g11n, Globalization: Encompasses both Localization and Internationalization. Globalization is the process of designing, developing, and testing applications with extensibility, allowing for flexibility in functionality and content to serve varied global markets. Several examples of areas the globalization process encompasses are: local or regional HR hiring processes, payroll integration systems, and mailing address requirements and validations.

Can't Find What You Need?

Check out our FAQ section which may help you find the information you're looking for.

FAQ Section