Most organisations assume they have a cloud problem. In reality, the challenge is far more specific and far more persistent: cloud management. Infrastructure did not suddenly become unmanageable because enterprises embraced hybrid or multi-cloud strategies. The real issue emerged when environments evolved faster than the tools responsible for operating them. Over time, platforms multiplied, workloads dispersed across locations and accountability became fragmented. The long-promised “single pane of glass” quietly turned into a collection of disconnected views.

by Raif Abou Diab, General Manager – South Gulf & Sub-Saharan Africa at Nutanix

What stands out is that control was not lost the moment organisations adopted hybrid or multi-cloud models. Control was lost when cloud management approaches stalled at partial, platform-specific visibility, despite the environment becoming increasingly interconnected.

Seeing Everything Still Isn’t the Same as Being in Control

Most cloud management tools provide extensive visibility—dashboards, alerts, metrics and visualisations that explain what is happening across environments. That information is valuable, but only to a point.

Operations teams quickly learn that visibility without context creates noise. Alerts arrive from multiple platforms, each offering a fragment of the truth. The real challenge is rarely identifying what is happening, but understanding what action to take and how quickly it needs to happen.

This is where the concept of a “single pane of glass” often breaks down. In practice, it frequently means a unified view limited to a single vendor’s environment. As soon as workloads extend beyond that boundary or span locations, teams revert to switching between tools to piece together the full picture.

A cloud management platform should do more than observe. It should respond when pressure builds, take action when thresholds are reached and give operations teams the time they need to resolve issues properly.

Why Day-to-Day Operations Break Down Under Pressure

Infrastructure teams do not usually struggle with design—they struggle with time. They are expected to maintain stability, manage growth, control costs, enable new digital initiatives and respond to incidents, often all at once. In Middle East and Africa, this pressure is amplified by rapid digital transformation, regional expansion and the introduction of data-intensive workloads, including early AI initiatives, into already busy environments.

When issues occur, they tend to surface at the worst possible moment—during critical business processes that cannot be paused.

Payroll is a straightforward example. It runs periodically, consumes significant resources in a short window and must complete successfully. If it fails, the impact is immediate and highly visible across the organisation. In those moments, teams are not interested in architectural diagrams or long-term capacity trends. They need the platform to adapt, absorb the spike and give them breathing space to address the root cause.

When a management platform can automatically respond as resources come under pressure, the situation changes dramatically. The issue still exists, but the urgency and panic disappear—and that alone has a tangible operational impact.

Building Guardrails That Scale with the Environment

Governance is another area that is often misunderstood. It is still framed as restriction or approval, when effective governance is really about consistency. As cloud estates become more distributed, relying on manual enforcement becomes unsustainable. Rules drift, exceptions accumulate and outcomes vary depending on who is involved and how stretched teams are at that moment.

Embedding governance into the management layer removes that variability. It ensures workloads are deployed, scaled and managed in line with agreed standards wherever they run, while enabling safe self-service without sacrificing control.

This becomes even more important as automation is introduced. Automation is rarely immediate or effortless. It requires upfront design, scripting and planning, which can feel challenging when teams are already under pressure. What is often overlooked is that automation is not a recurring burden. Once implemented, it delivers returns quietly over time. Most organisations already automate informally through scripts and scheduled tasks. Formalising those efforts is less about ambition and more about ensuring actions are consistent, auditable and secure.

From Cost Visibility to Confident Decision-Making

Cost visibility has also evolved rapidly. As FinOps practices mature, organisations have become far more aware of consumption, but awareness is sometimes mistaken for restriction. In reality, understanding cost is about enabling better decisions, not halting progress.

The analogy is familiar. Reviewing a bank statement does not mean stopping spending altogether—it provides clarity on where money goes. That awareness supports better trade-offs. The same principle applies to infrastructure. When teams understand what workloads consume and what that consumption costs the business, discussions become more constructive. Overprovisioning can be challenged, resources can be right-sized with confidence and growth can be planned deliberately rather than guessed.

Why Hybrid Isn’t a Phase, but the Default State

One of the clearest lessons from organisations managing complex estates successfully is that hybrid is no longer a transitional phase—it is the operating model. Early public cloud enthusiasm has given way to more balanced considerations around cost predictability, data sovereignty and resilience, while on-premises environments continue to evolve rather than disappear.

Success in this model does not come from forcing everything into a single environment. It comes from managing different environments consistently. Platforms that treat each location as a separate problem tend to introduce friction. Those that recognise them as variations of the same operational challenge reduce it.

This is where cloud management must refocus: away from labels and architectural debates, and toward outcomes such as stability, predictability and the ability to respond calmly when things do not go to plan.

Putting Cloud Management Back Where It Belongs

Cloud management lost direction when it became more focused on describing environments than running them. Organisations that succeed use platforms that fade into the background—quietly enforcing governance, supporting automation and enabling better decisions under pressure.

What I consistently hear from customers across the MEA region is that while technology matters, outcomes matter more. When organisations focus on the benefits derived from management capabilities—and invest the time to implement them properly—they regain control without slowing the business. As infrastructure continues to become more distributed, that balance is what ultimately defines effective cloud management.