When Safety Becomes the Enemy: The Paradox of the 5 Divers in the Maldives

I can't forget the news. Five professional divers, dead during a dive in the Maldives waters. People who knew exactly what they were doing. Certified. Experts. Dead.

What struck me wasn't the tragedy itself — unfortunately, accidents happen even to the best — but the way people tried to interpret it. "Violations of safety protocols," they said. "Negligence," they concluded.

Perhaps. But in my experience as a Diving Assistant Instructor, there's another story behind this tragedy. A story that has little to do with safety itself, and everything to do with how we approach it.

The Paradox of Over-Regulation

Years of work in diving taught me a disturbing lesson: an excess of procedures can become the worst enemy of real safety.

It seems paradoxical, right? But think about it. In diving, as in your professional life, every immersion (every project, every decision) is planned according to strict protocols: maximum depth, bottom time, air consumption, communications, contingencies. All documented. All rigid.

And ninety-nine times out of a hundred, it works. The protocol saves lives.

But that hundredth time? When conditions change in three seconds? When the perfect plan collides with the chaotic reality of the environment?

That's when something insidious happens: divers begin to trust the protocol more than their instinct and their awareness of the present moment. The mind finds comfort in the written procedure. "If I follow the steps, I'll be safe." It's false.

Applying a rigid protocol in a dynamic environment is like trying to navigate using a 1995 road map on a street that changes every day.

The Lesson No One Wants to Learn

In my work as an IT consultant — whether ERP implementation, data migration, infrastructure renewal — I see the same dynamic every single day.

Auditors, compliance teams, project managers who have never seen the "mud" of a real implementation, write brilliant procedures. 100 pages of governance. Endless checklists. Gates for every decision.

And then the real problems arrive: - The vendor updated the software two days before go-live (not foreseen in the plan). - Migration data contains undocumented exceptions (the protocol didn't account for them). - The underlying infrastructure can't handle the expected load (the test wasn't representative).

What do teams do? They follow the perfect protocol, and fail spectacularly.

What do teams that survive do? They understand the protocol as a map of intentions, not a Bible. They maintain situational awareness. They decide to adapt when reality demands it.

The Real Meaning of Planning

Here's the point I want to drive home, and what I believe killed those five divers:

Planning is not a document to follow. It's a mental exercise to understand risks, prepare contingencies, and develop the judgment necessary when everything goes wrong.

A good diver (like a good IT manager, like a good parent) is not someone who follows the plan perfectly. It's someone who has internalized the principles behind the plan, has developed the right level of paranoia about risks, and knows when and how to deviate from the plan without being killed by impulsiveness.

If those five divers had memorized a rigid procedure and followed it to the letter, would they still be alive? Maybe yes, maybe no.

But if they had remained fully aware of their limits, of the environment, of the danger signals (that's what real briefing consists of), they probably would have understood when it was time to surface and abandon the dive.

Not because the protocol said so. But because their situational judgment said so.

Applied to Your Life

Whether you're an entrepreneur, technical lead, project manager, or simply someone trying not to mess things up:

1. Always plan. But plan to understand, not to control.

2. Memorize principles, not procedures. Procedures change when the world changes. Principles remain.

3. Develop situational awareness. Can you read the signals your environment is sending you? Or are you too busy checking boxes on a checklist?

4. Be willing to fail. If your plan is so rigid that the only option is success or total disaster, you've planned poorly. Robust plans include "emergency exits" — moments when you can say "stop, this isn't working."

5. Cultivate intuition through experience. Excess safety dulls instinct. Keep alive your ability to "feel" danger, even when the data says everything is fine.

The Moral

True safety doesn't live in a document. It lives in your ability to understand risks, maintain awareness, adapt when reality doesn't follow the script.

Five expert divers died. Not because they lacked the procedure — they had the procedures. But probably because at some point safety itself became a mental cage. And when the environment decided to change the rules, they were trapped following the old ones.

In your work, in your life: don't be afraid to plan rigorously. But be even more afraid of becoming a slave to the plan.

Planning exists to free you from making stupid decisions under pressure. Not to force you to choose between the protocol and survival.

When you find yourself facing that choice, the protocol has already failed.

---

P.S. If today you're stressed because a project doesn't follow the perfect plan, the detailed briefing, or the 200-page governance document: take a break. Ask yourself if you're facing a real risk or just chasing reassurance in the Excel sheet. It might save you months of unnecessary agony.