The Problem With Knowing
Most organizations run on knowledge that lives in people’s heads. The executive director knows why a policy was written that way. The longtime volunteer knows which city office to call. The board member remembers why they chose one vendor over another.
When those people leave, the knowledge leaves with them. The next person starts from scratch, makes the same mistakes, and reinvents solutions that already existed. This happens in every organization, and most accept it as normal.
We don’t think it should be normal.
What the Wiki Is
The Ktown Team wiki is a public knowledge base with 186 articles across 16 collections. It documents how the organization is designed to work - from governance and financial processes to team structure and platform tools.
Every collection serves a purpose:
- About Ktown Team - who we are, what we believe, how decisions get made
- Fundamentals - the thinking frameworks behind our work
- Community Structure - every role and how they connect
- Working With Us - what it’s like to be part of the team
- Legal - all policies, in full, with a plain-language summary
- Financials - how money comes in, how it goes out, who decides
The wiki isn’t a brochure. It’s the organization’s operating manual, published for anyone to read.
Why Public
Most organizations keep their internal documentation private. There’s a logic to that - some information is sensitive, some is half-formed, some might be misunderstood without context.
We made a different choice. The wiki is public because transparency only works when the information is accessible before someone asks for it. If a resident wants to understand how Ktown Team makes budget decisions, they shouldn’t need to email someone and wait for a response. The budget process article is already there.
This also keeps us honest. When anyone can read how we say we operate, we have to actually operate that way. Published commitments are harder to quietly abandon than internal memos.
Why Now
The wiki exists before Ktown Team has launched programs, hired staff, or opened its doors. That’s deliberate.
Building the documentation during the founding stage means the organization starts with shared knowledge from day one. The first volunteer doesn’t have to guess how things work. The first team lead can read the onboarding process before their first day. The first community member who questions a decision can point to the governance framework and ask whether it was followed.
Starting with documentation also forces clarity. You can’t write down how something works until you’ve decided how it works. The act of documenting is the act of designing.
What It’s Not
The wiki is not finished. 186 articles describe the blueprint, not the lived reality. Some of what’s documented will change when it meets real conditions. Teams will adapt. Processes will evolve. Policies will be revised.
That’s expected. The wiki is a living document, not a constitution. The commitment isn’t to getting it right the first time. It’s to keeping the documentation current so the organization’s memory doesn’t depend on any single person.
The Standard
The standard we’re setting is simple: if it matters, write it down. If it’s written down, make it findable. If it’s findable, keep it current.
Institutional knowledge shouldn’t be a privilege of tenure. It should be infrastructure - available to everyone, maintained by everyone, owned by the community it serves.
That’s what the wiki is for.