There is a specific kind of exhaustion familiar to almost every MENA SME founder past a certain size. It is not the exhaustion of too much strategic thinking. It is the exhaustion of being interrupted twenty times a day by decisions that, on paper, someone else should be making. A refund request. A late delivery complaint. A vendor asking for slightly different payment terms. None of these individually feels like a big deal, but together they add up to a founder who spends most of the working day reacting instead of leading.
This pattern has a name: the absence of an escalation protocol. Most MENA SMEs have never actually defined, in writing, what counts as a decision a manager can make on their own, versus what genuinely needs to reach the founder. Without that definition, the default setting for every member of staff becomes escalate everything, because escalating feels safer than guessing wrong, and guessing wrong once is often enough to make someone escalate everything forever afterward.
Why this defaults to the founder specifically
Escalation defaults upward for a simple reason. In the absence of a documented threshold, people escalate to whoever has historically had the final word, and in most MENA SMEs that is the founder, regardless of whether the decision actually requires founder-level judgement. A manager who could reasonably approve a modest discount, or resolve a client complaint within a known service standard, escalates instead, not because they lack the judgement, but because nobody ever told them explicitly that this particular category of decision was theirs.
The result is a founder who becomes, in effect, a human escalation matrix, holding the entire decision tree of the business in their head, re-deciding it fresh every single time a similar situation comes up, because none of it has ever been written down as policy.
Why this is particularly acute across MENA SMEs
Across MENA markets, this tends to be reinforced by two factors. First, many SMEs in the region grew out of a founder's direct, hands-on involvement in every client relationship, and staff naturally continue routing decisions the way they always have, even after the business has grown well past the point where that made sense. Second, the reluctance to make a wrong call in front of a client or a business partner runs deep in relationship-driven markets across the region, and escalating a decision feels lower-risk than owning it, even when the actual decision is low-stakes.
This creates a business that scales in headcount but not in decision-making capacity. Adding staff without redefining what those staff are allowed to decide simply adds more people funneling more decisions toward the same single bottleneck, which is precisely why some MENA SMEs feel just as founder-dependent at forty employees as they did at ten.
Building an escalation protocol that actually holds
The fix is a documented decision rights framework paired with a specific escalation matrix, built around the categories of decisions that actually recur in your business, not a generic template imported from elsewhere. This starts by cataloguing what has genuinely been escalated to the founder over the past few months, which almost always reveals categories of decisions that are far more routine than they felt in the moment.
From there, each category gets a clear owner and a clear threshold. A refund under a certain amount might be fully within a manager's authority. A refund above that amount, or one involving a repeat complaint from the same client, might require a second sign-off but still not the founder. Only a narrow, clearly defined set of decisions should genuinely require the founder's direct involvement, and naming that set explicitly is what gives staff the confidence to stop escalating everything else.
The matrix only works if the team is actually trained on it using real scenarios, not just handed a document to read once. Walking staff through recent real examples and showing them exactly where those examples would land on the new matrix builds the confidence needed to change behavior. Within a few weeks of proper rollout, most MENA SME founders notice a real drop in the volume of small decisions reaching their desk, freeing up the mental space to focus on the handful of decisions that actually require them.
An escalation protocol is not about reducing the founder's involvement in the business. It is about making sure that involvement is reserved for the decisions that genuinely need it, rather than being consumed by the ones that never should have reached the top in the first place.
See how this works in practice.
See the Escalation Protocol