A weekly project review that leads somewhere
Five questions that turn a review into a decision and a practical next move.
Start with evidence
What changed since the last review? Bring the work itself where possible: a prototype, a draft, a practice record or a decision. Distinguish completed work from time spent thinking about it. Both may matter, but they tell different stories.
Find the constraint
What is currently limiting progress? It may be time, unclear scope, missing knowledge, a dependency or a decision you have avoided. Choose the constraint that would make the largest difference if resolved.
Choose the decision
What needs to be decided now? State the options and the evidence you lack. Some decisions deserve more research; others need a small reversible test. Name who will decide and by when.
Make one commitment
What will you deliver before the next review? Specify an action, a visible result and a date. “Make progress” is too vague. “Test the prototype with two people and record the findings by Thursday” gives you something to review.
Retain the useful part
Keep a short record of the decision, the reason and the next commitment. You do not need a transcript of the whole conversation. At the next gathering, start here. If priorities changed, record that deliberately instead of quietly abandoning the commitment.
A weekly project review checklist
Set aside a short review at the end of a work block. Open the work itself and answer five questions: What exists now? What limited progress? What decision is needed? What will I complete next? When will I review it? Write one or two sentences for each rather than a detailed account of everything you did.
For example, “worked on the portfolio” records activity. “Drafted two case studies; still waiting for permission to show one image; will ask today and publish the other case study on Thursday” gives next week a usable starting point. Put the next commitment into your weekly planner and keep the decision beside the work.
A review that changes next week
Illustrative example: a maker planned to test a prototype with two people, but spent the week refining its appearance.
- The evidence
- The shell looks better. Nobody has tried the core action yet.
- The constraint
- The maker has not decided what a sufficient first test looks like.
- The decision
- Test the unfinished prototype with one willing person before making further cosmetic changes.
- The commitment
- By Thursday, record whether that person completes the core action, where they hesitate and what help they need.
- The next review
- On Friday, use those observations to choose one functional improvement. Keep the cosmetic work outside this week’s scope.
Put it into practice
Download and print a weekly project planChoose priorities and realistic time estimatesCommon questions
How do I review a week when I did not finish my tasks?
Compare the plan with what actually happened: available time, interruptions, missing inputs and the size of each task. Keep work that still matters, change its estimate or scope, and remove work that no longer serves the result. Carrying every unfinished item forward unchanged hides the same capacity problem.
What is the difference between a weekly review and weekly planning?
A review checks the evidence from the week that ended. Planning allocates the time available in the week ahead. Review first so that the next plan reflects what you learned about scope, dependencies and realistic task durations.
Give the plan a regular review.
For one project that needs private attention, Finish Sprint provides six weeks of scoping, reviews and written check-ins. For an ongoing hosted forum, explore Weekly Counsel.
Use these guides independently, or bring your plan and the work itself into the conversation. If you need help producing an agreed deliverable, see Project Work examples.