An Invitation
The Ktown Team wiki has an article called Read Everything. It’s exactly what it sounds like - a guided reading path through 130 articles, organized in a sequence that builds on itself. Start with who we are. Move to how we think. Then how we’re organized, how money works, what we’re building, and where we’re headed.
Most organizations would never publish something like this. The internal documentation stays internal. The org chart stays in a slide deck. The financial processes stay in a board packet. The thinking behind decisions stays in the heads of the people who made them.
We published all of it because we think the people affected by an organization’s decisions should be able to understand how those decisions get made.
Why 130 Articles
The wiki has 186 articles total. The Read Everything path covers the 130 that tell the complete story. The remaining 56 are reference material - individual platform tool pages, team descriptions, and detailed legal documents. Useful when you need them, but not meant to be read front to back.
The 130 articles on the path are organized into 15 parts:
- Who We Are - the basics
- How We Think - the frameworks behind decisions
- How We’re Organized - every role and how they connect
- Getting Involved - how to participate
- Programs - structured ways to contribute
- Working With Us - culture, expectations, growth
- Initiatives - where we focus community energy
- Teams - how work gets done
- Advocacy and Policy - how we engage with civic systems
- Technology - what we’re building and why
- Research and Data - how we gather and use information
- Community Impact - how we measure what matters
- Money - how finances work
- Looking Outward - the model beyond Koreatown
- Legal - the legal foundation
Nobody has to read all of it. But anyone can.
The Participation Problem
Here’s the pattern most community organizations follow: they invite residents to participate, then make participation dependent on information that isn’t publicly available. Come to the meeting, but don’t expect to understand the budget. Vote on the proposal, but don’t ask how it was developed. Volunteer your time, but don’t ask why things are done this way.
The result is participation that stays shallow. People show up, but they can’t meaningfully engage because they don’t have the context. The decisions that shape the organization remain in the hands of the people with access to internal information.
The Read Everything path is designed to solve that. If you’re going to vote on a budget, you should be able to read the budget process. If you’re going to join a team, you should know how teams work. If you’re going to evaluate whether the organization is doing what it says, you should be able to read what it says.
Informed Disagreement
One thing we expect from publishing this much is disagreement. Someone will read the governance structure and think it’s wrong. Someone will read the flat hierarchy model and be skeptical. Someone will look at the financial strategy and see a gap.
That’s the point. Informed disagreement is more valuable than uninformed agreement. When someone challenges a decision with reference to the documented reasoning, the conversation starts at a higher level. Instead of “I don’t like this,” it becomes “I read why you chose this, and here’s why I think a different approach would work better.”
That kind of feedback makes the organization stronger. But it’s only possible when the information is accessible.
The Ongoing Commitment
The wiki will change. Articles will be revised as the organization learns what works in practice. New articles will be added as new questions arise. Some sections will be rewritten entirely.
The commitment isn’t to perfection. It’s to access. Whatever the organization knows, the community should be able to know too. Read Everything is the starting point for that.