M.A.I. Consulting
GuideEntry23 September 20264 min read

Before and after the meeting: AI workflows for prep, follow-up and action plans

Meeting prep in minutes, same-day follow-up emails, hour-long training sessions and workshop notes turned into owned actions all work with AI when you ask for the right few outputs and add the personal detail yourself.

A call lands with ten minutes' notice, a workshop ends with forty sticky notes and no plan, a promising conversation needs a follow-up that never quite gets written. The work around a meeting is where momentum is lost, because it is rarely scheduled and always rushed.

Four examples show how a few well-chosen requests close those gaps. Each ends with something only you can supply, and that is worth planning for.

Before: prepare in the time you have

The ten-minute meeting prep

A client call arrived with ten minutes' notice and no time to reread the account history. The source article describes twenty minutes of scrolling reduced to the time it took to walk to the room. You paste in the last few email threads and ask for three things:

The point is not to know everything. It is not to be caught out by the one thing you should have remembered. Treat this as a floor. If the meeting is about a proposal, you still need to read the proposal.

A training session in under an hour

A new hire needed a walkthrough that usually got a half-day workshop, with an hour to prepare and no materials to reuse. The structured hour came from three requests:

The scenario was rewritten by hand because it needed a detail from the learner's actual role. A check-in question cannot be fully generic. The best hour-long session is built for the hour it has, not cut down from the full one.

After: close the loop while it is fresh

The two-minute follow-up

A good call ended with three action items and a vague promise to follow up soon, and soon usually meant when there was time to write something professional. The two-minute version, which the source says made same-day sending far more likely:

You then add by hand the small detail that shows you listened, such as an offhand comment about a shared connection. The email does not need to be memorable. It needs to exist while the conversation still does.

From workshop notes to action plan

A two-day strategy workshop ended with whiteboard photos, a disorganised shared document and about forty sticky notes of ideas everyone liked and nobody had turned into next steps. Closing that gap used to take a week. The afternoon version ran like this:

  1. Transcribe everything into one raw document, unsorted, before trying to make it look like a plan.
  2. Ask what patterns appear across the ideas, rather than assuming the themes. This surfaced groupings the room had not noticed while generating them.
  3. Ask for one owner and one concrete next step per theme, which is what makes the plan usable on Monday.

The facilitator still had to judge. Two themes that looked separate were one underlying issue in different language, and only someone who had been in the room reading the group's energy would have merged them.

What the four have in common

Moment Ask for Add yourself
Prep Status, likely topics, one good question The proposal, if it matters
Training Outcome, a check, what is out of scope A scenario from the learner's role
Follow-up Next step first, matching tone A personal detail
Workshop Themes, one owner and one action each Merging themes that are really one

In every case the request is short and specific, and the output is something you can act on within minutes.

What to do next

Series · Working with AI day to day · part 8 of 9
Keep reading
03 ยท Team AI Training

How should AI be used in my role?

If this is the question on your desk, a thirty-minute call tells you whether the service fits, or that you do not need us yet.