Frankfurt, Tallinn, Abu Dhabi and Nairobi rarely appear in the same sentence, let alone the same strategy deck. Yet when we sit across the table from leadership teams in each of these markets, we keep running into a version of the same problem: a gap between what the organization believes it can execute and what it actually delivers once a decision leaves the boardroom.
The gap is real in every case. What changes is the name it goes by locally, and the cultural lens through which it gets explained away.
In Frankfurt, the gap usually gets called a “governance” issue. Committees exist for good reason, and process rigor has genuinely prevented costly mistakes. But the same rigor that protects against risk can also protect against speed. Decisions that should take days move through six approval layers, and by the time the market opportunity is confirmed, a competitor has already moved.
In Tallinn and the wider Baltic tech scene, teams are lean, digitally fluent and comfortable shipping fast. The gap here rarely shows up as a technology problem — it shows up as a commercial one. Product moves faster than the commercial function can absorb it: pricing, contracts, customer success and account management are often under-resourced relative to engineering, so momentum stalls after the initial sale.
In Abu Dhabi and across the wider Gulf, credibility is built through relationships first. That is a genuine strength — doors open that would stay closed elsewhere. The risk is that relationship-driven momentum can outrun operational clarity: a mandate gets agreed in principle before anyone has mapped who owns delivery, what “done” looks like, or how success will be measured.
In Nairobi, teams are used to solving problems with limited resources and improvising when a process does not exist. That resourcefulness is a real asset in a fast-moving market. It also means that structural gaps — a missing handoff step, an undocumented dependency — get patched informally instead of fixed, and the same gap resurfaces at the next scale-up.
In every one of these cases, the underlying issue is the same: a disconnect between strategic intent and operational execution. What differs is the cultural and operational lens each market uses to explain it. Frankfurt calls it governance. Tallinn calls it prioritization. Abu Dhabi calls it relationship management. Nairobi calls it resourcing. None of them call it what it usually is: an execution design gap that would show up anywhere, dressed in local language.
The gap does not disappear when you change markets. It just changes its name, and its disguise.
MentalX
Organizations expanding across EMEA and beyond often solve the same underlying problem multiple times, once per market, because each local team diagnoses it using local vocabulary. That is expensive and slow. A more useful approach is to separate the local dialect from the underlying pattern.
Cross-market growth does not fail because every market is different. It fails when leadership assumes every market’s problem is different too, and spends the same effort rediscovering a gap that a sister market solved six months earlier.