This week HeedPost started speaking 21 languages: Arabic, Bengali, Chinese (in characters and in Pinyin), Dutch, English, French, German, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Portuguese (Brazil), Russian, Spanish, Swahili, Tamil, Turkish and Urdu. Three of them, Arabic, Hebrew and Urdu, read right to left.
This is what changes for a team running a board, and what stays the same.
Your customers see their own language
A customer opening your board sees it in the language their browser asks for: the menus, the buttons, the form, the roadmap, the changelog. If their browser doesn't ask for one we speak, they see your workspace's default. They can switch at any time.
That sounds like a small thing. It isn't, for someone who reads English slowly. A form in your own language is a form you finish. A board in your own language is a board you come back to.
Their email arrives in their language
When a post they follow moves, or something they asked for ships, the email arrives in the language they read the board in. Not in your language, not in English by default. The words are the product's, translated with the same care as the screens.
What they write stays as they wrote it
Posts and comments are your customers' own words, and we don't change them. A request written in Spanish stays in Spanish. That matters: the person who wrote it should recognise their own post, and your team should be able to see what was actually said.
If you want readers to see posts in their own language too, that's a choice you can make.
Your team can answer in theirs
The hard part of a multilingual board has always been replying. A team that only writes English either replies in English, which feels cold, or doesn't reply, which is worse.
What you might notice
You may well see more posts from places that were quiet before. Not because those customers had nothing to say, but because saying it in English was harder than it needed to be. That's feedback you were missing. Now it has somewhere to go.
What we'd suggest
Set your workspace's default to the language most of your customers read. Name your statuses and labels in that language too, since those are your words rather than ours. Then let each reader's browser do the rest.