Hamad Aish

In this story

1. The decision before the job
2. Education alongside experience
3. Networks across a wider territory
4. When the institution changed
5. A service rather than a single project
6. Moving infrastructure without losing the service
7. The decisions behind consolidation
8. Continuity when staffing changed
9. Who gets the credit
10. The limits he has had to learn
11. Direction before complexity

The decision before the job

Hamad Aish first imagined a career connected with aircraft. Travel interested him, and airplane engineering seemed a possible way of turning that interest into work. His published career accounts describe a change of direction towards computer science instead. What drew him was the range of problems technology could address and the possibility of building practical systems. His route into banking technology therefore began with a choice between disciplines, rather than a fixed plan to become a data-centre leader.

The next stage combined study with employment. In his Insights Success and Enterprise World career accounts, Aish describes working as a network engineer at Commercial Bank of Dubai while completing his undergraduate education. Learning was taking place in two settings at once: through the degree and through the demands of an operational job. His account presents that combination as an early lesson in managing commitments and maintaining focus.

The work also placed him close to the equipment and connections on which services depended. Before he managed wider responsibilities, he was developing experience inside the network layer. That starting point remains part of how he describes his later career: understanding technology through the work of maintaining it, then taking on responsibility for the people and decisions around it.

Education alongside experience

Aish continued studying beyond his undergraduate qualification. His published profiles identify a master's degree in Management Information Systems from the University of Dubai. The subject connected his technical background with the organisation and management of information systems. In the career account, further education was part of his development while his professional responsibilities were expanding, rather than a replacement for operational experience.

His reflections on learning extend beyond formal qualifications. He describes adaptability, analytical thinking and continued study among the strengths that have supported his work. Communication and empathy appear beside those technical and intellectual habits. He does not present being able to analyse a problem as sufficient on its own; colleagues also need to understand one another and work together on the response.

In his public announcement about further professional study, he returns to that connection between management and technical depth. He describes strategic leadership in terms of enabling people, accountability and delivery, while discussing reliability as something that must be built through disciplined work. The point he makes is about applying learning to responsibility, rather than treating a title as the source of authority.

Networks across a wider territory

After his early work at Commercial Bank of Dubai, Aish joined National Bank of Abu Dhabi as a senior network engineer, according to his published career profiles. The CIO Arab account describes responsibility for networks in Dubai and the Northern Emirates. It also recalls the demands of travelling between Dubai and Abu Dhabi. His development was tied to a working routine as well as to changes in position.

This stage gave his technical work a regional scope. The account moves from an engineer combining employment with study to someone supporting a bank's network responsibilities across several locations. It is a specific part of his progression, before the later emphasis on data centres and service ownership.

Aish's public reflections on infrastructure still draw on that foundation. He discusses the relationship between systems, availability and the choices that shape change. His earlier network work helps explain why his later accounts are concerned with maintaining service while altering the underlying environment. The career did not begin at the level of a transformation portfolio. It developed through responsibility for infrastructure already in use, with people and operations depending on it each day.

When the institution changed

The merger of National Bank of Abu Dhabi and First Gulf Bank is a turning point in Aish's published account. He describes the creation of a larger institution bringing new responsibilities and opportunities. The profiles connect that transition with his move into leadership of an international data-centre team, followed by a wider remit covering international and local teams.

That progression changed the nature of his work. Responsibility was no longer described only through a network or a territory. It also involved bringing together people working across data-centre services. His career narrative eventually reaches the role of Service Owner for Data Center Management at First Abu Dhabi Bank, the position through which the longer published features introduce him.

The merger also provides context for the consolidation work that appears later in the story. A separate public post from the account alexmolodtsov describes the infrastructure left by combining two banks: multiple data centres, overlapping applications and ageing systems. The post names Aish among the people involved in the subsequent work. It places him within a wider infrastructure effort, alongside other teams and named colleagues, rather than making him the sole author of the institution's transformation.

A service rather than a single project

The Enterprise World describes Aish's service-owner responsibilities across planning, implementation, optimisation and maintenance. Those activities span the life of a service. The published account is concerned with how infrastructure is introduced, how it performs and how it is improved after it has become part of normal operations.

Aish's stated priorities include availability, security and reliability, connected with the bank's business objectives. He also describes working with cross-functional groups and building relationships with stakeholders. In this account, leadership means keeping the technical work connected with the organisation that uses it, not treating the data centre as a separate world with its own isolated goals.

His interest in sustainability appears within the same set of responsibilities. He discusses greener practices alongside innovation, people and processes. The profile presents the challenge as balancing those concerns while keeping services dependable. It is a broader conception of the role than selecting equipment or supervising a facility.

That perspective also explains his emphasis on developing colleagues. An operating service requires people able to maintain it and respond when conditions change. In his account, encouraging ideas and strengthening the team's skills belong within service management, rather than sitting outside it as occasional leadership activities.

Moving infrastructure without losing the service

One of the clearest projects in Aish's published record is a data-centre relocation from Al Ain to Dubai for National Bank of Abu Dhabi. Insights Success, CIO Arab and The Enterprise World describe his involvement in supervising the move. Their accounts connect the relocation with maintaining operations and preparing the destination environment, rather than treating the physical transfer as the whole assignment.

Cooling is another concrete part of that work history. The profiles describe a data-centre chiller replacement project and the need to maintain cooling while changing the equipment. Aish's story therefore includes facilities work as well as networks and computing systems. The operating environment behind the hardware was part of the service responsibility.

