Meetings, and what happens after them

Adaeze has a call booked with MedSupply — the equipment supplier from module 4's handover file — to renegotiate a contract that renews automatically in three weeks. Thirty minutes on the calendar. No agenda. Left to itself, this call will run forty-five minutes, cover the pricing question twice because nobody wrote down that it got answered the first time, and end with "let's circle back" on the one thing that actually needed a decision.

An agenda is not a formality you add to look organised. It is the single intervention most likely to make a meeting shorter, because it forces the decision about what the meeting is for to happen before the meeting, when there is time to think, instead of during it, when there is not.

A meeting without an agenda is a conversation. A meeting with one is a piece of work with a start and an end.

Four things, every time

A working agenda is short enough to read in the time it takes to sit down. It has four parts, in this order:

1. Objective. One sentence: what decision or outcome this meeting exists to produce. If you cannot write this sentence, the meeting probably should not be thirty minutes on someone's calendar — it should be an email.
2. Topics, each with an owner and a time box. Not "pricing" — "pricing: renewal rate, MedSupply to present, 10 min." A time box next to every topic is what stops the first topic eating the whole meeting.
3. Pre-reads. Anything a participant needs to have looked at beforehand, named specifically, sent with the agenda — not "the usual documents."
4. Decisions needed. The one or two things that must be decided before anyone leaves, stated as questions with a yes/no or a choice, not as open topics. "Do we accept the 8% increase or counter at 4%?" — not "discuss pricing."

Worked example

For the MedSupply renewal call, the objective read: decide whether to accept the proposed 8% increase, counter, or move to the alternative supplier scoped in June. Three topics, each timed — MedSupply presents the increase, we compare it against the June quote, then decide — and one decision needed by the end: accept at 8%, counter at a number, or give 30-day notice today, since the window closes in three weeks. The full template, ready to fill in for your own meetings, is in the worksheet pack above.

Notice what this does before the call even starts. MedSupply now knows they need to justify the number, not just state it. Adaeze knows the meeting cannot end vaguely — one of three named outcomes has to happen. And you, taking notes, already know the shape of what you are listening for.

Send it the day before, not the morning of

An agenda sent an hour before a call is barely better than no agenda — nobody has time to look at the pre-read or think about the decision in advance, so the meeting still does that thinking live, which is exactly what the agenda was meant to prevent. Twenty-four hours is the useful minimum. For anything with a pre-read longer than a page, give it two working days.

When there is no agenda and you cannot get one made

Sometimes the other side calls the meeting and won't produce an agenda — a client's accountant, say, who "just wants to chat through a few things." You can still impose structure from your side: send a one-line note beforehand — "Ahead of tomorrow, is there anything specific you'd like Adaeze to have looked at, or a decision you're hoping to reach?" — which usually surfaces the real objective even when the other party hadn't named it to themselves.

The MedSupply call happens. Thirty-eight minutes of talk: pleasantries, a story about a shipping delay in April, the actual pricing negotiation, a tangent about a trade show, and finally the decision. A transcript of all of it would run to nine pages. Nobody will ever read a nine-page account of this call — not Adaeze, not you, not future-you trying to remember what was agreed six months from now.

Meeting notes are not a record of what was said. They are a record of what changes because of what was said.

The test for every sentence

Before writing anything down during a meeting, run it through one question: if this sentence didn't exist, would anything Adaeze does next week be different? If yes, capture it. If no — however interesting, however true — leave it out. The shipping-delay story is genuinely interesting. It changes nothing about what happens next. It does not belong in the notes.

Four categories, and only four

Good meeting notes sort everything into four buckets. Nothing else earns a line:

1. Decisions. What was actually decided, stated as a fact, not a discussion. "Accepted MedSupply's renewal at 5%, countered down from their initial 8%" — not "we talked about pricing for a while."
2. Actions. Who does what, by when. Covered in full in lesson 5.3 — this is where the meeting's talk becomes someone's task list.
3. Open questions. Things raised but not resolved, that need an answer from someone not in the room, or more information before a decision can be made.
4. The parking lot. Things that came up, matter to someone, but are out of scope for this meeting. Written down so the person who raised it feels heard, and so it doesn't get raised again next meeting because it was never acknowledged.

