e-governance projects have a built-in bias towards technology and back-end integration than user-centric designs. Examine.

How the bias towards technology and back-end integration emerges

• Database-centric design: Projects often prioritise registries, unique identifiers, interoperability and data integration before simplifying the citizen interface.
  • Examples: Aadhaar/UIDAI, GSTN, PFMS, India Stack and state service-delivery gateways demonstrate strong back-end integration through identity, payments, databases and APIs.
• Administrative rather than citizen perspective: Systems are frequently designed around what ministries need to monitor rather than what citizens need to complete a service.
  • 2nd ARC: Emphasised that e-governance should involve process re-engineering and citizen service, rather than merely computerising existing files.
• Technology-first procurement: Large technology systems and infrastructure are easier to measure and procure than improvements in user experience, accessibility or trust.
  • Result: Government dashboards may show successful transactions while the citizen still struggles with the actual service journey.

Manifestations at the front end

• Digital divide: Technology-heavy systems can exclude citizens with poor connectivity, low digital literacy or limited access to devices.
  • Example: Portals requiring English, captchas or OTPs can disadvantage elderly persons, migrants and households where the mobile phone is not personally controlled by the beneficiary.
• Authentication over access: A technically successful authentication system does not necessarily mean successful service delivery.
  • Example: Aadhaar authentication may fail for elderly persons or outdoor workers despite the underlying entitlement being genuine.
• Urban and language bias: Platforms may assume smartphones, reliable internet and standard languages, making rural and linguistically diverse users relatively disadvantaged.
  • Example: CoWIN demonstrated the contrast between a strong national digital back end and difficulties relating to rural connectivity and language.

Consequences of the bias

• Exclusion and denial of entitlements: A technical failure can become a barrier to welfare, identity or public services.
• Loss of human discretion: Rigid automated rules may reject genuine beneficiaries because of data mismatches, leaving little room for contextual judgment.
• Weak accountability: Departmental dashboards may measure whether a transaction was completed rather than whether the citizen actually received the intended outcome.
  • Example: Sevottam and Right to Public Services frameworks emphasise time-bound citizen services, but technology must measure actual service delivery rather than merely backend processing.
• Privacy concerns: Large-scale integration of personal data increases the importance of consent, lawful processing and data protection.
  • Example: The DPDP Act, 2023 requires e-governance systems to incorporate lawful processing and appropriate safeguards for personal data.

Towards genuinely user-centric e-governance

• Citizen journey first: Design the service around what a first-time user actually needs to accomplish, and build the technology architecture around that journey.
  • Test: Can a citizen complete the service in a local language, with assistance, without unnecessary visits or paperwork?
• Human-centric interface: Provide local-language interfaces, simple navigation, assisted kiosks and accessible design.
• Offline fallback: Digital failure should not mean denial of a legal entitlement; offline and assisted alternatives should remain available.
• Human grievance redressal: Automated decisions should have an accessible human appeal mechanism.
  • Example: CPGRAMS can provide the institutional layer through which digital service failures are converted into accountable grievance resolution.

The challenge is not to choose between technology and citizens, but to align technology with citizen needs. India’s strong digital infrastructure should therefore be retained while reversing the design sequence: citizen journey → accessible interface → grievance redressal → back-end integration. The ultimate measure of e-governance is not the sophistication of the data centre but whether the last citizen receives the service efficiently, fairly and with dignity.