A weekly project review you can finish

Friday arrives and you know you've been busy. You remember a difficult afternoon, a useful conversation, and several hours at the desk. But explaining what changed in the project takes longer than expected.

A weekly project review is a short pass through the work you can actually inspect. It ends with a few decisions: what moved, what remains uncertain, and where to begin next week. You can write it for yourself, share it with a collaborator, or adapt it into a project update.

Start with fifteen minutes and one project. That's a suggested budget, not a rule. The review is finished when the next step is clear enough to start.

Bring the work into view

Open the latest draft, repository changes, notes, or completed tasks. Use the calendar and recorded sessions to jog your memory, but keep the results nearby. “Three sessions on the landing page” tells you where some time went. “The pricing copy is drafted and the small-screen layout still needs review” tells you where the project stands.

If you use Pomo Cowork, your projects can help you find the task you're continuing, subject to the account options shown in the app. A paper list works too. Don't spend the review building a new tracking system before you've looked at the work.

Separate activity from a change you can point to

An activity describes what you did: reading, discussing, drafting, testing. A result describes what is now available or understood because of it.

Sometimes the result is a finished piece. Sometimes it's a decision that an approach won't work. Both can matter. Be specific enough that next week's version of you won't need to reconstruct the context.

For example, replace “Worked on importing files” with “The importer handles the sample file; duplicate rows still produce two records.” The second sentence contains both progress and the next problem.

Avoid turning every small action into a milestone. You only need the changes that affect what happens next.

Try this fifteen-minute review

1. Minutes 0–4: collect the evidence. Skim the week's tasks, session notes, and changes. Open the current version of the work.
2. Minutes 4–8: write what changed. Choose a few results, decisions, or findings. Link to the relevant material in your own notes if useful.
3. Minutes 8–12: name the unfinished work. Separate a task you can continue from a dependency you can't resolve alone.
4. Minutes 12–15: choose the first next action. Put one realistic work block in the coming week and make sure you know how it begins.

If you have several projects, repeat the short review only for those you actively worked on or need to decide about. A paused project may need one sentence confirming that it remains paused.

A template with a complete example

Here's a fictional example for a small website project. The names and results are illustrative, not a customer story:

Project: Portfolio refresh
Changed this week: Drafted the two case-study summaries and replaced the old screenshots in the first case study.
Evidence: Current draft and updated image folder.
Still open: The second case study needs an image I haven't located. Its layout also needs a phone-width check.
Decision: Publish the first case study before expanding the second.
First next action: Read the first summary against the project brief and mark any unsupported claims.
Time reserved: One 25-minute block on Monday, then reassess.

You can copy the same six labels into a blank note: project, changes, evidence, open work, decision, first action. Add a time reservation if it helps you follow through. Remove any field that repeats information you already have in front of you.

Read focus time alongside the result

Time records can help you notice that a recurring task takes more attention than you budgeted. They can't tell you, on their own, whether a decision was sound or a draft is ready.

If a task used several sessions and remains unresolved, look at what happened inside those attempts. Did each block advance the same problem? Were you waiting for input? Did the scope change? The appropriate response might be a smaller task, a question to someone else, or a different approach.

Resist comparing your session count with a coworker's. Two people may be handling very different amounts of uncertainty. A coworking check-in can focus on what is ready and where help would be useful instead.

Turn the review into a manageable next week

Choose one next action before listing everything the project might eventually need. Make it physical and recognizable: open the sample file, check three references, sketch the error state, or send the missing question.

Then give it a block you can actually attend. If the task has been expanding every time you touch it, define a stopping rule using timeboxing. For a straightforward restart, the 25-minute timer is a reasonable place to begin.

You can keep the review private. If you share an update, include only information you're comfortable making visible, and check links for internal or client material. A public update doesn't need your full working notes.

Leave the review where you'll see it at the next session. The most useful final sentence is often very ordinary: “Open the first case study and check the second paragraph.” On Monday, that is enough to get back to work.