If you’ve ever walked out of a capital review meeting thinking, They just don’t get it, you’re not alone.

You know the machine is unreliable. You’ve watched operators fight the same chronic issue every shift. You’ve seen scrap creep up, overtime spike, and customer commitments tighten because the line won’t stay in run. From your vantage point, the solution feels obvious: fix it or replace it.

But here’s the uncomfortable truth: capital requests usually aren’t denied because leadership doesn’t care. They’re denied because the case wasn’t built in the language leadership uses to allocate capital.

If you want your next request approved, here’s what you should do.

1. Start with Data, Not Frustration

On the shop floor, problems feel obvious. In the boardroom, they aren’t.

Statements like “This equipment is old” or “We’re constantly fighting downtime” may be true, but they’re not persuasive. Executives don’t approve capital based on how painful something feels. They approve it based on measurable exposure and expected return.

Before you ever submit a request, you should be able to answer specific questions with confidence.

·       How often does the line go down?

·       For how long?

·        What is the scrap impact?

·       How much overtime is directly tied to breakdowns?

·       What revenue or margin is at risk?

If you can’t quantify the impact, you don’t yet have a capital case — you have an operational complaint.

In They Just Don’t Get It, Bob and I describe the site leader’s real job as standing in the middle — translating execution into business results and business strategy back into operational priorities. Capital approval lives in that translation. When you speak in operational frustration, executives struggle to respond. When you speak in quantified impact, they lean in.

2. Convert Downtime into Dollars

The shift that changes everything is simple: stop describing what’s broken and start quantifying what it costs.

Consider a line that loses 45 minutes per shift to recurring micro-stops. On the floor, that feels like irritation. In a capital meeting, irritation carries no weight. Numbers do.

45 minutes × 3 shifts × 5 days × 50 weeks = 562.5 hours annually

Multiply that by your contribution margin per hour, and irritation becomes a six-figure business exposure.

The equipment hasn’t changed. The framing has.

Executives rarely deny clear returns; they deny unclear ones. Your responsibility is to remove ambiguity.

3. Build the ROI Before You Submit the Request

Most denied capital requests fall into predictable traps — and all of them are avoidable with discipline.

The first trap is vagueness. Words like “reliability issues” or “efficiency concerns” sound serious but don’t translate into financial impact. Specificity does. Downtime frequency, scrap percentage, overtime tied to breakdowns, shipments at risk — those details elevate the conversation from opinion to evidence.

The second trap is stopping at operational logic. You may fully understand how a new piece of equipment improves run uptime, stabilizes changeovers, or reduces scrap. But finance doesn’t approve uptime. They approve margin improvement, capacity creation, cost reduction, and risk mitigation. Your job is to translate operational gains into financial results. Convert run uptime into capacity. Convert capacity into revenue or cost avoidance. Convert scrap reduction into margin improvement.

The third trap is ignoring the cost of waiting. When budgets tighten and you hear, “Not this year,” the wrong reaction is frustration. The right reaction is analysis. What does another year of downtime cost? Are maintenance costs climbing? Is performance degrading? Is customer risk increasing?

Often, the cost of inaction quietly exceeds the cost of the investment — but only if you prove it.

4. Treat Every Capital Request Like an Investment Proposal

Capital allocation is a competition. Every dollar has multiple potential homes. Your request isn’t being evaluated in isolation; it’s being compared against other opportunities.

That means your proposal must align with strategic priorities. It must use conservative, credible assumptions. It must address implementation risk honestly. And it must show a clear payback timeline.

Don’t ask for money.

Present an opportunity.

That mindset shift changes everything. You move from requesting relief to offering return.

5. Build a Track Record of Credibility

Over the course of eight years, I submitted more than a hundred capital requests. None were denied. That wasn’t because every idea was brilliant or because funding was unlimited. It was because we applied discipline.

If a project didn’t meet ROI thresholds, we refined it until it did — or chose not to submit it. If a proposal was strategically important but financially tight, we previewed it early and sought feedback rather than surprising leadership in a formal review. And we delivered exactly what we promised.

Credibility compounds. When leadership sees that your projections become reality, approvals accelerate — not because of politics, but because of trust.

That discipline — using data as a universal language, building ROI thinking into your DNA, and translating operational pain into business impact — is exactly what we unpack throughout They Just Don’t Get It. It’s not a book about getting executives to “understand.” It’s about helping site leaders become fluent in both languages.

6. Remember What Capital Approval Really Tests

Capital approval isn’t really about equipment.

It’s about translation.

Operations speaks in terms of pain and urgency. Executives speak in terms of return and risk. If those two languages never meet, the answer will be no.

The site leader’s real job is to connect operational reality to business impact with clarity, discipline, and evidence. When you do that well, you stop saying, “They just don’t get it,” and start helping them see exactly what’s at stake — and why the investment makes sense.

That’s how capital gets approved.

And that’s what leading from the middle actually looks like.

Where the Data Comes From

None of this works without reliable data.

You can’t convert downtime into dollars if the numbers are debated. You can’t build a credible ROI case on yesterday’s reports and gut feel.

That’s why we built Flex-Metrics — not as software, but as an Ops Guy’s tool for real-time visibility. It gives you clear, defensible data on run time, downtime, speed, and scrap — the exact inputs you need to build capital cases that hold up under scrutiny.

And if you want to go deeper into the leadership discipline behind this — translating operational reality into business impact and earning credibility from the middle — Bob and I unpack that in They Just Don't Get It: How Manufacturing Site Leaders Translate Between Strategy & Execution.

Because when you learn to speak both languages — execution and return — approvals stop feeling political and start feeling predictable.