Why “plain” matters in public leadership

Welcome. This series is written for you. It is meant to support reflection, insight, and growth. It is written for people who care about how decisions are made, how government works, and why good intentions so often fall short.

My aim is simple. To explain public work plainly, without jargon or doublespeak. To share what experience teaches when theory runs out. Bad actors, and evil intentions do not cause most failures in public leadership. They are caused by fear, uncertainty, and doubt. The result? Obfuscation, a lack of transparency, and language that hides reality. In large organizations, especially public ones, we develop a habit of speaking around problems instead of about them. We use careful phrases, layered explanations, and policy-safe wording. Over time, this creates distance between what is, what could be, and what is being said. That distance is where trust erodes, and the ‘Why’ of Simon Sinek is missed. Plain language is not about dumbing things down. It is about discipline, trust, and acceptance. It forces leaders to name the actual problem before proposing a solution. It brings appropriate criticism from stakeholders. It ensures decisions are forged in the fire of democracy. When language becomes vague, accountability becomes optional. The complexity of government and public opinion encourages this drift. There are many stakeholders, real constraints, legal boundaries, and political risks. Plain speech can feel dangerous because it removes cover. Saying “this is not working” is harder than saying “we are continuing to evaluate outcomes.” But only one of those statements is true. I have seen teams work themselves into circles trying to produce the right words instead of the right outcome. Meetings become about alignment rather than action. Documents are written to survive review instead of to drive change. Do we truly understand the problem if we are unwilling to describe it plainly? The cost shows up in small ways at first. Delays become normalized. Workarounds replace fixes. Frontline staff stop offering input because they know it will be translated into something unrecognizable. Eventually, the public senses the gap between what is promised and what is delivered. Plain language restores a connection between responsibility and reality. It gives teams permission to focus on what matters instead of what sounds acceptable. It also signals respect. People can handle the truth. What they struggle with is ambiguity, false measures, and marketing presented as progress. This series is called In Plain Service because public work deserves plain words. Not slogans. Not performance. Not meatball charts, Not red light, yellow light, green light dashboards. Just an honest account of how government works, where it fails, and what it takes to make it better. Thank you for joining me. - Leland



Comments

Popular posts from this blog

Breaking the Bottlenecks: Information, Access, and the Fight for Time ACRD 2026 Annual Conference Keynote: Kissimmee, Florida

The McDonaldization of the Social Security Administration

Obfuscation Is Not Security