How do I keep up in meetings at a new job?

Stop trying to follow every reference. In your first weeks at a new job you aren’t behind on the last two minutes of the meeting. You’re behind on the last two years of the team: its acronyms, its people, its old decisions, the project everyone calls “the migration”. No meeting catches you up on that, and trying to decode it live means you miss the part you could have followed.

So the job changes. Follow what this meeting is deciding, collect what you don’t understand, and get it explained outside the meeting.

Why meetings at a new job feel so fast

The meeting isn’t faster than usual. You’re processing more of it. A teammate who’s been there two years hears “let’s not repeat the Q3 thing” and gets the whole story in four words. You hear four words and a gap. While you’re working out what the Q3 thing was, the conversation has moved on two points.

This is a working memory problem. You’re holding the current discussion and trying to fill in the background at the same time, and the background loses. Remote work makes it worse. In an office you could lean over and whisper “what’s Q3?” On a call there’s no one next to you, and asking out loud feels like stopping the meeting.

The people talking usually don’t notice. Psychologists call this the curse of knowledge: once you know something, it’s hard to imagine not knowing it. The name comes from a 1989 paper by economists Colin Camerer, George Loewenstein and Martin Weber. Your new colleagues aren’t leaving you out on purpose. They can’t hear their own shorthand any more.

What you’re actually missing

Not all missing context is the same, and each kind gets filled in a different way.

• Words. Acronyms, project codenames, internal tool names, customer names. These are the easiest to fix. They have definitions, and someone can give them to you in a sentence.
• People. Who owns what, who actually decides, who to ask about what. You learn this by watching who speaks on which topic and whose opinion closes a discussion.
• History. Why things are the way they are. “We tried that.” “Like last time.” “After what happened with the launch.” This is the slowest to learn, and you mostly pick it up in one-on-ones, not in group meetings.
• The last few minutes. What was said while you were stuck on one of the above. This is the only kind a tool can give back to you in the moment.

What to follow during the meeting

You can follow a meeting without understanding every reference in it. Keep track of three things:

1. What this meeting is trying to decide or produce. If there’s an agenda, read it beforehand. If there isn’t, the first few minutes usually say it.
2. Who decides. Notice whose “OK, let’s do that” ends the discussion. That person is often not the one who talks most.
3. What’s asked of you. Any question or task with your name on it. Write these down word for word.

Everything else goes on a list: each acronym, name, and “like last time” you didn’t follow. Don’t stop to work it out. Write the word as you heard it and go back to the conversation.

Speak when you have something to add, but at first, keep it to questions and what you know from your previous job. “At my last company we handled this with X, would that work here?” is useful and doesn’t need any history.

When to ask in the meeting and when to ask after

Ask live when the answer changes what you’d do: the question is about your task, a decision is about to land on you, or you can’t follow the main point without it. “Sorry, quick one, what’s the Atlas dashboard? I’m still learning the names” costs everyone ten seconds.

Everything else goes on the list and gets asked afterward. Take the list to a teammate, your onboarding buddy or your manager, ideally the same day. Ten minutes with someone who knows the history fills in more than a week of listening for clues. If the same terms keep coming up, ask whether there’s a team glossary. If there isn’t, start one. It’s a useful first contribution, and you’re the only person who can still see which words need defining.

Being new makes asking cheap. Nobody expects you to know what the Q3 thing was in week one. They’ll be more surprised in month six, so use this early.

Where each kind of help comes from

Help	Words and acronyms	Who’s who	Team history	The last few minutes	When you get it	Bot in the call?
Asking in the meeting	Yes	Yes	Briefly	Yes, if you ask	Live	No
A teammate or onboarding buddy	Yes	Yes	Yes	If they were there	After, or by DM	No
Docs, wiki, past meeting notes	Sometimes	Sometimes	Sometimes	No	Whenever you look	No
Recording or bot notetaker	You can replay it	No	No	Yes, after the call	After the meeting	Bot: yes
Canary (live summary, no bot)	You can search the transcript after	No	No	Yes, during the call	Live	No

Look at the history column. Only people, and sometimes old docs, fill it. No meeting tool knows why your team abandoned the old pricing model. A tool can give you back the part of the meeting you missed while you were stuck on a word. The words, the people and the history come from asking.

Where Canary fits

Canary is a real-time, bot-free meeting summarizer. It captures your computer’s system audio (no bot in the call, no plugin) and shows a live, multi-resolution rolling summary, from what’s being said right now to the whole call, so you can catch up the instant your name is called. For a new hire, that helps in three places:

• After a stretch of jargon. If three minutes went by in acronyms you didn’t know, the “2 min” or “5 min” view of the multi-resolution summary tells you in plain sentences what was discussed and whether anything was decided. You can follow the outcome even when you couldn’t follow the words.
• When your name comes up. Being called on while you’re still working out the last point is the new-hire version of getting called on after drifting. The “now” view shows what was just asked. See what did I miss in the meeting?
• After the call, with your list. The post-call review has the full transcript, and you can search it. When you wrote down “something like Sigma?”, you can find the sentence it was in and take the exact context to your teammate. You can export the notes as markdown to keep in your own onboarding doc.

And where it doesn’t:

• It won’t fix the words for you. Speech-to-text is weakest on internal acronyms, product codenames and people’s names, which is exactly the vocabulary you’re learning. The transcript may spell them wrong. See word error rate for why. Check the spelling with a person before adding it to your glossary.
• It won’t tell you who’s who. Speakers are labelled “Speaker 1”, “Speaker 2” and so on, not by name. Learning names and roles is still on you.
• It doesn’t know your team’s history. It summarizes what was said in this call. It can’t explain what “like last time” refers to.
• It works in English. Transcription is currently set up for English.
• On long calls, the full-call view leans toward the most recent part of the discussion.

Before you install anything at a new job, check your company’s policy on AI tools that process meeting audio. Then tell your team you’re using it. Canary puts no bot in the call, but being open about it is still up to you. How to tell participants you’re using an AI notetaker has wording that works. If your company blocks notetaker bots, here’s what that does and doesn’t rule out.

Bottom line

In your first weeks, you won’t follow every reference, and you don’t need to. Follow the decision, who makes it, and what’s asked of you. Collect the words, names and history you don’t understand, and get them explained by a person the same day. Ask live only when it changes what you’d do. A live summary like Canary’s helps you get back in after a stretch of jargon. The context that makes meetings easy to follow comes from your team, one question at a time.