This redesign of Data.gov was created as part of a contract pitch while I was at a consulting firm.
UX Designer
Data.gov is the U.S. government’s central open data platform, providing public access to thousands of datasets from federal, state, and local agencies. It serves a wide range of users from researchers and journalists to developers and policy analysts - offering information across topics like climate, infrastructure, education, and public health.
This redesign of Data.gov began as a challenge: how I could modernize a government website while working within strict federal design standards? At the time, the consulting firm I worked with was pursuing the Data.gov contract, and my lead encouraged me to take on the site as a redesign to strengthen our pitch.
While not a complete overhaul, this project focused on improving the look and feel of the interface, refining visual hierarchy, and creating a more cohesive experience. It was also an opportunity to work within the U.S. Web Design System (USWDS) while adhering to accessibility guidelines under Section 508 and WCAG.
Since this was a speculative redesign without access to user testing or analytics, I grounded my process in two main areas: a heuristic evaluation of the current Data.gov interface and comparative benchmarking against other government and data-heavy websites. Together, these methods helped shape the visual direction and guided practical UI improvements.
The site’s interface felt fragmented and difficult to navigate. On the homepage, key metrics were displayed with little context, and the filter system, particularly filtering by document type, lacked clarity and cohesion.
I conducted a heuristic evaluation of the existing Data.gov interface to better understand where users might encounter friction. This method helped me identify usability issues based on established design principles - focusing on consistency, clarity, and cognitive load.
Each dataset in the search list displays multiple color-coded tags and a diagonal banner representing the government agency type (e.g., city, county, state). The result is overwhelming visual clutter.
In the search results, file type tags (e.g., JSON, XML) are color-coded but not consistent: JSON and XML sometimes share the same red tone, but later appear in different colors like orange or green-yellow.
Breadcrumbs like “Home > [Icon] > State of Washington” include icons with no label or context, making navigation unclear.
Metadata is separated from “metadata source,” but the purpose isn’t clear to the user. Downloadable files again use inconsistent color tags, repeating earlier file type confusion.
These issues revealed opportunities to simplify the interface, use visual hierarchy more effectively, and improve semantic clarity.
Before diving into wireframes, I studied how public and private sector platforms present complex data. My goal was to understand the visual and functional boundaries of credible government design and see where I could push for more clarity.
Primary benchmark for layout structure, clear navigation, and proper use of the USWDS.
Showcased intuitive filtering and logical IA - demonstrated how to surface relevant content efficiently.
Helped define how far visual styling could go while remaining credible within a U.S. government context.
Surprising use of visual polish and editorial-style design - proof that aesthetic depth is possible in the public sector.
Informed download flow design and inspired how file types could be presented more clearly.
Offered clarity in layout and refined visual spacing for data-heavy content.
Helped reimagine how filters and study datasets could be organized, especially for users navigating large volumes of information.
Inspired ways to organize study filters and downloadable content especially in tandem with Wiley.com.
Although Data.gov serves an important function by centralizing access to government datasets, its interface poses several usability challenges. The experience feels visually fragmented and inconsistent, which can make tasks like searching, filtering, and downloading data more difficult than necessary. These design shortcomings introduce friction during common interactions and can complicate access for users who may not be familiar with open data platforms.
Visual clarity: the interface felt fragmented, with inconsistent use of color, spacing, and structure, making it difficult for users to scan or interpret content confidently.
Usability: key functions like filtering and downloading datasets lacked intuitive labels and patterns, which created friction during typical user flows.
Discoverability: important metadata and navigation elements, like breadcrumbs and source information, were either buried or confusingly labeled.
Expectation mismatch: compared to other government platforms like VA.gov and design-forward sites like CIA.gov, Data.gov’s UI lacked the polish and consistency users now expect from public sector digital experiences.
Information overload: dense search results and overuse of color-coding overwhelmed users rather than aiding navigation or decision-making.
Designing for a government website means balancing modernization with regulation. For this concept project, I challenged myself to work within the U.S. Web Design System (USWDS) - a framework built to ensure consistency, accessibility, and Section 508/WCAG compliance across federal websites. While the system provides a solid foundation, it can also feel limiting when trying to bring a more modern, polished experience to life.
One of the biggest challenges was figuring out how far I could push the visuals while still respecting the “government look.” I drew inspiration from sites like Census.gov, which appeared to use elements influenced by Material Design, and aimed to find that sweet spot between clarity, accessibility, and modern UI patterns. The goal was to subtly elevate the experience without making it feel out of place in the federal digital ecosystem.
Stay within USWDS - maintain federal consistency and accessibility standards
Improve visual cohesion - reduce clutter and unify styling across filters and datasets
Add modern UI cues without overwhelming the government tone
Respect data integrity - Ensure no redesign choices disrupted the utility of the data
Use pattern inspiration - Draw inspiration from Census.gov and Material.io
To modernize the Data.gov experience while respecting the constraints of USWDS and federal accessibility standards, I focused on four goals:
Unify layout and styling to reduce visual clutter and make the site easier to scan.
Rethink filter logic and search layout to support more intuitive interactions.
Reorganize the layout to align with user expectations.
Introduce subtle visual enhancements.
Since the goal of this project was to support a contract pitch, I approached the homepage with care - I didn’t remove any existing sections outright, but instead focused on reorganizing and modernizing the layout to improve clarity, context, and visual cohesion.
The original homepage included a basic search bar, a mission statement, a note about Data.gov turning 15, and several data visualizations with little context. While the content may have been necessary for compliance or stakeholder visibility, the structure felt disjointed and under-designed.
I made updates to the global navigation for better clarity and discoverability. I moved the “User Guide” from a prominent callout to a more expected location within the menu, and added “Contact Us” and “Login” buttons. The login function existed on the original site but was buried - I surfaced it in the nav to support users who may need persistent access.
Modernized the hero section by upgrading the search bar and introducing filtering tabs (e.g., "Most Viewed") to replace a somewhat arbitrary "Trending" section found deeper in the site.
Moved the “User Guide” into the header menu to reduce visual clutter and align with standard site behavior
The original data visualizations lacked context and hierarchy, making it hard for users to understand their relevance at a glance. My approach focused on refining the layout, simplifying visual elements, and ensuring each chart supported user comprehension rather than adding to the noise.
The original bar charts felt fragmented, so I first tested stacked bar charts for a cleaner presentation. However, accessibility checks showed low contrast,
I pivoted to horizontal bar charts with a limited 4-color palette to reduce cognitive load. I removed the original “Dataset Age” chart and replaced it with a “Most Viewed Datasets” section to align with search trends and existing UI cues across the site.
I gave data visualizations stronger context by introducing clear headings and a prominent banner above them with key stats.
Inspired by Gov.uk’s clean and utilitarian approach, I began by wireframing a two-column layout: filters on the left, results on the right. I kept the search term visible at the top of the page, alongside the number of results returned, to provide better orientation and feedback to the user.
The left panel of the page housed filtering options, while the right panel displayed dataset results. I added a clear page header - e.g., “Search results for ‘electric vehicles’” to ground the user in their journey.
Restructured the page into a two-column layout: filters on the left, dataset results on the right
Added a clear page header (e.g., “Search results for ‘electric vehicles’”) to orient users and reinforce search context
Created visual separation between filtering and content areas to reduce cognitive load and improve scannability
The original filters were presented as ungrouped, standalone buttons with no clear hierarchy. I reorganized them into drop-down menus, which made the filter system feel more structured and digestible. While I didn’t alter the actual category content (due to lack of user data), I focused on streamlining the information architecture to reduce visual overwhelm.
The original dataset cards used multiple bright, color-coded tags for both file types and organization types. While meant to aid quick recognition, the overload of colors made it harder to focus on the actual content.
In the first iterations, I replaced government type banners with smaller, single color tags and retained file type tags, but unified their color for consistency.
In later iterations, I removed the file type tags entirely and replaced them with a simple text string (e.g., “File types: JSON, CSV”) in muted italics. This significantly reduced cognitive load and improved scannability.
The original dataset detail page felt cluttered and loosely structured, making it difficult for users to quickly find critical information like downloads, metadata, or publisher details. There was little visual hierarchy, and elements such as contact info and download buttons were scattered across the layout in a way that didn’t reflect their importance or logical relationship.
To create a more intuitive and polished experience, I drew strong inspiration from Wiley.com’s studies layout, which excels at presenting dense information in a structured and scannable format. My redesign focused on reorganizing the page into a clear two-column layout, grouping related information and actions while improving the overall visual hierarchy.
Moved publisher and contact details from the left panel to directly below the dataset title
Improved visibility of source attribution to help users immediately understand dataset ownership
Prioritized credibility and context by surfacing trust-building information at the top
Moved Download, Share, and Link buttons into a grouped action block in the right column
Because this was a speculative redesign for a government contract pitch, it was essential that the updated UI not only improved usability but also remained fully aligned with the U.S. Web Design System (USWDS). Every design decision was made within the boundaries of government accessibility, consistency, and trust-building standards.
To validate my designs, I used plugins like Stark and Contrast to check color contrast ratios and visual accessibility. I also kept the WCAG guidelines open throughout the project to cross-reference compliance as I made visual and structural decisions.
Although this redesign was speculative and not implemented, it served a dual purpose: helping strengthen a contract pitch and challenging me to apply design thinking within the strict constraints of government standards.
The final concept presented a cleaner, more organized interface that honored the structure of Data.gov while modernizing its usability and visual clarity. It also gave me hands-on experience working within the U.S. Web Design System (USWDS) and deepened my understanding of accessibility compliance in the public sector.
Conduct usability testing with real users to validate design assumptions
Explore ways to streamline or combine certain filters based on usage patterns
Prototype a few key flows (e.g., filtering datasets, viewing metadata, downloading files) to test accessibility and navigation at scale
Collaborate with engineers or accessibility specialists to confirm technical feasibility and compliance alignment
This project pushed me to think differently about visual design - specifically how to create meaningful improvements without stepping outside a highly structured system. Unlike commercial products, government platforms come with unique constraints: accessibility mandates, rigid design systems, and visual expectations rooted in trust and neutrality. Working within those limits challenged me to find creative ways to simplify, clarify, and modernize without over-designing.
It also reminded me how much clarity can be gained from simply reorganizing information. By focusing on structure, hierarchy, and consistency, even a dense platform like Data.gov can become more approachable. While I didn’t have access to user feedback or analytics, this project helped me refine my design instincts and gave me more confidence working within real-world limitations.
Designing within strict systems like USWDS can spark creative solutions - not limit them
Small structural changes, like better grouping and layout, can dramatically improve clarity
Even speculative projects can sharpen real-world skills, especially around government standards and design compliance
