When Words Get Ahead of the Work

When something big breaks, people check the explanation against what they can see. The US did that all week. Your staff does it to you every day.
Seven big systems went down in six days this month, from Microsoft's email to the FAA to the NSA. Officials say nobody attacked us and none of it is connected. Maybe that’s true? We (the public) don’t know.
What I know is that many of us made our minds up anyway. We compared what officials said up against what they did - both in this instance and before. I've used that same tool on organizations for years.
Think, say, do
Every organization has three things going at once: what it believes, what it says, and what it does. When two of them match, I call that aligned. When all three match, that's structural integrity.
From outside, you can't see belief. You can only get a sense of what’s said and done. If they match each other and whatever they say they believe, you move on. If they don't, you guess at a belief that makes sense, and that tends to mean you’re weighing what they do more heavily than what they say.
The FAA's week
What they said
Friday: old equipment failed.
Saturday: a new router, installed during an upgrade, caused it.
Sunday: security agencies say it wasn't an attack.
What they did
Asked the FBI to send agents to help examine the router.
Pulled a second router for testing.
Switched off a feature on about 60 similar routers.
Paused new installs nationwide.
The announcement sounded confident. But they didn’t match what was actually happening - because the investigators were still investigating. The actions were good ones... what we’d hope a careful agency would do if they weren’t certain.
It’s the gap between what was said and done that did the damage. Once the story changed, the early words looked false when they may have just been an early impression delivered before it was ready. From outside, those two look the same.
On Monday the Transportation Secretary admitted, "we don't have clarity yet." For the first time all week, the words and actions matched.
Why it happens
The cameras want an answer in hours, but investigators need weeks. So the first answer goes out early and sounds certain, because uncertainty can (and does) read as weakness in the administration.
This administration has made a habit of saying things quickly. The FBI Director twice said that a suspect in a shooting was in custody, and both times the person was let go. Homeland Security officials described a fatal shooting in Minneapolis in terms that video proved wrong.
Every early answer that isn’t clearly labeled a guess will erode trust. When enough of them go bad, people stop distrusting just the claim, and begin to distrust the speaker. After that, even a true "this wasn't an attack" gets interpreted as an admission that it was.
You've seen this at work
A product ships with a defect, and leadership tells the sales team it's an isolated case. That same week, the quality team pulls three months of units for inspection. The inspection is the right call. "Isolated" was the mistake, because the reps can see the pallets coming back.
Your people can't see your beliefs. They watch what you do, and they act accordingly.
What I'd tell them
Say what you're doing. "We've asked the FBI to check our work, we've shut off the feature on 60 routers, and we don't know the cause yet." People will read your actions anyway, so put them in the statement.
Let "we don't know yet" be an answer. Add when you'll speak next. It costs less than a guess you have to take back. (Though I’ll acknowledge that the boss might not take it well.)
Check the words against the work. If the statement says "contained" while the team has barely investigated anything, make the words match reality before anyone talks.
Was it an attack? I still have no clue. But I do know that announcing “we don’t know yet” on Friday would’ve earned more trust than all three statements claiming that they did.


