12. Communicate More When Things Are Unclear¶

During a product-stability crisis, a different pressure was building.

The app experience had started degrading in ways the business could feel but the team could not yet fully explain. Some flows were unstable. Some fixes created new uncertainty. The visible symptom was delay and inconsistency. The hidden cause could have been tech debt, unclear ownership, capacity mismatch, or all three at once.

The update went out before anyone had the full picture.

No confirmed root cause. No clean timeline. No fix in hand. The message went anyway, because the alternative was silence, and silence in a crisis does not stay empty.

What the update said was narrow on purpose. Here is what we know. Here is what we do not know yet. Here is who is checking which piece. Here is who owns which thread of the investigation. Here is when the next update will come.

Nothing in that message projected confidence the team did not have. The goal was not to reassure. The goal was to stop silence from writing a story worse than the truth.

The CEO pushed back.

The push was for more aggression. Faster movement.

I did not resist this. I just defined it.

"I agree we need to be more aggressive. But I want to make sure we are aggressive against uncertainty — not against the team."

That reframe is what mattered. Aggression against uncertainty looked like this: shorten the diagnosis cycle. Assign clearer owners. Escalate blockers faster. Cut unnecessary scope. Move in smaller recovery steps. Commit to the next update at a specific time, even if the answer is still incomplete.

That version of "faster" the team could actually use.

The other version — pressure pushed downward without clarity — would have produced motion without progress. People moving harder, not thinking better. The team absorbing heat instead of working the problem.

The consequence of the reframe was practical. Leadership could see urgency without needing to chase it. The team could investigate without absorbing blind pressure from above. The issue stayed framed as a recovery process, not a blame session.

That is the discipline I want to talk about in this chapter.

Reducing uncertainty in public while solving the problem in private.

What bad leadership usually does¶

There are two default moves in this situation. Both feel responsible. Both make the situation worse.

The first is the silence move.

Wait until you have the full picture before communicating. The intention here is not laziness. It is good. People want to be accurate. They do not want to put out an update that turns out to be wrong. So they wait.

But silence does not stay empty.

When no update arrives, people fill the vacuum with their own story. Leadership starts assuming the team is passive. The business starts assuming tech does not care. The technical team feels pressure building from outside, because they are working hard and nobody can see the work happening.

Then the conversation shifts. It stops being "what is the problem and how do we fix it?" It becomes "why is nobody handling this?"

The actual issue may be technical. Silence turns it into a trust issue.

By the time the update finally arrives, the leader is managing two problems. The original one. And the perception damage created by the silence. The second problem did not exist until communication stopped.

The second default move is the theater move.

When the layer above pushes for speed, the leader transmits the pressure straight downward. Tell the team to move faster. Look decisive upward. Create chaos downward.

This looks like leadership. It is not. It is just a transmission belt for panic. The team gets more pressure but no additional clarity on what to do with it.

That is aggression against the team. Not aggression against the problem.

The principle¶

In uncertainty, silence creates assumptions.

A leader's job in a crisis is not to hold communication back until the picture is complete. The job is to send structured, honest, incomplete updates often enough that the people around the problem stop inventing their own versions of it.

Incomplete and honest beats complete and late.

Why it matters¶

Stakeholders do not wait neutrally. They never have. They fill the gap with fear, frustration, or blame.

If we let the gap exist, we are not protecting accuracy. We are paying for our delay with someone else's anxiety.

When that anxiety reaches the team, it does not arrive as useful information. It arrives as blind pressure. People work harder without working smarter. They stop raising risk because raising risk now feels like adding to the bad news. They start filtering what they tell the leader, because they can feel the heat coming from above and they do not want to be the one carrying it.

Then the leader stops getting the truth.

That is when the original technical problem becomes a leadership problem. Because the leader can no longer see the actual situation through the noise that silence created.

The cost is compounding. Every hour of silence does not just hold the gap open. It widens it.

What better leadership looks like¶

A leader in a crisis communicates more, not less.

Not with fake certainty. Not with reassurance language. The update should sound like a status report from inside the work, not a press release.

What better looks like is concrete. Send the update before you have the full answer. Name the unknowns explicitly. Say who owns each thread. Commit to the next update at a specific time, even if you already know the answer at that time will still be partial.

Then keep that commitment.

For me, the strongest crisis line is not "we are fixing it." Everyone says that. The stronger line is: here is what we know, here is what we do not know yet, here is who owns the next step, and I will update you again at this specific time.

That sentence does more work than three meetings.

It tells leadership the situation is held. It tells the team what shape the communication will take, so they can plan around it instead of being interrupted for status. It tells stakeholders the next data point is coming, so they do not need to chase.

That is what reducing uncertainty in public actually looks like. Not spin. Not message control. A cadence honest enough that nobody around the problem needs to invent their own version of it.

The tool — Two-tier communication discipline¶

This is not a template. It is a standard.

In the first few minutes of a crisis, do not start with a heavy formal format. Default to a 5-field minimum.

5-field minimum — first response

What happened
Who or what is affected
What we are doing now
Who owns it
When the next update will come

That is enough to break silence. It can be sent in five minutes. It does not require a complete picture. It just requires honesty about the picture you currently have.

If the issue continues, becomes serious, or becomes visible to leadership, expand into the full 7-field format.

7-field full format — serious or CEO-visible

Situation
Impact
Current action
Owner
Unknowns
Risk
Next update

The threshold for moving from 5 to 7 is simple. If the issue has stopped being contained inside one team, expand the format. If executives are watching, expand the format. If the recovery will take longer than the time between two updates, expand the format.

The discipline underneath both tiers is the same.

Never send vague reassurance.
Never hide unknowns.
Always give the next update point at a specific time.

The third one is the one most leaders skip. They send a status, but leave the next checkpoint open. That is how an update accidentally becomes a closing statement, and the silence comes back.

A specific next time, named in the message, is what keeps the cadence alive.

Simple rules¶

Send the update before you have the complete answer.
Name the unknowns explicitly. Do not soften them.
Assign owners to each thread of the problem in the message itself.
Commit to the next update at a specific time, not "soon" or "shortly."
Keep the commitment, even if the only thing you can say is that the situation has not changed.
When the layer above pushes for speed, define what speed means before transmitting it.
Aggression goes against the uncertainty, not against the people working the problem.

Reflection questions¶

In the last crisis I led, how long did silence last before the first update went out?
Did I name unknowns clearly, or did I cover them with general language?
When I committed to a next update time, did I keep it?
When pressure came from above, did I redefine it before passing it down — or did I just pass it down?
Did my last crisis update help the team focus, or did it add noise to what they were already carrying?
Is the cadence I run during a crisis predictable enough that people stop chasing me for status?

Reminder¶

I will update you again at this specific time, even if the answer is still incomplete.