Skip to content
Keel
Blog / Method

Write the Friday update from the work

Status updates rot because they are written from memory. Since 4.10, Keel drafts each project's update from what moved that week. What goes in, what we leave out, and how leads edit it.

Every Friday, somewhere, a project lead opens a blank document and tries to remember what happened this week. The result is optimistic, a bit vague and out of date by Monday. Leadership reads it, nods, and asks for a meeting.

Keel already knows what happened: which issues closed, which scope was added, which dates moved. Since 4.10 it writes the first draft at 08:00 on Friday. The lead edits it, picks a health, and shares it.

Checkout v3 · Friday updateOn trackdrafted 08:00
64%
  • HAL-214Coupon field keeps the pay button disabled
  • HAL-207Saved cards on the new checkout
  • HAL-202Address autocomplete on checkout

Saved cards went to review on Wednesday. Coupons are the last blocker before the 10% launch on Dec 14.

Fig. 1 · The draft for Checkout v3. Issues come from the project; the last line was written by Ana.

What goes in

  • Progress as a single number, with the change since last Friday.
  • Issues that moved to Done or In review, by title.
  • Scope added this week, and by whom.
  • Any milestone whose date is now later than the cycle that holds it.

What we leave out

Adjectives. The draft never says “great progress” or “slight delay”. It says 64%, up from 51%, and Dec 14. The lead adds the one sentence that needs a human: why the coupon bug matters, or why the date is fine anyway.

After eight weeks, leads on our own team spend four minutes on the Friday update instead of twenty-five. More importantly, the update is right, because it was written from the work and not from memory.

Camille RoyProduct engineer, web at Keel, in Montréal since 2022.

Keep reading

Ship something by Friday.

Free for three people, for as long as you like. Bring your issues over in minutes.