Backend engineer
Kenji Ito
I plan the week as a short list of outcomes, and the day notes keep the rest honest.
Kenji works on payments infrastructure, where a week can change with one incident. He wanted a plan that stayed short enough to survive that.
Each Sunday he writes three outcomes for the week and one line per day for what he expects to ship. Day notes record what actually happened.
When an incident takes a day, the unfinished work moves forward with one action. The next Sunday starts from what was done, not from what he hoped.