e-governance projects have a built-in bias towards technology and back-end integration than user-centric designs. Examine.
Approach · directive: “examine”
What it asks · Assess whether Indian e-governance has favoured technology and back-office integration over citizens' ease of use, with evidence on both sides and fixes.
The question has 2 parts — answer each
- Examine: evidence that e-governance projects privilege technology and back-end integration over citizens' ease of use
- Examine: the counter-view, and the fixes that make e-governance user-centric
Open with · e-Governance succeeds only when citizens can actually use it — yet many projects are built from the department's back office outward.
Cover
- The bias: success measured by servers, databases and files digitised — outputs rather than citizen outcomes.
- Evidence: complex, English-first portals, multiple logins, online-only access and biometric authentication failures in welfare delivery.
- Digital divide: the rural poor, women, elderly and persons with disabilities are left dependent on intermediaries.
- Counter-view: back-end integration is what makes services work — DBT on JAM, GSTN, DigiLocker, UPI show integration benefiting users.
- User-centric examples: UMANG, e-Sanjeevani, Passport Seva redesign, multilingual interfaces through Bhashini.
- Remedies: process re-engineering before digitisation (2nd ARC), user research, accessibility standards, assisted access via CSCs, grievance and feedback loops.
Close with · Technology is the means and citizen experience the measure — e-governance must be designed with users, not merely for departments.
Question: UPSC's CS (Main) 2025, GS Paper II — paper ↗. Approach: Minimalist IAS, checked 30 Sept 2026 (how we verify) — UPSC publishes no model answers. ·
Model answer · 210 words (UPSC limit 150) · Minimalist IAS
e-Governance succeeds only when a citizen can actually use it, yet many Indian projects are built outward from the department's back office rather than inward from the user's need.
Where the bias shows
- Metrics: success is counted in servers installed, records digitised and transactions processed — outputs, not whether the citizen got the service faster.
- Design: English-first portals, multiple logins, online-only access and biometric authentication failures in welfare delivery that exclude the very people a scheme targets.
- Digital divide: the rural poor, women, the elderly and persons with disabilities end up dependent on intermediaries.
- Process copied, not re-engineered: paper workflows are digitised as they are, so the queue moves online instead of disappearing.
The counter-view
- Back-end integration is what makes services work: JAM-based DBT, GSTN, DigiLocker and UPI show integration that citizens feel as convenience.
- User-centric design exists: UMANG's single app, the Passport Seva redesign, eSanjeevani tele-consultation, multilingual interfaces through Bhashini.
Making it user-centric
- Re-engineer processes before digitising them, as the Second ARC urged; run user research and accessibility standards; keep assisted access through CSCs; build feedback and grievance loops into every service.
The bias is real but not inevitable: technology is the means and citizen experience the measure — e-governance must be designed with users, not merely for departments.
Written by Minimalist IAS from facts checked at source (how we verify) — a little fuller than exam length, so every part of the question is covered; in the hall, keep the structure and trim the detail. UPSC publishes no model answers: compare your structure and coverage with this, then write your own.