FIELD NOTE |
March 5, 2026
The System Was Designed for Someone
Every system has a default user, even when nobody consciously chose one. The people who do not fit that default are often the first to reveal the design.
Years ago, while working with a housing organization, I encountered a pattern that didn't make sense at first.
The average person on the waitlist had been waiting for years, yet much of the available housing was going to people who had entered the process far more recently.
The eligibility rules were being followed. Applicants were moving through an established process. From the perspective of the individual transactions, the system appeared to be functioning.
But the outcomes raised a different question.
Who was actually able to move through the process?
Applicants who already had the expected documents, understood the institutional language, could navigate the online requirements, and responded quickly were easier to move forward.
People who needed translation, had nontraditional documentation, or required additional help faced a more complicated path.
They might be just as eligible for housing. But eligibility and the ability to navigate the eligibility process weren't the same thing.
No one needed to write a rule saying that applicants with more resources or institutional familiarity should have an advantage. The design of the process could create that advantage without anyone explicitly intending it.
That experience eventually shaped software I built to reduce the burden the process itself was creating.
More importantly, it changed where I look for bias.
The default path is not neutral
Every system has a person for whom it works especially well.
Usually, we don't identify that person. They simply have the right documents, understand the language, know which questions to ask, can use the technology, and have enough time to complete the steps in the expected order.
When that person moves through the system, the process feels straightforward.
When someone else enters, we discover how many assumptions were embedded in the design.
I find exception paths particularly interesting for this reason.
They reveal the boundaries of what the system was built to accommodate.
What happens when someone can't produce the expected documentation? When they communicate differently? When their family, work history, body, finances, or circumstances don't fit the available categories?
Does the system contain another way forward?
Or does the person have to find someone willing to improvise one?
Sometimes an exception is genuinely unusual. No system can anticipate every circumstance, and attempting to do so can create complexity that makes the system harder for everyone to use.
But sometimes the exception is only unusual relative to the assumptions of the people who designed the process.
If a substantial portion of the people a system is intended to serve cannot navigate its default path, I don't think we can reasonably treat all of those people as exceptions.
At some point, the pattern tells us something about the design.
A system that works only when people conform to its assumptions hasn't eliminated complexity.
It has transferred complexity to the people who don't fit.
Accommodation can preserve the burden
I think about this in my own life, too.
The concept of legally mandated accommodations forced me to reckon with the possibility that I hadn't been operating on a level playing field.
It took years to accept that I could need an accommodation even when I was capable of forcing myself through the default.
That distinction mattered.
I had spent a long time treating my ability to accomplish something as evidence that the conditions were workable.
If I could get through it, perhaps the problem wasn't really a problem.
But the ability to accomplish something doesn't tell us what it costs to accomplish it.
And it certainly doesn't establish that everyone should have to pay the same cost.
Organizations can offer accommodations and still place most of the responsibility for accessing them on the person who needs them.
The person has to know the accommodation exists. Understand the process for requesting it. Explain why it's necessary. Sometimes disclose personal information. Wait for approval. Navigate other people's interpretations of whether the request is reasonable.
The accommodation may be available, but accessing it becomes additional work.
I don't think that makes accommodations unimportant. They can be essential, and individual needs will always vary.
But the existence of an alternate path doesn't tell us whether a system is accessible.
We also have to look at the cost of using it.
How many additional steps are required? How long does it take? Who has to ask? Who gets to decide? What happens if the person doesn't know that another path exists?
And how much of that work could have been avoided by designing the default differently?
The same question applies to the housing process.
Providing additional assistance matters. But if applicants who need assistance must navigate a slower, more complicated process to receive the same consideration, the assistance may not fully address the disadvantage created by the original design.
The question isn't simply whether another path exists.
It's whether people can realistically use it.
Design shapes who appears capable
One of the things that interests me most about systems is how readily we attribute their outcomes to the people moving through them.
Someone who completes an application quickly appears prepared.
Someone with the expected documentation appears organized.
Someone who understands the institution's language appears competent.
Someone who needs more time, clarification, or assistance may appear less prepared, less responsive, or more difficult to serve.
Sometimes those judgments reflect meaningful differences in people's circumstances or behavior.
But sometimes they reflect how closely someone matches the system's assumptions.
The person who fits the default spends less capacity navigating the process itself.
The person who doesn't fit has to accomplish the original task while also figuring out how to make the system work for them.
And then we may evaluate both people as though they encountered the same conditions.
I don't think this is limited to public services or accessibility.
We do it in hiring, education, healthcare, customer experiences, and organizations.
We define what a successful participant looks like, often through seemingly practical decisions about timing, documentation, communication, technology, and sequence.
Then we observe who succeeds.
It's tempting to interpret that success as evidence that the people who moved through the system were simply more capable.
But before reaching that conclusion, I want to understand what the system made easy for them.
And what it made difficult for everyone else.
This doesn't mean every difference in outcome is evidence of bias. Nor does it mean a system should have no standards or requirements.
Standards can be necessary. Eligibility can matter. Some information really is required to make a responsible decision.
The question is whether the requirement serves the underlying purpose or merely reflects the way we've become accustomed to doing the work.
Does the system need a particular piece of information, or does it need that information presented in one familiar format?
Does someone need to demonstrate a capability, or do they need to demonstrate it through a particular communication style?
Does an applicant need to meet an eligibility requirement, or do they need to be unusually skilled at navigating the process designed to verify it?
Those are different questions.
And the differences can have real consequences.
I keep coming back to the people on that housing waitlist.
The average wait had stretched into years, while some applicants were moving through much more quickly.
I don't know that every difference in wait time could be explained by the design of the process. Housing allocation involves eligibility, availability, priorities, and constraints that don't disappear because we make an application easier to complete.
But the pattern was enough to make me question what we were actually measuring when we described someone as ready to move forward.
Were we measuring their eligibility and need?
Or were we also measuring their ability to navigate the institution?
Those are not necessarily the same thing.
And when the system is responsible for distributing something as consequential as housing, the distinction matters.
I don't expect systems to anticipate every person or every circumstance.
But I do think we have a responsibility to notice when the same kinds of people repeatedly encounter the same barriers.
Especially when those barriers are produced by choices we have the ability to change.
The easiest path through a system tells us something about whom the system expected.
The harder question is what the system does when someone else arrives.