Government Leaders Don’t Need to Be Great Orators. They Need to Be Understood
Why the ability to explain complicated decisions clearly is one of the most undervalued skills in public administration
By Scott Webber, DrPH, MBA, MPA, MPH
I’ve spent more than two decades working in New York City government, and I’ve come to appreciate that some of the most consequential decisions begin with a relatively simple question:
Can you explain what you’re asking for?
It sounds straightforward. But anyone who has worked in a large government organization knows how difficult that can be.
A technology project may involve millions of dollars, multiple vendors, cybersecurity requirements, procurement regulations, budget approvals and operational dependencies. The person responsible for explaining it may have only a few minutes to make the case.
I’ve worked extensively in procurement, budgeting and public administration, where technical complexity is often unavoidable. But complexity doesn’t excuse poor communication.
A presentation can contain accurate information and still fail because the audience doesn’t understand the central issue.
I’ve increasingly come to believe that public speaking is not primarily about charisma, polished delivery or the ability to command a room.
It’s about helping people understand a problem well enough to make an informed decision.
And in government, that is a management responsibility.
The Best Public Speakers Aren’t Necessarily the Most Impressive
When people think about public speaking, they often imagine politicians delivering speeches, executives addressing large audiences or motivational speakers commanding attention.
Those skills have their place.
But most government communication is far less theatrical.
It’s a manager explaining why a contract needs to be renewed.
A budget analyst defending a funding request.
An engineer presenting alternatives for an infrastructure project.
A public health official explaining an emerging risk.
Or an agency representative responding to questions from elected officials.
The objective isn’t applause.
It’s understanding.
I’ve encountered plenty of complicated government issues where the most valuable contribution would be a clear, concise explanation of what was happening, why it mattered and what decision was required.
That doesn’t necessarily require an elaborate presentation.
Sometimes it requires three minutes and a well-organized argument.
A government leader who can explain a complicated problem simply has an advantage over someone who understands every technical detail but cannot communicate its significance.
Start With the Decision, Not the Background
One of the easiest mistakes to make during a presentation is beginning with too much history.
Government employees often feel compelled to explain everything that happened before the current issue arose.
We describe previous contracts, prior funding decisions, organizational changes, technical requirements and the sequence of events that brought us to the present.
Some of that information may be important.
But the audience usually needs to understand the decision first.
Consider a hypothetical presentation involving the replacement of an aging technology system.
One approach is to begin with the system’s history, technical architecture, procurement challenges and previous maintenance arrangements.
Another is to begin:
“We need approval to replace a critical system before manufacturer support expires. Continuing with the existing equipment creates an increasing risk of service interruption. We’ve evaluated three alternatives, and the recommended option has the lowest projected five-year cost while meeting our operational requirements.”
The second approach establishes the issue immediately.
The technical details can follow.
In my work overseeing IT procurement and budgeting at the New York City Department of Correction, I frequently deal with matters that require substantial background analysis.
But the work involved in reaching a recommendation shouldn’t be confused with the information an audience needs to evaluate it.
The speaker’s responsibility is to do the analytical work before the meeting—not require everyone in the meeting to repeat that work.
Numbers Need Context to Become Meaningful
My background in finance and budgeting has also influenced how I think about presentations.
Numbers can be persuasive, but only when the audience understands what they represent.
Suppose an agency proposes spending $4 million on a technology modernization initiative.
Is that expensive?
The answer depends on what the agency is purchasing, what alternatives exist, how long the investment will last and what consequences might result from doing nothing.
A $4 million project that replaces several unsupported systems and reduces substantial recurring maintenance costs may be financially attractive.
A $4 million project that duplicates existing capabilities and creates additional annual expenses may not be.
Simply announcing the price doesn’t establish value.
I believe financial presentations should distinguish among acquisition costs, recurring operating expenses, anticipated savings and risks.
They should also distinguish cash savings from productivity improvements.
If a new system saves employees 5,000 hours annually, that may represent a substantial operational benefit. But unless the agency reduces expenditures or avoids additional costs, those hours shouldn’t automatically be described as budget savings.
Credibility depends on explaining those distinctions.
The same applies when discussing percentages.
A projected 20% improvement sounds impressive, but the audience should understand the baseline, the measurement period and the assumptions behind the estimate.
Good public speaking doesn’t make numbers sound bigger. It makes their meaning clearer.
Know Who Is Listening
An effective presentation to a technology team may be ineffective when delivered to a budget office.
A presentation appropriate for agency leadership may require substantial revision before being delivered at a public hearing.
Different audiences have different responsibilities.
Technical employees may need to understand system architecture, integration requirements and operational dependencies.
Budget officials may focus on affordability, funding sources, alternatives and recurring obligations.
Agency executives may be primarily concerned with mission impact, implementation risk and timing.
Members of the public may reasonably want to know how a proposal will affect their lives.
The underlying facts should remain consistent.
What changes is the emphasis.
In government, this is especially important because decisions frequently require cooperation among people with very different professional backgrounds.
A technically sound recommendation can encounter unnecessary resistance when presented without regard to the audience’s concerns.
I don’t view adapting a presentation as manipulating the audience.
I view it as respecting the audience’s responsibilities.
The goal should be to provide people with the information they need—not simply the information the speaker finds most interesting.
Public Speaking Is Also an Exercise in Accountability
Government communication carries obligations that don’t necessarily apply in the private sector.
Public officials and employees may be explaining decisions involving taxpayer money, statutory responsibilities or services affecting vulnerable populations.
That creates a responsibility to communicate accurately, including when the facts are inconvenient.
I believe a government representative should be comfortable acknowledging uncertainty.
If a project has significant risks, identify them.
If the financial assumptions are preliminary, explain that.
If an implementation date depends on a procurement or regulatory approval, don’t present it as guaranteed.
And if someone asks a question you cannot answer reliably, say so.
There is nothing inherently unprofessional about acknowledging that additional information is required.
What’s damaging is confidently presenting information that later proves inaccurate.
I’ve found that the credibility of an argument often depends as much on what the speaker acknowledges as on what the speaker advocates.
A presentation that fairly addresses competing considerations is usually more persuasive than one that pretends no reasonable objections exist.
Public confidence isn’t built by making every government decision sound perfect. It’s built by explaining decisions honestly and demonstrating that legitimate concerns were considered.
The Most Important Part of a Presentation May Be the Questions
A prepared presentation allows the speaker to organize information in advance.
Questions reveal whether that information has been understood.
They also expose assumptions that may not have received sufficient attention.
Why can’t the existing contract be extended?
What happens if funding is delayed?
Could another agency’s system meet the same need?
What are the consequences of selecting a less expensive alternative?
These are precisely the kinds of questions that can improve government decisions.
I believe managers should anticipate difficult questions rather than regard them as interruptions.
Before presenting a major recommendation, I would encourage employees to identify the strongest arguments against their own proposal.
If the recommendation is sound, it should withstand reasonable scrutiny.
If it cannot, the analysis may need more work.
This is particularly important when presenting vendor proposals.
A vendor may emphasize the benefits of its product while minimizing implementation challenges or long-term costs.
Government employees should be prepared to explain both the proposed benefits and the limitations.
We owe that level of diligence to the agencies we serve.
A Five-Part Framework for More Effective Government Presentations
I would encourage public-sector managers to organize consequential presentations around five elements.
1. State the issue. Explain the problem in one or two sentences. Establish why the audience should care and whether a decision is required.
2. Present the evidence. Use the most relevant facts, financial information and operational considerations. Distinguish verified information from assumptions.
3. Explain the alternatives. Identify realistic options, including maintaining the status quo when appropriate. Compare cost, risk, timing and expected outcomes.
4. Make a recommendation. Explain why the preferred approach offers the best balance of public value, affordability and operational feasibility.
5. Define the next step. Specify what approval, funding, direction or action is needed, who is responsible and what happens afterward.
For a complicated proposal, the supporting documentation may run dozens of pages.
But the central argument should still be understandable in a few minutes.
I would also encourage employees to rehearse presentations with colleagues unfamiliar with the subject.
If an intelligent colleague cannot explain the central recommendation after hearing it, the presentation probably needs improvement.
And if the speaker cannot summarize the issue without relying on slides, that may indicate the argument hasn’t been sufficiently organized.
We Should Develop Public Speaking Skills Throughout Government
Public speaking shouldn’t be treated as a skill reserved for commissioners, elected officials or senior executives.
Analysts, procurement professionals, engineers, supervisors and program managers all benefit from communicating effectively.
An employee who can present a well-supported recommendation is better positioned to contribute to organizational decisions.
A supervisor who can explain expectations clearly may prevent misunderstandings and improve performance.
An analyst who can communicate financial findings without unnecessary jargon can help leadership make better use of data.
I believe government training programs should place greater emphasis on practical communication exercises.
Employees could practice delivering concise budget presentations, defending procurement recommendations or explaining technical issues to nontechnical audiences.
Managers could provide feedback on organization, clarity, factual support and responsiveness to questions.
The goal wouldn’t be to turn every employee into a polished keynote speaker.
It would be to help employees communicate their expertise effectively.
That’s a professional development investment with applications across nearly every government function.
The Real Measure Is What Happens After You Speak
After more than two decades in public administration, I’ve become convinced that the ability to communicate clearly is inseparable from the ability to manage effectively.
Government decisions are rarely made in isolation.
They require coordination among people responsible for budgets, legal compliance, technology, operations and public accountability.
Each participant brings different expertise.
Progress depends on making that expertise understandable to others.
I’ve earned advanced degrees in business administration, public administration and public health, and I value the analytical perspectives those disciplines provide.
But an important part of applying that knowledge is communicating it in terms that other people can use.
A sophisticated financial analysis has limited value if decision-makers cannot understand its conclusions.
A sound procurement recommendation accomplishes little if leadership doesn’t understand why it matters.
And a worthwhile public policy may struggle if government cannot explain its purpose to the people it is intended to serve.
The best government presentations aren’t necessarily the ones people remember because the speaker was impressive. They’re the ones that help people make better decisions.
We should spend less time worrying about whether public employees sound like professional speakers and more time ensuring that they can explain complicated issues accurately, concisely and persuasively.
Because in public administration, communication isn’t simply about delivering a message.
It’s about turning knowledge into informed action.
Government doesn’t need more impressive presentations. It needs more presentations that make government work better.
The views expressed in this article are my own and do not necessarily represent the positions of the New York City Department of Correction or the City of New York.
