How to run a weekly review and prepare the next plan

A weekly review helps prepare the next plan when the team goes over completed results and the reasons for carryovers. By the end of the meeting, a concrete decision should emerge that can be verified in the next work cycle.

This kind of review works even for a small team without a dedicated process manager. To start, one project, its promises for the week, and the actual state of work are enough.

Gather the facts before the discussion

Open the original plan for the week and the current tasks. Find the promised results, the actual handoffs, and the recipients' responses. If needed, clarify time entries and significant requirement changes.

Don't judge the week only by the number of closed cards. One delivered piece of work can matter more than several internal small items. Compare the result with what the team agreed on at the start of the cycle.

If there was no original plan, start with the promises that are clearly known. Note this gap and agree to record upcoming results before the next week so the comparison becomes more accurate.

Separate completed, carried over, and cancelled

For completed items, clarify who received the result and whether further review is needed. For carryovers, name the remaining work and the reason. For cancelled items, explain why the task lost its relevance.

This kind of breakdown helps avoid automatically carrying over the entire remaining list. Some tasks need to be reduced, renegotiated, or removed from the upcoming plan if they no longer lead to the needed result.

If the work is finished by the assignee but is waiting for a response, name the owner of the next action. Otherwise, the finished material will endlessly take up space on the list without a clear reason for waiting.

Analyze the causes using concrete examples

The phrase "we didn't have time" describes the outcome but doesn't explain what to change. Clarify when the deviation occurred, what information was missing, and what decision could have influenced the next step.

The causes can vary: new scope, late approval, several parallel commitments, incomplete source materials, or a wrong estimate. Each needs its own actions.

Don't turn the review into a search for someone to blame. Check the conditions and agreements that the team can actually change. If the cause lies with an external participant, discuss a way to see the risk earlier and report it.

Example: recurring waiting for feedback

A training situation: two results during the week were delayed because of a late client response. The manager sent almost finished materials on the last day, leaving little time for comments.

The team decides to test an early draft handoff. The manager agrees on the feedback moment in advance, the assignee prepares the material for that point, and the final handoff is planned taking the response into account.

A week later, the participants look at whether the early review took place and how it affected a specific piece of work. They don't declare the new procedure successful just because they held an extra meeting.

Choose one improvement and a way to verify it

Formulate the change as an action: request source materials earlier, limit parallel work, or clarify the definition of done before starting. General wishes like "communicate better" are hard to verify.

Name the person responsible, the project where it will be applied, and the date to return to the result. Determine which observable fact will show that the change was made and helped.

You don't have to introduce a permanent policy after a single case. First test the solution on the next similar step. If the conditions differ, discuss them before extending the conclusion to the whole team.

Carry the conclusions into the next plan

Update the upcoming commitments taking into account the unfinished work and the new knowledge. Check that the carryover doesn't conflict with tasks already promised for the next week.

If the result is no longer needed, agree to cancel it. If the scope has grown, clarify the conditions and the deadline. If the obstacle remains, assign an action to remove it, not just a new due date.

At the start of the next cycle, briefly remind everyone of the chosen improvement. Then the review will be connected to real work and won't remain a separate conversation that no one returns to.

How to use PRO-dela for the review

Projects and tasks in PRO-dela provide a working basis: descriptions, statuses, deadlines, and discussions. From them, you can reconstruct changes and compare promises with the actual result.

Keep the reasons for carryovers and the next decision in the relevant context. Link the tasks of the next cycle to the current statement of work so the assignee doesn't continue working under outdated conditions.

The review itself remains a team ritual. The material doesn't imply an automatically prepared retrospective, a performance forecast, or a guaranteed reduction in timelines.

How to keep the review useful

Limit the discussion to questions that affect the next actions. A debate about the details of one task can continue separately with the relevant participants, keeping the outcome in its context.

At the end, briefly repeat the decisions: what is completed, what is carried over and for what reason, and which change we are testing. Participants should understand the next step in the same way.

If the same problems are discussed week after week, check whether the previous decision was carried out. Perhaps it had no owner, no conditions for application, or no moment of verification.

Frequently asked questions

Do you have to run the review on Sunday?

No. Choose a convenient moment at the end of the work cycle, for example Friday. The order of the series' publications doesn't require the team to work on weekends.

Is a meeting of the whole team needed?

It depends on the number of participants and shared dependencies. Some facts can be gathered in advance, and only decisions affecting several people need to be discussed together.

How do you know the review is bringing benefits?

Check whether the next plan changes based on the conclusions and whether the chosen actions are carried out. The mere fact of a regular meeting doesn't yet answer this question.

Start with one project

Choose a project in PRO-dela, compare the weekly promises with the results, and write down one improvement with an owner and a verification date. Use this conclusion when drafting the next plan.

Sign up for PRO-dela. The current terms of use are available on the pricing page.