Staff Meeting: What It Is, How Often to Hold It, and How to Run It

A staff meeting is the regular check-in where a manager and their team look back at results, share what others need to know and agree on what comes next. It is not a managers meeting, where team leads meet each other: here one manager meets the people they lead. Below: the definition, purpose, frequency, topics, a ready meeting format, and what to record.

What is a staff meeting?

A staff meeting is a recurring meeting where a manager and the people who report to them review results, share updates, and agree on priorities for the next week or month. Those people are the manager's direct reports. The Collins English Dictionary defines the term more broadly: a meeting of the people who work at a company, school or similar organization to discuss how it is run.

Other names for a staff meeting

A staff meeting also goes by team meeting, employee meeting, department meeting, "weekly staff" or team huddle. A team huddle is the short version, often daily and held standing up. An all-staff or all-hands meeting covers the whole company instead.

Work meeting vs working meeting

A work meeting is any meeting held for work; a working meeting, or working session, is one where people do the work together during the call instead of reporting on it. Other words for a work meeting: business meeting, check-in, sync. A staff meeting is a work meeting; editing a document together or fixing a bug on screen is a working meeting. If your staff meeting keeps turning into one, split that work off.

What is the purpose of a staff meeting?

A staff meeting exists to keep everyone on the same priorities: look back at results, share what others need to know, and surface the decisions the team has to make next. Kim Scott, author of Radical Candor, gives a staff meeting three goals in her 3+3 formula:

1. Review how the previous week went.
2. Let people share important updates.
3. Clarify the most important decisions and debates for the coming week.

On large teams, she moves those decisions to separate meetings with their own owners.

A good staff meeting also does work for the team:

• Employee recognition: wins get named in front of peers, which supports morale.
• Accountability: people stay accountable by reporting against last week's commitments.
• Shared context: everyone, including people at home, hears the same news at once.
• Feedback from the team: the manager hears what's blocked or unclear early.

As the one leadership moment the whole team sees together, the staff meeting also shapes team culture.

How often should you have staff meetings, and how long should they last?

Hold a staff meeting once a week for half an hour to an hour if you manage one team; for a department of 20+ people, a monthly meeting plus weekly check-ins inside smaller teams works better. These are editorial recommendations, not research data:

The 20-person line follows Kim Scott, who moves decisions to separate meetings past about 20 people.

A work meeting has no standard length: book a staff meeting for the time in the table and end it a little early, so people get a break before the next call. Google Calendar's Speedy meetings setting, under Event settings, does this for you: a 30-minute event ends 5 minutes early and an hour-long one 10 minutes early, as Google describes it.

What to discuss in a staff meeting: topics and ideas

A staff meeting should cover the few things that need the whole team: results against goals, wins worth recognizing, priorities for the next period, blockers that need someone else's help, and announcements. Eleven meeting topics work as standing items:

1. Results against goals.
2. Wins and kudos, each with a name attached.
3. Priorities for the next period, ranked.
4. Blockers that need someone else's help: a problem-solving slot, not a status line.
5. Dependencies on other teams.
6. Changes to processes, tools or policies.
7. Customer feedback: a quote, a complaint, a request.
8. Deadlines, launches and time off.
9. A short learning slot: one person teaches a tool or a lesson.
10. Open questions from the last staff meeting.
11. Announcements that need discussion; the rest go out in writing.

Ideas for the first staff meeting of the year

The first staff meeting of the year works as a reset: look back, set direction, and agree on how the team will meet.

• Review last year: three wins and three lessons.
• Name three priorities for the year: strategic planning on one slide.
• Refresh meeting norms: start time, written updates, cameras.
• Mark key dates: launches, peak seasons, holidays.
• Ask each person for one goal for the quarter.

For a new manager's first team meeting, replace the review with two questions for each person: "What should I keep?" and "What should change?"

Ideas to keep staff meetings engaging

A staff meeting keeps engagement up when team members run parts of it instead of only listening.

