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.
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 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.
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.
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:
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.
| 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.
AI-assisted tasks run fast when you name the output format first, make the model flag ambiguity, treat the first result as a draft you check against the source, and pick one small workflow to repeat.
Team AI Training · 5 minFramework · 13 September 2026Three things a manager can set in an afternoon: a specific list of what never goes into a chat, a norm of disclosing AI use, and five agreed terms so meetings stop talking past each other.
AI Use Policy · 4 minGuide · 21 September 2026Four targeted checks to run before AI-assisted work leaves the building, covering sources, boundary cases, judgement calls and omissions, without redoing the whole task by hand.
Team AI Training · 3 minIf 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.