When systems reward escalation, people learn to chase the override. At protocol scale, the better question is how a rule changes in the open.
The customer-service desk is almost closed.
This is past “late in the day.” The drawer is half-counted. The returns bin is full. Everyone in a vest has started moving like they can survive the rest of the shift if nothing new happens. The lights feel louder. The floor has the remnants of the last pass made by the broom hours ago. The person behind the counter is already halfway out of their own body.
Then she steps up.
Coupon in one hand. Receipt in the other. A whole case is already built in her head.
The register says no.
That should be the end of it. A date was missed. A condition didn’t apply. The thing she thought she had in her hand wasn’t the thing the system recognized. Ordinary retail stupidity. The kind of small print nobody reads until it costs them three dollars and forty-nine cents.
But she isn’t arguing with small print anymore.
She’s arguing with the counter.
The cashier looks at the screen, then at the coupon, then back at the screen, because that’s all there is to look at. The register has already made its decision. The policy’s sitting there like weather. The person in front of her wants a different reality, and the only human-shaped object attached to the system is wearing a name tag.
So all of it lands on the cashier.
The coupon. The purchase. The disappointment. The policy. The insult of being told no by a machine and then having a person repeat it out loud.
A line starts forming behind her. Someone sighs too hard. Someone else pretends to study the carts full of returns. The cashier keeps their voice flat, because that’s the last move they have left.
They can explain the rule. They can’t make the rule care.
And once that becomes clear, there is only one move left:
Let me speak to your manager.
People don’t reach for that move by accident. They learn it one counter at a time.
A return gets rejected because the receipt is two days outside the window. A fee appears because an account crossed some invisible line at midnight. A flight change costs more than the ticket did. A form gets denied because one box was checked wrong six weeks ago.
At first, the answer is simple.
Sorry, that’s what the system says.
The person in front of you can explain it. They can apologize for it. They can point at the screen like the screen might help shield them from some of the blame.
But they can’t change it.
Then the manager appears.
And sometimes the whole room changes.
The screen has an override. The fee has a waiver code. The policy has an exception. The expired coupon can work this one time because everyone involved would rather end the scene than keep explaining why it shouldn’t.
The rule isn’t always the rule.
Sometimes it’s just the first obstacle between you and the person with enough authority to bend it. That can be true even when the demand is unreasonable and the person behind the counter is trapped in the middle.
If the system rewards the pressure, people remember where to push.
The manager who gives in isn’t always confused, either.
Sometimes they know the coupon has expired. They know the register is right. They know the cashier followed the policy. They know the whole thing makes less sense the longer it goes on.
But the line is growing. The desk is closing. The customer is getting louder. Everyone nearby is pretending they aren’t listening while absolutely listening.
The coupon has stopped mattering. The scene is the problem now. Finding the real problem would mean staying with the mess.
Maybe the coupon was badly written. Maybe the sign made a promise the fine print took back. Maybe the policy made sense in a meeting and turned into a trap at the counter. Maybe the cashier was never trained on the edge case. Maybe the customer read what she wanted to read.
Any one of those might be true. None of them can be sorted out with a line forming and the desk closing.
Giving in takes thirty seconds.
Override the screen. Comp the order. Refund the item. Make the scene stop.
That buys quiet. And once a system starts buying quietly, people notice.
For a second, it looks solved.
The coupon works. The refund goes through. The item gets comped. The customer leaves with the story she came for: she pushed hard enough and the system finally listened.
The line moves again. The cashier can breathe. The manager gets to feel practical. For a second, everyone gets what they wanted.
Then the same coupon stays in circulation. The same sign keeps hanging over the aisle. The same policy waits for the next person who reads it wrong, or reads it right and still gets trapped by it.
The register keeps doing exactly what it was built to do.
The confrontation ends, but nothing behind the counter has changed.
It can feel like mercy in the moment. It might even be the humane call for the cashier, the customer, and everyone waiting for the scene to end.
But it solves the pressure, not the cause.
The source is still sitting there.
Rewrite the coupon. Fix the sign. Train the cashier. Change the register. Admit the policy is bad.
An exception bends the rule for one moment.
Repair changes the conditions producing the moment.
At a checkout counter, the damage can stay contained.
A manager bends the rule. The store eats the cost. The cashier gets an annoying story. The customer learns whatever lesson the scene teaches. It’s messy, but it stays inside the room.
A protocol isn’t a room.
The rules touch everyone using the network. They define what the system accepts, what it rejects, what it preserves, what it upgrades, and what it refuses to do.
They aren’t a coupon code. Everyone is living under them. So if a protocol rule is wrong, unclear, outdated, or failing the network, the question can’t stay at: Who can bend this for me?
It has to become: How does this rule change?
People can still argue. They can still make cases. They can still apply pressure.
But at protocol scale, pressure can’t be the whole mechanism.
Tezos governance doesn’t make politics disappear. Incentives stay. Conflict stays. Bad outcomes still happen.
But it does give a protocol change somewhere formal to go.
It enters governance as a proposal. Delegates vote. The proposal moves through formal periods. If it clears the requirements, the protocol can adopt the upgrade itself.
The argument still exists. So does the pressure. The politics still hold their weight. But they have to enter the process.
It doesn’t settle every fight. If the rule needs to change, the answer isn’t supposed to be finding the right person above the counter.
Put the change where the network can see it.
The manager’s reflex is easy to understand.
People don’t invent it out of nowhere. A rule can sometimes be escaped by finding the person with the override, the waiver code, the discretion, or the patience to make the scene end.
Sometimes that works. That’s exactly why it spreads.
But when pressure becomes the path, people start chasing the override instead of the repair. They look for the person who can make an exception instead of the process that can change the rule. The scene becomes the mechanism.
People are still going to argue. And they should.
Rules fail. Policies age. Edge cases appear. Networks change. When that happens, pressure has to become more than a scene.
One path keeps looking for the person with the override.
The other puts the proposed change in the open, where it has to become more than pressure before the system can adopt it.
Let Me Speak to the Manager was originally published in Tezos Commons on Medium, where people are continuing the conversation by highlighting and responding to this story.