Managing Organizational Change Effectively

When Kuwait International Bank converted from conventional to Islamic banking, every product, every process, every contract, and every customer communication had to change. I was there. The technical conversion was complex, but the part that kept me up at night was the 800 employees who had built their careers around a system that was about to disappear.

Organisational change fails or succeeds based on how the people inside the organisation experience it. Not how the board presents it. Not how the consultants plan it. How the person at the branch counter on day one of the new system feels about what just happened to their job.

Why Change Programmes Fail

Most change initiatives in the GCC follow the same pattern: leadership decides on a change, a consulting firm produces a transition plan, the plan is communicated in a town hall, and then everyone is expected to adapt. When they do not, management blames "resistance to change" as if it were a character flaw rather than a rational response to uncertainty.

People resist change when they do not understand why it is happening, how it affects them personally, or whether they will be supported through the transition. Address those three things and most resistance dissolves. Ignore them and no amount of leadership messaging will help.

Communication Is Not a Town Hall

During the KIB conversion, we learned early that a single announcement was insufficient. People needed to hear the "why" repeatedly, from different sources, in different formats. Their direct manager explaining what changes tomorrow mattered more than the CEO explaining the five-year vision. Both were necessary. But the local, specific, immediate information was what reduced anxiety and enabled people to function.

Effective change management requires communication at three levels simultaneously: the strategic reason (why the company is doing this), the departmental impact (what changes for your team), and the individual reality (what changes for you, specifically, starting when). Most companies handle the first level and skip the other two.

Train for the New Reality, Not the Old One

At Ali Alghanim and Sons, when we implemented new management systems for the stock market listing, the training programme was not a single session. It was a structured rollout where each team learned their specific new workflows with hands-on practice before the old system was switched off. The people who adapted fastest were the ones who had time to practice before the change was mandatory.

I see companies in Kuwait announce a system change on Monday and expect full adoption by Wednesday. That is not a training plan. That is a stress test. People need time to build new habits. The transition period, where both old and new approaches overlap, is where operational support matters most.

Measure Adoption, Not Announcement

A change is not complete when it is announced. It is complete when the new way of working has become the default behaviour. That takes measurement. Are people using the new system? Are the new processes being followed? Where are the workarounds appearing?

At Dallal, we track adoption of every new process through our operations platform. When we introduced a new leave approval workflow, we could see within a week which managers had adopted it and which were still approving leave over WhatsApp. That visibility let us address the gaps with specific support rather than generic reminders.

Organisational change is not a project with an end date. It is a transition that succeeds when the new behaviour becomes normal. That requires patience, measurement, and consistent support long after the announcement has been forgotten. The companies that do this well treat change as a core capability, not a one-time event.