The System, Not the Citizen
A strategic design exploration into cross-government service coordination
2026
//
Strategic Design, Innovation Consulting, Systems Thinking, Service Design, Platform Strategy, Public Sector Innovation, Digital Government, Journey Orchestration
Three layers, one missing connection
Mapping how Sanad actually works reveals three layers operating in parallel rather than in sequence. Policy and mandate sit at the top, defining what should exist but holding no direct control over execution. Service ownership sits in the middle, with each ministry running its own rules, workflows, and approvals. Platform and access sits at the bottom, providing trust, identity, and the visible entry point. The citizen interacts with the platform, but the outcomes are produced two layers up.
The result is a Trust Gateway: centralized trust, fragmented execution, citizen burden. Trust is concentrated in one place; responsibility for outcomes is distributed everywhere; and the cost of coordinating between them is pushed onto the user.
Looking across cases, the same pattern repeats. The platform appears to suffer from inefficiency or inconsistency, but underneath is a stable architecture: incentives that reward procedural completion over substantive resolution, accountability that disperses across actors, information that moves unevenly, and informal compensation by capable staff that quietly absorbs the system's failure modes. People are not failing inside the system. They are adapting to it.
Four tensions the platform cannot resolve on its own
Sanad's structural limits show up as four recurring tensions between what the platform centralizes and what the system fails to coordinate.
Unified Access vs Fragmented Outcomes. Citizens authenticate through one trusted interface, then encounter disconnected journeys, repeated verifications, and invisible dependencies. Effort shifts to the citizen; outcomes remain fragmented.
Trust Transfer vs Authority Boundaries. Trust is centralized at the platform layer, but authority over approvals, exceptions, and operational delivery stays fragmented across entities. Coordination depends on manual handoffs and goodwill.
Perceived Accountability vs Institutional Ownership. Because the platform is the visible front door, users hold it accountable for outcomes it does not control. Ownership is unclear; accountability is misdirected.
Platform Ambition vs Institutional Capacity. Digital government ambitions expand, but coordination complexity grows faster than institutional capacity. Silos stay intact. There is no shared mechanism to define or manage end-to-end journeys.
None of these are usability issues. They are structural. They will outlive any redesign of the interface.
Evaluating four scenarios against legitimacy conditions
Designing for this kind of system means accepting hard constraints. Jordan's public sector is not going to absorb a new budget line, a new ministry, or a wholesale governance reform to fix Sanad. Any intervention has to respect authority boundaries, sit within existing institutional capacity, improve citizen experience, and still address the root coordination problem.
Four scenarios were evaluated against those four legitimacy conditions:
A. Build Another Centralized Platform - fails on all four. It duplicates Sanad without resolving fragmentation.
B. Ministry-Led Coordination Portal - improves trust and user value, but cannot mandate coordination across peer ministries.
C. Third-Party Orchestrator Model - violates institutional legitimacy by placing authority outside government.
D. Journey Definition Layer (JDL) - the only scenario that scores high across all four conditions.
The JDL is not another platform. It is a coordination layer that sits above fragmented systems and below the services people use. It connects entities, rules, data, and users through policy-driven workflows, identity and access, data integration, and audit and compliance - without disrupting who owns what. Ministries keep their services. Sanad keeps its role as the trusted front door. The JDL is what makes end-to-end journeys legible, definable, and accountable for the first time.
The coordination advantage is straightforward: turn fragmented systems into coordinated outcomes through policies, workflows, and trusted data exchange, governed by foundation principles - secure by design, user-centric, interoperable, policy-driven, scalable by default.
From front door to operating system
The strategic move is to stop treating Sanad as a destination and start treating digital government as an operating system - one with a coordination layer that the platform, the ministries, and the citizens all plug into.
This reframes the question from "how do we improve the platform" to "how do we define and govern the journey the platform sits inside." That is a different design problem, and it produces different reform priorities: invest in cross-government journey orchestration, set clear platform expectations that nudge coordination without claiming authority, and build learning loops that turn repeated friction into system-level signals that actually inform redesign.
When a system repeatedly produces the same failure, the system is speaking. The task is to build the layer that can listen - and act.
