← Blog

Strategy & Results · 9 min read

Project Focus, Part 4: The Weekly Rhythm: A 30-Minute Meeting That Runs the Business

Part 4 of a weekly series: a five-part, 30-minute weekly meeting with a scoreboard, commitments, projects and decisions, plus rules that keep it short.

A small team in a short stand-up meeting in a bright office, one person speaking and the others listening
One voice at a time, one page on the table, thirty minutes on the clock. Then everyone leaves knowing what happens next.

Most owners tell me they have too many meetings. Then I ask how many of them end with a decision, a name and a date. The room goes quiet. They do not have too many meetings. They have too few of the right one.

This is Part 4 of the series Project Focus for business success. Part 1 put the method on a single page, Part 2 introduced the three engines (leads, operations and sales) with operations at the center, and Part 3 gave you a scoreboard of three numbers. Now we add the thing that makes all of it move: a weekly rhythm.

Why a rhythm beats a plan

A plan is a picture of a day that has not happened yet. A rhythm is a habit that keeps correcting the picture. Imagine two companies with the same plan. The first looks at it twice a year. The second looks at it every Monday for half an hour. After three months, the second one has had twelve chances to notice a drift, ask a question and fix it while it was small. The first has had one, and the drift has become a crisis.

That is the whole argument. It is also the reason that, in construction, the weekly look-ahead meeting exists, and why Kanban teams review the board every day. A small business does not need heavy governance, and the lightweight governance guide explains why, but it does need a regular moment where the numbers and the work meet.

The 30-minute meeting, in five parts

The meeting works because it has a fixed shape. Everyone knows what comes next, so nobody needs to prepare a performance. Here is the shape, with the minutes.

1. The scoreboard (5 minutes)

Look at the three numbers from Part 3, one for each engine if you can: a number for leads, one for operations and one for sales. Read them out. Say whether each is better, the same or worse than last week, and say nothing else. No explanations yet. The point is to put the facts on the table together, so that the rest of the meeting starts from the same picture. If you keep the dashboard honest, this takes two minutes.

2. Last week's commitments (5 minutes)

Every week the meeting ends with commitments: who will do what by when. The next meeting begins by checking them. Read each one. Done, not done, or moved. Moved needs a new date and a reason. It sounds strict. It is the opposite of strict: it is the one habit that turns "we should" into "we did".

3. The projects (10 minutes)

In Project Focus, every improvement is a project with an owner. In this part of the meeting each owner gives a one-sentence status and a color: green (on track), yellow (a risk is visible and I have a plan) or red (I need help or a decision). If a project is red, it gets one more minute: what exactly is blocked and what do you need? The detail waits for the next part. If you use a status report, the one-page version is the sheet on the table.

4. Decisions (5 minutes)

Collect the decisions that need someone with authority: spend this, stop that, hire for this, change the date. Decide them now when you can. If a decision needs more information, name who will bring it and when. A decision log, even a simple list, makes it easy to see what was decided and why. The RACI chart is useful here: it says who decides, who must be consulted and who needs to be told.

5. New commitments (5 minutes)

Close with a list: what, who, by when. Read it back. Write it where everyone will see it. That list is the first item of the next meeting. If a commitment cannot be said in one sentence, it is not yet a commitment.

Four colleagues standing around a wooden meeting table looking at one printed page with pens in hand
One page on the table: the scoreboard, last week's commitments and the projects.

The rules that make it work

Five small rules protect the thirty minutes:

  1. Same time, same place, every week. A habit needs a trigger. Monday morning works for many teams. A midweek slot works for others. What matters is that it does not move.
  2. Start on time and end on time. If the meeting ends early, celebrate. If it runs over, something went wrong, and you should ask what.
  3. One page. The scoreboard, the commitments and the project list sit on one sheet. If it takes a slide deck, the meeting will become a presentation.
  4. Park the problem-solving. If a topic needs more than two minutes, write it on the parking list with an owner and a time. The smallest group that needs to solve it meets afterward. This one rule saves hours.
  5. Only owners attend. Everyone who is responsible for a number, a project or a decision. Everyone else gets the page afterward.

An illustrative example: a nine-person home services company

Here is a made-up business to show how it works. A nine-person home services company has three projects running, and the owner has been "too busy to meet" for a year. She starts the Monday meeting. Her three numbers are the number of new quotes requested this week (leads), the share of jobs finished on the scheduled day (operations) and the number of quotes won (sales).

In the first meeting, the scoreboard shows 14 requests, 71 percent on-day jobs and 4 wins. Nobody explains. In the project part, the person responsible for scheduling says yellow: two crews are double-booked on Thursdays. The decision part takes three minutes: she decides to add a Wednesday planning call at 3 p.m. The new commitments are three lines long.

By week six the picture has changed. On-day jobs are at 84 percent. The Wednesday call is no longer needed because the schedule is fixed on Mondays. Quote requests are steady, but wins have not moved, so the next project is about follow-up. That is Project Focus Part 2 in action: the numbers show which engine is leaking, and the weekly rhythm lets you aim a project at it. The numbers in this example are illustrative, not from a real business.

What the meeting is not

A few things look like this meeting and are not:

  • A status round. If each person talks for three minutes about everything they did, you have a ritual, not a rhythm. The color and the one sentence are enough.
  • A brainstorm. Ideas are welcome, but they go on a list, and the owner of the list decides what becomes a project.
  • A blame session. A red project is a request for help. If the room punishes red, people will report green until the day they cannot.
  • A substitute for a plan. The weekly meeting steers. The 90-day sprint and the one-page plan from Part 1 say where you are steering to.
A small team of four seated around a small table in a short meeting with one laptop and notebooks
A small table and a short meeting are enough. The rhythm is what matters.

