Files
kfitz.info/content/blog/2022-12-16-tasks-matter.md
Kathleen Fitzpatrick 655ad0ded8 upgrade to 3.0
2024-10-14 19:27:15 -04:00

3.8 KiB
Raw Permalink Blame History

title, permalink, date, tags
title permalink date tags
Tasks Matter /tasks-matter/ 2022-12-16T14:35:48-05:00
reflecting
post

At some point in the last couple of weeks, a link passed through my hcommons.social feed pointing me to Ben Newtons post on task-tracking in Obsidian. I loooooooove Obsidian. Love it. I keep all of my research notes in it, as well as a wide range of personal notes (e.g., the list of Christmas shopping I have not yet completed). But Im super-aware that Ive barely begun to scratch the surface of what it can do. And so with tasks. Ive had a long-standing morning routine of looking at my to-dos, which Ive captured and tracked in Things 3 (which I also love!), and transferring my top priorities to a daily note that helps me think through how the day will be structured. It had honestly never occurred to me to track my to-dos in Obsidian, much less that doing so might help me automate some of my day-planning, not to mention help me prevent random action items emerging from meetings from getting forgotten as I jump to the next Zoom call. But the combination of Newtons post and Ellane Ws article on creating daily and weekly notes that feed into one another convinced me to start tinkering.

The first thing I did, after installing the Obsidian Tasks plugin, was to create a Tasks list using the gist that Ben provides at the bottom of his post. And then I experimented a lot, changing the parameters that each of the subcategories in the list uses to gather and filter tasks, the ways that theyre displayed, and so on. (The Obsidian Tasks documentation is awesome.)

Then I used the Obsidian Columns plugin to create two callouts at the top of my daily notes template (which relies on the Periodic Notes plugin), one for daily calendar events and one for the priority tasks for the day. It wound up looking like this:

Today's daily note

Each morning I now create the days note, which uses the following code in the template to generate the callouts:

An ugly mess of code that I cannot get to render in markdown

The first column is for the days events; I havent (*yet*) found a way to pull my schedule from Outlook, so for now Im manually creating a list of scheduled meetings and such each morning. The second column, however, automatically pulls exactly the tasks I want to see each morning: the routine items I do each day, plus the tasks Ive created that are due soon (or are overdue) and that have been marked as priority items. Its not the prettiest piece of logic but it works.

One of the routine tasks thats included in the list is “change block to done.” At the end of the day today, Ill open up that code block and change the logic for the list of tasks from not done and that knot of parentheticals to instead read done date 2022-12-16, which will show me a nice checklist of what I managed to accomplish.

I do this for two reasons: it prevents the days note from updating if I open it on subsequent days (as it will always be “today”), and that allows me then to aggregate each days note, using Ellane Ws method, into a weekly record of what got done.

Plus, each days notes, down below the events and tasks callouts, can include action items (such as those from todays grant planning call) that then get aggregated to the task list.

So far, I love it, and its making me love Obsidian even more to see the power of what it can do. If youve used Obsidian for this kind of thing, Id love to hear more about it.