Doing More with Less Requires Real Trade-Offs

Begin with the arithmetic, not the slogan

'Do more with less' can be a challenge to innovate, but it can also become a way to avoid naming a decision. If demand grows while staffing, time, or funding shrink, something in the system must change. Productivity may improve. Scope may narrow. Service levels may fall. Backlogs may grow. Risk may move to employees or the people seeking help. Often, several of these happen at once.

The first leadership task is to make the capacity problem visible. How many requests arrive? How much work can the current system complete? Where does work wait? Which steps protect quality or rights, and which exist mainly because the process accumulated them over time? A useful conversation replaces the vague word 'efficiency' with demand, throughput, cycle time, backlog, quality, burden, and risk.

Efficiency can remove waste—or merely move it

A change is not automatically efficient because one department spends less. A shorter form that creates more follow-up calls, a self-service portal that people cannot understand, or an automated notice that produces more appeals may shift cost rather than reduce it. The receiving employee, partner organization, family, or member of the public still experiences the work.

This is why process improvement should follow the complete service journey. Reducing duplicate entry, unclear instructions, avoidable approvals, preventable rework, and unnecessary handoffs can create real capacity. Cutting a step that protects accuracy, accessibility, safety, or due process may create a faster process and a worse service.

Technology is one possible lever. It can reduce administrative burden and help staff focus on work requiring judgment or human contact. It can also make a confusing process harder to question and easier to scale. The right sequence is to understand the service, simplify it where appropriate, and then decide which parts technology should support.

Public service improvement needs measurable promises

Recent federal customer-experience work offers a useful lesson. In 2025, GAO reported that many high-impact service providers planned digital improvements, but it also found that government-wide goals lacked sufficiently clear quantitative targets and time frames to assess progress. Activity was visible; the overall result was harder to judge.1

The same report described a more concrete example: an online direct farm-loan application was reduced from 29 pages to 13, and the provider reported that average completion time improved by about 50 percent. Page count and completion time do not tell the entire story, but they create a testable claim rather than a general promise to modernize.1

Performance.gov's federal customer-experience framework similarly emphasizes improving service delivery, reducing burden, using customer feedback, and building organizational capacity. The principle applies beyond federal agencies: define the experience and outcome being protected before choosing the efficiency measure.2

A better decision frame for constrained resources

When leaders face a real constraint, I would rather see a short, explicit set of choices than a broad demand for innovation. Each option should show what changes, who experiences the impact, how quickly the benefit may appear, and which risks must be watched.

• Protect: Which outcomes, rights, safety controls, and human relationships must not be weakened?
• Remove: Which delays, duplication, corrections, approvals, and handoffs add little value?
• Redesign: Can demand be prevented, shifted earlier, combined, or resolved at a simpler point?
• Enable: Where could better information, training, data, or technology increase staff capacity?
• Choose: If the remaining demand still exceeds capacity, which service level, scope, funding, or timing decision must leadership make?
• Measure: What baseline, target, guardrail, owner, and review date will show whether the change worked?

Honesty is part of efficiency

Sometimes there is a genuine opportunity to improve service while reducing cost. Sometimes the available options all involve loss. Good leadership does not manufacture optimism when the arithmetic does not support it. It explains the constraint, removes avoidable waste, protects what matters most, and makes the remaining trade-off understandable to the people who must authorize or experience it.

That approach is not a rejection of innovation. It is what makes innovation credible. People are more likely to support change when leaders can describe both the intended benefit and the burden that may remain.