• Rotate the facilitator every week.
• Open with an icebreaker question, such as "What's one thing you learned this week?"
• Run a recognition round: each person thanks someone by name for something specific.
• Ask for "one thing I need help with" and match helpers on the spot.
• Split into pairs for brainstorming on one question, then share each pair's best idea.
• Once a quarter, ask what to drop, keep or add in this meeting, in a shared document or an anonymous survey, then change one thing.

Save longer team building activities for a separate session.

How to run a staff meeting: a 60-minute format

Run a staff meeting in three moves: collect updates in writing before the meeting, spend the live time on metrics and decisions, and end by confirming who owns each next step.

Before the meeting:

1. Share the meeting agenda early. GitLab's handbook page on all-remote meetings says agendas should be shared 72 hours in advance, 24 hours at minimum. Write agenda items as questions, each with an owner.
2. Collect status updates in writing. Each person adds three to five lines to a shared document or a Slack channel: done, next, blocked.
3. Update the metrics dashboard. In Kim Scott's version, it's a spreadsheet with a few numbers.

The live part below adapts Kim Scott's 3+3 agenda (20 min of key metrics, 15 of written updates, 30 to identify decisions and debates) to one hour with an opening and a wrap-up:

Decision-making gets the biggest block because written updates can't replace it. In Kim Scott's version, people write and read updates in the meeting itself; if updates don't arrive in advance, use the first half of this block for writing.

Three habits separate an effective staff meeting from a status readout:

• No one-on-ones in front of everyone. When two people go deep on one topic, take it offline.
• No status updates read aloud. They're already written.
• Remote team members speak first. With hybrid work, people on video lose the thread when the room talks over them.

Plan it with the 5 P's

The 5 P's of meetings have no single standard list: iSixSigma uses Purpose, Participants, Preparation, Process and Progress, while a four-P version based on the work of researchers Kim Cameron and David Whetten uses Purpose, Product, People and Process. The iSixSigma 5Ps entry lists five variants, all starting with Purpose; Toastmasters Magazine described the four-P version in January 2024. Together, the two lists give six questions for a staff meeting:

What to say to open a staff meeting

Open a staff meeting with three sentences: the purpose, what must be decided by the end, and the timing.

During the meeting, three questions keep it moving: "Who owns this?", "By when?" and "What do you need from the team?"

What to record after a staff meeting

After a staff meeting, write down four things: decisions made, action items with an owner and a due date, open questions, and anything a person who missed the meeting needs to know. For a staff meeting, meeting notes like these are enough; send them the same day. If your school, nonprofit or board must keep formal meeting minutes, the record also lists attendance, motions and votes, and the group approves it later.

Illustrative example: names and details are invented.

Staff meeting notes: customer support team, Tue Nov 3

Decisions
- Weekend coverage moves to a two-person rotation from Nov 14.

Action items
- Dana — publish the November rotation — Nov 6
- Luis — ask billing about the duplicate-charge bug — date not set

Open questions
- Pause chat during the Nov 20 maintenance? Dana answers next meeting.

For anyone who missed it
- The new refund policy starts Nov 9.

If your staff meeting runs in the browser version of Google Meet, Zoom, Microsoft Teams or Webex, a bot-free AI note taker can draft this record. Meetlens is a Chrome extension that records the meeting tab's audio without a bot joining the call, then produces a transcript with speaker labels and an AI report. Pick Team Sync in the format drop-down above Start recording: its report has a Brief, Team Summary, Participant Updates, Decisions, Blockers, Open Questions when any came up, and tasks with an owner and a due date. Check each owner and date before you share it. For formal minutes, use General Meeting, the default format, and add attendance, motions and votes yourself.

Meetlens records audio only, from desktop Chrome, not from the Zoom or Teams desktop apps; for an in-person staff meeting, import an audio recording if everyone agrees. On the Free plan, one recording runs up to an hour. With no bot, the call shows no recording notice from Meetlens, so announce it yourself:

Staff meeting vs all-hands vs one-on-one

You need a staff meeting when one manager's team has to share results and make decisions together; company news belongs in an all-hands, and personal topics belong in a one-on-one. Cancel the live meeting in any week when no number is off track and no decision is waiting, and let the written updates stand. An all staff meeting gathers the whole company, so it carries news and strategy rather than team decisions. Frequencies here are recommendations too: