How does Steve Huynh say engineers should write status updates that leaders actually read?

Steve Huynh recommends a short here's-what-you-need-to-know update with a plain subject line such as a project name, milestone and date, followed by three or four top-down bullets. The bullets should answer whether the next delivery is green, yellow or red, what the blockers are, and whether the reader's help is needed and by when. Low-level technical detail goes below a line marked as more detail, or is left out entirely.

• Huynh says over-communicating impactful work carries almost no penalty, because readers filter out what they do not care about.
• On a Prime Video project with nearly 100 engineering teams, Huynh sent a daily technical email to nearly a thousand stakeholders for about three months.
• Huynh says those emails contributed to his promotion to principal engineer, though he matches frequency to the stakes rather than making daily email a rule.

▸In their words

“People really only care about three things.” Steve Huynh · at 12:31 — open in the transcript →

Source: our own transcription of the episode. The full conversation is on A Life Engineered (2026-10-12). Read the whole episode summary →

▸More from this episode