Meetings and email are where most professionals lose most of their week. They are also where AI help is most oversold, so let us be precise about what works.
Meeting notes: the recording is not the point
Automatic transcription is now good in most major languages and cheap or free in most video tools. That is not the win. A transcript of a 60-minute meeting is 9,000 words nobody will read. You have converted an hour you cannot get back into a document you will not open.
The win is the layer above it. From a transcript, ask for exactly three things:
- Decisions. What was decided, and by whom. Not what was discussed — decided.
- Actions. Who owes what, by when. Name, task, date. If a date was never said, write "no date agreed" rather than inventing one.
- Open questions. What was raised and not resolved.
That structure works for a hospital handover, a school department meeting, a client call, a municipal committee. Notice what it excludes: the discussion. Almost nobody needs the discussion. They need to know what they now owe.
Then read it. Attributions get scrambled — transcripts confuse speakers, especially on bad audio, in accented English, or when people talk over each other. "Priya agreed to cover the shortfall" when it was actually Rahul is not a small error; it is the kind that turns into a dispute.
Before you record: ask
Recording and transcribing a meeting is not a neutral act, and consent rules vary widely by country and by state. Some places require every participant's consent. Some workplaces forbid it outright. And beyond the law, there is the plain fact that people speak differently when a machine is listening — the half-formed idea, the honest doubt, the thing said carefully off the record. Say at the top of the call that you are recording, and say where the notes will go. If someone objects, take notes by hand.
Do not record a meeting where clients, patients, students, or personal grievances are discussed unless your organisation has explicitly approved the tool for that. See the next lesson.
Email: triage over composition
Everyone reaches for AI to *write* emails. The bigger gain is upstream.
- Reading a hostile or confusing thread. "Here is a 14-message chain. What is actually being asked of me, and what has already been agreed?" This is compression on something painful, and it works well.
- Deciding what needs you. "Sort these subject lines into: needs a decision from me, needs a reply, needs nothing." Rough, but rough is fine for triage.
- The difficult reply. Not "write this for me" — "here is my angry draft; keep every point but remove everything I would regret." You keep the substance, lose the damage.
Two rules I would not bend
Never let it send. Auto-reply and auto-send is where quiet disasters live: a wrong commitment, a wrong price, an apology for something you did not do. Draft, always. Send, never.
Do not paste a whole thread into a public chatbot without thinking. Email threads carry other people's names, salaries, complaints, medical details and contract terms. You did not write most of it and it is not yours to share. That is the next lesson, and it is the one that matters most.
Before you move on