In the middle of the nineteenth century, Admiral Sir Francis Beaufort was obsessed with the idea that the invisible could be mastered if only it were described with enough precision. He did not merely want to know if it was windy; he wanted to categorize the wind into thirteen distinct stages, from “calm” to “hurricane,” based on how it affected the sails of a man-of-war.

For years, he refined these descriptions, believing that by providing a universal language for the weather, he could eliminate the ambiguity that led to shipwrecks and lost cargo. It was a noble pursuit of total documentation, an attempt to turn the chaotic movement of the atmosphere into a structured library of predictable outcomes.

Yet, as history often proves, the sailors on the deck rarely consulted the chart when the gale actually hit; they looked at the whitecaps and felt the sting of the spray on their faces, relying on a visceral, inherited understanding of the sea that no thirteen-point scale could ever fully capture.

The Drowning Power of Ink

Because we fear the silence of an unrecorded process, we fill the organizational void with ink, which is also how the ink eventually drowns the person trying to find the way out. This is the central paradox of the modern equipment finance operation. We believe that by documenting every possible permutation of a payment deferral or an end-of-term residual buyout, we are exercising control over our portfolio.

We build massive, sprawling repositories of Standard Operating Procedures (SOPs) that act as a sort of sedimentary rock of corporate anxiety, each layer representing a past mistake that someone vowed would never happen again. But as these libraries grow, they undergo a strange metamorphosis. They cease to be a guide for the living and instead become a monument to the dead-a collection of rules that everyone acknowledges but no one actually uses.

Documentation vs. Memory

I have felt this fragility firsthand recently, though not in a boardroom. A few weeks ago, I accidentally deleted three years of photos from a personal drive-thousands of moments captured with the intent of “preserving” them. I realized, as the progress bar vanished and the folders turned up empty, that the documentation of my life had become a substitute for the memory itself.

I wasn’t looking at the photos, but I felt “safe” because they existed. When they were gone, the reality of the events remained, but the formal proof had vanished. In business, we do the same thing. We assume the existence of a 400-page procedure manual is synonymous with having an orderly business. It is a comforting lie that lasts exactly until someone actually needs to know the approval limit for a high-risk payment deferral.

The SharePoint Prehistory

Suppose a junior collections officer is faced with a customer asking for a 90-day pause on their lease payments. The officer knows there is a procedure document for this. It is a PDF, roughly 71 pages long, buried in a SharePoint folder that requires three different clicks to locate.

On page 44, the document states that a Vice President must sign off on any deferral exceeding $12,000. But when the officer mentions this to a senior colleague, the response is a dismissive wave of the hand. “That changed last quarter,” the colleague says. “We don’t go to the VP anymore; we go to the regional credit lead, and the limit is actually $15,000 now.”

Parallel Realities

The colleague is right. The document is wrong. Yet the document remains in the library, marked as “current” and “controlled,” and it will be referenced again by the next person who doesn’t know the right person to ask. This creates a dangerous bifurcation in the company.

You end up with two parallel universes: the formal world of documentation, which is audited and certified and pristine, and the real world of “how things actually get done,” which is transmitted through Slack messages, coffee-room chats, and the collective memory of the staff.

A Fortress of Efficiency

I will admit that I was once a True Believer in the power of the manual. Early in my career, I spent nearly six months drafting a comprehensive SOP for a logistics firm, convinced that I was building a fortress of efficiency. I thought that if the instructions were clear enough, the human element-with its tendency toward error and improvisation-could be neutralized.

I was wrong. Within three weeks of the manual’s “Go Live” date, the drivers were ignoring my meticulously mapped routes because a new toll bridge had opened that I hadn’t accounted for. They didn’t tell me; they just fixed the problem amongst themselves. My manual became a ghost, a haunting reminder of a reality that no longer existed.

The Sommelier’s Warning

“If you provide a customer with too much technical data about a glass of water before they take a sip, they stop tasting the water entirely. They start tasting the description.”

– Michael J., Water Sommelier

In the same way, when we over-document a business process, we stop our employees from seeing the actual work. They become so focused on following a checklist that may or may not be accurate that they lose the ability to exercise judgment when the situation doesn’t fit the template.

Rational Distrust

This volume of documentation doesn’t just fail to provide control; it actively destroys it. As the corpus grows, the probability that any single page is up-to-date drops precipitously. The staff, being rational actors, correctly learn to distrust the entire set.

They realize that the “source of truth” is more likely to be found in the head of a manager who has been there for nine years than in a document library that hasn’t been scrubbed since 2022. Once that trust is broken, the documentation ceases to be a tool for guidance and becomes merely a tool for blame. It exists so that when something goes wrong, a manager can point to page 52 and say, “You didn’t follow the procedure,” even if the procedure was practically impossible to follow in the first place.

The Shift to Intelligence

This is why many forward-thinking lenders are moving away from the “Documentation First” model and toward a “Workflow First” model. If the rules of the business-the approval limits, the delinquency queues, the end-of-term options-are baked into the equipment finance software itself, then the need for a 71-page PDF vanishes.

The system becomes the carrier of the operational rules. If a deferral requires a specific sign-off, the software routes it there automatically. The employee doesn’t need to remember who the regional credit lead is or what the current limit is; the system knows. This moves the “control” from a static, decaying document into a living, breathing part of the daily work.

When you shift the intelligence from the manual to the platform, you eliminate the “Documentation Tax”-the hidden cost of employees searching for, misreading, or ignoring outdated instructions. It allows the human beings in the equation to focus on the things that software cannot do: building a relationship with the customer, negotiating a difficult settlement, or spotting a macro-economic trend that isn’t in the data yet.

Knowledge vs. Files

The irony of our digital age is that we have made it so easy to create content that we have forgotten how to curate it. We keep adding pages to the library, thinking we are building a more robust organization, but we are actually just building a thicker fog. Like my deleted photos, the sheer volume of our digital artifacts can give us a false sense of security.

We think because the server is full, the knowledge is safe. But knowledge is not a file; it is a current state of understanding.

If your portfolio servicing relies on a set of binders or a directory of PDFs that your team hasn’t looked at in six months, you don’t have a controlled process. You have a museum of old intentions. Real control is found in the configuration of the tools your people use every hour of the day. It is found in the workflows that guide a contract from booking to payoff without requiring a detour into a “procedure library.”

“The manual survives only by sacrificing its relevance to the very hand it was written to guide.”

We must eventually ask ourselves what we are actually auditing. Are we auditing the work, or are we auditing the documentation of the work? If the two have diverged-as they almost always do in high-volume environments-then the audit itself is a performance, a piece of corporate theater where everyone pretends that the PDF on the screen is the thing that actually happened.

To regain control, we have to stop writing about the work and start building the work into the system. Only then can we stop looking at the clouds and finally trust the ship.