A Friday review template that takes five minutes
Most Friday reviews are either a meeting nobody prepared for or a doc nobody reads. This template is neither. It takes five minutes to run and keeps momentum visible.
The Friday review is the part of the weekly rhythm that dies first. Monday is exciting. Wednesday is useful. Friday is tired. If you do not actively protect it, it becomes a private note and then not even that.
Here is a shape that works. It takes five minutes to fill out per person, five minutes to read as a team, and generates the context Monday starts from.
The template
For each teammate, three sections. Three lines each. No paragraphs.
### [Name]
**Shipped**
- [one line]
- [one line]
**Didn't, and why**
- [one line]
**Roll to next week**
- [one line]
That is it. Three questions, no long form.
Then the team lead adds a closing paragraph at the bottom.
## Team wrap-up
One paragraph. What is the one thing we learned this week. What will we do differently next week. Celebrate one thing out loud.
Why this shape
Short fields force honesty. "Shipped: login flow redesign, 14-day retention dashboard, hiring loop round 1" is fine. "Shipped: worked on a lot of things this week, mostly unblocking the team and preparing the onboarding work for next week, also some hiring prep, also helped with the retention dashboard" is noise.
One line per item. Multiple lines allowed. Paragraphs not.
A "didn't and why" section beats a "blockers" section. Blockers are a Wednesday thing. On Friday, the question is different: what did we say we would do and not do, and what does that tell us about next week.
A "roll to next week" section beats a separate rollover list. Every unfinished item either rolls forward or gets explicitly dropped. There is no third category. Items that are not named here quietly disappear and the team stops trusting the review.
One team wrap-up paragraph beats a dashboard. Dashboards are for reading. Paragraphs are for thinking. The team lead's wrap-up is the weekly equivalent of a 1:1 summary — it synthesises, it names the pattern, it celebrates one win.
When to write it
Write it before 5pm Friday, not Monday morning. The reason is blunt: the review is the thing that teaches Monday what to do. If it gets written on Monday, Monday was working without context.
An async review written by everyone individually, then read once on Friday afternoon by the team lead, then closed out with a paragraph, takes the team lead about fifteen minutes total for a team of ten.
What to do with the output
After three or four weeks you will have a stack of reviews. The high-leverage use is not archival; it is pattern-spotting.
- Which team members keep rolling the same items forward? Usually a scope or prioritisation problem, not a capacity one.
- What is your "didn't and why" pile telling you? Usually: missing decisions, unclear ownership, or scope being set optimistically on Monday.
- What do the wrap-up paragraphs actually say about this team? That is your retro material for the next one.
The review is not primarily for the team. It is primarily for the team lead, because it is the only artefact where "what we actually did vs what we said we would do" is written down, honestly, every week.
That gap is where the job lives.