←

Documenting Meetings

Basic Principles

  1. Have a clear objective for your meeting notes.
  2. Keep your notes concise without losing important information.
  3. Use tools like Toggl for time tracking, if needed. Don't spend time making notes ;)
  4. Atomise meetings to create lists of information, questions, and action items. Utilise hashtags to represent them, such as #Question, #ToDo, #Idea, #Decision, #PeopleName, #ProjectName, and #MajorFeature.
  5. Convert recurring meetings into notes and link them. For example: Project A Private or Broken Links
    The page you're looking for is either not available or private!
    , 1-1 with Person A Private or Broken Links
    The page you're looking for is either not available or private!
  6. Use Obsidian Periodic Notes or Logseq's Daily page for dumping daily notes, instead of one-note-per-meeting

By doing an efficient search you can find any notes : For instance: Project A Private or Broken Links
The page you're looking for is either not available or private!
, #Question #PersonC will take you to daily logs with notes about Project A, that has Questions and Person C.

File Example :

File : 10-Feb-2023.md

- 11:00, Meeting on Project A  Private or Broken Links
The page you're looking for is either not available or private! 
 
	- #Info We are not building that feature in this sprint #PersonA
	- #ToDo Update the figma, remove the feature 
	- #Question Are we updating the documentation?, to #PersonB
	- #TIL, the date we shared with client is Q3, not Q2
- 13:00, 1:1 with Person A  Private or Broken Links
The page you're looking for is either not available or private! 
 
	- #TODO Prepare next year hiring count and budget
	- #Question Ask #PersonC, if we are hiring remote or to WFO
	- #Idea, add a survey along with Project A  Private or Broken Links
The page you're looking for is either not available or private!

My current method

  • I use journal to make live meeting notes.
  • Notes are then moved to my Obsidian daily logs.
  • Notes are either Decisions or Questions. (New things I learn from a meeting, are technically a decision. I don't differentiate them)
  • Journal takes care of the To-Dos. (Same live meeting notes)
  • For projects I use 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.