When organizations face budget pressure, scope is almost always the first casualty. Deliverables get cut, timelines compress, and the project that reaches completion bears little resemblance to what was originally planned. Eric Hall, a senior program and product management leader based in Charlotte who has managed portfolios up to $10 million across banking, software as a service (SaaS), and compliance-driven environments at firms including Wells Fargo and TIAA, operates from a different premise entirely. The 20% savings that leaders are looking for are usually inside the plan, but they have not been found yet. “You don’t cut features to cut costs,” Hall states. “You cut waste. Plan sharper, automate smarter, and lead with structure.”
The Savings Are Hidden in the Estimates
Most unexpected project costs do not emerge mid-execution. They are embedded on day one in inflated estimates, duplicated resources, and assumptions that nobody challenged during planning. By the time the budget pressure becomes visible, the waste has already been authorized and is in motion. Hall’s first intervention is to surface that waste before a single task executes. In waterfall planning phases and agile planning sessions alike, he challenges headcount assumptions, work effort hours, and contingency buffers against the actual scope of work.
The question is not whether the numbers seem reasonable; it is whether they are calibrated to the real work or have absorbed the organizational habit of padding for uncertainty. “When you align the numbers to the actual work,” Hall notes, “savings of 15 to 20% appear before execution even begins.” That alignment requires someone willing to ask uncomfortable questions early enough to act on the answers.
Eliminate the Rework, Not the Requirements
The second source of recoverable cost is the hours teams spend on repetitive manual work. The tasks that could be handled through automation, templates, or smarter tooling but are instead being done by people whose capacity could be directed toward actual project delivery.
Hall points to a regulatory program where he cut implementation time in half by redirecting the team’s attention from manual execution to process efficiency. No requirements were removed. No scope was sacrificed. The same deliverables were produced in significantly less time because the production method was redesigned. Rework is one of the most consistent and underestimated budget drains in complex programs; it compounds quietly, and its cost rarely appears as a distinct line item, which is precisely why it persists. Identifying where teams are solving the same problem more than once and building the process to prevent it is often faster than any other cost intervention.
Structure Is the Fastest Path to Savings in a Troubled Program
When a program is drifting, the instinct is often to add oversight, tighten reporting, or bring in additional resources. Hall’s experience points toward a different intervention: structure. Coaching teams through Scrum principles, establishing clear roadmaps, and implementing short feedback loops have helped him reduce delivery costs by up to 50% in programs that were significantly off track. The mechanism is straightforward: focus protects scope, and structure creates focus. When teams understand exactly what they are building, in what order, and with what constraints, the ambiguity that generates waste disappears.
Sustainable cost reduction in project delivery is not a matter of scope negotiation. It is a discipline applied to planning precision, process design, and structural clarity. The 20% is there. It is sitting in estimates that were never challenged, tasks that were never streamlined, and programs that were never focused. Finding it requires a leader willing to look ahead to budget pressure rather than after it arrives.
Follow Eric Hall on LinkedIn for more insights on program management, cost discipline, and delivering complex initiatives without sacrificing scope.
