There are loads of posts like this out there. Everyone and their Mom has a way of using Notion to manage their life now. It makes sense. Itās flexible and robust. However, that strength is also itās greatest weakness in my opinion. At least for someone like me who gets so caught up in building the bike shed, instead of the actual task at hand.
Thatās why, this year, I set out to create something simple that works well enough for me, without over complicating my life with layers of processes I wonāt stick to. It started with me trying to clearly define my intentions, and the guardrails I need in place for myself to succeed.
I started by journalling out what I needed and the typically things I fail that I needed to safeguard against. Something I wanted to be sure Iād let myself do this time around, is only systematize what needed to be systematized, when it needed to be systematized. No premature optimisations. This is the list I came up with:
- Adding a new item should be quick and painless
- Getting the info I need, when I need it, should be easy
- Allow me to review when things were accomplished
- Properly setup my daily, weekly, monthly and yearly goals
- Be reminded of those goals when selecting my tasks for the day
- Be flexible enough to evolve with my needs as they change
Out of the methods Iād tried in the past the one that stuck with me the most is the Getting Things Done (GTD) methodology. Particularly, the review process. If youāre unfamiliar with the GTD methodology, I highly recommend this pragmatic 15 minute intro guide: https://hamberg.no/gtd.
My one failing has been keeping up with the weekly review. So far itās been a few weeks and I havenāt missed it yet but I can tell itās not lodged deeply into any weekly routine I have yet. And, I tend to struggle with routines outside of a daily schedule, so Iām hoping to figure that one out soon. If anyone reading this has advice on setting up routines outside of a 24 hour period, Iād love to learn more!
Though GTD covers the core principles of what Iām after, I decided against using the entire system for simplicity sake. I also found that with GTD, the greater context of my tasks get lost. I have a hard time seeing the forest for the trees when Iām hyper focused on daily todos. It makes losing the why behind certain tasks a little too easy for me. Thatās why I only kept a few core parts:
- The idea of an āInboxā or āInā list
- The āNext Actionsā list
- Weekly Reviews
Adding to these 3 points, I want to make reviewing on monthly and yearly time scales easier. This is where Notion really shines with itās databases. Being able to create goals on a longer time scale and referencing them within tasks lets me create a graph of where my time is being spent, and how effective Iām being at accomplishing those goals. Which, Iāll talk about how thatās setup in the next sections.
Whatās the setup?
I have 3 main pages with 2 databases setup. Thatās it. The rest of the pages have to do with writing longer form content like blog ideas, journal entries or meeting notes. Though, most of my journal entries or meeting notes end up living in GoodNotes or Nebo on my iPad now, so I donāt use it for much long-form content other than blog posts.
Iāve blocked out some task & goal titles using black bars since they contain sensitive information.
Iāll start with the Databases since each page is built based on them.
Goals
Goals are āend statesā Iād like to achieve. The way I define goals isnāt unique, but what having them defined in this way lets me do is associate each one to other tasks and goals. This heirarchy lets me understand what each component is building towards. Iāve tried to set a limit for myself by only allowing 3 goals in each time horizon and domain (work or personal). This constraint will reduce the chances I have too much on my plate at a given time. It forces me to prioritize based on whatās most important in my life. My goals are allowed to change at any time. After all, Iām human, and our needs have to adapt. If I finish a goal before the time limit, I will not add a new one. That just means I have more time to focus on the other things. The same goes for removing a goal if I decide it no longer serves a purpose.
Each year, month, and week Iāll sit down to review what Iād like to accomplish, and break it out into smaller components.
Letās take my āYearlyā goal of ā52 Weeks of Creationā for example. Every month, Iāll sit down and perform a monthly goal review and see if there are month-level goals I want to achieve for the yearly creation goal Iāve set. If there are, Iāll break it down into a monthly component. Then every week, Iāll look at each monthly, or yearly goal without monthly components, and define week-level achievements.
Anatomy of a goal
The properties are fairly simple, with most of the complexity happening in the āTime Leftā property, which is just a formula to calculate how many days are between āTo Accomplish Byā and todayās date. āActionsā is a āRelationā property type that will point to any tasks assigned to this goal directly. Parent Goal & Child Goals are any goals of a different āTime Horizonā that relate to the goal Iām looking at.
āCompleted on Timeā is a check-mark I manually tick off if I complete a goal before I reach the deadline set. This way I can go back and analyze what types of goals I drag ass on. Iād love to automate checking that box when a goal āStatusā is marked as āDoneā but unfortunately Notionās feature set doesnāt allow for side-effects based on interactions. Iād probably have to reach for something like Zapier to accomplish that. If anyone has any tips, Iād love to know!
Action Items
The āAction Itemsā database is just that, a list of every task Iāve added. Each of the pages (Inbox, Next Actions and Today at a Glance) use a Linked Database filtered by different criteria to ensure each of those pages keeps a specific focus.
The anatomy of a task
A task itself is pretty simple. The title of the task is the action I need to perform, and the content of the page, if required, contains any extra context I might need.
You might notice I have āDomainā listed three times. The first āDomainā is the domain thatās pulled from the goal, the other property āDomain (Today)ā is for tasks that donāt fit a specific goal but still belong to one of the Domains. As youāll see below in the filtered views of the āNext Actionsā database, I group tasks by āDomain (Group)ā which is a formula that takes the text from the ones thatās filled so I can group the tasks properly.
The 3 pages are:
- Inbox
- Next Actions
- Today at a Glance
Each of the pages have an almost identical layout but filter āNext Actionsā using different criteria to ensure that I limit the amount of noise depending on which step of the process Iām in. For example: during inbox clearing, I donāt want to see tasks that Iāve already organized. This could also be achieved by having a singular āPlanningā page and using different views with the āNext Actionsā table. I just find itās more satisfying switching pages and having the title & image change. It shifts my mindset the same way changing physical environments does.
Inbox
My Inbox is the āIn listā in the GTD methodology. Itās where I dump any unprocessed action item I need to get done. Sometimes itāll contain ideas as well. Basically, anything that I want to remember to process but at a later date. A good example of that is sometimes, when Iām in bed, Iāll get an idea for a blog post, product, etc. I want a place I can quickly add something and know that tomorrow morning Iāll deal with whether or not itās actually important. It lets me offload any mental processing to when Iām in a state to actually do it.
The setup is pretty simple. It contains reminders of the intent behind this phase of the process, a link to the next step of processing my āNext Actionsā, then a list of my goals grouped by domain.
Having my goals always visible help me triage my inbox items with a more critical eye. If a task doesnāt fit into those goals, do I really need to do it? Unfortunately, most times they do still need to be done, but itās always nice to call the things youāre doing into question. Why waste time on unimportant things if you donāt have to?
Processing an inbox item typically goes as follows:
- Open the page and rename the title to something more āactionableā
- Set the progress to āNext Actionā
- Change āReview Stateā to āActionā
- Attach a goal (if applicable) and set the āDomainā if no goal is selected
- Add any extra context to the body of the page that the action might require
Like in the GTD method, something I do my best to hold to is, if the item can be done in ~2 minutes, then do it immediately. I often have tasks to contact someone about the status of something, or reach out to a friend I havenāt spoken to in a while. Those types of tasks typically get knocked out during processing. In which case, I immediately set them to āDoneā and set the āMarked Doneā date to today.
Once my inbox is empty, I move on to the āNext Actionsā list.
Next Actions
The setup is almost identical, except that Iām now looking at things in a card view split by domain. This gives me a glance at what my backlog is like for tasks. This is where priority & time start to play a part in my planning for the week.
I tend to ping-pong between this page and the āToday at a Glanceā page to make sure Iām not over-committing what I can do in the day.
Iāve internalized the Eisenhower Matrix when it comes to organizing my tasks. Iāll typically asses a task based on how long ago it was added, and if itās been over 2 days that I havenāt touched it, Iāll strongly re-consider its value. Those tasks might fall into the āDonāt Doā bucket of the matrix. If itās a task Iāve been dragging my feet on but is still importantāthis mostly happens with personal home tasksāIāll do my best to kick my ass into gear and get it done today. After using time, Iāll asses the goal the task is attached to. Is it a goal with a deadline coming up? Iāll try to complete items that fit that criteria first.
Tasks that should be done today get marked as āDoing Todayā which get moved to my āToday at a Glanceā board. Tasks that donāt get moved stay here so that tomorrow I can go back and look through them again to re-prioritize.
Today at a Glance
This page is where my focus lands for the rest of the day. I try to keep this open on my iPad at all times so I can quickly glance at what I should be working on right now. I havenāt been diagnosed, but I strongly suspect I have some form of attention deficit, since I can get sidetracked incredibly easily.
This page forces me to reassess where Iām spending my time during the day, and gently remind me that thereās a task I have āIn Progressā that I should be crossing off my list.
For the most part it works. There have been times this past week where meetings run long or Iām a little more tired/scattered, so I lose sight of this page. I havenāt yet figured out the optimal way to keep this list top-of-mind while working.
What can be improved?
I still donāt have a great review system setup. This project is ongoing, so I didnāt expect to have one until I needed one. Outside of weekly reviews, Iāve yet to hit my first month using this system, so Iām sure itāll evolve as time goes on.
Iād love to be able to sit down and create a productivity/focus chart with the data from these databases. Itāll help me understand where my time was spent month over month, and the distribution of tasks with and without a goal. I might even be able to see how long tasks take me to complete on average, and by looking at the titles, be able to start classifying tasks by ātypeā of work. Do I drag on admin work? Engineering work? Product work? What seems to excite me vs drain me?
Part of what I plan on refining over the next few months is a proper retrospective for myself. Iāll be sure to write about the journey, since I think it would be fun, and meta, to reflect on a retrospective.
As I said throughout this post, if youāre reading this and youāre screaming at your screen with ideas, feedback or questions, feel free to email me: alex [at] alexcaza [dot] com.
If you enjoy my work and want to show some support, you can donate a few bucks through ko-fi. Your generosity won't be forgotten š