Reorganisation is not transformation.
Most attempts to fix an underperforming function change who reports to whom and leave the work itself untouched. Six months later the same bottleneck produces the same numbers under a different structure.
Operational transformation starts with the physical and informational flow of the work — who touches what, in what order, with what information — and changes that. The structure follows the redesigned work, not the other way round.
What we find on the floor.
The process assumes a layout that changed
A receiving or routing step was designed for a site configuration that no longer exists. Nobody told the system, and the system never told anyone.
Exceptions all escalate
Nothing is decided at the edge because no rule exists and nobody below has the authority or the data.
Different definitions of done
Two sites report the same metric using different rules, so the numbers are not merely scattered — they are incomparable.
Headcount added ahead of volume
The function scales by hiring because the process will not scale, and the cost per unit never improves.
A parallel spreadsheet
The real operating record lives outside the system because the system does not fit how the work is done.
No owner for the metric
The number is reported upward and nobody at the level that causes it is measured on it.
What the engagement actually includes.
Walk the operation
On the floor, on shift, with the people doing the work. We count steps, time queues and record what actually happens rather than what the procedure says.
Establish the baseline
A measured starting point for cycle time, cost and quality that both sides accept — because without it no improvement can be claimed or disputed.
Agree the definitions
What counts as a completed job, an exception, an accrued cost. Agreed with the people who run each site, in the room, before any platform discussion.
Redesign the process
Sequence, decision rules, authority at the edge, and the information each role needs at the moment they need it. Technology is applied afterwards, to a process that works.
Change management as a workstream
A named owner at each site, a budget line and a metric of its own. Not a training session in the final month.
Hold the gain
The new metric sits with the supervisor whose team causes it, reviewed on a weekly cadence, with the control catalogue handed over.
Measure, redesign, enable, hold.
Technology is applied after the process works. These are the layers we most often touch when redesigning an operating function.
Ranges observed on Al Jawad engagements. Your targets are agreed in assessment, before the work starts.
Do you start with technology?
No. Automating an inefficient operation makes it fail faster. We measure, then redesign the process, then apply technology to a process that works.
How long before anything changes?
The baseline takes two to four weeks. First measurable operational change is typically three months, on one site or one work front, before any wider rollout.
Will this reduce headcount?
Usually it changes cost per unit rather than absolute headcount — the function absorbs growth without hiring ahead of volume. Where roles do change, we say so in the design, not after.
Do you work across multiple sites at once?
We prove the redesign on one site first. Rolling out an unproven design across six sites multiplies the cost of being wrong.
Start a conversation.
Choose the one that fits where you are. None of them is a sales call. Each is an advisory conversation calibrated to a specific question.