Becoming the Edge Case

I spent much of my career designing systems meant to catch people when something went wrong. I understood failure modes intellectually. I had mapped them, prioritized them, deferred them.

Then I became one.

What changed was not the mechanics of the system. It behaved exactly as designed. What changed was my position inside it.

Processes I once defended revealed their sharp edges. Timelines that felt reasonable from the inside became destabilizing from the outside. Requirements that once read as neutral exposed their hidden assumptions.

The system did not break. It worked. That was the problem.

Each interaction carried an unspoken premise: if something had gone wrong, it must be correctable through persistence. Try again. Submit another form. Wait for the next review cycle.

Those instructions assume a surplus of time, energy, and stability. When those are absent, process becomes pressure.

I learned how quickly context disappears once a person is reduced to a case. Nuance gave way to eligibility. Explanation gave way to policy. The system optimized for throughput, not understanding.

There was no single failure to point to. No appealable moment. Just accumulation.

That experience changed how I think about risk. I no longer evaluate it only by likelihood or scale. I evaluate it by reversibility.

A system that cannot absorb human variance without cascading harm is not resilient. It is brittle, even if it performs well on paper.

Designers often believe they understand this. Living it teaches something sharper.

When you are inside the system, you feel every assumption. You feel how quickly support becomes suspicion. You feel how silence functions as a decision.

I do not believe systems should be built around worst-case users. I believe they should be built to withstand ordinary fragility.

The difference is subtle, but consequential.

Since then, I design differently. I look for places where the system demands more than a person can reliably give. I question defaults that assume endless advocacy. I push for escape hatches that do not require escalation.

Not because it is elegant. Because one day, the system will not see you as the designer.

It will see you as the edge case.