Worked example: the same 38 minutes, two ways

Notice the shipping-delay story and the pleasantries appear nowhere in the right-hand column. That is not an oversight — it is the whole discipline. Ninety seconds of the call mattered. The rest was the social fabric that makes people willing to have the conversation at all, valuable in the room, worthless on paper afterward.

Capture live, clean up within the hour

Write the four buckets as headings before the meeting starts, and drop lines under them as things happen — you will not remember the exact wording of a decision made forty minutes ago if you wait until the call ends to start writing. Then clean the raw version into the sent-out version within the hour, while the context is still fresh enough to fix anything ambiguous.

"We should look into whether the insurance portal can be set up for automatic renewals." Someone said this in a meeting, everyone nodded, and it will never happen — because it is not an action. It is a thought wearing the costume of an action. Nobody owns it, nothing is due, and "look into" doesn't describe a task anyone could actually finish and check off.

Talk becomes work only when it has a verb, an owner, and a date. Remove any one of the three and it quietly reverts to a thought.

The shape every action needs

Every line in the actions bucket from lesson 5.2 should be checkable against this shape before it's written down:

Worked example: vague to owned

Notice the fourth and fifth lines have owners who were not you or Adaeze. That is deliberate — an action list only for your own side's tasks is half a record. If MedSupply's Tunde owes a confirmation, write it down with his name on it, same as anyone else's. It is what makes the follow-up in lesson 5.5 possible at all: you cannot chase a debt nobody wrote down.

When the meeting doesn't give you a date

People often agree to do something without naming when. Don't quietly assign a date yourself and hope nobody minds — ask, in the room if you can, or in the follow-up note if you can't: "By when should we expect the early-termination check?" A date supplied afterward, in writing, that nobody objects to, functions the same as one agreed live. A date you invented and nobody confirmed does not — it just moves the ambiguity from "when" to "did we actually agree to that."

Send the list within the hour, and ask for silence to mean agreement

The follow-up note — decisions, actions with owners and dates, open questions — should go out within an hour of the meeting ending, while everyone still remembers agreeing to it. Close it with one line: "Flag anything here that doesn't match your understanding — otherwise I'll take this as agreed." That single sentence turns a passive record into an active one: silence becomes confirmation, not ambiguity.

An automatic transcription or note-taking tool can join a call, produce a rolling transcript, and hand you a first draft of a summary before you've even finished typing your own notes. Used well, it is a genuine time-saver. Used as a replacement for paying attention, it will eventually put a wrong number in front of a client and your name will be on the email that sent it.

A transcript is a first draft, never a final record. It listened to the audio. It did not understand the meeting.

Where these tools are strong

Automatic transcription is genuinely reliable at catching the general shape of a conversation — who spoke roughly when, the rough sequence of topics, and a searchable text version of a call you might otherwise have no record of at all. For a low-stakes internal check-in, the raw transcript is often good enough on its own. The failure modes below matter most exactly where the stakes are highest: numbers, names, and who-said-what in a negotiation.

The five errors worth specifically watching for

1. Numbers and percentages, misheard or mis-transcribed. "8 percent" and "80 percent" sound close enough on a mediocre connection that either can come out wrong, and a wrong number in a pricing note is the single most expensive kind of transcription error in this whole module. Verify every number that affects money or a deadline against your own live notes.
2. Proper nouns and acronyms, mangled. Names the tool hasn't seen before — "Tunde," "MedSupply," "HealthPlan" — get autocorrected into the nearest dictionary word, or spelled a different way each time they're said. A transcript with three spellings of the same supplier's name across one call is common, not a fluke.
3. Speaker attribution, wrong during overlap. When two people talk over each other — common in the moment someone jumps in to push back on a price — the tool often assigns the interjection to the wrong speaker, or merges both into one. This matters enormously for a negotiation, where "who actually said 5%" is the whole point.
4. Accents and audio quality, systematically worse for some speakers. Transcription accuracy is not evenly distributed — it tends to be measurably worse for accents underrepresented in the tool's training data, and worse again on a poor mobile connection. In practice this means the same call can produce a clean transcript for one participant and a garbled one for another, for reasons that have nothing to do with how clearly either person spoke.
5. Silent gaps, not flagged as gaps. When a connection drops for a few seconds, some tools simply skip the missing audio rather than marking a gap — so the transcript reads as continuous when a chunk of the conversation, possibly including a decision, is simply missing. A transcript that looks complete is not proof that it is.

