The Weekly Project Meeting

Chapter 1 Episode 4

The weekly project meeting is the most regular touchpoint in your research life. This article will be a bit lengthy (compare with the previous ones), so I am going to give you the actionable suggestion first, then explain the rationales behind, because some of you might feel bored reading the rest of the text, which is fair enough.

Actionable Suggestions

One best practice is to keep one shared slide document for the project, and add new slides for each meeting so that every report, discussion point, and action item lives in one cumulative place. When it is time for the next meeting, you continue the document, and over weeks and months, this single file becomes the most complete record of how your project evolved, including what was tried, what worked, and why decisions were made.

With the documentation in place, you should organize the meeting itself in the following five parts, regardless of how long the session runs (under 30 minutes is ideal, but might be a bit challenging for junior researchers).

1. Revisit the to-do list that was agreed on at the end of the last meeting and check what was completed, what was delayed, and what shifted, so everyone starts the conversation from the same shared understanding of where things stand.

2. Share a small number of papers that you believe are worth the whole team’s attention, for instance, because they are highly relevant to the current work, inspire a new direction, or carry implications for a decision the team needs to make. At the early stages of a project, this might be as many as five papers, and as the direction firms up, one or two is usually enough.

3. Present the progress report, which is where the real substance of the meeting lives. Walk through what you and any supporting researchers did to tackle the problems on the to-do list, the obstacles you encountered along the way, what you tried in response, your rationale for each decision, and the results. The rationale is the critical piece because your other team members do not know how to comment on an action without understanding the rationale behind it, whereas a report that includes the reasoning gives your advisor and teammates something concrete to push back on, build on, or confirm.

4. Present any problems that remain unsolved despite the work described in the progress report. More importantly, you should propose solutions with the rationale behind them. For the same reason above, walking into a meeting with “I am stuck, what should I do?” puts the entire burden of problem-solving on the rest of the team, while walking in with “I tried A and B, here is why neither worked, and I think C might address the issue because of X” gives the team a starting point that is far more productive.

5. Lay out a tentative to-do list for the coming period, which closes the loop since the items from this meeting become the first thing reviewed at the next one.

What Leading a Project Actually Means

Leading means much more than having your name appear first on the final paper, since the leading researcher should be the person who has the strongest drive to complete the work to a high standard and on schedule, and is responsible for pushing the project forward day by day, week by week.

I have seen many students treat the weekly meeting as the place where the advisor examines their homework, and I understand why, since most of their academic life up to that point followed exactly that pattern. The meeting I just described works differently because the leading researcher is the one driving the conversation, and the team is responding to the thinking and doing, which means the quality of what comes out depends directly on the quality of what the leading researcher brought in. The meeting, as a result, becomes the leading researcher’s tool for collecting intelligence from the team, since you walk in with your own thinking already formed and walk out with the team’s input layered on top of it.

When I serve as the corresponding author, my role shifts to something closer to a project manager, which in practice means I coordinate the team, help remove obstacles that team members cannot clear on their own, provide directional guidance when the work drifts off course, and ensure the deliverable meets the standard the whole team expects. The leading researcher, in turn, takes responsibility for executing the work and collaborating with the supporting researchers to move things forward.

I make this explicit because I have seen many students carry an assumption that the advisor wants the project completed more than they do, and that their job is to help the advisor get it done. In my case, if I need something done on my timetable and to my standard, I take the leading role myself so I can be directly responsible.

The Meeting as Practice

When a student leads, the project becomes their exercise in developing the independence this entire series has been building toward, including critical thinking, self-directed knowledge curation, problem definition, and the capacity to inspect your own reasoning and catch what you missed. The weekly meeting exists to support that development, because it gives the leading researcher a structured, repeating opportunity to practice independent thinking and then sharpen it against the team’s collective perspective.

Students will encounter obstacles, dead ends, and stretches where nothing works as expected throughout this process, and that is the point, since growth happens precisely when you step beyond what you already know how to do and find a path through problems you have never seen before. Each week that you wrestle with an obstacle, form a rationale, propose a solution, and bring it to the team, you are practicing every skill this chapter has described, from surveying the literature for answers to reading critically, extracting best practices, and documenting your reasoning so it serves you and your collaborators. The weekly meeting is where all of those skills converge into a single, repeating practice.

With the foundational skills from this chapter in place, the next chapter turns to the craft of research writing and design, starting with how to build a motivation, formulate a research question, scope a project, and write the core argument for your work.