Question Zero

On the one question your team keeps skipping, because answering it means disagreeing.

The claim was denied at 2:14am on Tuesday, with nobody in the building. A software agent read the file, weighed it against the policy, and closed it. The letter went out under a caseworker's name, because the agent's authority resolved to her account. That was the fastest way to give it standing, back when someone set it up. So the letter that reached the claimant carried her name at the bottom, and the claimant had never heard of the machine that wrote it.

The claimant was a man whose physical therapy had been approved for eight weeks and cut off at six. He would spend a while not knowing why. He would call, and wait, and be told someone would review it.

By the time a human actually read that letter, the same agent had made nine hundred more decisions like it. Some of them right. Some of them the same mistake, repeated at a speed no reviewer works at. That is the cost, and those are the people who eat it: a claimant denied faster than anyone can check, and a caseworker holding a decision she never made, on a letter that carries her name.

The essay walks back to the room where it was decided — four people, a demo everyone liked, and the one question nobody asked: what are we trying to do here. It follows that question through the arch and the keystone, the order after Question Zero, and why a runaway is a design a person can decline.

Continue reading Question Zero on Medium →

The link above is a friend link — no Medium membership required.