The Nature of Escalation

The air in the fourth-floor conference room feels like it has been recycled 51 times, heavy with the scent of lukewarm coffee and the collective breath of eleven people who would rather be literally anywhere else. On the screen, Ticket 101 glows with a peculiar, mocking luminescence. It has been sitting in the backlog for 41 days. For 41 days, the engineers knew the API was leaking data like a sieve in a rainstorm, but the risk assessment remained ‘Moderate’ because, technically, it only affected 11 users in a specific demographic. Or so the spreadsheet claimed. I’m staring at the flickering fluorescent light overhead, my stomach performing a rhythmic protest because I decided to start a diet at 4:01 pm today-a decision that feels increasingly like a personal betrayal as the meeting enters its second hour.

We pretend that escalation is a safety mechanism, a structured path for moving problems from those who find them to those who can fix them. It isn’t. In reality, escalation is just delayed honesty. It is the art of holding onto a truth until it becomes so heavy, so dangerously expensive, that you have no choice but to drop it on someone else’s desk. We treat it like a release valve when it is actually a dam. We build these complex hierarchies not to solve problems, but to buffer the discomfort of reporting them. If you tell your manager the truth today, you have to deal with their reaction today. If you wait until the system crashes and an executive screams, you aren’t reporting a failure; you are merely witnessing an event.

Sarah L.-A., a court sketch artist I met during a particularly grueling 11-day litigation period, once told me that you can see a lie in the shoulders before you see it in the eyes. She spent her days capturing the micro-gestures of people who were pretending to be surprised by things they had known for years. She’d sketch the precise moment a defendant’s posture would sag by 11 millimeters-the exact moment the cost of the lie finally outweighed the benefit of the silence. I think of Sarah L.-A. now as I watch our VP of Product lean forward. He has just been told that the bug in Ticket 101 didn’t just affect eleven people; it actually compromised 1001 accounts because of a cascading permissions error.

He is performing surprise. It’s a beautiful, curated performance. He widens his eyes, puts down his pen, and asks, ‘Why am I just hearing about this now?’ The room goes silent. This is the ritual. We all know why. We told the middle managers 21 days ago. They told the directors 11 days ago. But because the ‘Status’ was marked as ‘Investigating’ instead of ‘Critical,’ the information was allowed to ferment in the dark. Nobody wanted to be the one to break the silence because, in this office, the messenger isn’t just shot-they’re usually assigned 21 extra hours of documentation as punishment for ‘unnecessary alarmism.’

The silence is the most expensive part of the process.

The Diet of Reality

I find myself wondering if I should eat the granola bar in my bag. It’s 4:21 pm. My diet is approximately 20 minutes old, and I am already reconsidering my life choices. This is exactly how organizations work. We make a plan-a diet, a sprint, a five-year strategy-and we stick to the script long after the reality has diverged. We wait until the hunger is unbearable or the bug is a headline before we admit the original plan was a fantasy.

Escalation shouldn’t be a dirty word, yet we’ve turned it into a weapon. We use it to threaten people (‘Don’t make me escalate this’) or as a way to abdicate responsibility (‘I’ve escalated this, so it’s no longer my problem’). This creates a culture of passive observers. We become like those people on a subway platform who watch a trash fire start and wait for someone in a uniform to show up before they move their feet. We’ve professionalized the act of looking the other way.

This is why I’ve grown to appreciate systems that don’t allow for this kind of buffering. When you look at platforms like tded555, there is an inherent drive toward responsiveness that most corporate structures lack. In a high-stakes environment, the distance between ‘finding a problem’ and ‘surfacing a problem’ has to be near zero. If it isn’t, the friction consumes the solution. In most companies, that friction is measured in weeks and thousands of dollars. We spend $501 an hour on consultant meetings to discuss why a $1 problem wasn’t fixed when it was first noticed.

Maximum Escalation

I remember a time I worked on a project where we had 31 different ‘Red’ flags on the dashboard. Because everything was red, nothing was red. We had successfully escalated everything, which meant we had successfully ignored everything. The VP would walk past the monitors, see the crimson glow, and just nod, as if it were ambient lighting. We had reached a state of ‘Maximum Escalation,’ where the honesty was so loud it became white noise.

