A twenty-minute Friday review of everything you handed off this week

By Friday afternoon you have handed off a dozen things: a draft here, a summary there, a chore that now runs on its own. Which ones were worth it? Which cost you more in fixing than they gave back? Without a look back you carry on with the same habits, good and bad, for months.

A short weekly review turns a pile of handoffs into a system that improves. It takes twenty minutes, it is the same every week, and it works for tasks given to colleagues, tools or AI assistants. Here is the shape of it. The examples are illustrative.

Minutes 0 to 5: List what you handed off

Write down every task you delegated this week, one line each, with who or what took it. Your sent messages, your task list and your calendar will jog your memory. You cannot judge what you cannot see, and the small handoffs are the ones you forget.

Minutes 5 to 10: Mark each one

Give every item one of three marks: kept as it came back, needed light edits, or needed a redo. Be honest. The redo pile is the interesting one, and nobody else is going to read this list. For each redo, jot down roughly how long it took. It is surprising how often one small, recurring redo costs more than the one dramatic failure everybody remembers.

Minutes 10 to 15: Tally the reasons for rework

For each redo or heavy edit, write a single reason in a few words: “wrong audience”, “missing the file”, “too long”, “figures not checked”. After a few weeks the same two or three reasons keep returning, and those are exactly the places to improve your briefs. A tally of reasons is more useful than a vague feeling that it is “not quite right”.

Minutes 15 to 20: Choose one change for next week

Pick one change, no more. Maybe a line you will add to every brief, a task you will keep for yourself, or a check you will run before accepting a result. One change is easy to carry out and easy to judge a week later. Write it as a sentence you can check next Friday: “Every brief names the source file.” If you cannot tell whether you did it, the change is too vague. Five changes are a project, and projects get dropped.

For every recurring job: keep, change or stop

Beside each handoff that repeats, write one word. A routine nobody reads can stop. A routine that needs a rewrite goes on next week’s list. A routine that works is left alone. It is a ten-second decision per item, and it keeps your setup from filling up with things nobody needs.

A hypothetical Friday

Twelve handoffs. Seven kept, three lightly edited, two redone. Both redos have the same reason: “missing the file”. The change for next week is to attach the source file by name to every brief. The following Friday there is one redo, and the reason is a different one. That is the review doing its job.

Keep the pages

File each week’s page in one folder, newest on top. After a month you can look back at the tallies and see which reasons are shrinking and which are stuck. That is a better source of ideas than any checklist you could copy from somewhere else.

Where Octuo fits

We’re the Octuo team. Octuo is a personal assistant and one starting point for work across AI, tools and specialist services, and it reports back when a job is done, which gives your Friday review something concrete to look at. Octuo is moving fast, and every release widens what it can reach, so it is worth rereading your list of handoffs from time to time to see what else could now be handed over. Octuo is available for macOS.