How long should an all-hands update be?

The leadership update itself is often best kept to 10 to 15 minutes, leaving time for questions.

Should a leader read an all-hands update?

Script the key messages so they are clear and accurate, then deliver them naturally, ideally from a prompter rather than looking down at notes.

Should leaders share bad news in all-hands?

Yes, clearly and early. Teams trust leaders who are direct about challenges.

How to Script an All-Hands Update Leaders Actually Listen To

A practical structure for leadership all-hands updates, live or recorded, that are clear, honest and short, with an example script and delivery tips.

All-hands meetings, live or recorded, are often the main way leaders speak to the whole company. Too many turn into long slide reviews that people half-watch while answering email. A clear, honest, well-structured update earns attention.

A simple structure

Headline: the one thing people should take away.
Where we are: a short, honest status.
Wins: two or three, with thanks to specific teams.
Challenges: what is not going well and what you are doing about it.
What is next: priorities for the coming period.
Ask: what you need from the team.
Questions.

Lead with the headline

Do not save the main message for the end. Start with it:

If you remember one thing from today, it is this: we are pausing two projects so we can finish the platform migration by March.

Then explain.

Be honest about challenges

Teams notice when updates only include good news. Naming a challenge directly, and what you are doing about it, builds trust far more than a polished story.

Thank specific people

"Thanks to everyone for their hard work" is forgettable. "Thanks to the support team, who cut response times in half this quarter" is meaningful and motivating.

Keep numbers simple

Show one or two key numbers, explained clearly. Long slides of metrics lose people.

Recorded updates

Many leaders now record updates for distributed teams. Short, recorded updates of five to ten minutes can work better than long live meetings. Our guide to async video updates for teams covers formats.

Delivery

Script key messages so wording is precise.
Read from a prompter near the camera, so you look at the team rather than down at notes.
Slow down for important points.
Pause before and after the headline.

See how to sound natural reading a script.

Keep sensitive drafts private

Leadership updates sometimes contain information not yet public, such as reorganisations or financials. Drafting in a tool that keeps scripts on the device reduces the risk of early leaks. Cue has no account or cloud sync. See offline teleprompter privacy.

Leave room for questions

Questions are often the most valuable part. Collect them in advance as well as live, and answer the hard ones directly.

End with the ask

Finish with what you need from people this month. A clear ask turns an update into action.