The Cost of Functional Protection
Hidden expenses are the ones nobody owns.
Every function made its numbers. The company was still overpaying.
Earlier in my career, I led part of the technology organization at a large financial services company. Every year brought another expense initiative, and this one went out across the whole organization with the same question for every function: how can you take cost out?
At the corporate level, the major functions were already making their numbers. Finance was doing a good job. IT was doing a good job. By every scorecard anyone was looking at, nothing was wrong.
So in IT we started asking different questions. Not only what we spent directly, but what was being charged to us through allocations from Finance.
We were looking at every line. Somewhere in that review, a voice from around the table stopped at the allocation for procurement.
“That’s a pretty big number. How many vendors are we talking about?”
“I don’t know, but I can find out.”
At the next meeting, the answer came back. “I got your answer on the vendors. 1,800.”
“You’re kidding me.”
And that was just Technology’s vendors.
Nobody had chosen 1,800 vendors. Nobody had approved it as a strategy. It had built up one reasonable decision at a time, over years of managers solving their own problems with suppliers they trusted. When we looked at the spend, the old 80/20 rule held, or close to it: most of the money went to a small share of the vendors. Every one of the rest still needed a contract, a procurement process, invoices, renewals, and someone to administer all of it. Part of that cost sat in IT’s direct spend. Part of it sat in Finance and Procurement, and came back to IT as an allocation nobody had a reason to question.
The expense was everybody’s and nobody’s. That is the cost of functional protection. It doesn’t appear on any one function’s scorecard. It lives in the cracks between them.
Picture a relay team where every runner posts a personal best and the team still loses. It happens. Relays are won and lost in the handoffs, and the handoff doesn’t show up in anyone’s time. Each leg is timed. Nobody times the exchange.
Every function was winning its leg. The organization was losing the race.
The savings opportunity had been there all along. Nobody saw it because nobody was measuring it.
Once the number was visible, the head of Technology, an EVP who was in effect our CIO, took ownership of the whole thing. The case wasn’t hard to make: fewer vendors, less to administer, and better terms from larger relationships. On paper, everyone won.
We set a goal of getting to 300 vendors. Then we called the top 100 to 150 into a meeting and told them plainly: you are our preferred vendors. We are going to do more business with you. In return, we expect your best terms, or we will move our business.
For years, nobody had resisted, because there was nothing to resist. Nobody knew. Resistance showed up the moment the fix started to touch someone’s people, budget, or relationships.
IT managers pushed back on ending long-term vendor relationships. Some of those relationships were genuinely good ones, built over years, and the managers who owned them weren’t wrong that they worked. Finance defended its allocations, because fewer vendors meant fewer people and major process changes in Procurement and Finance. Then the mix of employees and contract staff in IT became its own source of contention.
None of it was bad faith. Every one of those positions made sense from inside the function holding it. That’s what makes functional protection so hard to see. It rarely looks like protection. It looks like people doing their jobs well.
It took 12 to 18 months. We went from about 1,800 vendors to between 300 and 400. The savings came from two places: better terms from the vendors who got more of our business, and the cost of administering more than 1,400 vendors we no longer had to manage. The change held for as long as I was there.
What changed wasn’t anyone’s intent. Nobody in IT or Finance had set out to waste money. What changed was that someone asked what was behind a number everyone had learned to accept, and then someone with the authority to act owned the whole answer instead of their piece of it.
This is the pattern I look for when I work with leadership teams. Silos don’t always form because people refuse to cooperate. More often, they form for reasons that each make sense on their own. Culture: stay in your own backyard. Metrics: we’re responsible for our own numbers. Systems: functional objectives and compensation that were never integrated. Optimization: each function tuned for its own leg instead of the whole race. And functional personality: sales wants to spend, accounting wants to save, legal wants to avoid risk.
None of those are character flaws. Together, they produce an organization where nobody is accountable for what falls between functions. When a leader tells me their team works well together, these are the questions I ask:
- What other parts of the organization do you rely on to do your job?
- Where and how do those organizations touch yours?
- To what extent is your year-end compensation tied to theirs, and theirs to yours?
The third question is usually the one that changes the conversation. If nobody’s compensation depends on the whole race, nobody is running it.
Somewhere in your organization there’s a number everyone has learned to accept. Who is going to ask what’s behind it?