Vision and mission
Public services worth trusting, delivered by government itself
A vision statement is only useful if it can be tested against real work. These are the commitments we expect to be measured on.
Vision
A Sri Lanka where dealing with government is straightforward, and where public institutions can improve their own services.
Mission
To design, build and connect digital public services with government institutions, and to leave lasting capability behind.
Objectives
Five objectives that can be checked
- 01
Services that respect people's time
Reduce the number of visits, forms and documents a person needs to complete a government interaction, and make what remains understandable in all three official languages.
- 02
Government systems that connect
Enable institutions to exchange information they are legally entitled to exchange, so citizens are not asked to carry data between counters.
- 03
Shared capability instead of repeated builds
Provide platforms, standards and patterns that many institutions can reuse, lowering cost and shortening delivery time.
- 04
Security and privacy as design requirements
Treat protection of personal information and resilience of national systems as conditions of delivery, not later additions.
- 05
Capability retained by the state
Ensure that after each engagement, the institution can operate and improve the service without depending on us.
Mandate
Where our mandate begins and ends
GovTech Sri Lanka (Private) Limited operates under the Ministry of Digital Economy. Our mandate is to provide delivery, advisory and technical capability to public institutions — it does not displace the legal responsibility any institution holds for its own services.
In practice this means the owning institution remains the decision maker. We are accountable for the quality of the work, the honesty of our advice, and the standard of what we hand over.
Delivery approach
The same six steps, on every engagement
- 01
Understand
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.
- User research
- Service mapping
- Legal and policy review
- 02
Design
Design the service end to end — content, forms, decisions, exceptions — and test it with real users before anything is built.
- Service design
- Accessibility review
- Content design
- 03
Build
Build in short cycles with the institution that owns the service, so capability stays inside government after delivery.
- Engineering
- Reusable components
- Delivery management
- 04
Connect
Connect the service to the data and platforms it depends on, using agreed standards rather than one-off integrations.
- Interoperability
- Data agreements
- Shared platforms
- 05
Secure
Assess security and privacy before launch, and keep assessing after it. Protect personal data by collecting only what is needed.
- Security assessment
- Privacy by design
- Independent testing
- 06
Improve
Measure how the service performs in use, publish what is learned, and keep improving it. A launch is a start, not an outcome.
- Performance data
- Support feedback
- Continuous iteration