A lead plummet is a heavy truth on a string. It is a simple tool, a cone of metal hanging by a cord, yet it is the only thing that doesn’t lie in a world of crooked eyes and optimistic levels. If you hold it still, gravity pulls it toward the center of the earth with an indifferent honesty.

My father taught me that a mason who ignores his plummet is just a man building a very expensive pile of rubble. In the business of stone and mortar, you cannot negotiate with the vertical. You either respect the weight of the thing or you watch the wall lean until the roof comes down.

The corporate change budget is supposed to be a plummet, a measure of what we can actually achieve in a year. It is meant to be a stabilizing force that keeps the operational house upright. But in the fluorescent-lit hallways of modern finance, the budget has ceased to be a measure of truth.

It has become a bucket of water in a room full of thirsty people, and the person who brings the biggest straw wins. We call it first-come-first-served, a phrase that suggests fairness and order. In reality, it is a race for a shared pool that rewards the hasty and punishes the thorough.

It is early February, and the air in the office is still thick with the residue of New Year’s resolutions. Sarah, who manages the receivables portfolio, has already submitted five requests for system configuration changes. She is efficient. She is precise.

By the tenth of the month, three of her requests have been approved. She is adjusting the way headers appear on client statements and tweaking the automated email triggers for thirty-day delinquencies. These are good changes, useful changes, but they are not structural. They are the equivalent of pointing a garden wall when the main chimney is crumbling. Sarah isn’t doing anything wrong. She is playing the game as it was designed.

01

The Thoroughness Penalty

Across the hall, Mark is sitting in the equipment finance department. He is not fast. He is meticulous. He is currently six weeks into a deep-dive analysis of a manual process that plagues his team every month-end.

Because their legacy servicing system can’t handle certain mid-term contract modifications without manual intervention, his staff spends four days every month in a frantic dance of spreadsheets and manual data entry. It is a leak that costs the company thousands in lost productivity and introduces a terrifying margin for error.

Mark is building a case. He is gathering data, calculating the ROI, and preparing a presentation that proves a single configuration change could save forty-eight days of labor per year.

In March, Mark finally walks into the committee room with his data. He is proud of his work. He lays out the problem and the solution with the clarity of a man who has finally found the straight line.

The committee looks at his numbers, nods in agreement, and then tells him that the allowance for the year is already committed. The “change tokens” have been spent. The mortar has been used on the garden wall. Mark is told to come back next January. He walks out of the room feeling like he’s been penalized for being right.

I used to think that the first person on a job site was the most dedicated worker. I was wrong. In my years as a mason, I’ve seen that the guy who starts mixing mortar at sunrise before the plans are even unrolled is often the most panicked, not the most prepared.

He is trying to claim the space, to establish his presence through motion rather than progress. I’ve made this mistake myself. I once rushed the foundation of a small smokehouse because the weather was turning, only to realize I hadn’t checked the soil density. The building didn’t fall, but it shifted just enough to make the door stick forever. It was a monument to my own impatience.

It teaches managers that the quality of their analysis is secondary to the speed of their submission. By the time the next January rolls around, the behavior in the office has changed. Mark hasn’t forgotten the lesson of the previous year.

On the second working day of the new year, both Sarah and Mark have ten requests on the committee’s desk. Neither of them has finished their analysis. Neither of them knows which changes will actually yield the highest benefit. They are simply grabbing as much of the pool as they can before it disappears. The design of the budget has produced the very conduct that the leadership later criticizes as “uncoordinated” or “reactive.”

The Scarcity Trap

It is currently 4:30 in the afternoon, and I am starting to feel the physical cost of a diet I decided to begin at 4:00. My stomach is a hollow cathedral of regret, and my patience for corporate inefficiency is wearing thin.

When you are hungry, everything looks like a zero-sum game. You start to see scarcity everywhere. This is the same atmosphere created by a rigid change budget. It puts everyone in a state of operational hunger where they feel they must eat now or starve for the rest of the year.

The irony is that many of these “changes” shouldn’t be competing for a special budget at all. In the world of

equipment leasing software,

the ability to handle routine in-life changes-like restructuring a lease or adjusting a payment schedule-should be a native capability of the platform, not a “project” that requires a developer’s intervention.

When a lender’s servicing operation is tied to a rigid, legacy architecture, every minor adjustment becomes a line item in a war for resources. You end up spending your innovation budget on basic maintenance. A bucket of lime should be part of the overhead, not a special request that requires a board meeting.

We have reached a point where the architecture of our software determines the culture of our management. If the system is closed and brittle, managers become hoarders. They hoard “change windows,” they hoard developer hours, and they hoard the attention of the IT staff.

They stop looking at the portfolio as a whole and start looking at it as a series of defensive positions. The equipment finance side of the house, which often deals with more complex asset tracking and mid-term adjustments than receivables, is particularly vulnerable to this scarcity. A single lease modification shouldn’t feel like a heist.

The solution isn’t to create a bigger budget; it’s to change the nature of what requires a budget in the first place. An API-first servicing platform treats configuration as a conversation rather than a construction project. When the manager can adjust the rules of the engine without needing to wait for the “change window” to open in six months, the race for resources ends.

The Tale of Two Walls

I remember a project in the late nineties where we were restoring a library. The lead architect had a “change fund” for the stone carvings. Every time a mason found a piece of detailing that was more decayed than expected, he had to apply for a portion of that fund.

Within two months, the masons working on the north wall-the side that gets the least sun and usually has the least damage-had claimed seventy percent of the money for minor aesthetic repairs.

When we got to the south wall, which was battered by decades of wind and rain, we found structural cracks that threatened the entire cornice. There was no money left. The architect had to go back to the donors and admit that he had funded the vanity of the north wall while the south wall was falling into the street.

We see this same tragedy play out in financial operations. The “north wall” managers are the ones with the simple portfolios and the quick requests. They look good on paper because their “projects” are completed quickly and on time.

Meanwhile, the “south wall” managers, like Mark in equipment finance, are dealing with the structural complexity of a diverse asset book. They are doing the hard work, but because that work takes time to define, they are left out in the cold. We are rewarding the absence of complexity rather than the mastery of it.

If we want managers to act like owners, we have to stop treating their operational needs like a limited supply of treats. The goal of a servicing platform should be to make the manager autonomous. When the tools are self-service, the “race” disappears.

Sarah can have her header changes and Mark can have his manual-process fix, and neither has to step on the other’s toes to get them. The budget can then be reserved for actual innovation-for the things that truly move the needle, rather than just keeping the lights on.

My diet is now ninety minutes old, and I am contemplating the structural integrity of a cracker. Hunger makes you short-sighted. It makes you prioritize the immediate over the important.

A corporate culture built on the scarcity of change is a culture in a permanent state of hunger. It is a room full of people staring at a plummet that is swinging wildly because everyone is trying to grab the string at the same time.

We have to let go of the string. We have to build a foundation where the ability to adapt is a given, not a prize for the fastest runner.

The Integrity of the Line

The plummet never lies about the wall, but the calendar always lies about the budget.

In the end, the most expensive change is the one you didn’t make because you were too busy waiting in line for the one that didn’t matter. We need systems that reflect the reality of the work, not the limitations of the queue.

Only then can we stop racing and start building something that actually stands. Only then can we look at the plummet and see a straight line. It is a simple goal, but in a world of crooked budgets, it is the only one worth pursuing.

If the mortar is dry and the stone is set, you can’t go back and fix the lean. You have to get it right while the mix is still wet. That is the only truth I know. It is enough.