Managing up when your manager isn’t regulatory

At a lot of companies, especially small or device-side ones, the person a regulatory lead reports to has never done regulatory work — an engineering VP, a head of quality, a CEO who is also the de facto head of everything that doesn’t have its own executive yet. That isn’t a flaw in the org chart so much as a fact of company size, and it changes the actual job. The hard part stops being whether your regulatory judgment is sound. It becomes whether you can get someone who can’t evaluate that judgment directly to act on it correctly anyway.

The gap isn’t knowledge, it’s register

A manager who has run engineering teams or P&Ls for a decade is good at weighing tradeoffs — that’s most of what the job is. What they can’t do is independently assess whether your reading of a regulation, a predicate, or an agency signal is the right one. Handing them the regulatory reasoning and expecting them to evaluate it the way a regulatory peer would is asking them to do a job they don’t have. The reasoning that convinces a regulatory colleague — the citation, the precedent, the specific agency language — usually isn’t what moves someone managing a product timeline and a budget. What moves them is the same thing that moves them on every other decision: what you’re recommending, what it costs or buys in time and risk, and what would change your mind. Being the only person in the room who can even frame the question this way is a familiar position — the difference here is that the person you most need to frame it for is the one you report to.

What to bring instead of the explanation

Lead with the recommendation, not the path that got you there: what you think the company should do, stated as a decision rather than a discussion. Follow it with the two or three factors that would change your answer, so the manager knows what’s actually load-bearing in your judgment without needing to evaluate the regulatory substance themselves. Then say explicitly what you need from them — a decision, a resource, a timeline tradeoff they have to own — because a non-regulatory manager often won’t know which question to ask you, and waiting for them to ask it is how a clear recommendation turns into a stalled one. The same discipline that makes an executive update land is what makes a one-on-one with a non-regulatory manager land, and if the two of you genuinely disagree once the tradeoff is on the table, that’s a different and more honest problem than the one you started with — closer to pushing back on a timeline someone else set than to explaining regulatory affairs from scratch.

None of this is about dumbing down the regulatory substance. It’s about recognizing that the substance was never going to be the thing your manager evaluated — your judgment was. The job is to make that judgment legible enough, in terms they already manage by, that the right decision doesn’t depend on them understanding regulatory affairs at all.