Notebook
planner, journal, codex, zibaldone, дневник
Why did I write it down? In order to remember, of course, but exactly what was it I wanted to remember? How much of it actually happened? Did any of it? Why do I keep a notebook at all?
Joan Didion, “Sloughing Towards Bethlehem” (1968), “On Keeping a Notebook”
The notebook is mostly made up of lists or logs. Besides being my main planner, it also acts as a note- and a sketchbook. I made this one myself. It’s in A5 and made up of 288 blank pages—nine signatures of eight A4 sheets each. The paper is 90, it’s what I had, but it isn’t great for writing. It’s alright for sketching. It’s also pretty thick for paper. I prefer blank pages for such multi-purpose notebooks. Writing in straight lines isn’t an issue, however, any markings tend to interfere with drawing. For only planners, I’d prefer dot grid. I use squared notebooks for writing morning pages, since the line spacing is tighter.
General Constituents ¶
- title page
- index/table of contents as a two-page spread
- meta as a two-page spread, comments on the use
- Future log as a two-page spread
- Monthly log
- Daily log
- various collections
- read and planned books
- recipe planning
- linking to pages where in the notebook they were written down
- this way I can add notes and adjustments
- linking to pages where in the notebook they were written down
- recipe planning
Some Notes ¶
It minimizes wasted pages. When I’ve dedicated two pages to some collection and have already started some log right after these pages, I find the next empty page, or a spread, and mark next to the last page number of the collection where it continues. The footer of the notebook may look something like this:
100 ->p. 110 101
Issues or Things to Think Through ¶
- tasks can be scattered and thus lost
- when writing tasks for the next day I have to check:
- tasks not done today that could be done tomorrow
- tasks in the weekly plan
- monthly tasks
- tasks in the future log
- any possible external source
- when writing tasks for the next day I have to check:
Markers ¶
Markers are found before each log item. They tend to start off as a “•” and then get turned into a different one.
•
an unfinished/undecided taskX
a completed taskv
a dropped tasks>
migrated into some log in the future<
moved to the monthly log^
scheduled in the future log-
a note+
a note that will turn into a longer journal entry during reflection/
delegated, along with an@
at the end of the task to signify where it went
Specifiers ¶
A log item’s marker may be preceded by an optional specifier.
*
important!
inspiration1/2
how many times the task has already been postponed, “2” means that I’ve tried to do it 2 times without luck. So maybe it’s time to drop it if I don’t find it important enough.
Future log ¶
The future log collects tasks scheduled for some time in the future, beyond the current month, that for this reason cannot be logged in the monthly log. It consists of columns for months and a column for the tasks. The tasks are logged sequentially and marked in one of the monthly columns with a bullet. Scanning down the monthly column then reveals the tasks associated with the particular month.
J|F|M|A|M|J|_______________2023
>| | | | | | 1 jan: task 1
| |•| | | | 3 mar: task 2
| | | |•| | 5 may: task 3
| | | |•| | 9 may: task 4
| | | |•| | 15 may: task 5
| | |•| | | 3 apr: task 6
| | | | |•| 6 jun: task 7
Monthly log ¶
Monthly log is always two facing pages with a calendar, made up of a list of dates, on the left page and a log of tasks and other notes on the right page. The calendar could be filled in after the fact to be used as a reference for a monthly or yearly reflections. The list of tasks on the opposite page initially gets filled from tasks from the future log and any unfinished but still necessary tasks from the previous month. The bottom half of the right-hand page has a weekly calendar for recurring tasks. It is drawn as a nine by nine grid with the first square dedicated for daily recurring tasks and the next seven for recurring tasks on a particular weekday.
The calendar accommodates a habit tracker–some number of columns along the right side:
November
M R
1 M x x
2 T x
3 W x
4 T
5 F
...
30 T
M - meditation
R - reading
The habit tracker can also provide an overview, like an index into the day. When I see later, for example during a reflection, that I had missed a day, I can check the daily log which may give some context into why I didn’t follow through with my habit that day.
Daily log ¶
This is the most typical log. It tends to get created at the end of the day.
- Starts with a header consisting of the date with the weekday:
20/09 samedi
- A log of the day’s activities: tasks, events, notes
- not only before they happen, but also anything significant that happened that day
- log the bigger events into the monthly log
- helps with reflections
- Any notes should have more context than you think necessary in the moment. The future you is incapable of deciphering anything.
- If relevant, write the amount of time it took to finish a task, could help with possible planning in the future
- Have items only in a single column to leave room on the right for reflections
Reflections ¶
Reflection, playing back the tapes, takes place at the end of something–end of the day, end of the week, end of the month, or year.
- tasks that got done
- tasks that didn’t get done and why
- do you plan to do too much, too little
- weekly
- once a week, such as every Sunday evening, write a reflection based on the concluding week
- writing a bit over half a page on the previous week and the rest is left for the next week’s tasks
- monthly reflection is done on the last day of the month
- the reflection tends to be shorter if it can fit somewhere on the pages of the monthly log
- create the next month’s log
Collections ¶
- a collection is a list that gathers a certain topic
- effectively everything is a collection
- however, here we mean a list that isn’t one of the regular lists
- e.g. a collection of books you plan to read this year
- projects should be planned out like lists of tasks
- a collection of tasks to complete the project
- a collection can serve as an intermediary before an index
- i.e. the index would point to the collection, and the collection could be an index of all the relevant pages for the collection, e.g a collection pointing to all the weekly reflections
Elsewhere: About, Bookbinding