Moving from regulatory affairs into program management

Regulatory affairs people make unusually good program managers, and most of them don’t realize it until someone else points it out. You already track a cross-functional timeline, translate between functions that don’t naturally speak to each other, and know exactly which dependency is about to become a problem three weeks before it does. What the move doesn’t hand you automatically is the authority you’re used to having over your own lane — a program manager owns the plan, not any one function’s decisions inside it, including the regulatory ones you used to make yourself.

What actually transfers

The parts of regulatory affairs that make the job hard are also the parts that make a good program manager: holding a submission timeline against a dozen upstream dependencies, writing updates that executives will actually read, and noticing early when a function is quietly behind rather than waiting for them to say so. How regulatory affairs teams are structured covers how much of the job is already cross-functional coordination even before you change titles — that coordination muscle is the one that transfers almost directly. What doesn’t transfer as cleanly is scope: a regulatory timeline tracks one function’s deliverables against a submission date, while a program plan tracks every function’s deliverables against each other, with regulatory as just one line among many.

Authority you had, and the influence that replaces it

Inside regulatory affairs, you had real decision rights — over the regulatory strategy, over whether a submission was ready, over what the agency needed to hear. A program manager has almost none of that over any individual function, including the one they came from. The job runs on influence instead: getting clinical, manufacturing, and commercial to hit dates you can’t compel them to hit, using visibility into the whole plan as your leverage instead of formal authority over any piece of it. People who move from regulatory affairs sometimes expect their old credibility to carry over, especially with their former regulatory colleagues — and are surprised when it doesn’t, because the working relationship has changed even if the people haven’t.

None of this means the move is a bad one — regulatory affairs is one of the better functions to make it from, precisely because the coordination instincts are already built. Moving from regulatory affairs into business development covers a similar trade in a different direction, and the regulatory affairs career ladder, explained covers where program management sits relative to the paths that stay inside the function. Go in clear-eyed about what you’re trading — depth and authority in one lane for breadth and influence across many — and the transition reads as a deliberate choice rather than a surprise six months in.