I designed a Minimum Viable Product (MVP) for an open-data dashboard to help government officials in Assam track regional development metrics in one unified view. By aggregating indicators across multiple schemes into a single platform, the design eliminates platform-switching and simplifies daily data analysis for district officials.
Jump to the solution →
Process
Mentored by Anushka Gokhale (Sr. Product Designer) and collaborating with cross-functional Research, Data and Tech teams, I led the user experience through four key phases.
*Gantt have a real project with clean cut phases
Understanding the problem
District performance metrics in India are siloed across multiple systems and scheme-centric platforms, making tracking slow and fragmented. Assam was selected as the first state to tackle this challenge.
CivicDataLab's data team was consolidating disparate scheme indicators into a single open-data pipeline.
To design the front-end user experience and help structure raw metrics into an intuitive dashboard for easy browsing.
Through the insights from our research and data science teams, we identified three core user priorities.
To spot patterns and problems
To establish trust in the data
For periodic data updates
Research
Research showed our users weren't very tech-savvy, so introducing unfamiliar patterns risked steep learning curves.
*Snippets of my notes from the mapping
In a quick 3-day sprint, I explored multiple layouts and information flows for the research team to user test and identify early friction areas and goal inconsistencies.
*Wireframing for government products looks like small decisions with big impacts
Designing alongside an evolving dataset created a two-way feedback loop with the data team to align user desires with technical constraints.
Informing pipelines: UI concepts helped the data team understand what level of granularity was needed in sections like the overview.
Scoping phase 1: Technical limits helped trim complex features into the Phase 2 roadmap.
OPPORTUNITY AREA
Wireframe testing and user research pointed to four essential requirements.
State → District → Department → Scheme for clear, scalable navigation.
A flexible interface designed for quick access whenever required.
Direct access to everything from key chart highlights to raw source data.
Quick-glance progress updates paired with print options for internal meetings.
Final I.A.
To build a foundation for the interface, I mapped an information architecture that followed a drill-down hierarchy based on the scope requirements.
*A high-level view of the IA
Solution
Core problems discovered and how they were solved for.
Closing
For a seamless handover and to prepare for Phase 2 of production, I delivered a comprehensive audit of the current design alongside full component documentation — and took stock of what the project taught me.
Explicitly documented non-MVP features for future roadmap planning.
Cataloged UI variations between Figma specs and web implementation.
Tracked baseline design assumptions to guide upcoming user testing cycles.
Detailed functional guidelines and state rules for each UI component.
Documented layout adaptations and breakpoint behavior for mobile screens.
Captured insights from data teams and end-users to justify layout and IA choices.
As my first fellowship experience, having full end-to-end ownership taught me how to navigate real-world constraints, align with diverse stakeholders in product, data and tech, and take a product from 0 to 1.