You Didn't Save That Money. You Moved It.
Last quarter you cut a cost. The line item shrank. The number went green. Someone got credit in a review.
Here is the question that wasn't asked in that meeting: Where did the cost go?
Because it didn't leave. Cost almost never does. It relocates - and it moves along the path of least resistance, which is almost always the path of least power. Off the budget you were watching, onto one you weren't.
Here's what that looks like when it's happening to you.
You automate a workflow and remove three roles. Real savings, visible on the page, defensible in the numbers. Then six months later the remaining team is spending its days checking the automation's output, correcting its edge cases, and absorbing the escalations it can't handle. The labor didn't vanish. It changed shape and moved - out of the line marked headcount and into a line marked nothing at all, carried by people who were already full. You cut a cost you could measure and grew one you can't. On paper you won. In the system you're underwater, and it won't surface for four quarters. That's not a mistake anyone made. It's a property of how organizations account for themselves. We're very good at measuring the cost that sits still and nearly blind to the cost that moves. So the moving kind accumulates - quietly, off-ledger, until it arrives all at once wearing a name like attrition, or rework, or why is delivery suddenly slow.
I find that cost before it arrives. That's the work.
It shows up in more than automation. A vendor contract that looks cheap moved its real price into your team's coordination time. A reorg that "flattened overhead" moved the overhead into the six side-channels people now use to get anything done. A trust problem - a manager nobody quite believes, a metric everyone games - moves its cost into every approval layer, audit, and double-check the organization bolts on to compensate. That machinery isn't free. You're paying interest on low trust in friction, delay, and turnover, whether or not anyone has ever put it on an invoice.
None of this is visible from inside a single dashboard, because a dashboard is a slice. It samples the fastest-moving, easiest-to-measure layer of a system that's actually running on several clocks at once - and then quietly treats that one layer as the whole picture. Most of the costs that matter to you arrive on a slower clock than the one you're watching.
My job is to read the whole ledger, not the visible line. I take a decision you're about to make - or one you already made and can't explain the aftermath of - and I trace where its consequences will actually land: which team, which quarter, which unmeasured account. Then I help you redesign the thing before the hidden bill comes due, while it's still cheap to change.
I use a method I've been building and testing in public for three years - I call it MDGP. You don't need to care what it stands for. What you need to know is what it does: it refuses to let a question collapse to the convenient frame too early, and it forces every decision through the perspectives your existing process is structurally built to skip - the stakeholder who isn't in the room, the cost that lands on a clock you're not watching, the team that will quietly absorb what the spreadsheet exported. That's where the money is. It's always where the money is.
If any of this landed, if you read "you cut a cost you could measure and grew one you can't" and felt a specific situation come to mind - that recognition is the diagnosis starting. The situation you just thought of is the place to look.
Here's how to start. Bring me one decision: something you're weighing now, or something you shipped in the last year whose aftermath doesn't add up. In a focused Diagnose and Advise engagement I'll map where the cost actually went, name who's carrying it and when it comes due, and give you a redesign you can act on. No framework homework, no philosophy. Just the missing dimension and the bill attached to it.
Find me at tlolllc.com, or reach out directly at James.German@TLOLllc.com or www.linkedin.com/in/JamesGerman
The cost you cut didn't leave. Let's go find where it went.
James German (Lord Stretch) runs TLOL LLC, a complex-systems consultancy in Durango, Colorado. He writes the “Digitally Yours,...” Linkedin newsletter weekly.