Knowledge capture: writing things down before the person leaves
Knowledge capture fails as a documentation project and works as a habit attached to real work. Where to start, what to skip, and why the expert is the wrong person to write it.
Decisions, owners and dates — a structure that takes five minutes and survives the week.
Useful meeting notes record three things: what was decided, who owns each action, and by when. Everything else — the discussion, the arguments, the digressions — is context that almost nobody rereads. Write the decisions during the meeting, confirm the owners before it ends, and send the notes the same day.
A transcript is not notes. If the person who missed the meeting has to read four pages to learn what changed, the notes have failed.
If a meeting produced no decisions and no actions, that is worth recording too — it is the clearest signal that the meeting did not need to happen. For a board or committee the requirements are stricter, and board meeting minutes template shows what has to be captured.
Where the notes land matters as much as how they are written. A note taking app that syncs, searches and shares turns scattered records into something a team can rely on afterwards.
Ettex Notes handles the mechanics: tags, checklists, links between notes and documents, and version history if you need to see what changed. Actions can become calendar events or board cards without retyping, since the apps share one account.
A recording is an archive, not a summary. It solves “what exactly was said” and does nothing for “what do I do on Monday”.
Not the person leading the discussion — they cannot do both well. Rotate the role, or give it to whoever is least central to the topic.
For an hour-long meeting, a screen. If it takes longer to read, the decisions are buried in narrative.
Somewhere every attendee can open without asking permission — permission requests are where notes go to be forgotten.
Knowledge capture fails as a documentation project and works as a habit attached to real work. Where to start, what to skip, and why the expert is the wrong person to write it.
A decision log records what was decided, by whom, and what was rejected. The format that takes two minutes, and why the rejected options are the part worth keeping.
An annual general meeting has rules about notice, quorum and voting that decide whether its resolutions are valid. What to get right, and what small companies can skip.