Note-taking process

We’ve come up with a process for taking notes at a governance and risk meeting to ensure accuracy, readability and consistency. Here’s how it goes.

Roles

Note-taking is at least a two person job and involves writers and a reviewer.

Writer

Takes initial notes, screenshots, and fixes notes in post-editing with the availability of the recording.

We recommend at least two people do this role, splitting up the work for the entire summary. Multiple writers have the advantage of supporting each other with formatting, screenshots, and quality assurance on sections that they are not taking the initial notes on. Writers use the :hand:(🤚) symbol during live calls to request help from another writer.

Reviewer

Sets up the initial working doc, does a full review of the summary after it's produced, quality checks for formatting and semantic errors, and also submits the final version of the summary to GitHub and the Forum.

Recommended to be done by one person.

1. Reviewer prepares working doc

Create a new doc in HackMD using the template and send it to the writers.

Governance call notes template

2. Writers take notes

Make sure you have the HackMD document to hand and join the governance call.

View calendar invite ↗

If you’re working with someone else on writing the notes, make sure you’ve decided which sections each of you will focus on. We recommend staying in contact with your fellow writers throughout the call.