What it is
A review that checks a product’s readiness for other languages and locales, including text expansion, right-to-left scripts, date and number formats, and culturally sensitive content.
When to use it
During Implement, before or alongside localization, and for any product serving multilingual audiences.
Why (value)
Surfaces layout, formatting, and content issues before translation, avoiding costly rework and broken interfaces in other locales.
How to run it
- List target locales and their requirements.
- Check text expansion and truncation risks.
- Verify date, time, number, name, and address formats.
- Check RTL support, fonts, and encoding.
- Flag culturally specific imagery or idioms.
Inputs and outputs
- Inputs: The design or build and the target-locale requirements.
- Outputs: A readiness report and localization-blocking issues.
Time and effort
Medium. Depends on locale breadth.
Evidence and limitations
Produces expert-review readiness evidence; it predicts localization problems but does not confirm usability for speakers of each language, which needs direct-user testing in locale. See Evidence and limitations.
Tips and pitfalls
- Plan for roughly 30 percent text expansion.
- Do not hardcode strings, formats, or layouts.
- Test with native speakers for critical locales.
Variations
Pseudo-localization testing, locale-specific audits, and RTL review.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Plain-language editing — Rewrite content so people can read, understand, and act on it the first time.
- Standards compliance review — Check a design against required standards, platform guidelines, and internal policies.
- Accessibility evaluation — Assess whether a product can be used by people with disabilities, against standards and with assistive tech.
