In descending order of urgency/size you would store the information into different "action notes" like: - Calendar events - [[Tasks]] or [[My Resources/My MOCs/Habits|Habits]] - [[Projects]] - Keep information and related notes of a project - Can also include other [[Outputs]] notes like [[Brainstorms]] or content that we are actively working on - [[Goals]] - [[Areas]] - [[Resources]] - Archives Technically resources and archives are not "action notes", but they should still be considered as potential places to put notes in when organizing by actionability. # Example > [!info] > From [[Knowledge Accelerator Presentation Slides]] - Projects 🚧 - Areas ⛰️ - Resources 📝 - Archives 🗄️ notes: You're probably familiar with Tiago Forte's PARA method where you organize notes on actionability. Whenever you come across a new piece of information, you start at the top and find the most relevant project, area, or resource to put it. For my productivity system I apply those principles but on steroids thanks to the link based nature of obsidian and the additional places in my setup --- - Calendar events 📆 - Tasks / Habits ✅ - Projects / Creative Outputs 🚧 - Goals 🎯 - Areas ⛰️ - Resources 📝 - Archives 🗄️ notes: So instead, my [[Information actionability hierarchy]] looks like this. If I start at the most actionable note and can't find it there, I can just visit the next level. I store calendars and events in akiflow, and everything else in Obsidian To see this in action, we can look at the knowledge process for creating this presentation itself ! --- ## Start - [[Knowledge Accelerator Presentation]] - [[Knowledge Accelerator Script]] - [[Knowledge Accelerator Presentation Slides]] notes: First I had to set up mental scaffolding for the ideas I'll need to store and thinking I have to do: - For my main central point, I created a project note that all relevant information will be inside of or existing notes will be linked to - Keaton gave me some suggestions of previous presentations to get a sense on what the presentation could be like, which I used to pick out any interesting ideas. i try to just keep any small snippets of information in the project note unless they grow big enough to warrant their own new note or be used in other activities - To figure out what I wanted to include in the presentation, I made a brainstorm note where I pooled together relevant notes and created my first outline - And to better present this information, I created a note for the slides I would use ---  notes: - Then yesterday, more information came from when i was doing a mock presentation with my friend Aidan. At the end of my demo, he sent this wall of suggestions, as well as other ones that came from chatting after. Instead of feeling overwhelmed by all the things wrong with it though, I just added them to my project note as tasks and slowly checked them off later on in the day. --- ## Moving ideas - Feedback -> Future checklist - Diagrams -> Atomic notes - Slides structure -> Future video tour notes: The next step is organizing information after the task is completed, but I'm still in the middle of presenting. Instead what I CAN tell you is how I would do so. so, let's go through the information inside or linked to this project and think about if there's anything reusable I can move to other notes Some of aidan's advice presentation can be helpful so i can create a note on public speaking note --- [[USV Documentation]] 📝 [[2024 Second Brain Tour]] 🚧 notes: can also use the way I went about this project as a reference a rough guideline to follow when i do another presentation, so after I do my reflection and think of some future improvements I can also link this to the existing ideas in my public speaking note Explanations and illustrations that emerged from the creation of these slides like the solar system diagram can be added to my overall setup documentation notes. The structure and flow itself can also be useful inspiration for an upcoming video note of my vault tour, so will link it to that video note. As a result of this additional maintenance, the effort from my time spent on this presentation ended up being unexpectedly helpful for a lot of other initiatives in my vault and is once again accessible thanks to organizing for actionability.