Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Trigger-based rapid checklists, published by VipulNaik on October 26, 2022 on LessWrong.
In this post, I describe an approach I've been following for the past few months, and that I feel has been moderately helpful to me: trigger-based rapid checklists. A trigger-based rapid checklist is a memorized checklist that I execute rapidly in response to a specific trigger. I'll explain with examples, and then talk of some of the general features.
Although this wasn't directly inspired by any specific life hack that others use, it has some overlap with trigger-action planning as well as with the ideas popularized by Getting Things
Done.
This post should not be taken as a documentation of the exact details of what I do -- I've left out some details and made some tweaks for simplicity. The information here should be thought of as mostly illustrative of how somebody might use trigger-based rapid checklists.
Examples of trigger-based rapid checklists
Some triggers
I currently have several trigger-based rapid checklists. Here is a list (not necessarily comprehensive):
Morning checklist: I execute this after I start using my laptop in the morning.
Night checklist: I execute this right before I plan to close my laptop in the evening (this is not right before I go to sleep).
Pre-outside trip checklist: I execute this right before leaving my home for an extended period of time (e.g., for shopping).
Post-outside trip checklist: I execute this right after returning from an outside trip.
Context switch checklist: I execute this when I'm switching context between different kinds of work.
Sample checklists
Here is a lightly-edited version of my morning checklist:
[ ] (W) Check the weather for the day
[ ] (E) Catch up on email: personal and work
Also check spam, trash, and all mail (I won't check these for each intermediate check during the day) - [ ] (M) Catch up on Facebook messages
[ ] (S) Catch up on Slack: personal and work
[ ] (C) Check calendar to plan my day
[ ] (A) Turn off alarm
[ ] (L) Run the loose ends script
And here's a lightly-edited version of my night checklist:
[ ] (W) Check the weather for the next 1-2 days
[ ] (E) Catch up on email: personal and work
[ ] (M) Catch up on Facebook messages
[ ] (S) Catch up on Slack: personal and work
[ ] (C) Check calendar for the next 3 days: - For next day, pay particular attention to implications regarding e.g., when to wake up; in particular, try to make it so that I go to sleep at least 9 hours before the time of the first appointment
For the two days after that, make sure that the calendar makes sense, e.g., I didn't mark an incorrect event; if there are things that need to be in sync across multiple calendars (e.g., across two jobs while I'm juggling them), make sure they are in sync
[ ] (A) Turn alarm on for tomorrow
The default alarm setting is 8:30 AM; this is fine for most days (I am usually awake well before this time -- the alarm is a fallback measure) - I should make sure that the alarm time is early enough to be at least 1 hour before any online meeting, and a larger amount of time for other kinds of events
Also use this occasion to make sure that the phone is plugged in and (charging or charged) - [ ] (W) Make sure bedroom window and hall terrace door are open
[ ] (L) Run the loose ends script
[ ] (C) Close lid and cover laptop
Important features of execution of the checklists
Trigger-based nature
These checklists are trigger-based rather than time-based. In general, I've found time-based things hard to adhere to, since there can be many sources of variation such as when I wake up or when I go to sleep. Trigger-based actions are easier to remember, because I just have to build in my mind the association from the trigger to the action. The LessWrong trigger-action planning tag has a bunch of great content explaining why tr...