The Weekly Operations Meeting: A Thirty-Minute Agenda for Small Teams

A small team communicates all day in chat, and yet on Friday nobody is sure who was going to call the supplier. Information is everywhere and commitments are nowhere. A weekly operations meeting of thirty minutes, run the same way every week, fixes this without adding bureaucracy.

What the meeting is for

Three things only:

1. See the same picture. Everyone looks at the same few numbers.
2. Remove obstacles. Problems that need more than one person are raised and assigned.
3. Make commitments. Each person leaves knowing what they will deliver this week.

If a topic serves none of these, it does not belong here.

Before the meeting

Preparation is what makes thirty minutes possible.

• Fixed time and day. Monday morning or Friday afternoon, the same every week.
• Numbers updated beforehand. A shared sheet or dashboard that people fill in before the meeting.
• Last week's actions visible.
• Topics submitted in advance. Anyone can add an item to a shared list by the previous evening.

People should arrive having read the numbers, so the meeting discusses them.

The agenda

1. Last week's commitments (5 minutes)

Go through the action list from the previous week. Each item is done or not done. No stories.

For anything not done: is it still needed, and what is the new date? If the same item slips three weeks in a row, it is either unimportant or blocked. Decide which.

2. The numbers (8 minutes)

Look at five to seven figures that describe the health of the business. For example:

• New enquiries.
• Sales this week and month to date against target.
• Orders delivered on time.
• Customer complaints.
• Unpaid invoices past due.
• Cash balance.
• Stock items running low.

For each: on track or off track. Discuss only those that are off. One sentence on the cause, one on the action.

3. Obstacles and decisions (12 minutes)

Work through the submitted topics, most important first. For each:

• State the problem in one or two sentences.
• Ask what is needed: a decision, help or information.
• Decide, or name who will decide and by when.

If a topic needs more than five minutes and involves only some of the people present, assign an owner and take it outside the meeting.

4. Commitments for the week (5 minutes)

Each person states their one to three priorities for the coming week. The facilitator reads back the action list: what, who, by when.

End on time.

Rules that keep it short

• Start on time, whoever is missing.
• One conversation at a time.
• No reading of status. If it could have been written, it should have been.
• Park long discussions. "Let us take that separately" is the most useful sentence in the meeting.
• Every action has one owner and a date. "The team will look into it" means nobody will.
• Notes shared the same day. A few lines: decisions and actions.
• Stand up, if the room allows. It discourages long speeches.

The action list

The meeting is only as good as its action list. Keep one simple table:

Review it at the start of every meeting. Closed items are removed. Open items past their date are discussed. This single habit is what turns talk into delivery.

Choosing the numbers

Pick figures that:

• Change weekly.
• Someone in the room can influence.
• Come from your systems without hours of compilation.

Give each number an owner who updates it and explains it. Review the set every quarter. If a number has not led to a decision in three months, replace it.

Adapting to your team

• Very small team, three to five people. Fifteen minutes may be enough. Keep the same four parts.
• Remote or mixed team. Use video, share the screen with the numbers and action list, and ask each person by name for their commitments.
• Several functions. Keep the weekly meeting for shared matters. Each function can hold its own shorter session.
• Shift workers. Record decisions clearly and post them where the other shift will see them.

Common ways it goes wrong

• It becomes a status recital. Each person talks for five minutes about their week. Fix: written updates beforehand, discussion only of exceptions.
• It becomes a problem-solving workshop. Two people debate while six wait. Fix: park and assign.
• No follow-up. Actions are forgotten by Wednesday. Fix: start with last week's list.
• The boss speaks the whole time. Fix: ask others first, and rotate the facilitator.
• It is cancelled when things are busy. That is when it is most needed. Shorten it, do not skip it.
• No numbers. Discussion drifts into opinion.

What else you need alongside it

The weekly meeting does not replace:

• Daily coordination in chat, or a five-minute stand-up for teams that need it.
• One-to-one conversations between manager and employee.
• A monthly review of finances and progress against plan.
• Deep work sessions on a specific problem.

Each has its own purpose. Keeping them separate is what keeps each one short.

Getting started

1. Pick the day, time and five numbers.
2. Create the shared action list.
3. Run the four-part agenda for four weeks without changing it.
4. Then ask the team what to adjust.

Polynusa brings sales, invoices, stock and team tasks into one workspace, so the numbers for the meeting are already on a screen and actions can be assigned as tasks with dates. See the pricing page.

Summary

Hold one thirty-minute meeting at a fixed time each week. Review last week's actions, look at five to seven numbers, resolve or assign obstacles, and close with commitments that have an owner and a date. Prepare the numbers beforehand, park long discussions, and never skip the action list.

FAQ

How long should a weekly team meeting last?

Thirty minutes is enough for a team of up to ten if the agenda is fixed and the numbers are prepared in advance. If it regularly runs over, too many topics are being discussed in detail. Move deep discussions to a separate session with only the people involved.

What should not be discussed in a weekly operations meeting?

Long problem-solving that involves only two people, status that everyone could have read beforehand, and individual performance issues. The meeting is for shared numbers, obstacles that need the group and commitments for the coming week.

Who should run the weekly meeting?

The owner or the operations lead usually starts. Rotating the facilitator after a few months builds ownership. Whoever runs it has two duties: keep to the time, and make sure every action has a name and a date.