How to organize a catch-up meeting

[Ehsanuls55]

The mechanism of daily update meetings is simple: gather your team and let them take turns addressing three issues:

What did you do yesterday?
What are you going to do today?
Is there anything blocking your progress?
This is the so-called "Round Robin" method , but you can also use the "Walk the Board" method , where the entire team discusses each task on the Board in a specific order (usually from left to right).

Think of the questions above as steps that each team member must follow to make the meeting yield the desired results. Let's explain each of them in more detail so you know what to look for in the answers.

Question 1: "What did you do yesterday?"
This question serves several important purposes, aside from the obvious tally of completed tasks. It demonstrates whether a team member can prioritize urgent tasks over those that can wait, which is crucial in a fast-paced environment.

ClickUp 3.0 Timeline View Detailed Local Workload

Visualize team workloads with the Timeline view to track progress and adjust task deadlines

At this stage, you can also uncover potential inefficiencies and planning errors. For example, if one team member says they didn't get much done while another was swamped with tasks, it's a clear sign that you need to rebalance the workflow and readjust the workload accordingly.

Finally, sharing information about completed tasks can help your team collaborate more it directors managers email list effectively and gain valuable insights they’ll need for their next assignments.

Someone may have already completed a task similar to what another team member will do next, so they can lend a hand.

Question 2: "What are you going to do today?"
One of the main points of a catch-up is to set the course for the next day and ensure that upcoming tasks are aligned with the overall goal. This step allows you to proactively filter out low-value work and increase your team’s effectiveness.

Let's say you've discovered an authentication vulnerability that needs to be patched urgently. If one of your team members says that their initial plan for the day was to complete a less time-sensitive task, such as refactoring legacy code, you can tell them to put it on the back burner and work on the security issue.