Fidelity Investments Japan

Translating an Investment Platform Across Cultures — Not Just Languages

Role
Solo Designer (only designer in Japan)
Duration
1-year contract (2020–2021)
Company
Fidelity Investments
Scope
Localization, UX design, user research
Note
Internal platform under NDA

Fidelity Investments was expanding an AI-assisted fund management platform — internally called "Hybrid" — into the Japanese market. The product helped high-net-worth users build and manage portfolios with AI-powered fund suggestions. Not real-time trading. A slower, more considered approach: review funds, evaluate risk, build a portfolio, confirm.

The platform existed. The design system existed. A global design team existed across multiple time zones. What didn't exist was a designer in Japan. I was brought in as the only one — tasked with making this product work for Japanese investors.

The product wasn't broken. It was foreign.

Different decision-making culture

Japanese investors want to understand everything before committing. Every detail about a fund. Every dimension of risk. Where American or European users optimized for speed and profit, Japanese users optimized for certainty. The existing design assumed users wanted to move fast. Japanese users wanted to move carefully.

Components that didn't translate

The global design system was built for English-first, speed-first contexts. In Japanese:

  • Text expanded. More information needed to be visible on the same page — not progressive-disclosed or hidden behind clicks. Japanese users expected comprehensive detail upfront.
  • Modals needed rethinking. Interaction patterns like modals had to accommodate fundamentally different content density. One design required seven tabs inside a single modal — a pattern the global team had never encountered.
  • Typography shifted. Font choices, paragraph spacing, line heights — everything that feels invisible until it's wrong. Japanese typographic rhythm is structurally different from Latin text.
  • Review flows grew. More confirmation steps. More risk disclosure surfaces. The "review before you confirm" pattern needed to be deeper and more thorough than the global standard.

No local research infrastructure

There was no prior user research for the Japanese market. No testing protocols. No existing insight into how Japanese high-net-worth individuals actually interacted with investment tools.

Designed the localized experience

Not a translation — a reinterpretation. I redesigned flows to match how Japanese investors actually think: detail-first, risk-aware, deliberate. More review pages. Persistent risk information. Content density that respected the user's need to see everything before acting.

Built and ran user research from zero

I established user testing for the Japan market — recruiting participants, designing protocols, running sessions (typically 2–3 rounds with 5 users each), and synthesizing findings. The most consistent insight: users could navigate the interface, but their primary concern was always whether they had enough information about the fund to make a confident decision. Speed was never the priority. Clarity was.

Fed insights back to the global team

This is where the role expanded beyond localization. I joined global design meetings and learning sessions across time zones — not because I had to, but because I wanted to understand the system I was building within. When the team held sessions for designers to present their work, I shared what was happening in Japan — the only window the global team had into that market.

The seven-tab modal became a case study in itself. My manager's requirement. An unusual pattern. I presented it to the global design system team — they adopted the concept (that modals might need to hold structured, multi-section content) even though they redesigned the execution. They later provided a properly branded version back to me. The feedback loop worked both ways.

Bridged global design to local reality

I wasn't just consuming the global design system — I was stress-testing it against a market with fundamentally different expectations. Every component I adapted became a signal back to the global team about where their system was flexible and where it was brittle. I translated local user insights into designs that showed the global team what was possible — and what they hadn't considered.

"You can't localize a product by translating its strings."

This project has no conversion metrics to share. Security restrictions prevent it. But impact showed up differently:

The offer

At the end of my one-year contract, Fidelity's global design team invited me to join them full-time. Not the Japan team — the global team, based in China. They wanted the person who had been bridging local insight and global systems to do it at a larger scale. I declined because it required relocation, but the offer itself is the metric: the global team recognized that what I was doing in Japan wasn't just localization — it was contribution.

The precedent

I established user research practices for the Japan market where none existed. The testing protocols, the findings, the insight that Japanese users optimize for certainty rather than speed — these continued to inform the product after I left.

The system feedback

Every adaptation I made became data for the global design system — evidence of where components needed to flex for non-English, non-Western markets. The modal pattern. The review flow depth. The typography adjustments. These weren't just local fixes. They were system-level insights.

You can't localize a product by translating its strings. You localize it by understanding what the original design assumed about its users — and then questioning every one of those assumptions for a new context. Speed vs. certainty. Progressive disclosure vs. comprehensive display. Efficiency vs. confidence.

The hardest part wasn't the design. It was earning trust across time zones — proving that the designer in Japan wasn't just executing the global team's vision, but expanding it.