Who Do You Call When the System Says No?

A few years into my career, a colleague came to my desk holding a printout. Her leave request had been declined, and the letter explaining why was two sentences long and said almost nothing. She wanted to know who had made the decision. I did not have a satisfying answer. The request had gone through a scheduling tool the company had bought from a vendor the year before, a tool that balanced staffing coverage against a dozen variables nobody in our department had ever fully seen. I could tell her the decision existed. I could not really tell her why.

That was an early, mild version of a problem that has only gotten larger since. Companies do not build most of the systems that now shape an employee’s working life. They buy them. A vendor sells a platform that screens résumés, or schedules shifts, or scores performance, or flags a claim for review, and the company signs a contract, rolls it out, and puts its own name on the outcome. The employee never meets the vendor. The employee meets me, or someone like me, standing at the front desk of a decision I did not build and often cannot fully explain.

I want to be fair to the tools themselves. Some of them do the job better than what came before. A consistent set of criteria, applied evenly, can be a genuine improvement over a manager working from instinct and a bad night’s sleep. I have seen automated systems catch things a tired, distracted human would have missed. That is a real advantage, and I do not think the honest answer to any of this is to throw the tools out.

But an advantage in the aggregate is a strange comfort to offer one specific person standing in front of your desk, asking why the answer was no. In my experience, that hand is almost never the vendor’s. It is mine, or it is whoever the company decided should be the human face of a decision made somewhere else, by people the employee will never meet and the company itself may not fully understand either.

This is the part of the job that keeps me up at night as much as the layoffs do, and I say that as someone who has done more than her share of those too. A layoff conversation is brutal, but at least everyone in the room usually agrees on what happened and why. The automated denial is different. It carries an unsettling kind of doubt into the room with it, a small, persistent question that neither side can fully answer: was this actually the right call, or just the call the system happened to produce.

I do not think most companies set out to create this gap on purpose. Buying a tool feels like buying a printer. You expect it to do the job it was sold to do, and you move on to the next problem. What gets lost in that transaction is the plain fact that the responsibility never actually left the building. The vendor wrote the code. The company still owns what happens to the person standing at the desk, whether or not anyone inside the company fully understands the decision they are now responsible for defending.

If there is a lesson from twenty years of standing at that particular desk, it is a modest one. Before any of these tools go anywhere near a person’s job, someone inside the company needs to be able to explain, in plain language, what the tool actually did and why. Not the marketing explanation. Not the vendor’s summary slide. An answer good enough to say out loud to the person it affected, and mean it.

That sounds like a small thing to ask for. In my experience, it is one of the hardest things a company can actually deliver, and the gap between how easy it sounds and how hard it is turns out to matter more than almost anything else in the room.