Disagreeing with your manager’s regulatory strategy is a different problem than disagreeing with FDA’s decision on a submission. This is an internal call — about risk tolerance, timing, or how aggressive to be in a pre-submission meeting — and your manager owns both the decision and its consequences. That changes what the right response looks like.

What actually earns you influence next time

The version of disagreement that builds trust is specific, timely, and offered once: you say what you’d have done differently and why, before the decision is finalized, and then you support the call that gets made. Bringing the same objection back after the strategy is already in motion — in a later meeting, to a colleague, or in how you execute the plan — doesn’t read as continued diligence. It reads as not having accepted the decision, which is a different problem than the one you originally raised. The practitioners who get asked for their view early are usually the ones who made their case cleanly once and then executed the decision that was actually made, the same discipline behind being the only regulatory voice in the room: your influence comes from being right often enough and gracious enough about the times you weren’t the deciding vote, not from being loudest.

When it’s worth escalating past disagreement

Most of what feels like a disagreement worth fighting over is actually a difference in risk appetite — your manager is willing to carry more regulatory risk into a submission than you would, or wants to hold back a finding you’d rather disclose proactively. That’s a legitimate judgment call for the person who owns the outcome to make, even when you’d have called it differently. A smaller set of disagreements are something else: a genuine belief that a plan crosses a legal, safety, or compliance line, not just a more conservative preference. Those deserve documentation regardless of how the conversation with your manager goes — keeping a regulatory decision log exists partly for this reason, so that what you flagged and when isn’t only a matter of memory if the call turns out to matter later.

Where this goes wrong

Treating a risk-appetite difference as a rules violation

Conflating “I would have been more conservative” with “this crosses a line,” which escalates a normal judgment call into a trust problem.

Re-raising a settled call

Bringing the same objection back after the decision has been made and acted on, instead of noting it once and moving on.

Skipping the record when it actually matters

For the cases that are a genuine compliance concern, not documenting what you flagged and when, leaving no record if the call turns out to matter later.

Most disagreements with a manager’s regulatory strategy are about risk appetite, not correctness, and treating them that way — say your piece once, document the rare case that’s actually a line rather than a preference, and execute the decision that gets made — is what determines whether your manager wants your view again tomorrow.

Sources & further reading

  1. Regulatory Academy — Handling a Regulatory Decision You Disagree With regulatoryacademy.com
  2. Regulatory Academy — The Case for a Regulatory Decision Log regulatoryacademy.com
  3. Regulatory Academy — Being the Only Regulatory Voice in the Room 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.