Worked example: the same line, three ways

The rule that makes this safe to use at all

Use the tool for what it's actually good at — a searchable backup, a way to catch something you missed live, a first pass at a rough summary you'll edit rather than send. Never paste its output directly into a client-facing note without reading every number, name, and disputed point against your own live notes first. Your live notes from lesson 5.2, imperfect and human, are the source of truth for anything with money or a decision attached. The transcript is a second opinion, not a substitute.

MedSupply's Tunde owed written confirmation of the 5% by Thursday. It's now Monday. You need that confirmation — without it, the contract renewal in three weeks is unprotected — but you also need Tunde to keep answering your emails for the next two years of this supplier relationship. Chase too softly and it never arrives. Chase too hard and you become the sender whose name makes people's stomach sink, which costs you every future ask.

The goal of a follow-up is never to make someone feel bad for being late. It's to make responding easier than continuing to ignore it.

An escalation ladder, not a single tone

The mistake most people make is picking one tone and repeating it — three increasingly polite emails, or three increasingly terse ones. Neither works, because each message should do a different job. Use a ladder that gets more specific and more visible at each step, never more emotional:

1. Friendly reminder, assuming good faith. One line. Assumes it slipped their mind, not that they're avoiding you. "Hi Tunde — just checking this hasn't slipped through the cracks: could you confirm the 5% in writing when you get a moment?"
2. Specific ask with a real deadline and the cost of missing it named plainly. Still polite, now concrete about why the date matters. "The renewal window closes on the 24th — I'd like to have written confirmation before then so nothing defaults to the old terms. Could you send it by Wednesday?"
3. Widen who sees it. Cc a decision-maker on their side, or loop in Adaeze on yours — not as a threat, framed as normal process. "Looping Adaeze in here so we're all aligned ahead of the renewal date." Being seen by one more person is often the single most effective lever, and it costs the recipient nothing to respond to.
4. Flag it to Adaeze as a risk, with a recommendation. If step three doesn't move it and the deadline is close, this stops being a task you're chasing and becomes a decision Adaeze needs to make — extend, escalate further, or accept the old terms by default. Bring her the situation and a recommendation, not just the problem.

Worked example: the ladder in practice

Over eight days chasing MedSupply's Tunde for that written 5% confirmation: Monday, a friendly one-liner assuming it slipped his mind. Wednesday, no reply — a specific ask naming the 24th deadline. Friday, still nothing — Adaeze gets cc'd, widening who sees it. Monday again, still silence — that stops being a message to Tunde at all, and becomes a note to Adaeze: what's outstanding, how long it's been, and a recommendation to call rather than email, with the early-termination notice as a fallback. Four fill-in-the-blank versions of this ladder are in the worksheet pack above.

Never let silence look like your fault

Every chase should be visible in the record — sent from the account, dated, saved. If a relationship later sours and someone claims "nobody told us the deadline," a paper trail of four increasingly specific, entirely reasonable messages is the difference between that being their problem and it becoming yours. This is also, quietly, self-protection: you did your job at every step, and it is documented.

Know when it isn't your call anymore

Step four exists for a reason: at a certain point, the decision about how hard to push, or whether to accept a missed deadline, stops being an assistant's judgment call and becomes the business owner's. The skill is not chasing forever — it's recognising the exact point where continuing to escalate on your own authority would be overstepping, and handing the decision back with enough context that Adaeze can make it in thirty seconds rather than needing to reconstruct the whole story.