- Part 1: Ali's undefined "be more profitable" became a specific target — +20% gross profit in 12 months, AED 9.24M to AED 11.09M — broken into four named drivers, each with one accountable owner, tracked monthly.
- Part 2: that target survived its first real test, when a carrier disruption threatened the utilization driver. It held because the risk had been mapped and a decision plan already existed.
What this article (Part 3) covers: having a plan and having a tracker doesn't guarantee anyone acts when the tracker flags a problem. This is what happened when a different driver — client mix — turned red, and why it took two months before anyone treated it as their job to fix.
With the carrier issue resolved, Ali's team turned back to the monthly tracker built in Part 1. Client mix — the share of shipments carried on higher-margin freight lanes, one of the four named drivers behind the AED 1.85M target — had been drifting the wrong way for two straight months. Everyone in the room had seen the number. Nobody had done anything about it.
What "Client Mix" Actually Measures
Why a driver having an owner isn't the same as a red reading having one
Client mix, in plain terms, is the share of the company's shipments that move on higher-margin freight lanes rather than lower-margin, commoditized ones. The Part 1 plan set a trajectory: rising from a starting point of 33% toward 40% by month 12, owned by the Commercial Director.
Instead, the tracker showed it falling — to 31% in month one of the slip, then 29% in month two, moving further from the target each time it was reported. Finance's rough estimate: if that direction held for the rest of the year, it would cost roughly AED 310,000 of the AED 1.85M target.
The number was visible both months. Everyone in the monthly review saw it. What didn't happen is the part that matters: nobody treated it as a specific problem with their name on it.
Owning a driver and owning today's red reading of that driver are two different commitments. The Commercial Director owned client mix in general, decided once at the start of the plan. Nobody had ever agreed who owns fixing it the specific month it goes wrong — and that decision has to be made again every time the number turns red, not assumed from the org chart.
Why This Matters: The Visibility Difficulty
It would be easy to assume the two-month delay meant the data was hard to get, or the cause was genuinely unclear. Neither was true. The tracker had the number both months. What Ali's team actually had was a Visibility Difficulty: a reporting gap being mistaken for an ownership gap. The number was visible. What was missing was a single person whose job, that month, was to act on it.
Three things let that gap persist. Too many priorities: the team was still absorbed in the carrier issue from Part 2, so a slower-burning problem lost the room. Silos: commercial blamed pricing pressure, operations pointed at leftover capacity constraints, finance just reported the miss — three explanations, no single fix. And no clear owner for the incident itself, even though the driver had an owner on paper.
The Five-Step Reflex
What replaces a blame discussion once a KPI turns red
Treat the tracker's own number as the trigger, the moment it turns red — not a supporting detail in a wider discussion about the month.
Translate the percentage-point miss into a currency figure against the strategic target, the way AED 310,000 makes a 5-point drop concrete instead of abstract.
Name one person accountable for this specific red reading, in the meeting where it's spotted — not the department that owns the driver in general.
Agree a specific, executable step before the meeting ends — not "we'll look into it," which is how a red KPI survives another month unresolved.
A specific date to check whether the recovery action worked — so the next review starts with an answer, not a repeat of this one.
The Red-KPI Response Plan
An escalation ladder fixed in advance, the same discipline as the driver plan from Part 1 and the trigger table from Part 2 — applied to an ordinary monthly miss instead of a one-off shock.
| Consecutive Red Months | Trigger | Decision | Owner |
|---|---|---|---|
| 1 | First red reading against trajectory | Flag it by name in the monthly review; note likely cause | Driver owner (per Part 1's plan) |
| 2 | Second consecutive red reading | Quantify the AED value at risk; assign a named recovery owner and a dated check-in | Driver owner, confirmed in writing |
| 3+ | Third consecutive red reading | Escalate to the founder; review weekly, not monthly, until back on trajectory | Driver owner & founder |
Ali's team was already two months in when this table finally got used — which is itself the lesson. The plan existed in principle from Part 1. It only became real the day someone actually followed it.
A Composite AED 42M Freight Forwarding Business, Continued
A constructed composite reflecting patterns observed across UAE and GCC scale-ups in this revenue band — not a single named engagement
At the third monthly review, the Commercial Director was named explicitly as owner of the client-mix recovery — not just of the driver in the abstract. The recovery action was specific: re-prioritize the sales pipeline toward the three highest-margin lanes for the next six weeks, and stop quoting on the lowest-margin lane entirely. The next check-in was dated two weeks out, not left open-ended.
| Before | After | |
|---|---|---|
| Ownership | Client mix "owned" by Commercial Director in general; no owner for this specific miss | Named owner for the recovery, confirmed in writing at the review where the miss was flagged |
| Response time | Two months of visible red readings before any action | Recovery action agreed in the same meeting the second red reading appeared |
| Explanation vs. action | Three departments, three explanations, no fix | One recovery action, specific and time-bound |
| Follow-up | No date to check whether anything had improved | Next decision date set two weeks out |
| Outcome | Not tracked — the miss had no owner to report back | High-margin share recovered to 35% within two review cycles |
What Good Looks Like
Five questions worth answering at your own next monthly review: