A good weekly team check-in is short, predictable, and built around two things: what matters most right now, and what is getting in the way. Keep it to a tight agenda, hold it at the same time each week, and use it to surface blockers and reset focus rather than to collect status updates. Done well, it replaces a scatter of chasing messages with one reliable moment the whole team can count on.
What a weekly check-in is for
A weekly check-in keeps a team pointed at the right things between the bigger planning moments. Its job is to confirm the few priorities that matter this week, surface anything blocking progress, and agree who needs what from whom. It is a working session rather than a status report read aloud, and it works best when it stays focused on what helps people get on, not on proving everyone is busy.
Keep it short and predictable
Hold it at the same time every week so it becomes a fixture no one has to chase. Keep it short, often fifteen to thirty minutes for a small team, and time-box it so it does not sprawl. Predictability is the point. When people know the check-in is coming, they save things for it instead of interrupting each other through the week, and the calendar stays clearer as a result.
A simple agenda that works
- The priorities for the week, named plainly, so everyone is working to the same short list.
- Progress since last week, in a sentence each, rather than a detailed report.
- Blockers, with a clear owner for unblocking each one.
- Anything people need from each other this week, asked for out loud.
That is enough. Resist adding standing items that turn a sharp fifteen minutes into a slow hour. If a topic needs a real discussion, take it offline with the people involved rather than holding the whole team.
Run it around how people actually work
A check-in that only suits the loudest voice misses half the team. Some people think out loud, others need the agenda in advance to contribute well. Sharing the agenda beforehand, and knowing from each person's working with me manual how they prefer to take part, lets quieter or more deliberate colleagues prepare rather than be put on the spot. This is the same principle as working with different working styles in a team, applied to a recurring meeting.
Connect the weekly check-in to a quarterly rhythm
A weekly check-in works best as the short loop inside a longer one. The week keeps focus on the current priorities, and a quarterly review of those priorities resets them as the business moves. Without the longer cycle, weekly check-ins drift into habit and chase last quarter's goals. With it, the quarter sets what matters and the week keeps the team working to it, which is part of what makes up a team operating system.
Where this replaces chasing
One reliable weekly check-in does the work that a week of scattered messages and ad hoc calls would otherwise do. When the priorities and blockers come out in one predictable moment, a manager stops pulling for updates and the team stops being interrupted, which is part of how visible ways of working cut the load of too many one to one meetings. To set up a rhythm like this with your team in a single day, the workshop is a direct place to start, and a short call is there if you want to talk it through first.
Common questions
How do I run a weekly team check-in
Hold it at the same time each week, keep it short, and work to a tight agenda: the week's priorities, brief progress, blockers with an owner, and what people need from each other. Use it to clear obstacles and reset focus, not to collect status updates.
How long should a weekly check-in be
For a small team, fifteen to thirty minutes is usually enough. Time-box it so it stays sharp, and take anything that needs a real discussion offline with the people involved.
What should a team check-in cover
The few priorities for the week, a one-sentence update from each person, any blockers with a clear owner, and requests for help. Keep standing items to a minimum so it does not turn into a long meeting.
What is the difference between a check-in and a one-to-one
A check-in keeps the whole team focused on the week's priorities and blockers. A one-to-one is about the individual, their development, and what is in their way. Both have a place, and neither should exist only to move information that could be visible instead.
How often should a team review priorities
Keep the weekly check-in for the current week, and run a fuller review of priorities each quarter. The week keeps focus, and the quarter resets what matters as the business changes.