The best-prepared person in a meeting isn’t the one who read the agenda. It’s the one who remembers what happened last time — what was promised, what was still unresolved, and what the other side actually cares about. That kind of prep used to mean digging back through old notes, Slack threads, and half-remembered context ten minutes before a call. Most people skip it and wing it instead.
Why “winging it” is the default
Manual prep has a bad cost-to-benefit ratio. Finding the right thread from three weeks ago, re-reading it, and pulling out the two facts that matter can take fifteen minutes for a meeting that only lasts thirty. So people don’t do it, and they show up cold — which is fine for a routine check-in, but expensive for anything that actually requires judgment: a renewal call, a difficult 1:1, a negotiation.
The cost shows up as small failures
It rarely looks like a disaster. It looks like:
- Asking a client something they already told you last week
- Missing that a teammate had flagged a blocker that never got addressed
- Repeating an argument in a negotiation instead of building on where it left off
Each one is minor. Together, across dozens of meetings a month, they add up to a team that looks less coordinated than it actually is.
What good prep actually requires
Good prep isn’t a summary of the last meeting. It’s a synthesis of everything relevant, filtered down to what matters for this specific meeting. That means pulling from:
- The most recent conversation with this person or team
- Any open commitments or action items still outstanding
- Broader context from other meetings that touch the same topic
That third one is the part manual prep almost never covers, because it requires remembering connections across meetings that happened weeks apart — which is exactly the kind of pattern-matching a system with access to your full meeting history can do automatically.
Automating it without losing the nuance
The failure mode of automated prep is a bland summary that restates the obvious. A brief that says “discussed the Acme account” isn’t useful — you already knew that was the topic. A useful brief says what specifically is unresolved and why it matters right now:
Acme pushed back on the renewal price last week. Priya wants a revised quote by Friday — bring the updated tiers, and note that the pushback is coming from procurement, not the exec sponsor.
That’s a brief someone can act on. It required connecting the pricing discussion, the internal Slack context about the deadline, and a read on who’s actually driving the objection — three separate signals collapsed into two sentences.
Building the habit
If you’re doing this manually, the version worth stealing is simple: five minutes before any meeting that matters, ask “what’s still open from last time, and what does the other side actually want?” — and go find the answer instead of assuming you remember it.
If you’d rather not do that fifteen times a week, that’s the exact gap an assistant that’s already sitting across all your meetings is built to close — surfacing the brief before you ask for it, so you walk in already caught up.