An official website of Ministry of Digital Economy, Government of Sri Lanka
Secure connection. Look for https:// and .gov.lk
Our work
No single area delivers a working public service on its own. This page shows what each area covers and what it relies on.
Capability area
Making everyday interactions with government simpler: fewer visits, fewer forms, fewer repeated documents. Work in this area starts with how people experience a service, not with the technology behind it.
Connects to, ,
All capability areas
NoteThis taxonomy is an interface placeholder pending an approved GovTech capability model.
Services people actually use
Making everyday interactions with government simpler: fewer visits, fewer forms, fewer repeated documents. Work in this area starts with how people experience a service, not with the technology behind it.
Build once, reuse across government
Shared platforms that many institutions can reuse instead of each building its own. Reuse lowers cost, shortens delivery time and keeps the citizen experience consistent.
Related work
Systems that can talk to each other
Common data definitions, exchange standards and connections between institutions, so that information a citizen has already provided does not have to be provided again.
Proving who you are, safely
Capability area covering how people and organisations can be identified and authenticated for digital services, with privacy and consent designed in from the start.
Engineering capability inside government
Cloud, hosting, engineering practice and delivery capability that lets institutions build and operate digital services responsibly.
Tested before it is adopted
Structured assessment of technologies such as AI and automation for public-sector use — including where they are not appropriate.
Related work
Public services people can rely on
Security practice, resilience and trust measures for public digital infrastructure. Trust is a service requirement, not a feature.
Shared rules and shared skills
Standards, guidance and skills development so that quality does not depend on which institution is delivering.
Delivery approach
Research with the people who use a service and the officers who deliver it. Map the real journey, including the parts that happen on paper.
Design the service end to end — content, forms, decisions, exceptions — and test it with real users before anything is built.
Build in short cycles with the institution that owns the service, so capability stays inside government after delivery.
Connect the service to the data and platforms it depends on, using agreed standards rather than one-off integrations.
Assess security and privacy before launch, and keep assessing after it. Protect personal data by collecting only what is needed.
Measure how the service performs in use, publish what is learned, and keep improving it. A launch is a start, not an outcome.
Notices, procurement updates and delivery notes. Demonstration form — nothing is sent.
