Sahel & the Great Automation: Part 6 – Conceptual Challenges
13 Jan. 2026
digital-transformation
7m
Reader mode
A reading into the meaning of the state when it is automated: from digitizing procedures to redefining authority, service, and responsibility—where direction is determined not by tools, but by understanding.
Click here to download the full series in PDF format.

In this final part of the series, we have reached the point where speaking about an application, a platform, or a modern technical infrastructure is no longer sufficient in itself. After the structural causes have been unpacked, the technical pulse calibrated, governance consolidated, and the usability challenges revealed at the point where the state meets its citizens, only the question behind all these layers remains: what meaning do we give to digital transformation itself? The crisis was never a crisis of tools, nor a crisis of competencies, but a crisis of conception: what does the state mean when it operates digitally? What truly changes when authority is automated? Is digitization merely an acceleration of what already exists, or a reformulation of what ought to exist?

The conceptual dimension is the most serious dimension of this series, because it does not deal with what we see on the screen, but with what lies beneath in the institutional mind. If this dimension is impaired, it empties everything before it of meaning; and if it is sound, it turns “Sahel” and similar platforms into gateways for a transformation deeper than mere service improvement.

Confusing the Concept of the “State” with the Concept of the “Platform”

The first conceptual challenge, and the most common, is reducing the state to its digital interface. Much public discourse—and at times even institutional discourse—treats “Sahel” as though it were the state itself: outages are attributed to it, delays are blamed on it, and it is asked to do what no portal, however advanced, can possess. This reduction, though it may appear harmless, creates a dangerous shift in awareness: a complex sovereign entity is compressed into an application, while the institutional structure behind it is forgotten, with its laws, regulations, culture, and internal balances.

The digital state is not an application, but a system of governance operating in a different language. The platform is only a window that reveals the degree of harmony or disorder permitted by that language. The conceptual solution here begins by re-establishing this distinction in both public and official awareness: (1) “Sahel” does not create reality; it displays it. (2) It does not decide the path; it executes it. (3) It does not possess the authority to carry out structural reform; it reveals where such reform is needed. Accordingly, the discourse accompanying digital transformation must be recalibrated so people understand that the success of the platform depends on the success of what lies behind it, and that any real development should not be demanded of the application, but of the state itself—in its laws, pathways, and definitions.

Digitization as “Acceleration,” Not “Transformation”

The second conceptual challenge lies in viewing digitization as merely an acceleration of existing procedures, rather than a rethinking of them. This perception turns the digital state into a faster version of the paper-based state, not a state different in its logic. Steps are transferred as they are, approvals are automated as they are, and the same complexity is reproduced in less time, without any real questioning: why did this step exist in the first place? And is it still justified in a digital context?

This series has shown—in its structural and technical axes—that true automation does not begin with “How do we complete this?” but with “Should we be completing it this way at all?” A smart state does not speed up queues; it eliminates the need for them. It does not improve forms; it reduces them. It does not merely accelerate decisions; it redefines the conditions under which decisions are made. The solution here is conceptual before it is procedural: digital transformation must be redefined in public policy as a comprehensive re-engineering project for the public function, not a technology project. Any digitization of a service must be tied to a mandatory review of its legal and administrative logic, so that no service is digitized before asking: is this its simplest just form? And does it serve the purpose for which it was created?

The Absence of the Concept of “Service as a Right”

One of the deeper conceptual challenges is that many government services are still mentally administered as “administrative grants” rather than established rights. This perception is reflected directly in the design of digital services: long pathways to prove eligibility, a prior assumption of non-entitlement, excessive precautionary requirements, and automatic suspension over any formal deficiency. The smart state, in its original idea, is built on reversing this logic: service is a right, denial is the exception; and the default position toward the citizen and resident is entitlement, not suspicion.

When this concept is not settled, automation remains confined to improving appearance without touching the essence of the relationship between the state and those it serves. The solution begins by redefining basic services—legislatively and administratively—as callable digital rights, not administrative requests subject to rejection. This definition should then be translated in the “general protocol for smart government” into an operating logic: (1) automating entitlement whenever its conditions are met. (2) Reducing points of human intervention to exceptional cases only. (3) Placing the burden of proof, as much as possible, on the state rather than on the beneficiary.

Confusing “Control” with “Governance”

Many institutions face a conceptual difficulty in distinguishing between control and governance. When a unified protocol, a national standard, or a central performance mirror is proposed, it is sometimes interpreted as a reduction of an entity’s independence or an interference in its powers. This understanding produces silent resistance that empties standards of their substance through exceptions.

