AMGTA BRIEF • September 2026
Sustainability Has a Cost Problem
Resource efficiency is how sustainability works in manufacturing
By Sherri Monroe • Executive Director, AMGTA
~5 min read
I once asked a group of military manufacturing leaders how they think about sustainability.
A little sheepishly, they admitted they don’t think about it at all.
So, I asked whether they think about resource efficiency.
Suddenly we were talking the same language.
Resource efficiency is how manufacturing does sustainability. It is also how organizations stay ready, maintain economic viability, and compete at home and abroad. And the resources that must be managed well go beyond material and energy – to time, capital, labor, opportunity, and risk. The goal is value from what is spent, with less of it wasted.
Nothing about manufacturing had changed between those two questions – only the vantage point, and some baggage around a word choice. The appetite for sustainability language rises and falls with the market and the political climate; the material an organization wastes and the capital it ties up do not. In manufacturing, the economic case and the environmental case are often one and the same.
Additive manufacturing enables resource efficiency in ways specific to the technology – at the level of the part, the system it belongs to, and the enterprise that makes or uses it. A part that uses less material and performs better. A system with fewer components to assemble, stock, and fail. An enterprise committing less capital, later, closer to real demand. The efficiency at one level carries into the next.
How well an operation uses what it consumes, and how much it wastes, is not a question for the sustainability team alone. Regardless of motivation, the sustainability officer and the finance officer are working the same lever for different reasons, whether or not they realize it. Whether the aim is stated as protecting the environment or as sustaining the business, it comes down to the same question: what is used well and what is not. The motivation varies from one function to the next, and one market to the next – regulatory pressure in one, operational performance in a second, capital discipline in a third – and the lever is the same in every one.
And waste is broader than the scrap bin on the production floor. It is over-production and the obsolescence that follows. It is inventory tying up capital and floor space that could be used more productively. It is capacity built and never used, parts shipped that did not need to move, designs frozen too early and tooling written off. Each of those costs money and carries an environmental burden at the same time. In manufacturing it is often said that the most sustainable part is the one never produced. And I would add: the least sustainable part is the one produced and never used – all cost, no value.
That parallel between cost and impact showed up in a demonstration of a monitoring tool built to catch a failing additive process early and stop it – before more material and energy are consumed, and before the part is finished, inspected, and eventually scrapped. In the demo, $158,000 was saved in material, energy, and post-processing. Told this was a strong sustainability result, the company said they hadn’t started tracking sustainability yet. So, then, $158,000 of what? Material, energy, time. The economic savings and the environmental savings were the same, seen two ways. They had built something that delivered both without realizing it.
So, if resource efficiency is what sustainability looks like in manufacturing, where does the sense of conflict come from? Why is better environmental performance so often set against cost and operations? Usually because a cost is landing somewhere else – another department’s budget, a supplier, a customer, or society at large. The option that looks cheaper and dirtier often isn’t cheaper once the displaced costs are counted – the write-offs, the disposal, the burden pushed onto a supplier or the environment. The burden didn’t vanish; it moved off the budget driving the decision. This is the cost problem sustainability actually has: not that it costs money, but that the savings and the costs so often land in different places. The conflict is rarely in the manufacturing. It is in the accounting. Today’s cost accounting was built for conventional manufacturing, in an era when environmental impact was not a line anyone tracked.
The efficiencies additive enables reach past the part and how it is managed. Producing closer to actual need – in place or in time – avoids excess by lowering the volume at which production is viable, reducing or removing tooling, and letting commitments on volume and design wait until demand is clearer. The speculative inventory, the stranded capital, the obsolete design, the unnecessary transport it avoids are the waste that costs money and burdens the environment together. The result is not just optimized output. It is excess that is avoided – and what is avoided is often hard to see and measure.
There is an important exception. This convergence holds for avoided excess – what is never made, never warehoused, never scrapped. It does not automatically hold for how a given part is made. Substituting one material or process for another can cut cost while raising the footprint, or – the more familiar complaint – lower the footprint at a higher cost. Those are real trade-offs. But where the saving comes from excess avoided, the two move together, with no trade-off to manage.
Framing environmental performance as resource efficiency is not a retreat from sustainability. It is where those impacts actually arise and get measured, in a working operation.
Resource efficiency is how sustainability works in manufacturing – not beside the economics, not in tension with it. One outcome: call it sustainability or call it good business.
Or email info@AMGTA.org
Members shape this work
The analytical content AMGTA hosts—and the conversations it makes possible—exists because members make AMGTA’s work possible. The next sector brief, the next analytical thread, the next reviewed use case: built by members, in working groups, right now.