Fixing What Isn’t Broken for Us

“I missed the housing deadline because I didn’t know a bench warrant had been issued. Probation never told me the paperwork didn’t go through.”

The Interface Is the Policy

Walk into any public service office or government website and you will hear it:

“It’s just the way the system works.”

Systems do not simply work. They are designed.

When they work for some and consistently fail others, that is not failure. It is intent.

The myth of neutrality frames inaccessible forms, brittle portals, and biased logic as technical oversights. In practice, many of these systems perform exactly as intended for those they were built around.

Everyone else becomes an exception.

Or collateral.

The Default User

In commercial design, teams define target users.

In public systems, the default user is rarely named, yet always present.

White.
Literate.
Housed.
Able-bodied.
Cisgender.
Documented.

This is the silhouette the system anticipates.

Everyone else is required to adapt.

An interface that cannot be used with assistive technology is not inconvenient. It removes people.

A housing portal that requires a permanent address to apply does not contradict itself. It excludes.

Design does not simply reflect culture.

It enforces it.

Neutrality as a Shield

Neutrality is often used to avoid accountability.

Teams point to compliance requirements, legacy infrastructure, or limited budgets as immovable constraints. Behind each of those constraints are decisions about whose experience matters.

Consider:

• A form that allows only binary gender selection
• A phone system that times out after minutes of inactivity
• A filing system that requires outdated software

None of these are neutral.

They center one group and require everyone else to absorb the cost.

This is not oversight.

It is exclusion expressed through interface.

“Works for Me” Is Not a Metric

I have been in rooms where teams review a public system and conclude:

“It seems straightforward.”

It does, if your access, literacy, time, and stability align with the assumptions embedded in the design.

For others, “straightforward” becomes a maze with no map and a clock running against them.

“It works for me” is not validation.

It is a signal that the system has not been tested against reality.

Designing Without a Default

Serving the public requires rejecting the idea of a default user.

Design must begin at the margins.

In practice, this means:

• Co-designing with directly impacted communities
• Auditing systems continuously for bias
• Treating multilingual, mobile-first, and trauma-informed design as baseline
• Defining digital equity as a measurable outcome

Public interfaces are not a convenience layer.

They are access to rights.

Toward a Civic Design Ethic

Design determines who moves forward and who waits.

It shapes expectations about what people can ask for and what they believe they deserve.

A system that works for a narrow slice of users is not broken.

It is operating as designed.

The task is not to fix what works for us.

The task is to build what works for everyone.