The best test of whether your weekly agenda is working is not the meeting itself. It is what happens on the Monday you are on a plane. If the meeting runs anyway, at the same quality, and the decisions still move, you have built an operating rhythm. If the meeting is quietly canceled or turns into a status round-robin the moment you are absent, you built a personality-dependent meeting and called it an operating rhythm. Those are different things.
I have run this weekly meeting in three different companies over the last decade. At Hana Group across 21 franchise units in 6 states. At Zareen's across a $30M Michelin-recognized Bay Area group. At SEOD Ventures with a smaller team. Same shape every time. Different content. And I have rebuilt the agenda from scratch at least five times, because agendas accumulate weight the way garages accumulate boxes, and every 18 months or so the meeting has to be stripped back to four items or it stops working.
What "runs itself" actually means
An agenda that runs itself is not one where nobody has to prepare. It is one where the preparation, the sequencing, the timing, and the accountability are all built into the template, not into the leader's head. When the meeting is well designed, the leader is the least important person in the room. The template runs the meeting. The general managers run the sections. The decision log runs the followup. The leader listens, asks the last question, and closes.
The moment you feel like the meeting cannot happen without you, that is the signal that it has become a leader-dependent meeting, not a leader-designed one. That version does not scale, does not survive a vacation, and does not teach the general managers to lead.
The template: 4 to 6 items, same every week
The single most important design choice is that the template does not change. Same items, same order, same time boxes, every single week for at least a quarter. This is the boring choice and it is the correct one. Novelty is what breaks meetings under load. Consistency is what lets a meeting build depth.
Here is the shape I keep coming back to for a regional operating meeting:
Regional standing agenda · Monday · 60 minutes
- Last week's numbers, worst unit first (12 min)
- Decision log review, three-week stale items only (8 min)
- This week's one commitment from each general manager (15 min)
- One shared problem, one owner, one deadline (15 min)
- Wins from the field, brief (5 min)
- Next week's timekeeper and section owners (5 min)
Notice what is not in there. No CEO update. No corporate news. No presentations. No "any other business." The agenda is a working meeting for the general managers, run by the general managers, that produces one shared decision per week. Anything that is not that gets pushed to a different meeting or to a different channel.
Fixed time boxes are the hidden discipline
The time box on each item is the second most important design choice. Without a time box, item one will absorb 40 minutes and items four through six will not get real attention. With a time box, the timekeeper calls time and the group moves on, even if item one is not "done." Meetings do not need to finish items. They need to move them.
Ownership rotation: quarterly, by section
The single change that made the biggest difference in my meetings was moving from "the leader runs the whole agenda" to "each general manager owns one section for a full quarter." Rotate every quarter. By the end of a year, every general manager has run four different sections of the standing agenda, which is a lot of leadership reps for people who otherwise would not get them.
The rules of ownership are simple. The section owner opens the section, runs the discussion, closes the section, and hands off to the next owner. They pre-read the numbers on Friday. They come with a point of view. They call on people. The leader does not present. The leader listens.
Fig. 1 · Every general manager runs every section over a year.
Two things happen when ownership rotates this way. General managers get real practice running a meeting, which is a leadership skill most of them never get to build. And the meeting develops resilience, because at any given quarter there are four people who know how to run each section, not one.
The decision log: one page, read at the top
Meetings that do not track their own decisions repeat the same conversation. Not because people are forgetful. Because there is no artifact that says "we decided this." A decision log is that artifact. One page. Four columns. Date, decision, owner, due date. Read the top of it at the start of every meeting.
Two rules make the decision log work. First, only decisions go on it. Not discussion topics, not "we should think about this," not ideas. Decisions. If a conversation does not end in a decision, nothing goes on the log. Second, any decision that has not moved in three weeks gets a conversation, not a note. The three-week rule is what keeps the log honest. Without it, the log becomes a graveyard of stale decisions and everyone quietly agrees to stop reading it.
The decision log is the memory of the meeting. Without it, the meeting has no memory and the same conversation happens four times.
The timekeeper: rotating, and never the leader
The timekeeper is the smallest role in the meeting and one of the most important. Their entire job is to call time on each section and force the group to move. It is a rotating role, and it is never the leader. If the leader is the timekeeper, the meeting becomes a leader-run meeting again, and the whole design breaks.
The timekeeper's script is three words: "Time on this." That is it. They do not add opinions on the content. They do not join the debate. They watch the clock and call it. New timekeepers feel weird about interrupting for the first few weeks. That is fine. They get comfortable by week three, and the meeting becomes noticeably crisper the moment they do.
The one thing rule
At the end of the meeting, every attendee names one thing they own for the next week. Not five. One. Written into the decision log. Read out at the top of next week's meeting.
The one thing rule is the antidote to the meeting that generated twenty ideas and moved none of them. It forces prioritization. It creates a public commitment. It gives the leader something concrete to follow up on that is not a vibe. And it teaches the general managers that the point of the meeting is not the meeting. It is the thing that happens between meetings.
Two mistakes I keep watching operators make
The first is turning the standing meeting into a status report. When the meeting becomes "each general manager reports their numbers," it has become a status round-robin, not a working meeting. Nothing gets decided. Nothing gets moved. Everyone leaves the room having spoken and nothing has changed. The fix is that the numbers get pre-read in the shared dashboard on Friday, and Monday's meeting starts with the worst-unit conversation, not the summary. If people are hearing the numbers for the first time in the room, the meeting has already failed.
The second is running the meeting from a laptop with slides. The moment slides appear, the meeting turns into a presentation. Presentations are one-directional. Working meetings are not. The dashboard is on a shared screen, the decision log is on the same screen, the section owner has notes on paper, and the room is talking to each other, not watching a deck. I have run this on every scale from a five-person leadership team at Zareen's to a twelve-person regional group at Hana Group, and the deck-based version has never worked as well as the dashboard-plus-log version. Not once.
How agendas get heavy, and what to do about it
Every standing agenda I have ever run has, at some point, gotten heavy. Someone adds a metric. Someone else adds a section. A special project needs a standing update. A new leader wants a briefing every week. Six months later the meeting has quietly stretched from 60 minutes to 90, and it is doing less real work than it did at 60.
This has happened to me at least five times. Every time, the fix is the same. Delete everything. Rebuild from four items. Fight the urge to add the fifth and sixth back on day one. Let the meeting run at four items for a month before you consider what else has earned its way in.
The pattern of accumulation is not a failure of discipline. It is the natural physics of a recurring meeting. Every stakeholder wants a hook in the room, and the leader who wants to be helpful will keep saying yes. The rebuild every 18 months is not a sign that you did it wrong. It is the maintenance cycle.
What I would tell an operator building their first standing agenda
Three things.
- Do not run it yourself. Not in the first month, not ever. If you run it, the meeting is you. Rotate ownership from week one, even if it is uncomfortable at first. The general managers learn faster in the deep end than they will in the shallow end.
- Cut it before you add to it. If a new item wants in, an old item has to come out. Six is the ceiling. Hold the line. Every operator I know who has a heavy agenda got there by adding without subtracting.
- Take a vacation and see what happens. This is the only real test. Book a week off in month four. Do not join the meeting. Read the decision log when you get back. If the log shows real decisions moved, you built a rhythm. If the log is empty or the meeting was skipped, you built a meeting that runs on you, and you have more work to do.
The point
A standing agenda that runs itself is not a magic template. It is a small set of design choices, held with discipline, over months. Fixed template. Rotating ownership. A decision log that gets read. A timekeeper who is not the leader. One thing per person per week. Rebuild every 18 months when it gets heavy.
Do those five things and the meeting will hold when you are on a plane. That is the whole point of building it. The best regional operators I have worked with all had one thing in common at their weekly meetings: nobody in the room, including them, thought the meeting was about the leader. It was about the region, and the region ran it. That is the shape you are trying to build.