The Michigan
Department of State

I served as the Project Manager and Lead UX Researcher for the Michigan Department of State in redesigning their historical election results website, transforming a static archive of election tables into an interactive dashboard that makes official election data easier to explore and understand. This work expanded on the Center for Civic Design's Power BI Voting Dashboard. My team and I introduced the project at a statewide press conference alongside Secretary of State Jocelyn Benson and the Deputy Chief of Staff Neil Tambe.
🚀 Project is set to launch ahead of the August 2026 Primary Elections.
TIMELINE
TEAM
1 Project Manager (Me)
2 UX Researchers
2 UX Designers



PROBLEM SPACE
Buried In Plain Sight
Government websites are rich in data but notoriously difficult to navigate. In an era of election misinformation, official data sources need to do more than provide data, they need to convey election information clearly and in context.
Michigan's existing historical election results website returns each election as one long, static page of tables. Finding a specific race means scrolling through hundreds of lines. There's no search bar. No visualizations. No context for what the numbers mean.




RESEARCH
Navigating Political Stakes
Elections in a swing state carry real weight. My team understood that this dashboard could significantly shape how voters, journalists, and officials interpret Michigan's election data. Because of that, neutrality was the foundation of the project. To uphold that standard, we built accountability checks into our process.
Client Alignment: Weekly syncs with Deputy Chief of Staff Neil Tambe ensured our design decisions aligned with what the Michigan Department of State could publicly support and defend.
Faculty Critique: Regular stand-ups with academic advisors and peers surfaced blind spots and challenged assumptions before they became design choices.
Neutrality by Design: Every design choice was evaluated through a nonpartisan lens with no biased framing, no editorial language, and no visual treatment that could favor a candidate or party.

Jocelyn Benson,
Secretary of State
“
Making those official sources of information more user-friendly, more accessible, and easier to understand makes them more useful. It prebunks misinformation and builds trust in our elections.
”

✅ Election Data Visualized
✅ Interactive Maps
🚫 Unintuitive Navigation
🚫 Limited Data Filtering
🚫 Lack of Context for Data
✅ Map & Pie Chart Visualizations
✅ Prominent Data Export Button
✅ Clear Update Timestamps
🚫 Data Heavily Text Based
🚫 Only Shows Past Election Results
✅ Clear Filtering & Navigation
✅ Data Source Clearly Labeled
🚫 Visualizations Are Static
🚫 Limited Data Views
✅ Clear Demographic Categories
✅ Data Is Contextualized
🚫 Color Contrast Issues
🚫 Static Charts & Filtering
🗳️
Voters
Want to find and understand what the data means to make decisions.
📰
Reporters
Want reliable, downloadable data to analyze trends and report accurately.
🧑💼
Clerks
Want to find and understand what the data means to make decisions.
👔
Elected Officials
Want flexible ways to view the data and visuals to share with the public.
"People don’t understand that unofficial data is unofficial for a reason. Clear messaging about when counts are final would go a long way in building trust"
"It’s important to provide context with data visualizations…too often, maps and charts can mislead people if they don’t explain what’s behind the numbers."
Click to Zoom
Click to Zoom
DESIGN
Design System & Accessibility
Rather than invent a new visual language, my team made a deliberate call to work within the established design documentation outlined by the Center for Civic Design and Michigan's Digital Guidelines. These established tokens and components are already trusted by government stakeholders and built to work within Power BI constraints. Starting from that foundation meant our design decisions could focus on information architecture and interaction patterns rather than fighting institutional expectations or platform limitations.
Every new component was evaluated for feasibility within Power BI and tested against WCAG 2.1 AA standards using WAVE and axe DevTools. All critical accessibility issues were resolved before handoff, while remaining refinements were documented for implementation.


Misinformation
Prebunking
Cascading
Search Filters
Data Sharing &
Exportation
Click to Jump to Each Section
Original Design
Initial Iteration
Final Design
Original Design
Initial Iteration
Final Design
Original Design
Initial Iteration
Final Design
52%
Average Task Time
43%
Average Difficulty
52%
Hardest Task Time
64%
Hardest Task Difficulty
Other Projects...









