Many small teams hold a weekly status meeting. Each person says what they did, the others listen politely and half of it is already known. Forty minutes for six people is four hours of working time every week.
A short written note can carry the same information. It is not a clever tool. It is a fixed format that takes about ten minutes to write and two minutes to read.
Step 1: the five lines
Every note has the same five lines, in the same order:
- Done: what was finished this week. Finished means the customer or the next person can use it.
- Next: what comes next week, at most three items.
- Blocked: what is stuck, on whom and since when. If nothing, write "nothing".
- Number: one figure that matters for the area, for example open orders, tickets waiting, or days to the next delivery.
- Decision needed: one question for a named person, with a date by which you need the answer. If nothing, write "none".
Keep each line to one or two sentences. If a line needs a paragraph, it belongs in a separate document and the note only links to it.
Step 2: who writes and who reads
- Writer: one person per area or project, the one who knows the work. Not a manager collecting texts from others.
- Time: the same day every week, for example Friday at 14:00. A fixed time makes the note part of the week, not an extra task.
- Readers: the manager and anyone who depends on the work. Keep the list short, so the note stays a note and does not become a broadcast.
- Place: one shared channel or one email thread. Not three places.
Step 3: how readers respond
Silence means "understood". Readers reply only in two cases:
- they disagree or see a risk the writer did not mention;
- they can remove a blocker or answer the decision line.
A reply is written under the note, so everyone sees it. If the manager needs a number that is missing, they ask for it once and the writer adds it to the next note.
For the numbers themselves, see weekly capacity check for a small team.
Step 4: when a meeting is still worth it
Some things do not fit into five lines. Call a short meeting when:
- the Decision needed line has no answer by its date and two or more people have to agree;
- the same item stays under Blocked for two weeks in a row;
- the notes from two areas contradict each other;
- something changed that affects the whole team, such as a lost customer or a new priority.
Give the meeting one question and a time limit. A useful companion is a twenty-minute weekly operations meeting for teams that want a fixed slot, and a one-page decision record to write down what was decided.
Step 5: review after a month
After four notes, spend ten minutes with the readers:
- which line was read and used, and which was ignored;
- whether the number was the right one;
- whether any meeting became unnecessary and whether any note was missed.
Cut what nobody uses. A good note gets shorter over time, not longer.
Where it usually goes wrong
- The note grows into a report and nobody reads it.
- The writer changes every week, so the format drifts.
- The decision line is vague, for example "thoughts?", so nothing is decided.
- The manager answers by calling a meeting to discuss the note. That brings back the meeting you wanted to remove.
Summary
Write a Friday note with five lines: done, next, blocked, one number and decision needed. Keep one writer per area, reply only when it adds something, and call a meeting only for a decision that the note could not settle. Review the format after a month.
Sources
- Common practice for small teams, offered as a practical guide. No client results or market figures are claimed in this article.
