The 10-minute staff meeting that gives your team most of a workday back every week

Monday, 10:00. Or 10:12.

The meeting is on the calendar for 10:00. It starts at 10:12, because the executive director is on the phone with the church next door about parking for Saturday's book giveaway, and nobody wants to start without them.

There are five people on staff. They meet at the big table in the back, which is also where donated school supplies get sorted, so the first thing anyone does is move two boxes of glue sticks onto the floor.

They go around the table. The program coordinator gives a long update on tutor sign-ups, most of which was in an email on Friday. The development lead needs a decision on the spring grant report, and somehow that turns into a conversation about whether the fall flyer has the old logo on it. Someone pulls the flyer up on a laptop. It does have the old logo. Someone else mentions the printer needs it by Wednesday.

At 11:05 the program coordinator says sorry, tutor orientation at noon, and leaves with half a granola bar. The rest of them wrap up around 11:30, when the first volunteer knocks on the door. Nobody took notes.

On Thursday, two staff members email the same school principal about the same field trip and give different dates. The grant report question is still open. The flyer went to the printer with the old logo.

This isn't a bad team. They like each other, and the Monday meeting is the one time all week they're in a room together. That's part of why it runs long. It's carrying everything.

Why the long meeting hangs on

Most weekly staff meetings are trying to do two jobs at once: share updates and make decisions. Updates are faster to read than to listen to. Decisions usually only need two or three people. Put both in one open-ended hour and the topic that wins is whatever came up last, not whatever matters most.

It's worth doing the math for your own team. Five people in a 90-minute meeting is seven and a half hours of staff time, every week. That's most of a workday, and on a small team it comes straight out of program time.

How to cut it to ten minutes

Here's how I'd set it up.

Keep the day and time. Shrink the meeting. Same slot as before, but ten minutes. Put a timer on someone's phone where everyone can see it. It'll feel a little rude the first week. That wears off.

Move updates into writing. A shared doc or a chat thread, a few lines from each person by Monday morning. Nobody reads them out loud. If you skimmed it before you sat down, you're caught up.

Ask each person two questions. What's the one thing you most need to get done this week? Where are you stuck, or who do you need? That's under a minute each, even for the talkers.

Park anything that needs a real conversation. Write it down, name who needs to be part of it, and pick a time before you leave the table. A logo question is a twenty-minute talk for two people. It shouldn't be a forty-minute talk for five.

Have one person write down who's doing what by when. Rotate the job. If the notes come out rough, AI can help here. Paste them in, ask for a short list of names, tasks and dates, and read it over before it goes to the team. Leave out anything private about the people you serve.

Once a week, keep the last two minutes for one shortcut. It's a short version of the weekly share-out from Kindling 1. Someone shows one thing they tried, maybe an AI prompt, maybe a better template for the monthly report. It goes into a shared document so everyone else can use it. Just one thing per week.

It won't run smoothly at first. Somebody will talk past the timer, and somebody will forget their written update and give it out loud instead. Let that go for a couple of weeks.

Back at the table

The first try ran nineteen minutes. The executive director stopped to explain the parking situation in detail, and nobody felt brave enough to point at the timer.

In week two, three of the five had posted their updates. The flyer got its own twenty minutes on Tuesday with the development lead, the coordinator and a laptop. They found the new logo file in an old email, and the next print run has it.

By the fourth week the meeting was running about twelve minutes. The program coordinator stayed for all of it, then ate lunch sitting down before orientation. The who-does-what list goes out by 10:30. When the field trip came up again, one person owned it, and the principal got one email.

It still drifts. Last week someone asked if they could go back to a long meeting once a month, just to catch up with each other. They're going to try that in November.