Comparative learning
Global Lessons
We turn global DPI experience into practical guidance. Not "copy this system," but "here are the patterns, tradeoffs, and safeguards that travel, and the conditions that make them work."
How we do comparison
Many countries have strong digital systems, but not every digital system functions as DPI. Our comparisons focus on whether shared building blocks can be reused across sectors, whether they are interoperable by design, and whether governance and accountability are real.
The transfer test
- What is stable: design principles and operating patterns that hold across contexts.
- What is local: legal frameworks, institutional capacity, and market structure.
- What is risky: choices that create lock in, exclusion, or unaccountable power.
Our comparison lenses
- Architecture: standards, protocols, federation, and interoperability.
- Governance: rule setting, oversight bodies, accountability, dispute resolution.
- Trust: privacy by design, security posture, consent, and grievance handling.
- Adoption: incentives, onboarding, support, and ecosystem participation.
- Sustainability: financing, operations, and evolution without fragmentation.
Our baseline definition of DPI
We use the broad, public benefit definition used by major DPI practitioners. DPI is a set of shared digital systems, built on open standards and designed for interoperability, governed by enabling rules, and intended to deliver services at societal scale.
In most global framing, DPI commonly focuses on three core societal functions: digital identity, digital payments, and data exchange, with other functions emerging over time.
Global lesson tracks in progress
These are the comparative tracks we are building. Each track will result in short notes plus a reusable checklist.
Digital identity models
How identity is issued, verified, and used across services without creating new exclusion.
Payment interoperability at scale
How ecosystems connect many providers and channels while keeping user experience coherent.
G2P end to end architecture
From targeting to reconciliation and grievance redress. What must be shared, and what must stay program specific.
Trusted data sharing safeguards
Legal and institutional safeguards that enable data exchange while enforcing rights, obligations, and accountability.
Feedback loops and governance
How systems evolve after launch: rule updates, measurement, incident response, and public oversight.
How to measure DPI maturity
Why measurement is hard, which indicators are useful, and where proxy metrics mislead.
How to cite this work
INA/LAB. (2026). [Lesson title]. Global Lessons. Retrieved from https://inalab.id/global-lessons/
Suggest a comparison topic
If there is a country experience, standard, or design question you want INA/LAB to cover, propose it with one sentence describing the use case and the decision you are trying to make.