The other beats of the rhythm

The weekly meeting is the heart, and two slower beats support it:

  • Monthly review (60 minutes). Once a month, look at the trend of the three numbers over the last few weeks, review each project's goal and decide what to keep, change or stop. This is also the time to look at the data from a wider angle, as in the data-driven project management guide.
  • Quarterly reset (half a day). Every quarter, choose the next three projects, using the idea of the 90-day sprint. Drop what no longer matters. Recheck whether the three numbers are still the right three.

Inside the week there are two small beats, too: a Monday 10-minute check by each owner on the plan for the week, and a Friday 10-minute look at what was done. They can be a message and not a meeting. A habit, not a ceremony.

How it fits a team that works remotely

The same shape works on a call. Share one page on the screen, turn on the cameras if you can and keep the five parts. Remote teams need the rules more: start on time, one voice at a time and no side conversations in the chat. Send the page after the meeting so that the commitments live in one place. For people who are not at the table, a short communication plan says who needs to hear what and how often.

Your first four meetings

The first meeting will feel awkward, and that is normal. A simple plan for the first month helps the habit stick.

  • Meeting one: set the page. Spend the time writing the three numbers and the list of projects on one sheet. Do not try to fix anything. The goal is that everyone can read the same page.
  • Meeting two: close the loop. Start with the commitments from meeting one. Notice how many were done. Whatever the number, say it out loud without blame, and ask what made the done ones easy and the missed ones hard.
  • Meeting three: trim. By now you will know which project updates are noise. Cut any number nobody looks at and any project nobody owns. A smaller page is a better page.
  • Meeting four: ask for feedback. Ask the room what to keep, what to stop and what is missing, and change one thing. Then promise to run the same shape for eight more weeks before you judge it.

Most teams notice the change around week three, when someone says, without being asked, "I will have that by Thursday," and then does. That sentence is the sound of a rhythm working. It is also the moment to protect the habit from the two enemies of every routine: the busy week and the clever idea. When the week is busy, shorten the meeting, but do not cancel it. When someone proposes a new format, thank them and wait until the eight weeks are over. A rhythm is valuable because it is boring, and boring is what lets everyone see the numbers move.

One last thing about tone

The tone of the meeting decides whether people tell the truth. If the first red project is met with questions about what the owner needs, the next red project will be reported a week earlier. If it is met with a sigh, the next one will be hidden until it is a crisis. Leaders set the tone with the first thirty seconds after bad news, so rehearse them: thank the person, ask what they need and write down the commitment. That small ritual is worth more than any template, and it costs nothing at all.

Mistakes to avoid

  • Skipping when it is busy. The weeks you skip are the weeks you most needed it.
  • Using the meeting to fix problems. Park them.
  • Changing the numbers every week. If the scoreboard changes, you cannot see a trend.
  • Letting the boss talk first. In the project part, let the owners speak before the leader comments.
  • No written commitments. If it is not written, it is a good intention.
  • No end. A meeting with no clock expands to fill the day. Use a visible timer.

Try it: schedule your first meeting

The tool below builds a minute-by-minute agenda for your own 30-minute meeting. Pick the start time and you get the five parts, with the clock time of each.

Interactive tool

Your 30-minute weekly meeting

Loading the tool…

What to do this week

  1. Choose a day and a time and put the meeting on everyone's calendar for the next eight weeks.
  2. Write the one-page sheet: the three numbers, a list of commitments and a list of projects with owners.
  3. Run the first meeting even if the numbers are rough. The habit is more important than the data.
  4. Start a parking list and a decision log.
  5. After four meetings, ask the team three questions: what should we keep, what should we stop and what is missing?

Next Thursday, in Part 5, we turn goals into owned projects with the project card: one page that says what, why, who and by when. The weekly meeting will have a list of projects to look at, and the card is how they begin. If you want help setting up the rhythm in your business, see my services or take the diagnostic.

Frequently asked questions

How long should a weekly business meeting be?

Thirty minutes is enough for most small teams if the meeting has a fixed shape: scoreboard, last week's commitments, projects, decisions and new commitments. If it regularly runs over, move the problem-solving into a separate short meeting with only the people who need to be there.

Who should attend?

The owners of the numbers, the projects and the decisions. Others receive the one-page summary afterward. A smaller room makes it easier to start on time and to keep the conversation on the page.

What if the scoreboard shows bad news?

Say it plainly and decide what to do about it. A scoreboard that reports only good news is not a scoreboard. The meeting's rule is that a red number or a red project is a request for help, not a failure, so people keep reporting honestly.

How is this different from a stand-up or a sprint review?

It is related. A stand-up is usually daily and about the work in progress, and a sprint review is about what a team delivered. The Project Focus weekly meeting looks at the whole business: the three numbers, the projects and the decisions. Teams that already stand up daily can keep it and still use this meeting for the bigger picture.

Monthly newsletterNext issue · Dec 1

Everything new, once a month.

One email on the 1st of every month with everything new: articles, series parts, news, website updates, project results, where I am working and the business opportunities I am looking at. No spam.

  • Fresh on the site right now
  • ArticleUtah Business, Part 3: Hiring and Staffing in a Tight Labor Market
  • NewsUS construction spending fell 1.9% in September: what to read before you react
  • SeriesThe weekly rhythm: a 30-minute meeting that runs the business

One email a month, on the 1st. Leave any time.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Be the first to react.

Comments

Loading comments…

Leave a comment

No email and no sign-up. Every comment is reviewed before it appears. Please keep it respectful and leave links out.

Keep reading

More ideas you may like.

Keep exploring

Related projects and services.

Next step

Let's find the project that moves your business.

Tell me where things are stuck. I will tell you which project I would start with.