There’s a meeting almost every growing business has that everybody agrees is worth having and everybody dreads. Usually it’s the weekly team check-in.
It’s where people find out what’s going on, who’s out next week, what’s stuck, and what’s changing. Without it, things fall through the cracks. With it, a chunk of everyone’s week disappears, and the last twenty minutes feel like a hostage situation.
What the owner usually wants to do
Cancel it. Cut it to every other week. Make it optional. It’s a reasonable reaction when people complain about a meeting.
But I’d separate “bad idea” from “good thing designed badly.” A weekly check-in is a good idea. If it’s painful, the design is usually the problem, not the meeting.
What I’d look at
First, what the meeting is actually for. Not what it’s turned into. Most weekly check-ins have a short list of real jobs: everyone hears what matters this week, problems surface early, and people know who will be out so work can be covered.
Then, where the time goes. In most loose meetings, it goes to:
- Updates with no format, so each one expands to fill whatever space it’s given
- Topics that matter to two people, discussed in front of ten
- Problems getting solved live instead of flagged and handed off
- No clock, so nobody knows when to wrap up
What I’d change
Give it structure:
- Time boxes for each part of the meeting.
- Timers, so the time box is real and not a suggestion.
- A clear update format, so people know what to bring and how long they have.
- Defined topics, so the agenda isn’t whatever comes up.
- A standing ask for upcoming time out, so coverage gets planned instead of discovered.
- The same shape every week, so people can prepare.
Anything that only matters to a few people gets flagged and moved to its own conversation. Problems get named and assigned, not solved live.
What I’d leave alone
The meeting itself. The team needs the shared information. The goal is to keep what’s valuable and cut what isn’t.
Then ask
After a few weeks, ask the team what they think. Not “do you like it?” Something more specific: what’s useful, what’s still too long, what’s missing.
The answer you might get is “useful, but still long.” That’s good information. A better-designed meeting isn’t automatically a short one. Meeting feedback is process data. You don’t redesign a meeting once and declare it done. You run it, ask, adjust, and run it again.
The tradeoff
Structure can feel stiff at first. Timers cut people off mid-thought, and some people hate that. Moving topics to a separate conversation can feel like being dismissed. Say out loud why: we’re protecting everyone’s time, and the thing you want to discuss deserves a real conversation, not the last three minutes of this one.
The bigger point
The instinct to cancel a painful meeting is the same instinct that leads businesses to drop useful processes, tools and even roles because they were set up badly. Sometimes the thing really is the problem. Often the thing is fine and the design is the problem.
If people like the meeting but hate how long it takes, don’t cancel it. Fix the format. Then ask them again.
The same goes for a lot of things that annoy a team. The monthly report nobody reads might need to be one page instead of six. The approval process everybody complains about might need a limit, not removal. The onboarding checklist people skip might just be too long. Before cutting something, ask what job it was supposed to do and whether that job still matters.
A few questions to try on your own weekly meeting:
- What is this meeting for, in one sentence?
- What part would people miss if it disappeared?
- Which topics only matter to two or three people?
- Does every update have a format and a time limit?
- When did you last ask the team what they think of it?
If your meetings, or anything else in the business, feel like a good idea designed badly, bring it to a Systems Fit Call.