Yet the digital state is not built on the centralization of control, but on the centralization of the rule. A unified rule does not cancel the independence of entities in implementation; it protects that independence from disorder and contradiction. Governance is not the stripping away of powers, but the regulation of those powers within a national framework that treats everyone equally. The conceptual solution here requires clear institutional discourse: that the protocol is not a tool of control, but a contract of trust; that the performance mirror is not a tool of exposure, but a tool of reform; and that compliance is not submission, but a condition of partnership within a single system. Once this understanding settles, governance transforms from an organizational burden into an institutional safeguard, and compliance shifts from silent resistance to conscious professional practice.

Confusing “Technical Bias” with “Institutional Neutrality”

One of the most serious conceptual challenges is the belief that digital systems are neutral by nature. An algorithm does not create justice on its own; it reproduces the assumptions on which it was built. If a service is designed on a mistaken assumption, automation will generalize that mistake at unprecedented speed. For this reason, the smart state must not delegate its values to lines of code without conceptual oversight. Automation must be treated as an instrument of authority, not merely a technical tool. And every instrument of authority must be subject to accountability: who designed it? On what assumptions? And in whose interest does it operate when cases conflict?

The solution here complements what was proposed in the governance dimension: subjecting the logic of automation to periodic legal and ethical review, linking any automated decision to the right of appeal and explanation, and not allowing algorithms to operate in the shadows without a clear accountability framework. A just digital state does not hide its decision behind code; it reveals its logic and assumes responsibility for it.

The Absence of a Long-Term Vision for the Automated State

Finally, a conceptual challenge emerges in treating digital transformation as a temporary project rather than a long-term path for reshaping the state. Initiatives are launched without a clear map of what comes after five or ten years: how will the relationship between legislation and automation change? How will administrative delegation be redefined? What will be the role of the human being in a state moving toward the self-operation of services?

A state that does not think about these questions early will, after years, find itself facing a gap between what technology can do, what the law permits, and what institutional culture can bear. The solution lies in including a “conceptual vision of the digital state” within national planning documents—not as a technical appendix, but as a political and administrative conception of how the state will operate when most of its decisions become automatable.

Conclusion of the Series: Intellectual Support for the Modern State Project

With this sixth part, the series “Sahel and the Great Automation” closes its circle—not to declare the completion of transformation, but to set a clear intellectual framework that protects it from deviation. From its very first entry point, this series has attempted to move the discussion from the level of the application to the level of the state; from improving the interface to re-engineering meaning; and from digitizing procedures to questioning authority itself when it operates in the language of the machine.
If digital transformation is completed in a radical manner, it does not produce only a faster state, but a state with clearer legislation, stronger activation of the law, and less room for individual discretion. When the legal rule is converted into clear operational logic, when service is tied to entitlement rather than temperament, and when procedures are managed by events rather than exceptions, the law becomes more present in people’s lives, not less; and the state becomes more capable of enforcing it with justice and consistency.

In this context, this series comes as intellectual support for that direction: an attempt to connect digital transformation to the project of the modern state, where technology is harnessed to strengthen the rule of law, not to bypass it; and to narrow the gap between text and application, not widen it. If this connection succeeds, “Sahel” will no longer be merely a service portal, but one of the instruments for building a state that operates by its rules, holds itself accountable before holding others accountable, and manages its authority with a rational digital mind.

O Allah, ordain for this nation a matter of right guidance.

Abdullah Al-Salloum
Thoughtful messages and inquiries are always welcome. Send a message
digital-transformation
Sparks
For this reason, the smart state must not delegate its values to lines of code without conceptual oversight.
The digital state is not an application, but a system of governance operating in a different language.
More sparks
Answers
How does the meaning of the state in the age of automation affect the economy?
Its effect appears in how costs, incentives, and resources are managed, and in the economy's ability to turn decisions into sustainable value. The direct context is into the meaning of the state when it is automated: from digitizing procedures to redefining authority, service, and responsibility—where direction is determined not by tools, but by understanding.
What is the difference between real digital transformation and surface digitization?
Real digital transformation redesigns processes, data, and responsibilities. Surface digitization merely moves paper complexity onto a screen without changing the service’s substance or efficiency.
Why does digital government need clear data governance?
Because digital service quality depends on data ownership, exchange, and protection. Without clear governance, systems become isolated islands rather than an integrated government experience.
How should government automation success be measured?
It should be measured by time saved, reduced manual intervention, better citizen experience, and more reliable decisions—not merely by launching a new platform or app.
More answers
Related articles