Most updates fail the same way: they describe what happened without explaining what it means. They are activity reports dressed up as communication.

Your manager doesn't need to know everything you did. They need to know what changed, what matters, what risk is live, and what decision — if any — is needed from them. That's the anatomy of a useful update. Everything else is noise.

A good update should let your manager do three things quickly: preserve context, adjust priorities, and intervene only where their authority or perspective actually helps.

The Anatomy of a Useful Update

1. What changed since last time.

Not what you did — what is different now. A new dependency emerged. A timeline shifted. A risk materialized or receded. Your manager can read a status report anywhere. What they can't generate on their own is your read on what just shifted.

2. What the current state actually is.

Not "we're on track" or "we're on track but with some risks." Be specific. If there's a 30% chance the launch slips by two weeks, say that. Uncertainty described precisely is useful. False certainty is expensive.

3. What risk is live.

If something could go wrong in a way that materially affects outcomes, it belongs in the update. Not as a vague worry — as a defined risk with a likely consequence and an indicator you'd watch. "The vendor might miss the deadline, which would push the launch to October. The indicator is whether we get the first draft by Friday."

4. What decision is needed — if any.

Updates that require action should say so explicitly. "We need to decide whether to proceed with the current scope or cut feature X to hit the Q3 date." Don't make your manager infer what you need from context. Name the owner, deadline, and consequence of waiting.

5. What you recommend.

Updates that include your recommendation — even when you're not sure — are more useful than updates that just describe. Your manager doesn't expect you to have all the answers. But they expect you to have thought about the problem. Recommendations, even tentative ones, show that.

When to Send It

Cadence matters as much as content. Sending updates too frequently trains your manager to ignore them. Sending too rarely creates information gaps that close with surprises.

The right cadence depends on velocity and risk. In a stable, low-risk stretch: weekly is fine. When something is in flux or a key decision is pending: more often, with more specific framing. When in doubt, err toward slightly more frequent — but make each update worth reading.

And if nothing significant happened since the last update: say that explicitly. "No material changes since last week" is a complete update. It signals that you're on top of things and there's nothing new to track. A filler update with nothing behind it trains bad habits — and wastes everyone's time.