If you realized that your entire operation was being held hostage by a spreadsheet that no one remembers creating, would you have the courage to delete it, or would you simply hire another person to check its math?

You sit in a mahogany-trimmed conference room or a sterile Zoom square, and you look at the evidence of your own success, which, in a strange twist of corporate fate, looks remarkably like a burden. You are staring at a spreadsheet titled “Recurring Servicing Activities – Q3 Review.” It contains 47 distinct tasks. Beside each task, there is a name-a guardian, a proprietor, a person whose very identity within the organization is tethered to the continued existence of that specific report, that particular manual reconciliation, or that exact weekly “alignment” call.

You watch the room as someone-perhaps a brave soul from Finance or a weary consultant-proposes identifying candidates for removal to save the team’s sanity. You notice the silence that follows; you see the way eyes dart toward the ceiling; you feel the collective intake of breath as the guardians prepare their defenses; you realize that in eleven minutes of discussion, only two suggestions emerge, and both are immediately neutralized by the requirement that “other functions” must agree to their demise.

You look at the final output of that two-hour meeting, a document with a section titled “Opportunities for Simplification,” and you find exactly three lines of vague, non-committal text.

The problem you are facing is not a lack of intelligence or a lack of desire for efficiency. The problem is that in the modern institution, addition has a lobby, while subtraction does not even have a desk. You are working in an environment where every new control, every additional reporting layer, and every “v3” of a tool is born with a built-in advocacy group, but no one is ever hired with the title of Chief Deletion Officer. You see the accumulation because it is visible; you see the “servicing tax” because it shows up in your headcount requests; you see the friction because it slows down every in-life contract modification you try to process.

The Structural Asymmetry of Obsolescence

You are witnessing a structural asymmetry that no amount of cultural exhortation can fix. If you tell your team to “simplify,” you are essentially asking them to volunteer for their own obsolescence or, at the very least, to insult their colleagues. You are asking them to look at a process that has been in place for seven years and declare it worthless, which is a political risk that carries no corresponding reward.

You see, when you add a process, you are “mitigating risk” or “enhancing visibility,” both of which look excellent on a performance review. When you delete a process, you are simply “the person who took away the report that the Head of Credit liked in 2018.”

I spent twenty minutes this morning trying to end a conversation politely, and it felt remarkably like trying to delete a legacy workflow in a bank-owned leasing company. You say the words that should signal the end; you offer the polite closing remarks; you summarize the next steps with a finality that should be unmistakable; yet the conversation continues, looping back onto itself like a recursive script that lacks an exit condition.

You are trapped in the momentum of the “just one more thing” culture. This is the same momentum that keeps manual payment reconciliation alive long after the software should have automated it. You find yourself nodding along because it is easier than being the person who hangs up, and in your business, it is easier to add a 48th task than to kill the 1st.

The Shadow Ledger Phenomenon

To understand how this actually works, we have to look at the “Shadow Ledger” phenomenon often found in portfolio servicing. When a lender’s core system is inflexible, a team member-let’s call her Sarah-creates a side-spreadsheet to track equipment collateral that the main system can’t handle. Sarah spends four hours a week updating this.

Two years later, Sarah is promoted. Her successor, James, is told that the “Collateral Tracker” is a critical control. James eventually gets a junior analyst to help him. Now, you have a “Collateral Tracking Function.” When you finally buy modern software that handles collateral natively, the Collateral Tracking Function does not disappear. Instead, it evolves into the “Collateral Data Validation Unit,” whose job is to ensure the new software matches the old spreadsheet. You have successfully added a million-dollar platform while keeping the hundred-dollar spreadsheet, and your cost per contract serviced has actually gone up.

You are currently paying a tax on your own history. You are paying for the fears of former executives who wanted “one more check” on every ACH file. You are paying for the technical debt of systems that were built when an API-first architecture was a futuristic dream rather than a baseline requirement.

