📢 How I Keep Leadership Updated Without Spamming Them

Executives want clarity.

But too often, updates feel like noise:

• 4-paragraph emails nobody reads

• Weekly status docs buried in attachments

• Decks that take longer to build than the project itself

At Amazon, I’ve learned:

Leaders don’t want more info—they want sharper info.

🔁 This Week’s Sync

1 Quick Insight from the Field:

Last week, I had to update a VP on a project slipping two weeks.

Instead of sending a 10-line email or attaching a doc, I wrote a 3-line update in Slack:

“Flagging: workflow launch moving from 6/15 → 6/29.

Cause: dependency on Privacy review.

Next step: Legal review this Friday; will confirm if new date holds.”

Her reply? Just:

“Crystal clear—thank you.”

That’s the bar: short enough to skim on a phone, clear enough to forward.

🧰 1 Repeatable Framework or Tactic

The 3-Line Leadership Update Formula:

1/ State the fact

→ “Launch moved from 6/15 → 6/29.”

2/ Give the reason

→ “Dependency: Privacy approval pending.”

3/ Say what’s next

→ “Review scheduled Friday; will update by EOD.”

That’s it.

No fluff.

Just signal.

Why it works:

→ Easy to read on mobile

→ Easy to forward to others

→ Builds credibility that you respect their time

⚡ 1 Challenge to Make You a Sharper Operator

Next time you owe leadership an update, cut it to 3 lines.

Fact. Reason. Next step.

You’ll get faster responses—and more trust.

See you next Sunday,

— Brett

🚀 Want more tactics like this? Subscribe to The Weekly Sync—real-world execution advice for PMs, delivered every week.

No fluff. Just frameworks, systems, and lessons from inside Amazon.