> Source: https://brendanlevin.com/insights/how-to-run-a-weekly-team-meeting/ > A 45-minute weekly operating review that your team runs without you chairing it: numbers first, stuck work second, decisions third. Here is exactly how it works and where it breaks down. For founders, owners, and operators # How to Run a Weekly Team Meeting That Actually Moves Work Forward By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m. Run a 45-minute standing meeting every week in this order: numbers first (did we hit them or not), stuck work second (what cannot move without a decision), decisions third (the founder unblocks and leaves). **The founder's job is to listen and decide, not to chair.** The team runs the room. See [how to build the wider cadence](/insights/how-to-build-an-operating-rhythm/) around it. Key takeaways - Numbers come before narrative: if a metric missed, say by how much before saying why. - The founder chairs nothing. A team member owns the agenda and keeps time. - Stuck work only makes the agenda if the owner has already tried to unblock it themselves. - Any decision that does not get made in the room gets a name and a deadline, not a follow-up email thread. ## Why ad hoc check-ins are killing your output When the weekly meeting does not exist, the founder becomes the meeting. People ping you when something is stuck. You answer. They move. You get pinged again. The work flows, but it flows through you, and the moment you stop responding the flow stops too. That is not a communication problem. It is a structure problem. The check-in pattern trains your team that the founder is the operating system. A standing weekly review breaks that pattern by giving everyone a predictable, shared moment to surface what is stuck and get it cleared in one pass. No pings. No async threads that go cold. One room, forty-five minutes, done. If your business stalls every time you step away, the meeting is one of the first things to fix. The honest test: take a full week away with no contact and watch what stalls. What stalls is still running on you. The weekly review is where you start handing it back. ## The 45-minute format, section by section The meeting has three sections in a fixed order. The order matters because it prevents status theater, which is what happens when the meeting becomes a round of people explaining what they did last week instead of surfacing what needs to happen next. Numbers first (15 minutes). Each function or owner reads their number: the one metric that tells you whether their work moved or not this week. Not a story. Not context. The number, and whether it hit the target. If it missed, one sentence on the biggest reason. That is it. If you do not yet have a number for each area, that is a Direction problem worth solving separately. [Setting a clear direction](/insights/how-do-i-set-direction-for-my-team/) gives each area something real to measure against. Stuck work second (20 minutes). Anyone who has a piece of work that cannot move without a decision from someone else puts it on the agenda. The rule: it only makes the list if the owner has already tried to resolve it themselves. This is not a place to report problems. It is a place to clear blockers. The team member states the blocker in one sentence, states what they need, and the room decides. If the founder is in the room, the founder decides in the room. Not after. Not by email. Now. Decisions third (10 minutes). Any decision that did not get raised under stuck work but still needs to be made this week goes here. Each one gets a decision or gets a named owner and a date by which the decision will be made. It does not leave the meeting as an open question. ## The founder's real role in the room You are not the chair. Someone on the team owns the agenda, keeps time, and calls on each section. That person is responsible for the meeting running to forty-five minutes and finishing with a clear record of what was decided and who owns what next. Your job in the room is two things: listen and unblock. You listen to the numbers and you form a view on whether the work is on track. You unblock whatever cannot be cleared without you. When a decision lands in your lap, you make it in the room. If you need a day to think, say so and say when you will have the answer. That is still a decision: the decision to defer, with a date. If you find yourself wanting to chair, explain, coach, or reframe what someone said, that is a signal worth paying attention to. It usually means you do not fully trust the team to own their work, or the [decision rights](/insights/decisions-route-back-to-me/) are not clear enough yet and everything still feels like it needs your judgment. ## The decision-rights rule that makes the stuck-work section fast The most common reason the stuck-work section becomes a slow, uncomfortable negotiation is that nobody is sure what they are actually allowed to decide without the founder. So everything escalates, even things that should not. Fix this with a written threshold per area. A real example of what this looks like in practice: any spend under $2,000 within an approved project, the owning person commits it and tells you after. Spend above $2,000 or outside an approved project comes to the weekly meeting or to the founder directly. That one rule removes a significant slice of the typical stuck-work pile because the owner already knows they can move. Written thresholds also change the culture of the meeting. When your team knows what they can decide, they stop bringing you things they can handle themselves. The items that reach the stuck-work section are genuinely stuck, not just unconfident. That is a meaningful difference. [Setting clear decision rights](/insights/how-to-set-decision-rights-in-your-business/) is the structural work underneath the meeting format. ## The failure modes that turn it into status theater Every meeting format degrades over time. Here are the specific ways this one goes wrong and what each one signals. The founder takes the chair back. This usually happens gradually. You start by asking one clarifying question, then you start reframing the stuck-work items before the owner explains them, then you are running the room again. The signal: your team stops preparing because they know you will guide them through it anyway. Numbers get replaced by narratives. Someone misses their number and leads with the context instead of the number. The room lets it go. Within a month every section is a story and nobody knows whether anything is on track. The fix is a standing rule: number first, always. One sentence on the reason, only if it missed. Decisions leave the room undecided. The ten-minute decision section closes with vague agreement to think about it. Nobody has a name on the decision or a date. The item appears again next week with the same outcome. This is the single fastest way to kill confidence in the meeting. If a decision cannot be made in the room, name the person who will make it and the date by which it will be made. That is the minimum exit condition for any agenda item. - The founder re-takes the chair: team stops preparing. - Numbers become narratives: you lose visibility on whether work is on track. - Decisions leave undecided: same items recirculate and trust in the meeting falls. - The meeting grows past 45 minutes: off-topic problems get parked as agenda items instead of being handled separately. ## What belongs outside the weekly meeting A common mistake is letting the weekly review become a catch-all. Project updates, client issues, hiring decisions, individual performance conversations: none of these belong in this room. When they land here the meeting loses its shape and people stop knowing what it is for. The weekly review covers three things: whether the numbers moved, what is stuck in the work, and what decisions need to be made this week. Everything else has its own context. Project updates belong in a project check-in. Client issues belong with the account owner. Individual performance belongs one-on-one. Protecting the format is the team lead's job, not yours. If your designated chair lets the meeting drift, that is a coaching conversation outside the room, not an intervention during it. The meeting cannot develop into a team habit if the founder is the one enforcing its structure every week. If your team meeting is running but work is still routing back to you, the Founder Dependency Diagnostic will show you where the real dependency sits. [Take the free diagnostic](/executive-diagnostic) ## Common questions How long should a weekly team meeting be for a small business? Forty-five minutes is the right ceiling for a team of eight to fifty people. Numbers, stuck work, and decisions each get a fixed block. When the meeting runs over it is almost always because either the numbers section turned into a discussion or a decision left the room undecided. Both are fixable with a standing rule before the meeting starts. Should the founder run the weekly team meeting? No. A team member should own the agenda and chair the room. The founder's job is to listen to the numbers, decide what is stuck, and leave. When the founder chairs, the team produces for the founder rather than for the work. That is a subtle but real difference, and over time it keeps the business running through you rather than through the team. What goes on a weekly team meeting agenda? Three things in order: the metrics each area owns and whether they hit target this week, the work that cannot move without a decision from someone else, and any decisions that need to be made before next week. Status updates, project narratives, and individual issues do not belong on this agenda. What do I do if my team brings the same stuck items every week? Recurring stuck items are almost always a sign that the decision rights are not clear enough. If your team does not know what they are allowed to decide themselves, they escalate everything to be safe. Write a threshold for each major area, a real number or risk line below which the owning person acts and tells you after. The recurrences usually stop. How is a weekly operating review different from a regular team meeting? A regular team meeting often becomes a round of updates with no clear output. A weekly operating review has a fixed format, a fixed owner who is not the founder, and a defined exit condition for every agenda item: a metric is on track or not, a blocker is cleared or has a named owner, a decision is made or has a date. If the meeting ends without those outputs it did not do its job. How do I know if my weekly meeting is working? Three signals that it is working: the ad hoc pings to you during the week drop noticeably, your team can tell you the status of their key metric without looking it up, and decisions that used to sit open for days get made in the room. Three signals it is not working: you are still being pulled into the same conversations on Tuesday that were raised in Monday's meeting, the numbers section is getting shorter because people stopped preparing, and you have started chairing again. Related: [how to build an operating rhythm](/insights/how-to-build-an-operating-rhythm/) · [how do i set direction for my team](/insights/how-do-i-set-direction-for-my-team/) · [decisions route back to me](/insights/decisions-route-back-to-me/) · [how to set decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) · [what is a founder operating system](/insights/what-is-a-founder-operating-system/) · [why does my business stall when i step away](/insights/why-does-my-business-stall-when-i-step-away/) · [more insights](/insights).