Backgound | Challenge | Prepartion | Design Sprint Process | Outcome | Conclusion
How can user-centered design transform government services to improve accessibility and engagement?
The DigiLocker initiative, part of the Indian Government’s Digital India program, aims to provide secure digital storage for official documents. Despite its widespread adoption—serving over 1 billion users and facilitating 4 billion document retrievals—the platform faced challenges, including low Aadhaar linkage, user confusion about its functionality, and ineffective onboarding. These barriers limited the app’s potential to streamline document management and enhance user experiences fully.
To address these issues, the DigiLocker team partnered with Parallel, a design studio, and executed a focused Design Sprint. By identifying key pain points, reimagining the onboarding process, and simplifying the app’s features, the sprint delivered remarkable results: a 280% increase in user retention, 7.5 million new installs, and improved Aadhaar linkage rates. This success highlights the power of user-centered design in modernizing public services and empowering citizens.
Part 1: Background
DigiLocker, an initiative by the Government of India, is a cloud-based platform designed to securely store, access, and authenticate important documents such as driving licenses, passports, and car registrations. It plays a critical role in India’s digital transformation, enabling citizens to move toward a paperless and streamlined documentation system.
Despite its massive user base of 35 million, DigiLocker faced significant challenges in user adoption and experience. Many users found the platform confusing, struggled with onboarding, and had a difficult time understanding its purpose.
These challenges hindered DigiLocker’s potential to become an indispensable tool for digital documentation in India. To address these issues, a 10-day design sprint (including Determining Challenges, Discovering Information, Defining Opportunities, Developing Ideas, Delivering Solutions and Driving Changes) was conducted, focusing on human-centered design, co-creation, and rapid iteration to reimagine the platform’s user experience.
Part 2: Major Challenges
Through initial discovery conversations with stakeholders and users, three major challenges with DigiLocker were identified:
- Misconception of Purpose:
Many users mistakenly believed DigiLocker was only a digital document storage app rather than a secure platform for receiving and managing authenticated government-issued documents. - Onboarding Frustrations:
Users struggled with signing up and retrieving their first document. The broken onboarding flow caused many users to abandon the app before understanding its value. - Limited Perception of Functionality:
Users thought DigiLocker was limited to storing ID cards (such as Aadhaar), unaware that it supports a wide range of official documents, including educational certificates, financial records, and vehicle registrations.
These issues highlighted a need for a user-centered redesign to improve clarity, accessibility, and functionality.
Part 3: Preparation
Proper preparation was critical to the success of the DigiLocker design sprint. The team began by setting clear goals for the sprint. The primary focus was to simplify the onboarding process, clarify DigiLocker’s purpose as a platform for managing authenticated government-issued e-documents, and improve feature discoverability to highlight the platform’s full range of functionalities. These goals were aligned with the overarching aim of making DigiLocker more intuitive and user-friendly.
A multidisciplinary team was assembled to ensure diverse perspectives and expertise throughout the sprint. The team included designers to lead the visual and interaction design, developers to ensure technical feasibility and customer support representatives to provide insights into real-world user pain points. Key stakeholders, including management, were also involved to align on business goals and provide organizational buy-in. Facilitators were brought in to guide the sprint process, ensuring that the team stayed focused and productive. The belief that “everyone is a designer” drove a collaborative environment where every team member, regardless of their role, contributed to the design process.
Before the sprint began, the team researched to define the problem space. This included analyzing user feedback collected from customer support teams, reviewing app analytics to identify where users struggled (such as during onboarding), and exploring examples of user misconceptions about DigiLocker’s purpose. This research provided a foundation for understanding user needs and helped the team identify the most pressing challenges to address during the sprint.
To support the sprint process, the team ensured all logistical and technical requirements were in place. Collaboration tools like Miro were chosen for remote brainstorming and journey mapping, while Figma was selected for rapid prototyping. User testing platforms were also prepared to schedule and conduct testing sessions with real users. A dedicated workspace was reserved for the sprint to foster focus and productivity, and all team members were briefed on the tools and workflows to be used.
Finally, a detailed day-by-day timeline and agenda were created to guide the sprint process. This ensured that each day had a clear focus and deliverables, from problem discovery and ideation on Days 1–2, to storyboarding and prototyping on Days 3–4, to testing and iteration on Days 5–9, and finalization on Day 10. Stakeholders were also briefed on the sprint agenda and aligned on the expectations, emphasizing that the sprint’s goal was to validate solutions through prototyping and testing, not to create a finished product.
Part 4: The Design Sprint Process
Day 1: Discover User Needs and Define the Root Cause
The sprint began with a critical focus on discovering user needs and understanding the root causes of DigiLocker’s usability challenges. The team conducted an alignment workshop with stakeholders to gather insights from user feedback and app analytics. This process involved mapping the entire user journey and identifying moments of frustration, such as the onboarding experience and users’ struggle to retrieve their first document. The workshop highlighted that many users misunderstood DigiLocker’s purpose, thinking it was merely a document storage app rather than a secure platform for managing authenticated government-issued documents.
To ensure actionable outcomes, the team translated the identified challenges into How Might We (HMW) statements. For example, how might we simplify onboarding to reduce drop-offs, and how might we communicate DigiLocker’s full range of functionalities clearly? These HMW statements provided a framework for addressing the root causes of user dissatisfaction and ensured that the team had a shared understanding of the problems they aimed to solve.
Day 2: Co-Creation and Ideation
On the second day, the team focused on co-creating solutions to address the challenges identified on Day 1. A collaborative workshop was held involving all stakeholders, including designers, developers, management, and customer support representatives. The belief that “everyone is a designer” guided this session, encouraging participants to contribute ideas regardless of their professional background actively. To foster creativity, the team brainstormed solutions and sketched their ideas, focusing on simplifying onboarding, improving navigation, and showcasing DigiLocker’s broader capabilities.
The co-creation process brought fresh perspectives to the table, breaking traditional silos and enabling innovation. Even non-designers contributed unique and practical ideas, many of which were shortlisted for further development. By the end of the session, the team had a collection of diverse ideas to address the core problems, setting the stage for prioritization and prototyping.
Day 3: Prioritizing Ideas and Storyboarding
Day 3 was dedicated to prioritizing ideas and creating a clear plan for the prototype. The team displayed all the sketches from Day 2 in an “art gallery” format, allowing participants to review and discuss each idea. Using a note-and-vote method, team members voted on the most impactful and feasible ideas. Discussions focused on selecting solutions that would align with user needs while being practical to implement in the prototype.
The selected ideas were combined into a detailed storyboard, which mapped out the user flow for the prototype. This storyboard served as a blueprint, showcasing how users would interact with DigiLocker’s new design, from onboarding to document retrieval. By the end of the day, the team had a clear direction for building the first prototype.
Day 4: Develop the Prototype
On Day 4, the focus shifted to developing the first high-fidelity prototype. The design team worked diligently to translate the storyboard into a functional prototype that addressed the prioritized challenges. The prototype included a simplified onboarding process, improved navigation, and better visual cues to help users understand DigiLocker’s full range of features.
The goal was to create a tangible and testable version of the new design. The team ensured that the prototype was visually polished and interactive enough to simulate a real user experience. By the end of the day, the first iteration of the prototype was ready for testing with real users.
Day 5: User-Centered Testing
Day 5 was dedicated to user-centered testing, where the prototype was tested with real users. The goal was to observe how users interacted with the new design and uncover areas of confusion or friction. During the testing sessions, participants were asked to navigate the app, complete the onboarding process, and retrieve their first document.
Key insights emerged from these sessions. While users appreciated the simplified onboarding process, some still struggled with understanding how documents were saved and retrieved. The testing also revealed that certain design elements, such as icons and labels, needed further clarification. These insights were critical for guiding the next phase of iteration and refinement.
Day 6: Iteration and Refinement
Armed with feedback from Day 5, the team began iterating on the prototype to address the identified issues. A remote workshop was conducted using Miro, allowing stakeholders to collaboratively review testing insights and suggest improvements. The team refined the design by enhancing visual cues, simplifying document retrieval, and improving the overall navigation flow.
The iterative process ensured that the prototype became more aligned with user needs. By the end of the day, the team had updated the prototype to reflect the feedback, making it ready for further testing. This iterative approach underscored the importance of continuously refining solutions to create a truly human-centered design.
Days 7–8: Enhanced Prototype Development
Over the next two days, the team focused on building a more polished and detailed prototype. This second iteration incorporated all the feedback from the first testing phase. The onboarding process was further streamlined, and additional tooltips and guidance were added to help users understand DigiLocker’s features. The design also underwent visual enhancements to create a more intuitive and aesthetically pleasing experience.
The iterative process allowed the team to address even minor usability issues, ensuring that the prototype was as user-friendly as possible. By the end of Day 8, the enhanced prototype was ready for its final round of validation.
Day 9: Testing the Final Prototype
Day 9 was dedicated to validating the refined prototype through another round of user testing. Five new users were asked to interact with the prototype while the team observed their behavior. This testing confirmed that the onboarding process was now intuitive and that users could easily navigate the app and discover its full range of functionalities.
While most issues from the first round of testing were resolved, minor adjustments were identified for further refinement. The team gained confidence that the prototype was ready for implementation.
Day 10: Finalization and Handoff
On the final day, the team reviewed all feedback and made final adjustments to the prototype. Detailed documentation, including annotated designs and user flows, was prepared to ensure a smooth handoff to the development team. Stakeholders were briefed on the final design and the insights gained from the sprint.
By the end of the day, the team had a user-centered, validated design ready for development. The sprint successfully addressed DigiLocker’s major challenges, creating a platform that aligns with user needs and expectations.
Part 5: Outcome
The redesigned DigiLocker app achieved remarkable success:
- 280% increase in 30-day user retention (from 18% to 68%).
- 7.5 million new app installs within six months.
- 67% of page visitors downloaded the app from the App Store.
- 66% of Aadhaar linkage among users (up from 54%).
- 3.4 average documents fetched per user, compared to 2.7 previously.
The sprint improved the app’s design and empowered the DigiLocker team with a deeper understanding of user-centric design principles.
Part 6: Conclusion
The Indian Government’s DigiLocker Design Sprint demonstrated the power of user-centered design in transforming public services. By addressing key user pain points such as low Aadhaar linkage, user confusion, and ineffective onboarding, the sprint reimagined DigiLocker as a more accessible and functional platform. The results were remarkable, with a 280% increase in user retention, 7.5 million new installs, and a significant rise in Aadhaar linkage and document usage.
This success highlights the broader potential of Design Sprints in solving complex challenges within government initiatives. By prioritizing user needs and fostering collaboration, governments can create impactful, scalable solutions that improve citizen engagement and adoption. DigiLocker’s transformation is a testament to how design-driven innovation can modernize public services and empower millions.
Reference
- Argyll and Bute. (n.d.). Run a service design sprint. Retrieved from https://portal360.argyll-bute.gov.uk/service-manual/how-we/run-a-service-design-sprint
- Bradshaw, H. (2019, September 16). LabPlus: What do design sprints, game design and government have in common? NZ Digital Government Blog. Retrieved from https://www.digital.govt.nz/blog/labplus-what-do-design-sprints-game-design-and-government-have-in-common
- Chandler Institute of Governance. (n.d.). India’s Aadhaar system: Bringing e-government to life. Retrieved April 6, 2025, from https://www.chandlerinstitute.org/governancematters/indias-aadhaar-system-bringing-e-government-to-life
- Department for Culture, Media and Sport & Department for Digital, Culture, Media & Sport. (2022, July 28). Creative industries spillovers – research findings. GOV.UK. Retrieved from https://www.gov.uk/government/publications/creative-industries-spillovers-research-findings
- Design Council. (2022, June). Creative Industries Sector Vision Report: Maximising the spillover value of the creative industries to the wider economy. Retrieved from https://assets.publishing.service.gov.uk/media/62e10b63e90e0766b251ab73/Creative_Industries_Sector_Vision_Report_FINAL.pdf
- Hong Kong Police. (2019, May 8). ISW holds ‘Design Sprint’ workshop. Offbeat, Issue 1134. Retrieved from https://www.police.gov.hk/offbeat/1134/eng/7885.html
- Omar, A., Arpalikli, H., & Cottrell, R. (2023, January 9). How we ran a 1 day design sprint to help users understand visa options. Design in Government Blog. Retrieved from https://designnotes.blog.gov.uk/2023/01/09/how-we-ran-a-1-day-design-sprint-to-help-users-understand-visa-options/
- Parallel. (2020, October 30). Reimagining digital documents for a billion Indians with a Design Sprint. Sprint Stories. Retrieved from https://sprintstories.com/reimagining-digital-documents-for-a-billion-indians-with-a-design-sprint-b44e50c0a61f
- trendig. (2019, May 27). Hong Kong Police uses Design Sprint Framework to improve public services. Medium. Retrieved from https://medium.com/trendig/hong-kong-police-uses-design-sprint-framework-to-improve-public-services-ed5414fd696b
- trendig. (2019, May 27). Hong Kong Police uses Design Sprint Framework to improve public services.
- trendig blog. Retrieved from https://trendig.com/en/blog/hong-kong-police-uses-design-sprint-framework-to-improve-public-services/ Unboxed Consulting Ltd. (n.d.). Design sprint – Digital Marketplace. Digital Marketplace. Retrieved from https://www.applytosupply.digitalmarketplace.service.gov.uk/g-cloud/services/264741729886603
- Wytze, A. (2018, August 1). Could “Design Sprints” work in government? Code for Canada. Retrieved from https://medium.com/code-for-canada/could-design-sprints-work-in-government-aa167df9db8b
