Known Risks Must Be Planned: A Project Management Lesson from Malta’s Power Cuts

Introduction

Some problems are unexpected.

Others repeat themselves until they become predictable.

When the same disruption happens year after year, the question is no longer only technical. It becomes a question of project risk management, planning discipline and long-term execution.

Malta’s recent power cuts are a useful real-world example.

In July 2026, Enemalta said electricity demand reached a record 741MW during an intense heatwave, placing sustained stress on the distribution network while teams worked to repair cable faults and restore supply. Reports also described outages affecting residents, businesses and parts of Valletta.

The heatwave was extreme.

The demand was high.

But from a project management point of view, the key question is simple:

If a risk happens repeatedly, when does it stop being a surprise?

A Known Risk Must Be Planned

In project management, a known risk should not be treated as an unexpected event every time it occurs.

It should be identified, assessed, monitored and managed.

Summer heat is not unusual in Malta. Peak electricity demand is not a new concept. Infrastructure stress during extreme weather has already been discussed in previous years. In 2023, Enemalta reported an “unprecedented” number of cable faults during widespread outages, and in 2025 Malta again recorded high electricity demand while reports referred to another series of summer power cuts in 2024.

This does not mean every fault is easy to prevent.

It means repeated patterns should trigger stronger planning.

In practical terms, a recurring issue should move from:

“This happened again.”

to:

“This is a known risk. What have we changed since last time?”

The Problem Is Not Only the Fault

A technical fault is the visible event.

The deeper issue is often the system around it.

Good project risk management asks wider questions:

• Was the risk identified early enough?

• Was the impact properly assessed?

• Were vulnerable areas prioritised?

• Were resources prepared before peak demand?

• Were contingency plans realistic?

• Were lessons from previous years converted into action?

• Was progress tracked before the next summer arrived?

  
  

For industrial and infrastructure projects, this is critical.

A problem may start as a cable fault, missing part, supplier delay or overloaded system. But if the same problem appears repeatedly, the organisation must look beyond the immediate repair.

The real lesson is not only technical.

It is managerial.

Planning Is Not the Same as Reacting

There is a big difference between reacting quickly and planning effectively.

Reaction is what happens after the failure.

Planning is what reduces the likelihood, scale or impact of the failure before it happens.

Both are necessary.

Emergency crews, technical teams and site workers often do difficult work under pressure. Their response matters. But strong execution should not depend only on emergency recovery.

A mature project organisation prepares for predictable pressure points before they become public disruption.

That means:

• strengthening weak parts of the system

• preparing critical resources in advance

• testing contingency plans

• reviewing past incidents honestly

• prioritising work based on risk

• communicating early with stakeholders

• tracking corrective actions until they are complete

  
  

Planning is not paperwork.

Planning is prevention.

Lessons Learned Must Lead to Change

Many organisations hold lessons-learned sessions after a disruption.

The problem is that lessons are often documented but not embedded into execution.

A real lesson learned should answer three questions:

What happened?

Why did it happen?

What will we do differently before it happens again?

Without the third question, the lesson is incomplete.

If the same disruption returns every year, then the issue may not be the absence of lessons. It may be the failure to convert those lessons into funded, prioritised and completed actions.

This is where project governance matters.

Someone must own the corrective actions.

Someone must track progress.

Someone must escalate when deadlines slip.

Otherwise, “lessons learned” becomes only a report.

Infrastructure Planning Requires Long-Term Discipline

Infrastructure does not improve through statements alone.

It improves through long-term planning, investment, prioritisation and execution control.

Enemalta has publicly referred to reinforcement works, new underground cables and investment in the distribution network, including a joint statement about 60 kilometres of new underground cables and reinforcement works in localities such as St Paul’s Bay.

That type of work is important.

But the project management lesson remains clear: infrastructure improvement must be measured against recurring operational reality.

If demand is rising, temperatures are increasing and the same localities continue to experience disruption, planning must stay ahead of the risk, not chase it after the failure.

Communication During Disruption Matters

When people lose power during extreme heat, communication becomes part of the response.

Residents and businesses do not only need repairs.

They need clear information.

Uncertainty increases frustration.

For project managers, communication during disruption should be:

• timely

• factual

• consistent

• specific about affected areas

• honest about expected restoration

• clear about what is being done

• followed by visible corrective action

  
  

Communication does not solve the technical fault, but it protects trust while the fault is being resolved.

Poor communication makes a difficult situation worse.

The Wider Business Impact

Power cuts are not only an inconvenience.

They affect businesses, operations, equipment, stock, working hours and customer service.

Reports from the latest outages described business disruption, including restaurants needing to discard spoiled food, while political calls were made for compensation to affected families and businesses.

For any project leader, this is an important reminder.

The impact of a failure is not limited to the asset itself.

It spreads to users, customers, suppliers, employees and public confidence.

That is why risk impact should always be assessed beyond the technical system.

The Core Project Management Lesson

A predictable risk must be managed before it becomes an incident.

A repeated incident must become a corrective action.

A corrective action must have an owner, deadline, budget and visible follow-up.

That is the discipline of project risk management.

The issue is not whether problems happen. Problems will always happen in complex systems.

The issue is whether the organisation learns fast enough, plans seriously enough and executes corrective action before the next predictable pressure point arrives.

Conclusion

Project management is not about fixing surprises only.

It is about preventing the predictable ones.

Malta’s recurring power cuts show why planning, risk management and execution discipline matter in real infrastructure environments.

When the same problem appears year after year, it should no longer be treated as bad luck.

It should be treated as a known risk.

And known risks must be planned.

At Casaltech, we believe practical project management starts with visibility, ownership and action.

Because in real execution, the question is not only:

What failed?

The better question is:

What did we learn, and what did we change before it happened again?