# Earning and defending stakeholder trust under public scrutiny
In October 2013, the federal health insurance marketplace at HealthCare.gov launched and promptly crashed. Millions tried to enroll. Most could not. The site was designed to handle far fewer users than showed up, and the failures were public, immediate, and humiliating. Confidence in the entire program cratered before anyone could enroll.
The technical failure was fixable within weeks. The trust damage lasted years.
That gap, between fixing the thing and repairing belief in the thing, is the core problem of public sector marketing. You are not selling a product. You are asking skeptical people to keep believing that their money and your promises are safe.
A private company that loses a customer's trust loses a customer. A public agency that loses trust still has to serve that person, and that person still has to pay taxes for the service. Nobody gets to walk away.
Three audiences watch you at once, and they do not want the same thing:
A "watchdog" here means any external party whose job or mission is to scrutinize your performance. An inspector general (an independent official who investigates waste and fraud inside government), an investigative reporter, and a nonprofit ratings site are all watchdogs.
You cannot market past these audiences. You market through them.
Most agencies treat transparency as damage control: something you do after a reporter files a records request. That is reactive, and it always looks like you got caught.
Proactive transparency flips this. You publish the uncomfortable numbers before anyone asks.
Before launch, state publicly what success looks like and how you will measure it. This is a "pre-commitment": you lock in the standard while you still have credibility to spend.
Example: a city rolling out a new 311 service line (the non-emergency phone and app system residents use to report potholes, noise, or missed trash pickup) says up front: "We aim to resolve 80 percent of requests within five business days, and we will post the actual number every month, good or bad."
Now the metric belongs to the public. When you hit it, you get credit. When you miss it, you already framed the conversation as "here is our progress" rather than "here is what they hid."
Open performance dashboards are now a baseline expectation, not an innovation. Many governments run them. See the U.S. General Services Administration's Performance.gov for how federal agencies present goals and results in plain language.
The marketing lesson is not the software. It is the posture: we show our work continuously, so no single bad month becomes a scandal.
Skeptical audiences discount your claims automatically. So the way you phrase an outcome matters as much as the outcome itself.
Define two terms clearly:
Agencies love reporting outputs because outputs are easy to count and always sound busy. Taxpayers do not care how many workshops you held. They care whether anyone got a job.
Lead with the outcome. Use the output only as supporting evidence.
Weak: "The program delivered 1,200 service hours across the county."
Strong: "Wait times for benefits appointments dropped from three weeks to four days. We did it by adding 1,200 service hours."
The fastest way to lose a skeptic is to oversell. If your outcome has caveats, say them plainly.
Example: "Early results are promising, but this covers only the first six months and one region. We will know more after a full year."
Counterintuitively, admitting uncertainty makes the rest of your claims more believable. You sound like someone reporting reality, not spinning it.
Public audiences translate everything into "what did this cost me." So do the translation for them.
Instead of a $4.2 million budget line, try: "This program costs about the price of one coffee per resident per year." Anchoring an abstract number to something human is standard marketing practice, and it works especially well when the underlying spending is defensible.
Only use this when the math is honest. If a watchdog can redo your arithmetic and get a worse story, do not do it.
Every program eventually stumbles. Trust is defended in how you respond, not in pretending it will not happen.
When something breaks publicly, silence reads as guilt or incompetence. You do not need full answers in hour one. You need to show you know it is happening and you are on it.
A usable structure for a first statement:
1. Acknowledge: "We are aware the enrollment site is down."
2. Own your part: "This is our responsibility to fix."
3. Say what you are doing: "Our team is working on it now."
4. Commit to an update: "We will post the next update by 5 p.m."
Then hit that 5 p.m. deadline even if the only news is "still working." Missed update deadlines cost more trust than the original problem.
The HealthCare.gov team, to its credit, eventually stopped explaining the technology and started saying plainly that it was fixing the site and setting deadlines. What never works: implying users caused the problem, or that the demand was somehow unreasonable. In the public sector, "too many people wanted our service" is not a defense. It is your job.
Knowledge check
1. The HealthCare.gov launch illustrates a core principle of public sector trust. Which statement best captures that principle?
2. Why is losing stakeholder trust fundamentally different for a public agency than for a private company?
3. The excerpt argues you 'market through' watchdogs rather than 'market past' them. What reasoning underlies this claim?
4. Select ALL correct answers. What distinguishes proactive transparency from reactive transparency as described in the lesson?
Select all the correct answers.
5. Select ALL correct answers. Which needs correctly match the audiences watching a public agency?
Select all the correct answers.
Put the pieces together into a repeatable message framework. Use this before any launch, report, or crisis.
1. What did you promise? (Restate your pre-commitment.)
2. What actually happened? (Outcome first, with honest caveats.)
3. What did it cost? (In human terms, honestly calculated.)
4. What happens next? (Concrete, dated commitments.)
If your communication answers all four, a watchdog has far less room to build a "gotcha" story, because you already told the whole story.
The facts stay identical for everyone. The emphasis shifts.
Telling different stories to different audiences is where agencies get destroyed. If the board hears one number and the public hears another, that gap becomes the headline. One set of facts, three framings.
Ask your team: "If a hostile reporter got everything we know, and everything we are saying publicly, could they write a 'coverup' story?" If yes, you are hiding something, and you should publish it yourself first, on your terms.
Some agencies carry earned distrust from past failures. You cannot message your way out of that quickly. You rebuild it the slow way: make small, specific, public promises, and keep them visibly over time.
A parks department that broke promises for years does not restore trust with a campaign. It restores trust by saying "the north playground reopens April 15," reopening it April 15, and posting the photo. Then doing it again. Reliability compounds. It is boring, and it is the only thing that works.