At some point you’ll be the only regulatory person in a meeting where everyone else wants to move faster than you’re willing to sign off on. How you handle the next five minutes matters more than any policy document you could point to afterward.
Separate the requirement from your judgment call before you walk in
Not everything you say in a design or launch-readiness meeting carries the same weight, and it helps the room — and you — when you know which is which before someone pushes back. “We can’t skip design verification testing” is a requirement under 21 CFR 820.30; the design history file has to show it happened. “I don’t think this specific test coverage is enough for this risk profile” is your judgment call, informed by the regulation but not dictated by it word for word. Walking in already knowing which kind of statement you’re about to make keeps you from defending a preference as if it were a law, or treating an actual requirement as negotiable because the room is in a hurry.
This distinction also tells you how to respond to pushback. Pushback on a requirement gets a citation, not a negotiation — point to what the record has to show and why. Pushback on your judgment call is a real conversation, and you should be prepared to actually have it: what would change your recommendation, and what evidence would need to exist for you to move.
Answer in real time, confirm in writing afterward
The instinct to fill a silence with a confident-sounding answer is strong, especially early in a career, and especially in a room full of people who talk faster than you do. Resist it for anything you’re not sure about. Say exactly what you know, name what you don’t, and commit to a specific turnaround — “I’ll confirm by Thursday” is a complete, professional answer. A guess that turns out wrong costs you more credibility later than an honest gap does in the moment.
The meeting isn’t over when the room moves on. Send a short written recap the same day: what was decided, what’s still open, and who owns the follow-up. This is the same discipline behind keeping a decision log — not because anyone doubts your memory, but because a decision that only exists in five people’s recollection of a meeting becomes five slightly different decisions within a month.
Where this goes wrong
Softening a hard requirement into a suggestion to keep the meeting moving
It comes back worse later, once quality or an FDA reviewer asks about a record that was never built.
Answering a technical question you’re not sure about instead of confirming it
A wrong confident answer costs more credibility than a delayed correct one ever does.
Leaving the room without a written record of what was decided
The decision becomes whatever the loudest person in the room remembers it as, three weeks later.
None of this requires more seniority than you currently have. It requires knowing which kind of statement you’re making, saying what you actually know, and writing down what the room actually decided — the same three habits that make you easier to work with the next time you’re the one explaining the job instead of just defending it.
Sources & further reading
- 21 CFR 820.30 — Design controls ecfr.gov
- Regulatory Academy — The First Regulatory Affairs Hire regulatoryacademy.com
- Regulatory Academy — The Case for a Regulatory Decision Log regulatoryacademy.com
- Regulatory Academy — Teaching a Colleague What Regulatory Affairs Actually Does regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.
