Meeting notes should focus on clear information. Keep them simple so you can remember details later. Every meeting involves people, and conversations usually fall into a few categories. I use these basic principles to quickly summarize meetings.
I prefer using Obsidian Periodic Notes or Logseq's Daily page for daily notes, rather than creating a separate note for each meeting. I divide each meeting into headings and use tags to mark important points (e.g., Summary, Design, Question, Answer, and Decision). At work, I keep a to-do list within Logseq.
If it's something to hype about later, I tag it to my Hype DocHype Doc
Despite Documenting Meetings, creating a Design Decision Log, Save Screenshots, and having a clear How I use Bullet Journal method, I often draw a blank during yearly reviews. The H....
File Example :
File : 10-Feb-2023.md
## 11:00 1:1 with Person A Private or Broken Links
The page you're looking for is either not available or private!
- #SUMMARY Summary of the meeting goes here. Not Minutes.
- PROJECT1 Private or Broken Links
The page you're looking for is either not available or private!
will have seperate touch notes, for easier search.
- #QUESTION Bigger questions that comes in meeting.
- #ANSWER If someone answer. More answers are added.
- #DECISION Anything we all decide
- TODO Tasks related to meeting
- 10 Notes/Design Decision Log Private or Broken Links
The page you're looking for is either not available or private!
- Changelog as a consistent communication toolChangelog as a consistent communication tool
Changelogs are a great way of effective communication. It provides a clear idea on what is done, and why it's done. Also, it communicates to the user about the value the new feature adds / problem ...
This is the cleaned-up version of my brainstorming session with Parvathi Mohan, Product at Kaleyra, discussing the use of Obsidian and Logseq for work and meeting documentation.
