Public health has no shortage of people who can read an epidemic curve. It has a real shortage of people who can also read a budget, write a grant proposal that survives review, and manage a project through a government procurement process without losing momentum. That gap is one of the most consistent bottlenecks I’ve seen between a good public health idea and one that actually gets implemented.
I went back for a business degree after years of clinical and public health work because I kept hitting that exact wall — programs with strong scientific justification that stalled out on execution: funding structured wrong, stakeholders not aligned, a rollout plan that didn’t survive contact with a real bureaucracy.
Grant writing is a translation problem
Writing a successful grant proposal for advanced surveillance technology or program funding isn’t really a writing exercise — it’s a translation exercise. You’re taking an epidemiologic need and restating it in the language a funding body evaluates: measurable outcomes, budget justification, sustainability plans, risk mitigation.
Technically excellent public health work gets passed over constantly, not because the science is weak, but because the proposal didn’t translate that science into what a review panel is actually scoring. Learning to write in both languages — public health and program finance — is a skill most epidemiology training doesn’t teach, and it’s one of the highest-leverage skills a public health professional can build.
Project management is what turns strategy into delivery
A KPI framework, a data governance policy, a new surveillance protocol — none of it matters if it doesn’t survive implementation. Government projects come with real constraints: procurement timelines, multiple stakeholder sign-offs, staff turnover, competing priorities across bureaus. A PMP-level project management discipline — clear scope, realistic timelines, defined risk management — is what keeps a good idea from dying in the gap between “approved” and “operational.”
I’ve seen strong policies fail purely on execution: no clear owner, no realistic timeline, no plan for the inevitable staffing gap. And I’ve seen average ideas succeed because someone managed the rollout with enough discipline to get it across the finish line. The idea rarely determines the outcome as much as the execution does.
Stakeholder management is a public health competency, not a soft skill
Presenting surveillance findings to county stakeholders, coordinating across a health department’s bureaus, managing relationships with CDC and state partners — this work gets labeled “soft skills,” but it’s not soft. It’s the mechanism through which technically sound public health work either gets adopted or gets ignored.
A finding that isn’t communicated in a way that moves a stakeholder to act has, functionally, no public health impact yet. Business training sharpens exactly this: how to frame a recommendation for the audience in front of you, how to build the case for resources, how to manage competing priorities among partners who don’t report to you.
The case for cross-training
Public health doesn’t need fewer scientists. It needs more of its scientists fluent in execution — funding, project delivery, stakeholder management — because that fluency is what determines whether good epidemiology actually reaches the people it’s meant to protect.
That’s the argument for investing in this kind of cross-training, whether through formal education or deliberate on-the-job exposure to budgeting, procurement, and program management. The public health workforce that can do both — the science and the delivery — is the one that will actually move outcomes, not just publish findings about them.