The Reality of Koreatown
Walk three blocks in Koreatown and you’ll hear Korean, Spanish, English, Tagalog, Bengali, Thai, and more. Conservative estimates put the number of languages spoken in the neighborhood above twenty. That’s not a problem to solve - it’s a reality to design for.
Most organizations handle this by operating in English and offering translations when someone asks. That approach has a built-in flaw: it requires people to request help before they can participate. The people least likely to request help are often the ones most affected by decisions being made without them.
English-First Doesn’t Work
The standard model goes like this: write everything in English, then translate key documents into one or two other languages, usually Spanish and Korean. Post a sign that says “translation available upon request.” Congratulations, you’ve checked the box.
But checking the box isn’t the same as including people. Translation-upon-request means someone has to know the request is possible, feel comfortable making it, and wait for someone to fulfill it. At a community meeting, that delay means the conversation has moved on. In a planning process, it means feedback arrives after decisions are already shaped.
The inclusive communication initiative is designed to flip this model. Instead of starting in English and working outward, we plan to build multilingual access into every interaction from the start.
What This Looks Like in Practice
The platform includes a translation system designed to work across the tools people actually use - not just documents, but conversations, announcements, forms, and feedback channels. The goal is real-time or near-real-time access in multiple languages, not a PDF translated two weeks later.
The voice tools are part of this too. Not everyone communicates best through text. Some people are more comfortable speaking than typing, especially in their first language. Voice input with transcription and translation will open channels that text-only systems close.
Here’s what we’re building toward:
- Meeting materials available in multiple languages before meetings happen, not after someone asks.
- Live interpretation capacity at community gatherings, not as a special accommodation but as standard practice.
- Platform interfaces that default to each user’s preferred language, not English with a language toggle buried in settings.
- Feedback mechanisms that accept input in any language and route it to the right people with translation intact.
Beyond Translation
Translation is necessary but not sufficient. Language access also means cultural competence in communication style. A direct English phrasing can land differently in Korean. A formal Spanish construction might feel stiff in a casual context. Getting the words right matters less than getting the meaning right.
This is why we plan to involve community members in the communication design process, not just as translators but as cultural bridges. The people who navigate between languages every day understand nuances that no algorithm captures fully.
Why This Matters for Everything Else
Every other initiative Ktown Team is building depends on broad participation. Governance decisions need representative input. Programs need to reach the people they’re designed for. Feedback loops need to include the full range of community voices.
If language is a barrier to any of that, nothing else works as intended. The infrastructure of inclusion starts with communication - making sure that when someone wants to participate, the first thing they encounter is access, not a gate.
Twenty-plus languages is not a challenge. It’s Koreatown. And anything we build needs to work for all of it.