GTD: Getting Things Done in Logseq

Guide to Getting Things Done in Logseq

In this video, we will explore how to implement the principles of getting things done (GTD) in practice using Logseq. We will cover capturing, clarifying, and organizing tasks using tags and properties.

Implementing GTD in Logseq

• Consolidate all blocks at the block level under a tag or backlink of your choice.

• Use hashtags for everything coming into your database as part of your capture process.

• For next actions, use the built-in "to do" property by pressing control + enter.

• Use specific tags for context when adding blocks to make it easier to find them later.

Using Tags and Properties

• Think about what context you will need when resurfacing information and add relevant tags accordingly.

• Use forward slash scheduled or forward slash deadline to add calendar-based information to your blocks.

• Use metadata properties extensively, including type reference and project/person tags for reference items.

• Use the tag someday maybe for items that may be useful in the future but are not a priority now.

Reminders and Trash

• Use space repetition or forward slash read/forward slash watch for reminders on items you want to revisit later.

• Use trash for items that are no longer needed.

The transcript includes additional personal approaches used by the speaker.

Quick Capture Workflow

In this section, the speaker discusses their approach to using metadata and keyboard shortcuts to quickly capture information. They suggest thinking about mental triggers and context when entering data into a database.

Using Metadata and Keyboard Shortcuts

• The speaker's approach involves using metadata and keyboard shortcuts to quickly capture information.

• Mental triggers and context should be considered when entering data into a database.

• The "@" symbol can be used as a mental trigger for people, making it easy to find specific individuals in the database.

• Scheduled and deadline blocks can be used for time-based data entry.

Differentiating Context with Metadata

In this section, the speaker discusses how different contexts can be differentiated using metadata. They suggest using symbols like "@" or "$" to differentiate between people or places.

Differentiating Context with Symbols

• Symbols like "@" or "$" can be used to differentiate between people or places in a database.

• For example, "@" could represent a person while "$" could represent a place.

• This makes it easier to filter by context when searching for specific information in the database.

Actions That Can Be Performed in a Database

In this section, the speaker discusses various actions that can be performed in a database. They suggest using tags for next actions, adding energy levels, and using links for recurring meetings.

Actions That Can Be Performed

• Various actions can be performed in a database such as emailing someone or making a call.

• Tags can be used for next actions so that they are easily identifiable.

• Energy levels can also be added to tasks so that they are prioritized based on urgency.

• Links can be used for recurring meetings or projects.

Running Agendas with People

In this section, the speaker discusses how running agendas can be created with people in a database. They suggest using hashtags and filters to easily find information.

Running Agendas with People

• Running agendas can be created with people in a database by using hashtags.

• For example, "#inbox" and "#linda" could be used to filter information related to Linda's inbox.

• This makes it easier to find specific information when discussing topics with individuals.

Using Namespaces for Project Navigation

In this section, the speaker discusses how namespaces can be used for project navigation. They suggest collapsing linked references for easy access.

Using Namespaces

• Namespaces can be used for project navigation in a database.

• Collapsing linked references makes it easier to access project hierarchies quickly.

• This allows for efficient navigation between projects in the database.

Dashboarding with Notion

In this section, the speaker discusses the importance of using dashboards in Notion and how to set them up using queries.

Setting Up Dashboards

• Dashboards are an important part of the process in Notion.

• Queries can be used to set up dashboards, including advanced queries.

• Building great dashboards is possible with Notion.

Example of a Dashboard

• The speaker demonstrates an example dashboard on their main page.

• Quick access items can be added to the menu for easy navigation.

• The example dashboard includes a home page and various queries such as projects list, reminders, and to-do items.

Course Information

• More information about setting up dashboards will be available in other videos or condensed in the course.

• A poll will be put out in the community to gather feedback on whether viewers prefer separate videos or longer ones that are broken down into sections.

• Feedback is welcome regarding timestamps or anything else that would help viewers in future videos.

Video Preferences

• Longer tutorial-type videos may be done in future working sessions with friends.

• Feedback from friends has indicated a preference for shorter, more discreet courses where information is easily found.

• Viewers' preferences for breaking down longer videos into sections or keeping them as one long video are requested.

Conclusion

• The speaker thanks viewers for their support and promises more videos soon.

• This video has been on the back burner for some time but they are glad to finally get it out there.