Post 3 covered the structure of a useful update. This one is the field manual: how to take the thing you were about to send and turn it into signal before it reaches your manager.

The move is simple but not easy: convert activity into consequence.

Activity says what happened. Consequence says what changed, what it affects, and whether anyone needs to act.

Slack Example

Bad:

> Met with Data. They have concerns about the migration. Following up next week.

This creates work for the reader. What concerns? Does it matter? Are we blocked?

Better:

> Data flagged one migration issue: the customer table schema changed more than expected. Not blocked yet, but the current plan has a real risk of slipping by 1–2 weeks. I’m getting their revised estimate by Friday.

Now the manager can understand the state without interrogating you.

Excellent:

> Migration risk moved from “watch” to “likely slip.” Data found a schema mismatch that affects the customer table. If unresolved by Friday, launch probably moves 1–2 weeks. I’m testing whether we can split the migration and keep the core launch date. No decision needed yet; I’ll flag Friday if the split path fails.

This is useful because it names the shift, the consequence, the watchpoint, and the current owner.

Exec Update Example

Bad:

> The team is working hard on reliability improvements and has several fixes in progress.

Executives cannot use this.

Better:

> Checkout reliability is improving but still below the threshold we committed to. Current failure rate is 1.8%; target is below 0.5%. The remaining issue is concentrated in peak-load retries.

Excellent:

> Checkout reliability is the main launch risk. Failure rate is down from 4.0% to 1.8%, but we need below 0.5% before peak season. The remaining issue is peak-load retries. We can likely hit target with one more week of engineering focus; pulling that team onto the new promo work now would put the reliability target at risk.

The executive version connects technical progress to the business tradeoff.

A Useful Rule

If your update could be copied into a timesheet, it is probably activity.

If it helps someone understand the state of the work and act accordingly, it is communication.

Do the second one.