Why Reasonable Accommodation Is Too Late
*Opinions are mine, conclusions are yours. Take what resonates, leave what doesn't. Respectful disagreement always welcome unkindness never is.
There is a moment most people never witness. It happens long before any form gets filed, long before anyone in a position to help is made aware there is something to address. It is the moment a person realizes the environment they are in was not built with them in mind, and quietly begins figuring out how to survive it anyway.
They adapt. They find workarounds. They spend energy every single day navigating friction that nobody else in the room is paying. They do the math on whether to say something, weigh the risk of being seen differently against the cost of staying invisible, and usually choose invisible because the alternative has its own price. All of that happens before a single accommodation request is ever submitted. By the time the form exists, the cost has been running for a long time.
That is the part the system was never designed to see.
A Safety Net Is Not a Well-Designed System
Reasonable accommodation as a legal framework exists to ensure that when someone reaches the point of formal need, a minimum standard of response is available. That matters. For a lot of people it has been genuinely significant. But a safety net catches you after you fall. It does not prevent the fall, and it was never designed to.
The problem with building inclusion entirely around the accommodation request is that it places the entire burden of identification, documentation, and advocacy on the person already carrying the most friction. The system stays exactly as it is. Everyone else continues undisturbed. The person experiencing the gap is asked to formally name their own exclusion, prove it meets the threshold for a response, and wait while the process moves at whatever pace it moves.
Before a single form is ever filed, here is what has already been paid:
Cognitive energy spent building private workarounds for systems that never had margin for difference
Emotional labor spent calculating whether disclosure is safe, knowing it permanently changes how others see you
Time spent researching rights, preparing language, finding the words that will be taken seriously rather than explained away
The quiet weight of needing something different in a space that treats different as deficient
Relationships affected by advocating too visibly, and opportunities lost by not advocating enough
The ongoing, exhausting question of whether this environment is worth staying in at all
By the time the request is made, the person making it has often already decided whether they belong there. The formal ask is frequently a last resort. Not a first step.
What the Organization Is Actually Losing
For organizations treating accommodation as a compliance exercise, there is a different story underneath the numbers they are already tracking. Employees who are not adequately supported are not performing at their actual capacity. They are spending cognitive resources on adaptation and navigation that was supposed to go toward the work. The gap between a supported employee and an unsupported one is not a capability gap. It is a design gap. And it shows up in output whether or not anyone has traced it back to its source.
Attrition is expensive. Recruitment is expensive. The institutional knowledge that walks out the door when someone exhausted by friction finally leaves is expensive. None of that cost appears on the accommodation form. It appears months later in metrics that no one connects to the original design failure because no one thought to look there. The organizations that understand this are not waiting for requests. They are building environments where fewer people need to make them.
What Building It In Actually Looks Like
Proactive inclusion is not a complicated concept. It is the decision to build flexibility into the foundation before someone has to ask for it rather than in response to the asking. It does not require a legal trigger. It requires a different starting assumption about who is in the room.
In practice it looks like this:
Clear, literal communication as the default, not a special accommodation reserved for people who formally request it
Multiple pathways to complete a task so no single format becomes a barrier for the people it does not fit
Time structures that account for human variability rather than penalizing it
Feedback channels that do not require a person to perform their struggle in order to access support
Environments designed to reduce cognitive load rather than maximize sensory and administrative noise
Processes that do not begin from the assumption that the user is the problem
When the starting assumption shifts from most of our people are like us to our people are as varied as the human population actually is, the design changes. Not because a law requires it, because it is accurate.
The Request in Your Inbox Is Not the Beginning
If you are an organization, the accommodation request in your system is a signal that a problem has been present long enough that someone finally had the capacity to formally name it. The question worth sitting with is not how do we process this. It is how many people needed something and never asked. That number is larger than your data shows. The cost of that gap is already in your numbers somewhere. The dots just have not been connected yet.
Inclusion built into the foundation costs less than inclusion bolted on after someone had to bleed for it.