Gamma's website looks, at first glance, fully localized. But once you read a few lines, it feels like something else entirely — as if an NMT engine did the first pass, and a human made random touch-ups with no overall policy or review.

That mix creates what I'd call a half-localized experience: technically translated, but culturally unfinished. And that gap becomes immediately visible in small, telling details.

1. Inconsistent and unreviewed UI text

On Gamma's top page, the header correctly says 「概要」(About) and 「ヘルプ」(Help). But on other pages, the same items appeared as 「約」("approximately") and 「助けて」("help me!").

For Japanese users, that's not a small typo — it's a credibility killer.

Especially in B2B SaaS, this is fatal. Decision-makers in Japan (often 40s and older) evaluate professionalism partly through language quality. If your Japanese UI looks sloppy, your product gets disqualified before the demo.

Note: These specific UI errors have since been corrected. This analysis reflects Gamma's Japanese UX as observed in 2025 — and illustrates the kind of issues that appear when localization is treated as a one-off task rather than an ongoing system.

2. Localization in name only

Gamma's Japanese site gives the impression of being localized — but once you start using the product, you realize: there is no localization at all. From a business standpoint, that's not a minor gap — it's a structural one.

Component State at time of analysis Result for Japanese users
Help pages English only Users give up after searching
YouTube tutorials English audio, auto captions Subtitles make no sense
Feature announcements English only Users never hear about updates
Sample templates English text "How am I supposed to use this?" → immediate drop-off

What would fix it

3. Onboarding without localization = onboarding failure

Gamma introduced an AI assistant called Agent✨ — a great idea, but nearly invisible. The activation button sits quietly next to "Present," and unless you've read Gamma's English changelog or watched their videos, you won't even know it exists.

Without localized onboarding, help pages, or feature announcements, most users never learn what the feature does — or that it exists at all. For English speakers, that's mild UX friction. For Japanese users, it's a full stop.

Localization isn't just about language; it's how users discover and trust the product. An untranslated onboarding flow is, effectively, no onboarding at all.

4. Templates and Inspiration still in English

Gamma's template library is one of its strengths — but only for those who read English. Templates like "Brand Partnership Proposal," "New User Onboarding," and "Quarterly Business Review" remain untranslated, making the library feel like a wall of English text instead of an invitation.

That might sound like a small issue — but in Japan, language is the entry point. If users can't even read the templates, they'll never experience what Gamma does best.

The numbers back it up: according to the 2024 PROGOS Business English Speaking Test, only 7% of Japanese professionals have B2-level English proficiency. When your product experience starts in English, over 90% of Japan's market never makes it past the first click.

5. Where to start fixing it

If localization is to complete the product experience, the order of priorities looks like this:

  1. Localize official announcements and tutorials — Users can't use features they don't know exist.
  2. Translate help and onboarding content — So users can actually learn the product.
  3. Localize templates and inspiration materials — To help users expand how they use Gamma.
  4. Refine UI text and terminology — Ensure consistency and contextual clarity.

This isn't just about Gamma. Many global products face the same trap: thinking localization is a post-process, not part of product design. But for users, it defines whether the product even exists for them.