Chapter 12
Digital Nation-Building in Oman
"Nation-building begins with solving frustrations you've lived."
There is a particular kind of frustration that drives entrepreneurship in emerging digital markets. It is not the frustration of inconvenience — it is the frustration of knowing that a solution exists somewhere in the world and is simply not available where you are. You have seen how digital government services work in Estonia. You have experienced seamless insurance purchasing in Singapore. And you are standing in a queue in Muscat, holding a paper form, wondering why.
SuperJet Oman was born from that frustration. Not as a theoretical exercise in digital transformation, but as a practical response to problems I had personally experienced. The platform began with a simple premise: government services, insurance, and financial products should be accessible through APIs that any developer or service provider could integrate.
Building the Digital Infrastructure
The technical challenge was significant but solvable. The harder challenge was regulatory and cultural. Oman has a deliberative approach to digital transformation — one that values stability, compliance, and alignment with national values. This is not a weakness. It is a design constraint, and constraints, as I had learned at Huawei, are innovation accelerators.
We built SuperJet to be compliant from the ground up. Every API, every data flow, every user interaction was designed with regulatory requirements as foundational parameters, not afterthought patches. This approach — governance as accelerator — meant that when we went to market, we did not face the compliance delays that trip up companies that build first and regulate later.
"Digital nation-building is not about importing solutions. It is about building solutions that respect local constraints and local values."
The Sharia-Compliant Digital Bank
One demanding part of that work was developing a proposal for a Sharia-compliant digital banking solution. It brought technical architecture and the commercial model into the same conversation. Compliance needed to shape the design from the beginning, rather than being added after the product was conceived.
Preparing the proposal required market research, demographic analysis and careful attention to the assumptions behind the figures. I found that work demanding and enjoyable. It reinforced a lesson I had learned elsewhere: a credible discussion begins with preparation, and a proposal has to be understood in the context of the institution receiving it.
Digital nation-building, I learned, is not about importing solutions from more developed digital markets. It is about building solutions that respect local constraints and local values. The sharp reduction in citizen service frustration and the marked improvement in digital inclusion that SuperJet achieved were the result of this principle: constraint as design parameter, not obstacle.
In later digital transformation work, I saw organisations trying to optimize before they had stabilized. They wanted to scale before examining whether roles, responsibilities and working conditions could support the change. Importing a playbook could not answer those local questions.
This was the pattern I watched my father live in 1990. Stabilize first. Optimize after. It became a principle I returned to in my work: understand the constraint before deciding how to respond.
From the personal archive
