A weekly meeting can report on everything and decide nothing.
Numbers get read out. Updates get given. The same issue comes back next week.
Reporting feels productive. Everyone speaks, everyone hears the numbers, and the time fills itself.
Solving is harder. It needs a clear issue, a little silence and someone willing to say what the real cause is. Without a fixed agenda, the easy part wins.
The fix isn’t a longer meeting. It’s a different use of the same time.
Keep the agenda the same every week
Same order, every week: a quick check-in, the numbers, the goals, the to-dos, then the issues. Nobody has to plan the meeting. Reporting stays short because everyone knows what comes next, and the time goes where it should: solving issues.
Name the issue in one line
“Support is slow” is a complaint. “Customers are waiting more than 24 hours for a first reply” is an issue someone can solve. Name what you see, not the fix you suspect: one line, in plain words, with the name of the person who raised it.
Find the cause before the fix
At Harborline, the sample company we use across this site, two things were slipping. Dan’s training goal was off track. Average first reply had missed its target three weeks running.
Sam offered a cause: “We leave it to whoever is free.” Check that guess against the work: who covered the inbox on the slowest days?
A cause you can change is not always the real one. At Harborline, the check held up: nobody owned inbox coverage. Fix that, and you work on both symptoms at once.
Decide, then move on
Knowing the cause does not always settle the fix. There may be competing fixes, limits or a trial to run. Agree on one, write it down and go to the next issue.
Solve the issues that matter most this week, not all of them.
Leave with an owner and a date
A decision without an owner is a wish. Write it down: “Sam will own coverage and assign the schedule by Friday.” It becomes a to-do with Sam’s name and a due date.
Check that it helped
An issue isn’t solved when the to-do is done. It is solved when the agreed problem is resolved and the improvement holds.
Agree what “resolved” means when you choose the fix: for Harborline, first replies under 24 hours week after week, not one lucky week. If there is no number, agree what to look for instead.
Keep the issue open and check it next week. If the problem returns, give it a history: what you tried and what happened.
When this works, the same problem stops coming back. A longer issues list is not always a bad sign: a team that trusts the meeting may raise more.
