This page is for the founder of an established company in Miami or South Florida whose weekly leadership meeting has drifted into status updates or stops whenever the founder is away. Our guides to the founder bottleneck and to scaling a founder-led company name the weekly meeting as an early step. This page covers how to run it.
What should a weekly leadership meeting do?
A weekly leadership meeting should produce decisions and commitments that keep the company's plan moving between quarterly reviews. Owners update their figures before the meeting starts, so status comes from the sheet and the hour goes on what needs a decision.
Book one recurring weekly slot for the leadership team and run the same agenda every time. We recommend inviting the leaders who own a function and its results, usually the founder's direct reports. Each person arrives with updated figures and last week's commitments ready to report, so nobody spends the meeting reconstructing the week.
The meeting's record feeds the quarterly review. In the Founder Blueprint the company runs its plan on weekly, quarterly and annual meetings, and we add no other recurring management meeting to run it.
What is the agenda, and how long does each part take?
In the Founder Blueprint the weekly leadership meeting takes 60 minutes, in six parts that run in the same order every week. The top of the meeting sheet records the week, who leads the meeting and who is present.
The order matters. The two short reads bring problems to the surface before the team chooses which ones get its time.
| Part | Minutes | What happens | What it produces | The usual slip |
|---|---|---|---|---|
| Check-in | 5 | Each person shares one win from work and one from outside it, with no discussion | Everyone present and paying attention | The check-in turns into a conversation |
| Cash and scorecard | 5 | Cash first, then each metric against its goal, marked on track or off track | Off-track metrics added to the issues list | Someone starts explaining or fixing a miss |
| Commitments review | 5 | Each commitment from last week reported as done or not done | Unfinished commitments added to the issues list | An explanation replaces the done-or-not-done answer |
| Issues | 35 | List every issue, rank the top three and work them one at a time | Commitments with owners | Discussion moves between issues and nothing is decided |
| Done this week | 5 | The coming week's commitments written down, and a decision on who outside the meeting needs to hear what was decided | Next week's review list and an owner for each message | People leave with different understandings |
| Close and rate | 5 | Everyone scores the meeting out of 10 and the team records the average, aiming for 8 or higher | A shared view of how the hour went | Low scores pass without explanation |
How do you keep the scorecard and commitments to ten minutes?
Keep both reads to ten minutes by requiring prepared figures and short answers. Owners update the scorecard before the meeting starts.
Read the prepared scorecard, starting with cash, and mark each metric on track or off track. Put anything off track on the issues list without working on it yet. Our weekly scorecard guide covers what to track, how to set the goals and on-track rules, and what to do with a figure that is missing.
Next, read last week's commitments. Each owner answers done or not done, with no story during the read. Anything unfinished goes on the issues list. The meeting leader can stop an explanation politely: "That goes on the issues list. Let's finish the read."
How do you work an issue until it is settled?
Work an issue until the team records a decision and a commitment with an owner and a date, or an owner and a date for gathering what the decision needs. Begin by listing every issue, then rank the top three. Start with the most important and stay with it before opening the next.
The meeting sheet records each issue with a number, its owner and whether it became a commitment. Writing the issue down gives the team something precise to work on. "Delivery problem" needs a sharper description before anyone proposes a fix.
Ask what is causing the problem, and check that the team agrees on the cause before choosing an action. Otherwise people can agree to work that leaves the original problem untouched.
If nobody has the facts needed to decide, assign someone to gather them before next week's meeting. That becomes the commitment. Record that the underlying issue remains open, so gathering facts does not get mistaken for settling it.
Issues the team does not reach roll to next week's list and are ranked again alongside new ones. Ranking sets the order of work, and some weeks the team will settle only the first issue because it is the most important. When the 35 minutes end, write down where any open issue stands and give it a dated next step before moving to the closing parts.
What makes a good commitment?
A good commitment names work that one person can report as done or not done at the next meeting. We recommend up to three commitments per person each week. Fewer is fine.
Write the expected result and its owner, with a due date no later than the next meeting. Avoid wording such as "make progress" or "keep working on it", which leaves completion open to interpretation.
For work that takes longer than a week, name the part that will be finished this week. For example: the operations lead sends the revised delivery schedule to the affected customers by Friday. Read the wording back before the meeting closes, so the owner and the team agree on the finish point.
We treat a commitment that keeps slipping as an issue about the work or the person's load. Repeating the same promise each week leaves that issue untouched, so use the issues section to decide what must change before the owner commits again. Work that keeps returning to the founder is a separate problem, covered in our guide to the founder's delegation system.
Who should run the meeting, and where does the founder sit?
A named person inside the company should run the meeting, and that person does not have to be the founder. In the Founder Blueprint the same person organizes the weekly and quarterly meetings and follows up on commitments between them.
During the hour, the meeting leader keeps the reads brief and moves the team through the agenda. They also make sure each decision is on the sheet before the conversation moves on.
The founder takes part like everyone else, bringing issues and accepting commitments. Give the people responsible for the work time to explain the cause and propose an action before the founder offers an answer.
Keep the usual slot when the founder travels. If a decision needs the founder's input, write down the question and assign someone to get the answer, then continue with the rest of the agenda.
Why rate the meeting?
Rating the meeting gives the team a weekly signal of whether its use of the hour is improving. Everyone scores it out of 10, and the team records the average, with a target of 8 or higher.
Ask anyone giving a low score what would raise it next week. Keep the answer specific to something the team can change, such as starting on time or leaving with a written owner for every commitment.
Compare the average with prior weeks. A falling average belongs on the issues list. The score reflects the team's judgment, so use the explanation behind it to decide what to change.
What goes wrong in a weekly leadership meeting?
The meeting loses its purpose when updates take over the hour or decisions fail to become commitments someone checks. Watch for these five patterns.
- Status reports and fixes take over the reads. Stop after the figure or the done-or-not-done answer, and move explanations and proposed fixes to the issues section.
- Too many issues get shallow attention. List everything, rank the top three and stay with the first until it has an owned commitment or an owner gathering the missing facts.
- Nobody checks commitments. Carry the written commitments into next week's review and get a done-or-not-done answer from each owner.
- The slot moves or gets cancelled. Keep the recurring appointment and name a leader who can run it when the founder is away. If the meeting has already stopped, our guide to why a founder's operating system stops being used covers restarting it.
- The founder decides everything. Have the issue's owner explain the cause and propose the next action, and let the meeting leader give that discussion time before asking for the founder's view.
What should a founder do before next week's meeting?
Before next week's meeting, put the fixed slot and one meeting sheet in place.
- Book 60 minutes. Invite the leadership team to the same weekly slot and name the person who will run it, including when you are away.
- Prepare one meeting sheet. Put the week, the meeting leader and those present at the top, then the six parts in order, with space for the issues list and the new commitments.
- Ask owners to update their figures. Bring last week's commitments if they exist. If this is the first meeting, the team writes its first set in the closing parts.
- Explain the reporting rules beforehand. Metrics are on track or off track, commitments are done or not done, and explanations wait for the issues section.
At the meeting, protect the 35 minutes for issues. Before anyone leaves, confirm the commitments in writing and assign who tells people outside the meeting what was decided. Those commitments open next week's review.
- Keep the same leadership team in a fixed 60-minute weekly slot.
- Give the scorecard and commitments five minutes each, and move every miss to the issues list.
- Rank the top three issues, then work one at a time until each ends in an owned commitment.
- Name a meeting leader inside the company so the meeting runs when the founder travels.
- Record the closing rating and ask what would improve next week's meeting.
The Leadership Scorecard takes ten minutes and shows which parts of the company still depend on you.