In 1892, a clerk named Elias Thorne worked for the Great Western Railway in a basement office near Paddington Station. His job was simple but vital: he had to log the maintenance schedules for freight cars onto thick, linen-paper ledgers. For three months, Elias made the same mistake. He would record the wheel-greasing dates for the coal cars in the column meant for the grain wagons.

His supervisor, a man with a stiff collar and a belief in the power of the lash, did not fire him. Instead, he made Elias stay late every night to copy the railway’s rulebook into a notebook. The supervisor saw the error as a lack of discipline. He believed that if Elias knew the rules well enough, the ink would find the right column.

Elias Thorne knew the rules. He could recite the 1888 Freight Act from memory. The problem was that the ledger lines were faint, and the basement was lit by a single, flickering gas jet that threw shadows across the page. The columns for coal and grain sat side-by-side, identical in width and unmarked at the bottom of the sheet where Elias worked. He did not need more training. He needed a better lamp and a ledger that didn’t look like a Rorschach test.

We are still living in that basement. Today, when a lender misapplies a fee to 312 accounts, the response is rarely to change the “lamp.” Instead, the risk committee asks for a remediation plan. This plan always looks the same: a new training module, a refreshed procedure note, and a signed statement from every member of the team saying they have read it.

1

The Mirage of the Mind

The first way we hide operational rot is by pretending that errors are a choice of the will. When a team member selects the wrong fee code from a dropdown menu, we act as if they forgot what a fee is. We assume they need a 20-minute slideshow on the “Importance of Accuracy.”

I once spent four years as a formulator for industrial sunscreens. In that world, if a batch of SPF 50 comes out as SPF 30, you do not pull the chemist into a room and explain the concept of sunburn. You check the scale. You check the agitator. You check the pump that moves the zinc oxide.

I spent my early career thinking that if I just explained the “why” of the formula well enough, the workers would never make a mistake. I was wrong. I was arrogant to think my words could override a sticky valve or a poorly labeled vat. No amount of “awareness” prevents a human from misreading a label that is covered in chemical dust. In finance, the “dust” is a cluttered user interface and a workflow that asks a human to act like a calculator.

2

The Speed of the Lie

Training is the fastest thing a manager can “do” to prove they are “doing something.” Fixing a broken configuration in your core system might take six months of talks with the IT team. It might require a budget shift or a change in the API architecture. But a training module? You can whip that up in a weekend.

By Monday morning, you have a report that shows 98% completion. You can take that report to the risk committee and say, “The risk has been mitigated.” The committee likes this because it is a clean number. It is a metric. But the risk has not moved an inch. The two fee codes-let’s call them 402 and 403-still sit right next to each other in the dropdown. They still look identical. The team is just more nervous now when they click them.

3

The Ledger in the Dark

When we rely on training, we ignore the environment where the work happens. If your staff is processing 50 equipment leases a day while toggling between seven different browser tabs, the error is not in their head; it is in the tabs.

Most equipment finance software aims to put all the data in one place, but if the configuration is bad, the data just becomes noise. If a worker has to look at a PDF of a contract and then type the data into a servicing screen, they will eventually hit the wrong key.

This is a law of nature. The gale is the system. The tightrope is the manual entry.

4

The Accumulation of Shadow Procedures

Every time you add a new “refresher” training, you add a layer of complexity to the job. Over five years, a team can end up with 40 or 50 “supplemental guides” that they are supposed to follow. These guides often contradict each other. One was written after the “Great Fee Error of 2021,” and another was written after the “Collections Crisis of 2023.”

The staff eventually stops reading them. They create their own “cheat sheets” which they tape to the side of their monitors. These cheat sheets are the real manuals of the company. The official training exists only for the auditors. This creates a dangerous gap between how the work is actually done and how the board thinks it is done. The more training you pile on, the deeper you bury the truth of the process.

5

The Evidence Trap

We have built a world where “evidence of action” is more important than “result of action.” If a bank fails an audit, the regulator wants to see the “training log.” They do not usually ask if the dropdown menu was fixed. Because the regulator accepts training as a valid fix, the bank keeps using it.

It is a closed loop of theater. The bank pretends to teach, the staff pretends to learn, and the regulator pretends to believe that the problem is solved. Meanwhile, the root cause-perhaps a piece of legacy code that can’t handle a mid-term contract change-stays in the system for a decade. It sits there like a landmine, waiting for a new hire who hasn’t seen the “refresher” slides yet.

6

The Erosion of Expertise

When you treat every error as a training issue, you insult your best people. Your experts know why the errors happen. They know that the system “glitches” when a customer moves from a finance lease to an operating lease. They have told the managers this for years.

“A promise is a tension. When a brand says limited 16 times, the thread loses its memory.”

– Sofia, thread tension calibrator

When the manager responds by making those experts sit through a “Basic Contract Administration” course, the experts check out. They stop reporting the bugs. They realize the company is not interested in fixing the machine; it just wants to blame the operator. This drives away the people who actually understand the portfolio. You are left with a team of people who are very good at clicking “Next” on a training deck but have no idea how to handle a complex restructuring.

7

The False God of Human Error

“Human error” is a term used by people who don’t want to look at the blueprint. If a bridge falls down, we look at the steel and the bolts. We don’t say the cars drove across it wrong. Yet in finance, we treat the process as if it is made of thoughts and feelings rather than logic and code.

The real work of servicing a portfolio-tracking assets, billing, managing in-life changes-is a matter of plumbing. We need to stop asking our people to be better pipes and start hiring engineers who know how to build a system that won’t allow a leak to happen.

If you look at the 300 accounts that were charged the wrong fee, you will likely find that the error happened on a Friday afternoon or during a month-end rush. You will find that the system allowed the user to input a negative value where only a positive one should exist. You will find that the validation rules were turned off to “speed things up” two years ago.

The training module is a band-aid on a broken leg. It might hide the blood, but the bone is still snapped. To fix it, you have to go into the configuration. You have to use an API-first architecture that connects the origination data directly to the servicing records so no human ever has to type a fee code again. You have to build guards into the software so that if a user tries to click “403” for a contract that requires “402,” the system stops them.

The signature on the training log is the ink that blinds the eye to the broken dropdown.

We must stop the cycle of “teach and repeat.” It is a waste of time, a waste of money, and a drain on the soul of the workforce. Elias Thorne didn’t need to copy the rules. He needed a better lamp. Give your team the tools that make it hard to fail, and you will find that they suddenly become the “well-trained” experts you always wanted them to be.

The rot isn’t in the people. It’s in the gaslight. When the lights finally come up, you see that the errors were never about ignorance; they were about a system that was designed to fail and a management style that was designed to ignore it.

We can do better than the Victorian basement. We just have to be willing to fix the machine instead of the man.