Disaster-recovery testing and the removal of older infrastructure appear alongside those projects in the published account. Together, these examples show the kind of tasks through which his responsibilities developed: moving systems, changing supporting equipment, testing recovery and deciding what could be retired.

These are accounts of his project involvement, not a claim that he performed every specialist task himself. Their importance to the career narrative is the combination of technical change and continuity. The projects required attention to the environment being changed and to the service that still had to run through that change.

The decisions behind consolidation

Aish's own post sharing his Enterprise World feature identifies legacy data-centre decommissioning and cloud migration among the work undertaken with the FAB infrastructure team. He thanks colleagues and the infrastructure leadership for their support. The public account links the work with a cloud-first direction and with attention to energy efficiency.

The separate consolidation post from alexmolodtsov supplies a more detailed view of the choices surrounding that effort. It describes questions about where applications should go, what should happen to existing investments and how a business case should be assessed. Moving to another location, moving to cloud, changing application architecture and simply refreshing technology were different possibilities, not interchangeable descriptions of one action.

That post credits the FAB Infrastructure Services teams and colleagues across Group Technology. It names Aish within that collective work. The useful picture is of a programme requiring planning, design and execution across several groups, rather than a single individual's isolated technical intervention.

Read beside Aish's own reflections, the account gives his interest in alignment a practical setting. Decisions about an ageing estate involved dependencies, cost and the future destination of applications. Decommissioning was the visible endpoint of work that first had to determine what should replace the old arrangement and how the organisation would reach it.

Continuity when staffing changed

The pandemic introduced a different kind of disruption into Aish's published story. His Enterprise World and Insights Success accounts describe the need to continue data-centre operations while reducing the number of people physically present. Remote management and automation were part of the response he describes.

He also points to cross-training. Employees needed the ability to cover different responsibilities when staffing became more difficult. This was a people-development response to an operational problem: the service could not depend only on the normal availability of each individual in their usual role.

Health measures appear beside those technical and staffing changes. The published account describes testing and sanitation as part of protecting employees and helping them work with confidence. Communication platforms supported contact among teams and stakeholders while restrictions affected normal working arrangements.

Aish also describes resource optimisation and additional capacity in response to increased demand for digital services. His account does not present the period as one problem solved by a single technology. It brings together remote operations, team coverage, safety, communication and resource decisions. The experience illustrates the range of responsibilities he associated with continuity when the assumptions behind ordinary working routines no longer held.

Who gets the credit

Aish's own post about a FAB Group Technology and Transformation town hall offers a more personal view of team leadership. He describes the data-centre team receiving recognition and directs attention towards the people behind the work. His emphasis is on their contribution through difficult circumstances, not simply on the recognition itself.

He describes colleagues bringing different strengths to the assignment and thanks the leadership for its trust and support. The post treats the result as belonging to the team. It is consistent with the thanks he gives the wider infrastructure group when sharing his magazine feature.

His published advice to emerging leaders develops the same theme through delegation. He argues for giving people responsibility and encouraging ownership of their work. Recognition, in his account, matters at different scales, including achievements that may not attract attention beyond the immediate team.

These reflections make his leadership vocabulary more specific. Empathy is connected with understanding colleagues; communication with keeping them aligned; delegation with their ability to take responsibility. The town-hall post shows how he chooses to describe a shared achievement publicly, while his career interviews explain the habits he believes support that kind of collective work.

The limits he has had to learn

Aish's professional accounts include a less celebratory assessment of his own habits. He identifies perfectionism as a tendency that can delay work and overcommitment as a source of stress. His response is to pay closer attention to priorities and boundaries. The point is a practical one: diligence can become counterproductive when every task receives more attention than it needs or too many commitments compete at once.

He places emotional intelligence within his advice to other leaders. Managing one's own reactions and understanding the feelings of colleagues are part of building trust. Clear communication, regular updates and space for discussion help people understand the direction of the work and raise concerns.

His reflections on life outside work extend that attention to limits. He describes planning downtime rather than leaving rest to whatever hours remain. Reading, quiet time and other opportunities to disconnect feature in his account. Communication with family and employer helps make expectations clearer on both sides.

Balance is something he reviews and adjusts. He does not describe a permanent arrangement that removes all tension between work and personal commitments. Instead, self-reflection helps him notice when the routine needs changing. This sits beside his professional emphasis on adaptability: continued performance requires attention to the person doing the work as well as to the work itself.

Direction before complexity

Aish's own writing about digital transformation states his position more directly than the promotional features. In a public post, he argues that transformation is a leadership responsibility and that technology follows the direction people set. He distinguishes digital maturity from the number or sophistication of tools adopted.

He is explicit that artificial intelligence does not remove the need for judgement. Scale alone does not establish value, and speed without a clear purpose can fail to produce lasting results. These are his stated principles for decision-making, rather than claims that every programme associated with him has already achieved them.

A separate infrastructure-trends post shows the range of subjects he follows, including hybrid cloud, automation, cyber resilience, energy-efficient infrastructure and predictive maintenance. His leadership reflection supplies the counterweight to that interest in new tools: capability and alignment should guide complexity, not the other way around.

Current public author information identifies Aish as Senior Delivery Manager at FAB. A recent conference-organiser introduction describes the remit as Infrastructure Delivery and Portfolio Management. The older service-owner features remain useful accounts of the responsibilities through which he developed, while the newer role places that experience within a broader delivery setting. Across those accounts, his recurring concern is the connection between technical change, disciplined decisions and the people who must carry the work through.