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.
Meetings improve when the note exists before the meeting does. How to use one running note for the agenda, the decisions and the follow-ups — and what to keep out of it.
The difference between a meeting that produces something and one that produces a feeling is usually a note that existed before anybody joined the call. Not a long one: a heading, three topics with owners, and a blank space under each. Do that and the meeting runs itself; skip it and the first ten minutes go on establishing what the meeting is for.
Write two things as they happen: what was decided, and what somebody agreed to do by when. Discussion is what the meeting is for; recording it is almost never useful and occasionally harmful — minutes attributing positions to people make the next meeting more cautious. If something is unresolved, record it as unresolved with the name of whoever will resolve it, which is the item most often lost between a meeting and its notes.
Read the actions out loud before the call ends. It takes thirty seconds and routinely surfaces one action that two people each thought the other had taken on.
Verbatim quotes, who disagreed, and anything you would not be comfortable with the subject reading. Notes get forwarded, included in disclosure and found years later by somebody with different assumptions. The test is simple: if a line only makes sense alongside the tone of voice it was said in, leave it out.
Ettex Notes suits the running-note pattern directly: one note per recurring meeting, checkboxes for actions, and links out to the documents discussed. Where actions need chasing beyond the next meeting, they belong in a register with owners and due dates rather than inside the note.
Not the person chairing, if the meeting matters. Doing both well at once is hard, and the chair ends up recording their own version of events.
Short enough to read in a minute. Decisions, actions, owners, dates. Length is inversely correlated with how often they are read.
Per series for anything recurring. The previous fortnight sitting directly above today's agenda is what stops the same topic being raised twice.
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.