The Triumph of Paper vs. The Reality of Loss

We are currently celebrating a 29 percent increase in throughput. The floor manager, a man who wears suits that cost more than my first 19 cars combined, just walked by and gave a thumbs-up. He is ecstatic. He sees the green bars on the wall-mounted screens and thinks we are winning. The average handle time has dropped to exactly 2:59 minutes. On paper, this is a triumph. In reality, it is a massacre. I watched a recording of a call earlier today where the agent literally spoke over a crying woman to ensure he could hit the ‘end call’ button before the 3-minute mark. He met his metric. He kept his job. He also left a human being in 19 times more distress than when she started. This is the world we have built: a cathedral of data where the gods are KPIs and the sacrifice is the customer’s sanity.

The Ghost of Goodhart

It is a peculiar kind of madness, the sort that requires you to ignore the evidence of your own eyes in favor of an Excel spreadsheet. I’ve spent 99 percent of my career trying to optimize these flows, only to realize that the more efficient we become, the less effective we are. We manage the metrics, but the people-both the ones answering the phones and the ones calling in-have become inconveniences to the data.

The Philosophy of Ineffective Optimization

I find myself thinking about the philosophy of responsible systems. It is easy to game a number. It is much harder to look at a user and ensure they are actually safe, or heard, or respected. This is particularly visible in industries that deal with high stakes and high emotion. You see it in healthcare, you see it in finance, and you see it in the way platforms like ufadaddy have to balance the raw mechanics of engagement with the actual well-being of the player. If you only optimize for ‘time spent on site,’ you might end up destroying the very person you are trying to serve. Responsibility isn’t a metric that you can easily track on a 9-cell grid. It is a qualitative state, a sense of fairness that doesn’t always fit into a column.

Last week, I tried to explain this to the Vice President of Operations. I told him that our ‘first-call resolution’ rate was only high because agents were marking tickets as ‘resolved’ the moment they sent a templated response, regardless of whether the customer actually replied. I showed him 299 examples of unresolved issues that were coded as successes. He looked at me, then looked at his bonus structure, and then asked if I could find a way to make the 299 look more like 19.

The Perpetual Dance of Staffing

The Tuesday Spike Pattern

There is a specific kind of exhaustion that comes from being a ‘specialist’ in a field that feels increasingly like a shell game. My role as Ruby M.K. involves a lot of staring at traffic patterns. I see the 499-person spike at 10:00 AM every Tuesday. I see the way agents start to ‘ghost’ calls toward the end of their shifts when their energy is at 19 percent. I’ve tried to suggest that we increase the staffing by 19 people during the peak, but I’m told the ‘cost-per-contact’ metric wouldn’t allow for it. So, we continue the dance. We squeeze the agents, who squeeze the customers, who eventually just leave. And when they leave? We don’t even count that as a failure. We count it as a reduction in queue volume. We have managed to turn a mass exodus into a positive KPI.

The Game of Hot Potato

I remember my first week in queue management. I was 29, full of ideas about ‘Lean’ methodology and ‘Six Sigma’ precision. I thought I was solving a puzzle. I didn’t realize the puzzle was designed to be unsolvable. The goal of the modern corporation isn’t to solve the problem; it’s to manage the perception of the problem until the current leadership team can vest their shares and move on to the next victim. It’s a game of hot potato played with human souls. I’ve become an expert at the potato toss. My hands are burned, but my metrics are impeccable.

Quantifying Happiness

I laughed. It wasn’t a mean laugh, just a tired one. I told him that happiness is too hard to quantify, and if you can’t quantify it, you can’t optimize it. He looked disappointed. He’s only 29, still thinks the world is made of wax that he can mold. I wanted to tell him that the world is made of cold, hard numbers that end in 9, and the only thing we mold is the narrative we tell our bosses to avoid getting fired. But I didn’t. I just told him to go back to his 19 spreadsheets and find a way to reduce the wait time for the Tier 2 queue.

The Muted Alarms

We are losing the thread of why we started doing any of this. The metrics were supposed to be the instruments we used to navigate the ship, but we’ve become so obsessed with the dials that we’ve forgotten to look out the window. We are sailing straight into an iceberg, but we are very proud of how fuel-efficient our collision course is. The engine is running at a perfect 99 percent capacity. The hull is vibrating with the sound of 199 alarms that we’ve muted because they were ‘distracting from the core objectives.’

I don’t think I’ll ever find that here. My dashboard just turned yellow. The queue is up to 189. I have 19 seconds to decide if I’m going to adjust the routing or if I’m going to go check the fridge one more time.

I chose the fridge. There’s still nothing in it.

(But for those 9 seconds, the numbers didn’t blink.)

[the dashboard is a lie we all agreed to believe]

[the measure is not the truth]