First Months
Being useful in a meeting you were not briefed for
Getting pulled into a discussion with no context is routine, and there is a small set of contributions available to someone who knows nothing about the subject.
By Yash Agarwal3 min read

Nobody meant to leave you unbriefed
Invitations get forwarded. Somebody adds the whole team because it is faster than deciding who needs to be there. A manager pulls you in because they think you will pick things up by exposure, and then forgets to say so. The result is a room, or a call, where you have no idea what is being discussed and no obvious reason to be present.
The first thing to accept is that this is not a test you are failing. It is a scheduling artefact, and it happens to people at every level. What makes it uncomfortable is the sense that you must either contribute something substantive or justify your place, and neither of those is actually required.
Establish why you are there, quickly and once
A short question at the start is almost always welcome, because the organiser frequently does not know why you were invited either. Something like: I am not sure how much I can add here — is it useful for me to take notes, or is there a part of this you want me on? That is not an apology, and it does not read as one.
The reason to ask early is that it converts a whole hour of ambiguity into a defined role. Somebody says you are there because the follow-up work lands with your team, or that they wanted a second set of ears, or that the invitation was an accident and you may leave. Every one of those answers is better than sitting through the meeting wondering.
The contributions available without context
There are a few things you can supply while understanding almost nothing about the subject matter. Notes are the obvious one, and they are genuinely valuable in a discussion where nobody else has capacity to write. Decisions, owners, dates, open items. Sent afterwards, briefly.
Clarifying questions are the second, and they are more powerful than people expect. When a meeting has been running for weeks, participants develop shared shorthand that hides real disagreement, and a newcomer asking what exactly is meant by a term frequently reveals that two people have been using it differently. That is not naivety on display; it is a service, and experienced people know it.
The third is process observation. Noticing out loud that the discussion has drifted from the stated purpose, or that an action has been described without anyone agreeing to own it, requires no subject knowledge at all. Do it sparingly and without a tone of correction, and it is one of the few things a junior person can offer in a senior room that lands cleanly.
Silence is a legitimate option
The strong urge, particularly early in a career, is to say something in order to have said something. This is worth resisting. Contributions that exist to establish presence are recognisable from the outside — they restate what was just said, or agree emphatically with the last speaker, or raise a point that was settled ten minutes earlier — and they cost more standing than they earn.
Listening carefully in a meeting you do not understand is not wasted time. You are learning who defers to whom, which topics generate tension, what the group treats as settled, and which names come up repeatedly. That map is the actual value of being in the room, and it accumulates faster if you are not busy composing something to say.
Fix the pattern afterwards, not during
If unbriefed meetings are frequent rather than occasional, that is worth raising with your manager as a practical question rather than a complaint. Which of these do you want me in, and what am I meant to be getting from them? Some will turn out to be deliberate exposure, some will be habit, and a few can be dropped entirely, which is a straightforward gain in time for you and no loss to anyone else.
It is also fair to ask organisers for an agenda in advance, though how well that goes depends heavily on the place. In some organisations a one-line purpose is standard and requesting it is unremarkable. In others, meetings are called with no stated purpose as a matter of long habit, and one junior person is not going to change that. Knowing which kind you are in tells you whether to press the point or simply to prepare for ambiguity as a fixed cost of the job.
Common questions
Is it rude to ask why I am in a meeting?
Not if it is asked once, early, and framed around being useful rather than around whether the invitation was justified. Organisers generally appreciate it, since it prompts them to think about who actually needs to be present.
Should I decline meetings I have no context for?
Sometimes, but check with your manager first rather than deciding unilaterally, especially in the early months. Some of those invitations exist precisely so that you absorb background, and declining them can look like disengagement even when the reasoning was sound.
What if I am asked a direct question and do not know the answer?
Say so plainly and offer to find out by a specific time. That is a normal answer at every level, and it is far better received than an improvised one, which tends to be remembered and occasionally acted upon.
Contributing editor, After the First Job
Yash writes the explanatory pieces on first months, managing up, money at work and would rather show the working than assert the conclusion.





