Government of India · Mission Karmayogi

iGOT Karmayogi

The only thing 15M+ users share is the login screen.

Every officer sees a different set of courses, chosen by role and designation, across 23+ languages. What stays identical for all of them is how the platform behaves, one navigation model, one interaction language, regardless of who's using it.

The problem

Almost no shared context between 15M+ users.

iGOT Karmayogi is India's national digital learning platform for civil servants, covering every central ministry and department, with courses in 23+ languages. Its users range from field-level officers with low digital confidence to senior bureaucrats managing policy portfolios.

Underneath that user diversity sat more than 100 distinct workflows, ranging from the platform's most complex administrative processes to its simplest learner interactions. Each needed its own design resolution, without fragmenting the coherence of the platform as a whole.

Approach

One consistent interface, personalized underneath.

Across more than 100 of these workflows, I owned the design decisions, directing and mentoring the design team while keeping Product Managers aligned with client expectations.

Decision 01 · Load-bearing

Separated the content layer from the interaction shell.

Course recommendations and dashboards are driven by role and designation, so a field officer and a joint secretary see almost entirely different content. What doesn't change is the navigation structure and interaction patterns around that content, that consistency is what let one design system scale across a hugely varied population.

Decision 02

Matched research rigor to each workflow's complexity.

With 100+ workflows to resolve, one research method would have been either too slow or too shallow. Simple workflows ran on traditional research, ambiguous ones used AI-supported synthesis, and where access was fully constrained, HMHT reasoned through specific, clearly labelled user types before committing to a direction.

Decision 03

Standardised typography and iconography for legibility, not branding.

iGOT is built on Material Design 3 as its base system. Within that, moved the platform to Noto Sans and a single Material Icons set, covering the Indic scripts iGOT needs and cutting relearning cost for infrequent users. This later became a CoE standard adopted across other Tarento projects.

Outcome

Where the platform stands today.

100+

Workflows redesigned, from the platform's most complex processes to its simplest interactions.

15M+

Registered users on the platform, as of April 2026.

4,000+

Courses across every central ministry and department.

60M+

Total learning completions recorded on the platform.

Reflection

The content/shell separation went deepest where it mattered most first, then scaled outward as the pattern proved itself. Method-matching across 100+ workflows ran the same way, simple ones on judgment, harder ones earning deeper simulation. Next phase, I'd push that same rigor further down the list.