If I could give a small business just one operations habit, it would be a well-run weekly operations meeting. Not a status update where everyone reads out their task list, but a short, focused session that sets priorities, surfaces problems and ends with clear owners.
Done well, it replaces dozens of scattered messages, catches issues early and gives the founder clarity every week. Here’s exactly how to run one.
Why most weekly meetings fail
- No agenda, so the loudest topic takes over.
- Status reporting, with each person listing everything they did, which the hub already shows.
- No decisions, just discussion.
- No follow-up, so the same issues come back next week.
- Too long, so people dread it and start skipping.
The fix is structure: a fixed agenda, a time limit, prep before the meeting and a written outcome after.
The basics
- When: Monday morning, or Friday afternoon if you prefer to plan the next week before the weekend.
- How long: 30 minutes for teams up to about six people. 45 minutes at most for larger teams.
- Who: the founder, the person who owns operations (the OBM or operations lead) and anyone who owns a major area. Contractors join only for the items that need them.
- Where: a video call is fine for remote teams. Run it from your project hub, not from a slide deck.
- Who leads: the operations owner, not the founder. That frees the founder to listen, decide and think.
The prep (15 minutes before)
The operations owner prepares three things:
- The metrics snapshot: the five to eight numbers you track each week, compared with last week.
- The at-risk list: tasks and projects that are overdue, blocked or likely to slip.
- The decision list: anything that needs the founder or the team to decide.
Everyone else updates their tasks in the hub before the meeting. If tasks are up to date, nobody needs to report status out loud.
The 30-minute agenda
1. Wins (3 minutes)
One win per person, quickly. It sets a positive tone and highlights progress that would otherwise go unnoticed.
2. Numbers (5 minutes)
Review the metrics snapshot. Don’t discuss every number; only the ones that moved unexpectedly. “Leads are down 30% on last week. Why?” goes on the issues list.
3. At-risk work (7 minutes)
Go through the at-risk list. For each item, agree on one of three outcomes: unblock it now, change the deadline, or drop it. Never leave an item at “we’ll see”.
4. Issues and decisions (10 minutes)
Work through the decision list and any issues raised by the numbers. For each:
- State the issue in one sentence.
- Agree on the decision or next step.
- Assign one owner and a date.
If an issue needs more than five minutes, give it an owner and schedule a separate conversation.
5. This week’s priorities (5 minutes)
Agree on the top three to five priorities for the business this week. Not everyone’s full task list, just the things that matter most. Each priority gets one owner.
The rules that make it work
- Start and end on time, every time.
- One owner per action. “We’ll look into it” means nobody will.
- No status reading. If it’s in the hub, don’t say it.
- Decisions are written down during the meeting, not afterwards from memory.
- Phones away, cameras on for remote teams. Thirty minutes of focus is a small ask.
- The meeting happens even when the founder can’t attend. The operations owner runs it and sends a summary.
The follow-up (10 minutes after)
The operations owner sends a short written summary within an hour:
- This week’s priorities and owners
- Decisions made
- Actions with owners and dates
- Issues parked for later
Put it somewhere permanent, such as a meetings page in Notion or a Doc in ClickUp, so you build a searchable record of decisions over time. The actions go straight into the project hub as tasks.
Using AI to save time
AI helps with the admin around the meeting:
- Before: generate the at-risk list from your project tool, and draft the metrics snapshot from your dashboard.
- During: use a meeting note-taker to record the call.
- After: ask ChatGPT or Claude to turn the transcript into the summary format above, using only what was said. Then the operations owner checks it, fixes anything wrong and sends it.
The meeting itself should stay human. Its value is in the judgement and commitment of the people in it.
Adding a monthly review
Once a month, extend the meeting to 60 minutes and add:
- What worked this month, and what we should do more of.
- What didn’t, and what we’ll stop or change.
- Process improvements: which SOPs, tools or automations need updating.
- Next month’s focus: one or two bigger goals.
A template you can copy
Weekly Ops: [date]
Wins: …
Numbers: leads · calls booked · clients won · revenue invoiced · tasks overdue · client issues
At risk: item · owner · decision (unblock / move / drop)
Decisions: issue · decision · owner · date
Priorities this week: 1. … 2. … 3. …
Start this week
You don’t need perfect systems to start. Pick a day, block 30 minutes, use the agenda above and send a summary afterwards. Within a month, you’ll wonder how the business ran without it.
Running this rhythm is a core part of my monthly retainers. If you’d like someone to own it for you, see how I work.