Skip to main content

Using a Second Brain

For years I have collected books, URLs, Blog Posts, YouTube videos, pretty much anything I can to keep learning. 20 years ago I had a very well organized set of Browser Bookmarks that moved to GetPocket & Feedly. I didn’t realize it but for the last 20 years I have been building my “Second Brain”. A collection of my Goals, Projects, Tasks, Resources and Knowledge collected across a set of curated tools.


Recently I discovered that Notion.so (one of the tools I have used for the last 5 years) has a template for a Second Brain so I can pull everything together in one place through the power of relational databases. 


The image below shows work in progress the consolidation of my second brain, based around the P.A.R.A. Method by Tiago Forte and some lessons from the book Make Time by Jake Knapp. Each Brain Area has a definition and purpose, projects, tasks, resources and a knowledge base, each of which is just a view of the related databases that are filtered for each Brain Area.





I have found the process of modernizing my Second Brain very enjoyable knowing my knowledge and experience is now accessible any time on any computer, tablet or phone and all in one place. If you haven’t already, I highly recommend getting a free Notion account and investing in a second brain 🧠 

#secondbrain  #knowledgemanagement #productivity

Labels:

Comments

Post a Comment

Popular posts from this blog

Increasing Analytical Thinking in Agile Teams

Shameless promotion alert! I did a talk this week with the Agile Auckland meetup that was about increasing analytical thinking in Agile Teams. Agile Auckland kindly filmed the virtual session and its uploaded to YouTube here. If you are passionate about analysis and improving the quality of it in your Agile team, please go and check out the video. A link to the Youtube video is below
Post a Comment
Read more

Misusing the word Requirements

The more I think about the word #requirements the more I think it is and has been misused for decades, by myself included. Imagine I have a bunch of nuts, I don’t know what size the nuts are which means I don’t know what size spanner I need. I could write a BABOK format Requirement that explains that “The solution shall have a spanner that loosens a nut easily” but no one can build anything from it because we don’t actually know what size spanner to build. We don’t need a requirement. We need more information. How about a hypothesis instead? I believe that if I test a range of spanners on the nuts I will find the right size, I will know when I am successful as the nut will be turned by the spanner without slipping. Now this tells me what I need to do and how I know I will have found an answer. Let’s imagine the result is that we discover we need a 10mm spanner for our 10mm nut. Now I can write a requirement that says The solution shall provide a 10mm spanner that can turn a 10mm nut co...
Post a Comment
Read more