The Problem Was Never the Chair

On May 26, the Equal Employment Opportunity Commission (EEOC) announced it was suing Buc-ee’s, a regional gas station/convenience store chain, for disability discrimination.

This is a story about what happens when an organization becomes so committed to consistency that it loses the ability to exercise judgment.

According to the EEOC’s complaint, a cashier at Buc-ee’s Bastrop, Texas location was diagnosed with myasthenia gravis, a chronic neuromuscular condition. His physician restricted him from standing continuously for extended periods. He requested a reasonable accommodation: a chair at his workstation.

The company, as alleged, said no.

Eventually he was unable to return to work under those conditions and was terminated. In May 2026, the EEOC filed suit.

The accommodation at the center of the case was a chair. That detail matters because it forces a question. What exactly was being protected?

The employee was apparently capable of performing the core functions of the job. He could handle transactions, serve customers, represent the brand. The issue was not whether he could work. The issue was whether he could work while seated.

The EEOC’s announcement included a phrase worth pausing on. Acting Dallas Regional Attorney Ronald L. Phillips said employers often run into problems because of “inflexible thinking.”

That may be the most important phrase in the entire case. Inflexible thinking is not a policy problem. It is a systems problem.

One of the central arguments in The Inside Advantage is that strong systems and rigid systems are not the same thing. Strong systems create consistency around outcomes. Rigid systems create consistency around rules. At first glance they look identical. Both rely on standards, procedures, and accountability.

The difference appears when reality refuses to fit neatly inside the process.

Strong systems ask whether the rule is still serving the goal. Rigid systems ask whether the rule was followed.

That distinction matters because every organization eventually encounters situations that require judgment. A customer issue. A market shift. A safety concern. A health condition. Something that falls outside the normal operating pattern. When that happens, the organization’s real design reveals itself.

Do your managers have authority to think? Or are they simply responsible for enforcing the script?

Buc-ee’s is widely recognized for operational excellence. The stores are clean, the customer experience is consistent, and the brand has become one of the most successful retail concepts in the country. Those achievements are real.

But operational excellence contains a hidden danger. The more successful a system becomes, the easier it is to confuse consistency with correctness. “Everyone does it this way” becomes the operating principle, and eventually the process stops serving the mission and starts serving itself.

The issue was never the chair. The issue was whether anyone inside the system was empowered to ask a simple question: can this employee successfully perform the job if we make a minor adjustment?

If the answer was yes, the cost of accommodation was trivial. If the answer was no, the company needed to explain why. Instead, the dispute escalated until a federal agency became involved.

That progression should concern leaders far beyond disability compliance. Most organizational failures begin exactly this way. Not with bad intentions, not with dramatic misconduct, but with a small decision that nobody feels authorized to challenge. A rule survives one exception request, then another, then another. Over time the organization loses the habit of asking whether the rule still makes sense.

The result is what I describe as brittle infrastructure. Brittle systems look strong right up until they encounter a circumstance they weren’t designed to handle. Then they break. If your system does not consider the possibility of an event occurring, it’s susceptible to that event.

There are plenty of lessons here. The lesson I’d like to focus on is not that employers need better ADA training, though training matters and is good policy. The lesson is that every operating system needs a release valve. Someone empowered to say: the standard is standing, the objective is serving customers, this employee can serve customers seated.

Strong systems make room for that judgment. Rigid systems don’t.

One employee asked for a chair. The organization defended a rule. Now a federal lawsuit will determine whether protecting that rule was worth the cost.