The Wrong Question
Most organizations ask: “How can we use technology to amplify our message?” That’s the wrong question. If your technology is drawing attention to itself, it’s getting in the way.
The right question is: “How can we use technology to make the organization unnecessary in specific moments?” A resident finding legal aid shouldn’t need to know Ktown Team exists. They just need to find the aid. The resource hub that connects them is infrastructure, not a product.
What Invisible Technology Looks Like
At Ktown Team, we’re building dozens of platform tools to serve the Koreatown community. Most of them are designed to do quiet work:
-
Translate is designed to run behind every piece of content, making sure a Korean-speaking grandmother and a Spanish-speaking teenager can both access the same information. Nobody celebrates translation software. It should just work.
-
Hub is designed to connect residents to services, programs, and partners. The goal is that someone searching for housing assistance finds it in two clicks, not two phone calls.
-
Input and Survey are built to collect community feedback without requiring anyone to attend a meeting or fill out a formal complaint. The barrier to giving feedback should be as low as possible.
-
Emergency is designed to send multilingual alerts when they matter most. In a crisis, people don’t think about who built the alert system. They just need the information.
The Design Principle
Our technological philosophy comes down to this: technology is infrastructure for community work, not the work itself. The metrics that matter aren’t downloads, engagement, or user growth. They’re:
- Did someone find what they needed?
- Did language stop being a barrier?
- Did a volunteer connect with the right project?
- Did a resident’s feedback actually change something?
These outcomes are hard to measure and easy to miss. That’s because the best technology is felt, not seen.
Why Open Development Matters Here
We practice open development because invisible infrastructure shouldn’t be a black box. Every design decision, every tool we build, every process we follow is documented publicly. If a community in Detroit or Seoul wants to build a resource hub, they can study how we did it and adapt the approach to their context.
Open development also keeps us honest. When anyone can see the process - the decisions, the tradeoffs, the reasoning - there’s no room for hidden agendas, dark patterns, or features that serve the organization at the expense of the community.
The Trap
The trap for community tech organizations is the same trap that catches everyone: making the tool the point. Building a beautiful dashboard when a spreadsheet would do. Adding features because they’re impressive, not because anyone asked. Measuring success by platform metrics instead of community outcomes.
We fall into this trap sometimes. When we do, we go back to the question: is this making the organization more visible, or less? If the answer is more, we’re probably building the wrong thing.
What’s Left
When the technology works, what’s left is the community. People helping people, unmediated by software. The volunteer who shows up because the matching system connected them with the right opportunity. The business owner who got their permits because the translation was accurate. The family who found housing assistance because the hub had the right listing.
The organization disappears. The community remains. That’s the goal.