Quiet Exclusion

Most exclusion doesn’t announce itself.

It appears as:

• Forms that assume everyone has the same background knowledge.

• Office hours that require someone to miss work.

• Websites that only function on a desktop computer.

• Public notices written in language that large portions of the community can’t understand.

• Meetings held in locations that residents can’t access.

• Hiring processes that reward people who already know the unwritten rules.

These are often treated as inconveniences, but they are quiet exclusions, and they determine who can participate and who can’t.

Quiet exclusion isn’t necessarily discrimination, hostility, or even intent. It means a system or process was designed around assumptions that don’t apply to everyone expected to use it. Nobody explicitly says, “You don’t belong here,” but the impact is the same. It’s privilege manifested as process, and it makes participation harder.

Public systems exist to serve the public. All of the public. But many government services assume residents already understand agency structures, jurisdictions, eligibility rules, required documentation, and administrative vocabulary.

People using these services may only encounter government occasionally. They’re not experts. They’re just trying to solve a problem. The result is that people with the greatest need often face the greatest barriers to access.

This isn’t unique to government. It exists in membership organizations, schools, healthcare systems, community groups, and nearly every workplace.

Meaningful participation becomes concentrated among people who already know how things work. If someone can’t access a service, understand a process, navigate a form, attend a meeting, or obtain information they need, the system has excluded them.

One of the most important lessons I learned in government is that people encounter our systems while living their lives. They’re working multiple jobs, caring for children, navigating disabilities and language barriers, and trying to solve problems they may have never faced before.

Designing systems that work only for people who already understand them is exclusion. Period.

Before asking why people aren't participating, applying, attending, responding, or engaging, it's worth asking a different question: what assumptions does the system require people to understand before they can succeed?

Identifying those barriers isn’t just a matter of convenience or customer service; it’s a matter of dignity.