Reading Time:
6 min
Published on:
April 7, 2026

Optimizing Business Operations for Efficiency

Ali Bahbahani ​& Partners
Ali Bahbahani & Partners
Ali Bahbahani
Founder

I once spent a day observing the back office of a mid-sized Kuwaiti trading company. They had 14 employees processing purchase orders. Each order touched five people, three spreadsheets, two email threads, and a physical signature book that lived on the finance director's desk. He was out that day. Six orders sat unsigned until he returned the next morning.

Nobody in the company thought this was a problem. It was just how things worked. They had been doing it this way for nine years.

Operational inefficiency rarely announces itself. It hides in processes that people have stopped questioning. It lives in the workarounds that became permanent, the extra steps nobody remembers the reason for, and the manual tasks that could have been automated years ago.

Find the Bottleneck Before You Buy the Tool

The first instinct when operations feel slow is to buy software. A new ERP. A project management tool. A CRM. But if you automate a broken process, you get a faster broken process. You need to understand where the actual bottleneck is before you spend anything on a fix.

When we do operational optimization for clients, we start by mapping workflows as they actually happen, not as the policy document says they should. The difference between the two is usually where the waste lives. That trading company's purchase order process, once mapped, had 23 steps. We brought it down to 9. No new software was needed. Just removing approvals that added no value and consolidating three spreadsheets into one shared document.

A person with his hands on his headDescription automatically generated

The Hidden Costs Nobody Tracks

Most companies track the cost of materials, salaries, and rent. Almost none track the cost of waiting. The hours an employee spends looking for a file. The days a customer waits for a response because the request is sitting in someone's inbox. The week a project stalls because one person needs to approve something and they are in a meeting.

At Dallal, when we built our internal operations platform, one of the first things we measured was cycle time: how long it takes for a task to move from start to completion. The results were uncomfortable. Processes we assumed took two days actually took six when you counted the time spent waiting between handoffs.

If you want to optimize operations, start measuring time. Not just the time people work, but the time things wait.

A computer screen shot of a deviceDescription automatically generated

Simplification Before Automation

I am a believer in technology as a tool for operational improvement. But I have watched too many Kuwaiti companies spend six figures on systems they did not need because they skipped the simplification step.

Before you automate, ask: does this step need to exist at all? Does this report need to be produced? Does this approval add value? Does this meeting need to happen weekly or could it be monthly? In my experience, 30% of operational steps in a typical GCC company exist because someone created them once and nobody questioned them since.

At Ali Alghanim and Sons, when we prepared for the stock market listing, the governance compliance requirements forced us to document and review every operational process. The documentation alone revealed redundancies that had been costing the company time and money for years. The compliance exercise became an efficiency exercise.

A person looking at a computer screenDescription automatically generated

People, Not Processes, Are the Real System

The best process in the world fails if the people executing it do not understand why it exists. I have seen beautifully documented SOPs that nobody follows because they were designed by a consultant in a boardroom and handed down without explanation.

Operational change that sticks requires the people doing the work to be part of designing the change. They know where the real friction is. They know which steps are pointless. They have usually been working around the broken process for years and have ideas about fixing it that nobody asked them about.

The trading company's 14-person back office team, once we involved them, identified problems we would not have found through observation alone. Three of the best improvements came directly from the most junior staff. Operational optimization is not something you do to an organisation. It is something you do with the people inside it.

A white board with drawings on itDescription automatically generated