How to review your working week without tracking every minute

A useful weekly review starts with the work you wanted to move forward. Look at a small amount of relevant evidence, add what you know about the circumstances, and choose one adjustment for the week ahead. You do not need a minute-by-minute account to make a better-informed decision.

The purpose is to learn something you can use. If the review becomes another extensive reporting obligation, narrow the question.

“Why did the proposal keep slipping?” gives you a more useful starting point than “Was I productive?”

Start with what mattered

Choose a few pieces of work that deserved attention. These might include preparing a decision, understanding an unfamiliar system or developing a difficult piece of writing.

For each, ask what you hoped would be different by the end of the week. Then look at what actually changed. Use the work itself, feedback and your professional judgement to assess progress.

Keep this question separate from time spent. A long session may have revealed that the initial approach was wrong. A short conversation may have resolved a dependency that had held up days of work.

Both can matter. Neither is fully explained by its duration.

Bring together three kinds of information

Your calendar shows commitments and planned opportunities. A record of deliberate focused work shows the sessions you chose to capture. Your notes and recollection explain the circumstances.

Use them together without asking any one source to tell the whole story.

You can do this with a calendar and a few notes. If you use FlowQuota, Reporting provides a record of captured Focus and working patterns. Start with the question you want to answer, then use the relevant view.

Look for an explanation you can examine

Suppose you planned to prepare a recommendation on Tuesday, recorded Focus on Wednesday and completed the draft on Thursday.

It is tempting to conclude that Tuesday was a failure and Thursday was your best day. The sequence alone does not tell you that. Tuesday's meeting might have supplied the information you needed. Wednesday's session might have done most of the reasoning. Thursday might have been a final edit.

Ask what each period contributed. Then look for a condition you could change: missing inputs, poorly timed collaboration, unclear scope or insufficient space to stay with a problem.

This is also where you should challenge a pattern. Did a quieter afternoon help, or was the task simply more familiar? Did you record less Focus because you were interrupted, or because you forgot to record work?

An incomplete record can still be useful when you remember what it leaves out.

Choose one change and give it a fair test

A review is more useful when it ends in an action you can recognise next week.

“Be more disciplined” gives you little to evaluate. “Confirm the required figures before the Wednesday writing block” is concrete. So is “agree who covers urgent questions while I work on the analysis”.

Write down the change, why you are trying it and what you will look for. Keep the assessment proportionate. You are learning how to organise work, not running a controlled experiment.

At the next review, ask whether the arrangement helped and whether anything else changed. Keep it, adapt it or discard it on that basis.

Use FlowQuota to support the review

FlowQuota gives you several ways to examine your deliberate Focus. Reporting shows the recorded pattern. Focus Score provides a consistent, deterministic measure of recent Focus behaviour. AI Briefings interpret available evidence through Patterns, Risk Signals, Recommendations and Coaching Notes.

Those views can prompt a useful question or an adjustment you had not considered. You bring the knowledge of the work and the constraints around it.

Explore AI Briefings or see what Focus Score means.

Before closing your review, complete this sentence: “Next week, I will change ___ because ___.” If the answer is practical and connected to what you observed, the review has done its job.

Continue with making time for focused work around meetings or judging AI productivity advice.