Moving from regulatory operations into regulatory strategy

Regulatory operations and regulatory strategy sit inside the same function, and it’s easy to assume one is just a more senior version of the other. It isn’t. Operations work — compiling submissions, keeping trackers current, managing registrations and listings, routing correspondence — is execution against a plan someone else set. Strategy work is setting that plan, and deciding what to file, when, and on what basis. Moving from one to the other is a real transition, not a promotion that happens automatically once you’ve done the first job long enough.

What operations experience actually gives you

People who’ve spent real time in regulatory operations tend to underrate what that work teaches them. Knowing exactly what a submission tracker is actually telling you — not the optimistic version in a status meeting, but what’s genuinely stuck and why — is strategic knowledge, even when the job title attached to it says otherwise. The same is true of knowing what a label change costs to implement across every downstream document it touches, or what a registration deadline actually requires versus what people assume it requires. Strategy built without that grounding tends to produce plans that look clean on a slide and fall apart the moment someone tries to execute them.

What strategy work asks you to do differently

The shift isn’t really about scope, even though strategy roles often cover more of it. It’s about the kind of question you’re answerable for. Operations work is judged by whether the plan got executed correctly. Strategy work is judged by whether the plan was the right one — which means living with the discomfort of a recommendation that might be wrong, defending it before the data is fully in, and revising it in public when new information changes the picture. That’s a different daily experience than executing a decision someone else already defended, and it’s worth being honest with yourself about whether you’ve actually practiced it, rather than assuming competence in the first job transfers automatically to the second.

How to practice the jump before you’re given the title

The move happens earlier than people expect, inside the operations role itself, by changing how you show up to the work you already have. Ask why a submission is being sequenced the way it is, not just what the sequence requires of you. When a tracker shows a program stalling, bring a recommendation for unsticking it along with the status update, not just the status update. Treat the distinction between regulatory strategy and regulatory operations as something to study deliberately, not something you’ll absorb by osmosis once you’re in a strategy seat — by the time the title changes, the habit of thinking that way should already be established, not something you’re learning for the first time under pressure.

None of this means operations work is a waiting room for a better job. Plenty of people do it well for an entire career and are more valuable for it. But for the people who do want to move into strategy, the path runs through doing the operations work with a strategist’s attention — not around it, and not by waiting for someone else to notice you’re ready and hand you a bigger title.