Public health has plenty of people who can read an epidemic curve. It has far fewer who can also read a budget, write a grant proposal that survives review, and get a project through government procurement without losing a year. In my experience, that gap is one of the most common reasons a good idea never gets implemented.
I went back for a business degree after years of clinical and public health work because I kept hitting that wall. I watched programs with solid science stall on execution. The funding was structured badly, partners weren’t on the same page, or the rollout plan fell apart the first time it met a real bureaucracy.
Grant writing is translation
A strong proposal for surveillance technology or program funding is mostly translation. You take an epidemiologic need and restate it in the terms a funder scores: measurable outcomes, budget justification, sustainability, risk.
Good public health work gets passed over all the time. Usually the science is fine. The proposal just didn’t show the review panel what it was looking for. Most epidemiology training doesn’t teach you to write for both audiences, and I think it is one of the most useful skills anyone in this field can learn.
Project management gets things delivered
A KPI framework, a data governance policy, a new surveillance protocol: none of it matters if it dies during implementation. Government projects come with procurement timelines, several layers of sign-off, staff turnover, and competing priorities across bureaus. Basic project discipline (clear scope, realistic timelines, a plan for risks) is what carries an idea from “approved” to “running.”
I’ve seen strong policies fail because nobody owned them, the timeline was fantasy, or there was no plan for the staff vacancy everyone knew was coming. I’ve also seen ordinary ideas succeed because someone managed the rollout carefully. Execution usually decides the outcome more than the idea does.
Working with partners is part of the job
Presenting surveillance findings to county partners, coordinating across bureaus, and keeping relationships with CDC and the state health department in good shape all get filed under “soft skills.” I don’t think the label fits. This work decides whether sound public health findings get used or ignored.
A finding that never moves anyone to act hasn’t helped anyone yet. Business training made me better at this part: framing a recommendation for the person in front of me, making the case for resources, and balancing priorities among partners who don’t report to me.
More scientists who can deliver
Public health doesn’t need fewer scientists. It needs more scientists who also understand funding, project delivery, and partner relationships, because that is what gets good epidemiology to the people it is meant to protect.
That knowledge can come from a degree, as it did for me, or from time on the job deliberately spent on budgets, procurement, and program management. Either way, the people who can handle both the science and the delivery are the ones who change outcomes instead of only publishing about them.