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.
- 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.
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.