A traditional management consultant advising a hospital with a struggling department might begin with a restructuring proposal. New reporting lines. Different leadership. A budget reset. Fort Lauderdale consultant Nicholas Mukhtar tends to begin somewhere different. He asks what upstream conditions produced the failure in the first place.
That distinction, Mukhtar argues, traces directly to his public health training. Epidemiologists don’t treat individual patients. They’re trained to trace patterns of disease back to the systems that produced them. Applied to a healthcare organization, the same instinct yields a different kind of diagnosis. A struggling team is downstream of an upstream design failure most consultants never trace back to its origin.
What Public Health Methods Add to Hospital Advisory
Mukhtar earned dual master’s degrees in Public Policy and Public Health at Johns Hopkins as a Bloomberg Fellow, while running Healthy Detroit, a nonprofit public health organization. The American Public Health Association named the organization National Public Health Organization of the Year in 2017, according to Healthcare Business Today.
His consulting practice at Tera Strategies carries the same diagnostic discipline. When a medical director presents a problem (a department running over budget, a clinical team missing performance benchmarks), Mukhtar asks for the conditions, not the conclusions. Had decision-making authority been documented before the team scaled? Were communication expectations codified, or was everyone left to improvise? Those questions reveal far more, he argues, than a personnel review ever could.
How an Epidemiological Frame Shapes Recommendations
A 2025 paper in Frontiers in Health Services described systems thinking in public health as a methodology that “enables policymakers to comprehend the interconnections within public health systems and anticipate the potential consequences of policy implementation.” The framing translates into corporate consulting more cleanly than most executives realize.
A hospital department over budget, treated as a budget problem, gets a budget cut. Treated as a system problem, it gets a different prescription. Maybe the workflow assumes a staffing level the unit never reached. Maybe reporting cadences are missing the events that drive cost overruns. Maybe the supervisor is being asked to make decisions without the data infrastructure to support them. Each scenario calls for a different intervention. Each requires having looked upstream first.
The Communication Layer Behind Most Failures
Mukhtar has been consistent about where the deepest organizational problems live. “I kid you not, that seems to be 90% of the problems across the board,” he told Insights Success. “It’s just people need to talk.”
For hospitals, that pattern is acute. Care decisions involve multiple specialties, multiple shifts, and multiple administrative layers. A delayed conversation between a department head and a medical director can have consequences that move from operational to clinical inside a week. The interventions Mukhtar typically proposes sound simple: defined escalation paths, structured cross-functional meetings, documented decision rights. They tend to be, in his experience, the highest-leverage changes available.
What This Looks Like in a Hospital
A hospital that adopts the public-health-informed model usually starts with a small change. A daily five-minute cross-shift huddle. A documented authority matrix posted in a shared location. A weekly meeting where the medical director and the COO walk through the same operational dashboard together rather than in separate sessions.
The interventions look modest. The downstream effects, Mukhtar argues, are not. Medical directors recover hours of their week. Patient care decisions stop bouncing through email chains. Administrative staff have clearer line of sight into the clinical priorities driving their work. That kind of structural clarity, in his experience, outperforms any restructuring on cost, on retention, and on outcomes.