How many decisions made in a meeting have evaporated by Friday? How many “who was supposed to do what?” resurface the following week? Meetings cost time and attention, and yet the way we document them — hurried notes on a sheet of paper — is stuck in the nineties. We can do much better, with less effort.
The hidden cost of “taking notes”
There's a simple cognitive problem: while you write, you're not really listening. The brain doesn't do two things well at once. So, by taking notes, you miss the nuances, the implicit decisions, the tone in which someone said “we'll see”. And in the end you're left with a page of partial notes that nobody will ever open again — because rereading someone else's notes (or your own, written in a hurry) is almost useless.
The real goal of a meeting isn't “having notes”. It's remembering what was decided and acting on it. Everything else is trimmings.
Record, don't write
The first change of habit is the simplest and the most effective: capture the audio and stay present. With Itomori you record on the spot or upload the recording of a call, and from there on the tool does the work.
A common-sense note: recording other people requires transparency. Let the participants know and ask for their okay — it's a matter of respect, as well as good practice. In many settings a simple “mind if I record so we don't miss anything?” at the start is enough.
Transcript, summary and key points
From the audio you get three things. The full transcript in your language (with the raw text always available, if you want to go back to the exact source). A readable summary that condenses an hour of talk into a few paragraphs. And the key points: decisions, deadlines, things to do. What used to be a messy stream becomes a note you can check in thirty seconds.
Find everything later: search and connections
A meeting doesn't live in isolation: it ties into a project, earlier decisions, ideas voiced elsewhere. Itomori connects the note to the others by meaning, so you find it even weeks later by searching for a concept (not the exact word) and you see the threads that tie it to the rest of your work — a bit like a brainstorming session that, instead of ending up on a wiped whiteboard, stays and grows.
It's the difference between “having the minutes” and “having a memory”. Memory is what makes you say, three months later: “wait, we already discussed this — here's what we decided”.
From meeting to action
The last step is the one that matters most. From the key points you generate the follow-up in one gesture: a recap email for those who weren't there, a to-do list with the actions, an update for the team. It's the Create phase: the meeting doesn't end up in an archive, it ends up in something that gets things moving.
Not all meetings are the same
“What to extract” changes depending on the kind of meeting. Keeping three categories in mind helps you avoid drowning in the transcript:
- Decision-making (alignment meetings, committees): here what matters are the decisions and the owners. The summary has to answer “what did we decide and who does what”.
- Creative (brainstorms, kickoffs): here what matters are the ideas, even the ones tossed out casually. Better to keep them all and connect them to the project, because the value often emerges later.
- Informational (presentations, demos, client calls): here what matters are the facts and the objections. The summary is for those who weren't there and for you a month from now.
Knowing what kind of meeting you're in, before it even starts, makes the summary far more useful — because you know what you're looking for.
An example: from audio to follow-up
A forty-minute call with a client. While you talk, you really listen: no pen in hand. At the end you have the recording. In a few seconds Itomori gives you back the full transcript, a five-line summary and the key points: “the client is worried about delivery times”, “wants a demo by Friday”, “budget confirmed for phase two”.
From there, one gesture: you turn the key points into a recap email for the client and a to-do list for the team. And when, three weeks later, someone asks “what did we say about the timeline?”, you don't dig through your memory: you search, and the note is there, connected to the project. The meeting has become action and memory, instead of evaporating.
What about the participants' privacy?
Recording a conversation touches on a serious issue: other people's data. The golden rule is transparency. Always say that you're recording and explain why (“so we don't miss anything and I'll send you a recap”): in the vast majority of cases nobody objects — in fact, it comes across as professional. For calls with clients or suppliers, a line in the invite or a verbal okay at the start is enough.
Where those recordings end up matters too. With Itomori your data stays in the EU, under the GDPR: no small detail when a meeting covers clients, numbers and confidential decisions. A good work tool must, above all, be a place you can trust — that goes for your own thoughts and, all the more, for those shared with others.
A mini checklist
- Before: ask for the okay to record and state the goal of the meeting in one sentence.
- During: record and listen. No frantic note-taking: at most a mental asterisk on the important moments.
- After: generate the summary and key points, turn them into follow-ups, and let the note connect to everything else.
See how it works on the Product page, or find out how to turn voice notes into content.