Sarah L.-A. would have had a field day with that office. She would have sketched the engineers with their heads down, their spines curved into 21-degree arcs of resignation. She would have caught the way the project manager bit her lip every time the word ‘milestone’ was mentioned. There is a specific kind of physical toll that comes from knowing a disaster is coming and being told to wait for the ‘proper channels’ to acknowledge it. It’s the same feeling I have right now, knowing I have 11 more hours before I can reasonably eat a bagel.

We prioritize status over substance. If a junior dev finds a flaw, it’s a ‘discussion point.’ If a client with a $10001-a-month contract finds it, it’s a ‘War Room’ emergency. This teaches the organization that the validity of a problem is determined by the title of the person complaining about it. It’s a toxic feedback loop. It tells your best people that their expertise is secondary to the political climate. Eventually, those people stop reporting problems. They start looking for jobs where the truth doesn’t have to wait for a clearance level.

I once miscalculated a budget by $101. It was a small error, a rounding mistake in a spreadsheet that had 101 columns. I noticed it almost immediately. But the culture of that specific company was so punishing regarding ‘attention to detail’ that I spent 11 hours trying to figure out how to hide it rather than 1 minute fixing it. I escalated the problem to myself, debated the merits of honesty, and eventually realized that the anxiety of the secret was costing me more than the mistake ever would. When I finally told my boss, he laughed and said, ‘I saw that three days ago, I was wondering when you’d bring it up.’

That was a rare moment of grace, but it highlights the absurdity. We are all adults, supposedly working toward a common goal, yet we play these games of hide-and-seek with the truth. We treat our superiors like fickle gods who must be appeased with ‘Green’ status reports, lest they strike us down with a performance review.

Truth is the only thing that scales without breaking.

The Andon Cord and Trust

If we want to fix the escalation path, we have to stop treating it as a path at all. It should be a net. It should be possible for anyone, at any level, to pull the cord and stop the assembly line. The ‘Andon cord’ in Toyota factories is the classic example, yet we struggle to implement it in the digital world. Why? Because the digital world is built on the illusion of perfection. You can’t see the smoke from a failing server like you can see smoke from a failing engine. You have to trust the person who tells you they smell something burning.

And we don’t trust. We verify, we audit, we committee, and we postpone. We wait until the smoke is a fire, and the fire is a conflagration, and then we call a meeting to discuss the ‘Lessons Learned.’ I can tell you the lesson now, for free: stop lying to yourselves about the timeline.

My diet is now 41 minutes old. I am currently staring at a picture of a grilled cheese sandwich on my phone. My brain is telling me that I can start the diet tomorrow, or maybe at 5:01 pm. This is the internal version of the escalation ritual. I am negotiating with myself to postpone an uncomfortable reality-that I am hungry and I want carbs. If I were an organization, I’d be marking my hunger as ‘Under Review’ while secretly ordering a pizza.

Courage in the Face of Truth

We need to foster environments where the ‘uncomfortable truth’ is the highest currency. Where saying ‘This is broken’ is met with ‘Thank you’ instead of ‘Who let this happen?’ Sarah L.-A. once sketched a judge who looked directly at a witness and said, ‘The truth is the only thing that doesn’t require a good memory.’ I think the same applies to systems. A transparent system doesn’t require a complex escalation policy. It just requires the courage to look at the screen and see what’s actually there, rather than what we wish were there.

The VP finally stops his performance. He sighs, a long, 1-second exhale that signals he’s moving from ‘Shock’ to ‘Action.’ He assigns 11 people to a task force. He sets a deadline for 11 days from now. He feels like a leader. The engineers feel like they’ve been validated, but they also feel the weight of the 21-hour days ahead. And Ticket 101, which could have been fixed in 41 minutes if addressed a month ago, now becomes a 401-hour project. This is the price we pay for the ritual. We pay in time, we pay in morale, and we pay in the slow, grinding erosion of trust.

I’m going to eat that granola bar. The diet can wait until 5:01 pm. Some truths are just too immediate to ignore, and unlike the corporate world, my stomach doesn’t need to file a report to let me know there’s a crisis. It’s better to be honest about the failure now than to wait until I’m yelling at a coworker over a missing stapler. Let’s stop pretending the delay is a process. It’s just fear with a better vocabulary.