Skip to content
Leadership Advanced 4 min

No News Is Good News: Leading With Trust, Not Status

Daily status updates feel like control but teach a good team to perform progress instead of raising problems. Default to trust; invest in signals that surface the exceptions.

By Victor Robin •

The problem

Status-chasing feels like control and quietly corrodes a good team. Ask for a daily update and people don’t just report — they perform: padding ordinary in-progress work with caveats so nothing can later be read as a slip. You wanted visibility and you built a daily exam.

I did it three weeks out from a migration deadline. A short written status each morning — finished, doing, blocked; three bullets, ten minutes. By the second week the migration was no further along and the updates had gone careful and defensive. The tell came in a retro: “I figured if something was really wrong, you’d see it in the standup doc.” People had stopped raising problems directly because they assumed the ritual would surface them. It surfaced nothing; it just made everyone narrate progress.

The model

The default should be trust: assume things are fine unless someone raises a flag, then spend your energy making flags easy to raise and impossible to miss. No news is good news — but only if “news” reliably travels. Status-chasing is the tax you pay for missing trust and missing visibility, and the people who pay it are the ones doing the work. Autonomy isn’t the absence of oversight; it’s oversight relocated out of meetings and into signals, so a person can own an outcome end to end and trust the system will say so if it goes sideways.

What to do

  • Kill the standing status update, with no replacement ritual. Silence has to be allowed to mean “fine,” or trust-by-default is just a slogan.
  • Move oversight into signals. Let the state of the work live where the work lives — a board, a dashboard, the deploy pipeline. If you want to know where things stand, look; don’t make a person assemble it for you.
  • Make escalation explicit. Agree on what actually warrants a flag — a slipping date, a blocked dependency, a decision you must own — so people know exactly when to interrupt you, and know silence between those moments is genuinely fine.
  • Take 1:1s back from status. Use them for growth, friction, and the things people would never put in a written update.

The results

Everyone got roughly an hour a day back, but the time was never the real win. Over a few months the careful, defensive language faded, and people began bringing me problems earlier — while they were still cheap to fix — because raising a flag no longer felt like admitting to a failed exam. The migration after the one that scared me shipped with no status ritual at all, and it was the calmest delivery I’d run.

The caveat: trust-by-default has a failure mode, and I hit it. A quiet, long-running exploratory task drifted badly off course with no flag and no signal, because nothing was instrumented to watch it — silence meant “fine” right up until it didn’t. The lesson wasn’t to bring back status updates; it was that trust-by-default only covers the work your signals can see. For anything genuinely novel or unmeasured, I now set one explicit, lightweight check-in up front — not to monitor the person, but to admit the system can’t yet watch that corner for me.

Further reading