When Project Management Is Cultural, Not Technical

Why execution in small systems is about behavior — not just Gantt
charts

Disclaimer
Field Notes reflect the editorial analysis of the Managing Editor, informed by direct professional experience across Caribbean healthcare systems. These observations surface recurring structural patterns and do not represent the official positions of any government, institution, or commercial partner.

In the Caribbean, project management is often associated with cranes.

Capital builds.
Hospital expansions.
Infrastructure upgrades.
Large procurement contracts.

It is framed as technical oversight — timelines, budgets, risk logs, reporting structures.

But some of the most consequential project management work I have experienced in the region had nothing to do with concrete.

It had everything to do with people.

And that is where many small systems misunderstand project management.

Project management is not merely a technical discipline.

It is a cultural one.

The Capital Project Bias

Across the region, when we say “project management,” we often mean:

• Capital expenditure oversight
• Infrastructure builds
• Equipment installations
• Donor-funded initiatives

These matter.

But they are visible.

And visibility makes them politically and administratively easier to prioritize.

What receives far less structured oversight are the “soft” transformations:

• Redesigning referral pathways
• Implementing performance management frameworks
• Changing procurement governance
• Strengthening executive accountability
• Embedding digital workflows

These initiatives do not have ribbon-cutting ceremonies.

But they are often far more destabilizing — and far more important.

My Unexpected Extension Into the “Soft” Side

I had the unusual opportunity to extend a traditional project management role into organizational transformation — overseeing not just deliverables, but behavior.

Not just milestones, but alignment.

Not just risk registers, but resistance.

And what became immediately clear is this:

Execution failure in small systems is rarely technical.

It is cultural.

What “Cultural Project Management” Actually Means

In small systems, projects live inside tightly interconnected ecosystems.

Everyone knows each other.
Hierarchies are visible.
Politics are proximate.
History is remembered.

So execution depends on:

• Trust
• Psychological safety
• Informal influence networks
• Historical grievances
• Leadership credibility

You can build the perfect implementation plan.

But if department heads do not trust the sponsor, progress stalls.

You can design a flawless performance framework.

But if managers fear exposure, metrics will be quietly undermined.

You can introduce new procurement controls.

But if legacy relationships are disrupted without alignment, resistance will be immediate.

In small systems, behavior moves faster than policy.

That is why project management cannot be purely technical.

The Myth of Neutral Execution

Traditional project management frameworks assume rational alignment.

Define scope.
Assign responsibilities.
Monitor risk.
Report progress.

But in small states, execution is rarely neutral.

Every structural change alters power.

Every reporting line redesign affects influence.

Every performance dashboard introduces accountability.

Project management, therefore, becomes cultural navigation.

Not manipulation.

Navigation.

It requires:

• Mapping informal authority
• Sequencing change to manage relational risk
• Communicating repeatedly and visibly
• Protecting early adopters
• Creating shared wins

Technical skill sets the scaffolding.

Culture determines whether the structure stands.

Why This Matters for the Region

Small systems cannot afford repeated reform fatigue.

When initiatives fail, the cost is not just financial.

It is psychological.

Teams become skeptical.
Leaders become cautious.
Future projects face quiet resistance before they begin.

We often attribute failed reforms to funding gaps or capacity constraints.

Sometimes those are real.

But often the missing element is cultural project management.

Execution that accounts for:

• Identity
• History
• Proximity
• Political context
• Social interconnectedness

Project Management as Institutional Design

If burnout is structural, and brain drain is structural, then execution culture is structural too.

In many Caribbean systems, we do not lack strategy.

We lack sustained execution environments.

That requires:

• Clear sponsorship from the top
• Defined decision rights
• Transparent accountability
• Protected project governance structures
• Leadership development that includes change navigation skills

And critically:

An understanding that project management is not an event.

It is a way of operating.

A Reframe

Project management is not about controlling tasks.

It is about aligning behavior.

It is not about enforcing timelines.

It is about shaping how institutions absorb change.

In small systems, culture moves faster than compliance.

If we want reforms to last — in digital health, governance, performance, or finance — we must treat project management as a cultural discipline.

Because in the Caribbean, execution is never just technical.

It is relational.

And relationships determine whether systems move forward — or stall quietly.

About the Author

Mary Miller Sallah, MHA is the Managing Editor of Caribbean Currents and a healthcare operator with lived experience across Caribbean health systems. Her work focuses on health system transformation, leadership under constraint, and the practical realities of implementing change in small-state environments. She writes regularly on healthcare reform, digital health, and regional leadership.