You see this manifest in the way your team handles in-life modifications. If a customer wants to change a payment date or adjust a residual buyout, and your system requires a vendor ticket and a three-week wait, your team builds a manual workaround. You are essentially paying people to act as the glue between broken processes, and because those people are valuable, you cannot imagine letting the “glue” go, even if you finally fix the crack.

You must recognize that simplification is not a project; it is a budget line item that is currently empty. Most organizations treat simplification like a spring cleaning-something you do once a year when the clutter becomes unbearable. But you cannot “project-manage” your way out of a structural imbalance.

If addition is a continuous, 365-day-a-year activity funded by every department’s desire for growth, then subtraction must be a continuous, 365-day-a-year activity funded by the organization’s desire for survival. You are either funding the removal of the old, or you are unintentionally funding the suffocation of the new.

The Discipline of Scope

This is where the discipline of scope becomes the only real competitive advantage. When we look at how the most efficient lenders operate, they aren’t necessarily working harder; they are just working on fewer, more impactful things. They have realized that trying to own the entire “origination-to-end-of-term” lifecycle often leads to a bloated, “jack-of-all-trades” system that does nothing perfectly.

You see the difference when a platform is built to do one job-portfolio servicing-and do it with such technical depth that it eliminates the need for the “Sarahs” and “Jameses” of the world to build shadow ledgers. You are looking for a system that doesn’t just add features, but one that allows you to delete workarounds.

You are often told that the risk of migration is too high. You are told that moving your servicing book to a modern platform is like changing the engines on a plane while it’s flying. But you should be asking a different question: What is the risk of staying?

You are burning more fuel; you are flying lower to the ground; you are losing the ability to maneuver when a storm-in the form of a market shift or a new regulatory requirement-hits. You see the accumulation in your billing accuracy reports. You see it in the delinquency roll rates that refuse to budge because your collections team is too busy with manual data entry to actually talk to customers. You are watching your cost per contract serviced climb, and you are being told it’s just the “cost of doing business.” It isn’t. It is the cost of an organization that has forgotten how to say “no” to a new process and “goodbye” to an old one.

Making Subtraction a Career-Enhancing Move

You have to make subtraction a career-enhancing move. You have to create a culture where the person who identifies a redundant report is celebrated as much as the person who closes a new deal. You are likely skeptical of this because it sounds like “corporate culture” fluff, but it is actually a matter of architectural integrity.

If your servicing engine is 100% API-first, it means you are building for a world where you can swap out parts without breaking the whole. It means you can integrate with the best-of-breed origination tool today and a different one tomorrow, without the legacy of the old one dragging you down. You are building for modularity, and modularity is the natural enemy of accumulation.

You are probably looking at your current tech stack and feeling a sense of exhaustion. It’s the same exhaustion I feel at the end of a long livestream, where the “chat” has moved in a dozen different directions and I’m trying to pull the threads back together so we can all go home. You are trying to pull the threads of your portfolio together, but the threads are tangled in decades of “and also” and “just in case.” You are looking for a way to cut the knot.

You should consider that the most successful migration is the one where the back office never goes dark, yet when the lights come back on, the “Opportunities for Simplification” list has been fully checked off because the new system simply doesn’t allow for the old inefficiencies. You are not just looking for a new tool; you are looking for a new way of existing as an organization. You are looking for the permission to stop doing 47 things so you can do 10 things with absolute precision.

In the end, you are currently the gardener of a very large, very overgrown estate. You have plenty of people planting new flowers, but you have no one pulling the weeds. You can continue to hire more gardeners, or you can finally buy the tools that make the weeds stop growing in the first place.

You know which one you’re currently managing. You just haven’t been given the job of deleting the difference yet. If no one has given you that job, perhaps it’s time you took it for yourself. You might find that the most valuable thing you can do for your organization this year isn’t adding a single new process, but finally, mercifully, taking one away.

Is it possible that your most significant contribution to the bottom line is currently hidden in a “recurring activity” that no one has the heart to kill?