Meetings: Before, During, After

The real cost of a meeting

Do the math nobody does: a ninety-minute meeting with five participants is seven and a half hours of work consumed — almost a full staff day. If it produces neither a decision nor a clear action, it's not a meeting, it's a bonfire of collective time. Marc's firm holds about twelve meetings a month between internal check-ins, client appointments and file committees: the deposit is enormous, and it isn't found during the meeting, but around it.

Because that's the paradox: a failed meeting is almost always lost before it starts — no clear objective, no documents read, no memory of past decisions — and finishes losing itself afterwards — no follow-up, forgotten actions, the same debates the following month. The time in the room is only the visible part. Good news: the before and the after are precisely preparation, synthesis and follow-up tasks — everything you now know how to delegate. Chapter 3 gave you the minutes; this one completes the entire cycle.

Before: the decision-oriented agenda

A good agenda is not a list of themes ("invoicing update, migration update, misc"): it's a list of questions to settle, each with its allotted time and the person who presents it. "Approve the migration schedule: 15 min, presented by Marc" engages everyone differently than "migration update". To generate it, provide the meeting's objective, the participants, the duration and the recent history — typically the previous minutes, which you already have thanks to chapter 3.

Prepare the agenda for my monthly meeting with the client Bâti-Rénov (renovation company, 22 employees).
Context: duration 60 min, participants: me, my business partner, the owner and his in-house bookkeeper. Main objective: approve the quarter's budget forecast and settle the question of financing the new truck.
Here are the minutes of the previous meeting: <paste>.
Produce:
1. An agenda in 4-5 points maximum, each phrased as a decision to make or a question to settle, with duration and owner
2. The opening recap of last month's decisions to verify (2 min)
3. The list of documents each participant must have read before the meeting
Format: fits on half a page, ready to send.

AGENDA — Bâti-Rénov × Firm — Thursday 2pm (60 min)

0. Opening (2 min) — last month's decisions: held?
1. DECISION — Approve the Q3 budget forecast (20 min) — presented by: Marc
2. DECISION — Truck financing: lease or loan? (15 min) — presented by: partner
3. QUESTION — Hiring an apprentice: impact on payroll costs? (10 min) — presented by: in-house bookkeeper
4. Actions & next deadline (8 min) — who does what, by when

To read before the meeting: Q3 forecast (2 p.), financing comparison (1 p.)

Before: briefing the participants

Second preparation lever: make sure the meeting starts at hour zero of the thinking, not hour zero of the information. If the participants discover the numbers in the room, you're paying twenty minutes of collective reading at the price of five salaries. The remedy: a framing email sent 48 hours ahead, ten lines long — the agenda, the two attached documents each with a three-sentence summary, and the precise question each person will be asked to weigh in on.

This brief is generated in a single request from the agenda and the documents: you already know how to make calibrated summaries since chapter 2, and audience adaptations since chapter 3. Marc now sends this framing systematically, and the effect was immediate: his client meetings open with "I read your comparison, I have a question about the lease" instead of "so, what are we talking about today?". Same content, same sending time: two minutes — but fifteen minutes gained in the room, multiplied by the number of participants.

During: noting what matters

Chapter 3 taught you to turn raw notes into structured minutes; the remaining question is: what to note during the meeting? Counter-intuitive answer: almost nothing, but the right things. No need to transcribe the exchanges — note only the decisions the moment they land, the actions with their owner and deadline, the figures quoted, and the unresolved disagreements. Four categories, telegraphic notes, and the restructuring will do the rest. Whoever tries to write down everything is no longer participating in the meeting they're supposed to lead.

A facilitation trick Marc adopted: the last five minutes are sanctuarized for reading the noted decisions and actions out loud. "So we're approving the lease, file prepared by us for the 15th, correct?" This in-room read-back costs five minutes and eliminates the classic plague of minutes contested a week later — everyone heard and corrected live what will be written.

After: the follow-up that doesn't die

This is where 80% of meetings lose their value: the minutes go out (when they go out), then nothing until the next meeting, where you discover half the actions haven't moved. The missing link is a follow-up workflow — exactly in the chapter 5 sense: at D+7, take the action list from the minutes and generate the individual reminders, personalized by recipient and progress status. Courteous for the first one, more direct afterwards: the document-chasing mechanics, applied to commitments made in meetings.

Here are the minutes of our meeting on the 12th (Actions section): <paste the action list with owners and deadlines>.
We are at D+7. Here is where each action stands according to my information: <indicate: done / in progress / no news>.
Prepare:
1. A mini tracking table: action, owner, deadline, status, risk of delay
2. For each "no news" action: a short personalized reminder email (3-4 lines), courteous and precise tone, recalling the commitment made in the meeting and offering help if something is stuck
3. The list of actions to bring up at the opening of the next meeting
Do not chase the actions marked "done" or "in progress".

flowchart LR
  A["Before: agenda + 48h brief"] --> P["During: decisions, actions, figures"]
  P --> CR["Structured minutes from chapter 3"]
  CR --> S["D+7: follow-up and personalized reminders"]
  S --> O["Next opening: decisions held?"]
  O --> A

Reducing: the meeting you don't hold

The last lever is the most radical: some meetings no longer have a reason to exist. The weekly progress check-in, for instance, mostly serves for everyone to say where they stand — information that can be collected in writing in five minutes and synthesized into a half-page note everyone reads in two minutes. Marc replaced his Monday team check-in (45 minutes for four people) with this written ritual, and kept a real short meeting on Thursday for what deserves a discussion: the disagreements, the trade-offs, the sensitive topics.

The sorting criterion is simple: a meeting exists to decide together or to build the relationship — not to transmit information. Anything purely informative can become a well-written note (chapter 3); anything that is status collection can become a form and a synthesis. Keep meetings for what writing does poorly: settling a disagreement, negotiating, announcing difficult news, celebrating. Your team won't hold it against you — nobody has ever regretted a meeting cancelled for good reasons.

The special case of client appointments

Everything above applies to internal meetings as much as client appointments, but the latter deserve extra preparation: the session file. Before every important appointment, Marc requests a one-page brief on the client — latest exchanges, pending items, recent figures from the file, sensitive topics, and three questions to ask to move the relationship forward. This brief is generated by crossing the previous minutes, the latest emails and the file's data: everything chapters 2, 3 and 4 taught you, condensed into a five-minute read.

The effect on the relationship is disproportionate to the effort. The client who hears "last time, you were hesitating about the lease — where do you stand?" feels followed, not treated like a file number. That relational memory used to be the privilege of advisors with small portfolios; it becomes accessible to a busy firm, because the preparation costs two minutes instead of twenty. The perceived professionalism of an appointment often plays out in these prepared details.

The pitfalls of the meeting cycle

First pitfall: the showcase agenda, written to look serious but never followed in the room. The agenda is a contract of time: if a point overruns, you say so and arbitrate, otherwise the document loses all authority. Second pitfall: the follow-up that shames. The D+7 reminder must help ("where is it stuck? can I help?"), not police; the tone of your reminders shapes your team's culture. Third pitfall: moving everything to writing. If you cut too many meetings, you lose the weak signals — the worried business partner, the hesitant client. The goal is fewer meetings, but better ones; not zero meetings.