Dashboard Redesign
Feature delivery sped up by 30% and UX bugs got cut in half. I got there by introducing Double Track Agile and a consolidated Figma design system to a burned-out NielsenIQ design team.
eliminate designer burnout caused by reactive, development-driven decision-making, without sacrificing continuous delivery quality?
Traditional handoff cycles forced designers to respond to developer decisions rather than lead them. Teams were burning out fixing issues in production rather than driving product strategy.
There was no shared design system, so every designer worked in isolation. More than 60% of design time went into bug fixes, leaving almost no room for discovery or innovation. The team had lost the ability to be proactive.
The client's product UI itself is confidential. The interactive recreation further down shows the resulting dashboard without any client-identifying detail.
Double Track Agile ran discovery and delivery as parallel sprints, formally separating the space where designers could think ahead from the space where they supported delivery. That one structural change ended the reactive loop.
A consolidated Figma design system with tokens, components, and documented variants eliminated inconsistency at the source. Proactive KPI alerts and a democratized data dashboard gave the team visibility to anticipate problems before they reached production.
Double Track Agile: Structural Fix
The swimlane shows how separating Discovery and Delivery tracks ended the reactive loop. Designers stopped responding to developer decisions and started leading them. Hover each cell for detail.
Double Track Agile. The team was stuck in a reactive loop. By formally separating discovery and delivery tracks, designers stopped being responders and became leaders of the product conversation. It was a structural fix to a cultural problem.
It started emerging organically, midway through the project. If we'd planned for it from sprint one, the consistency gains would have compounded faster. The lesson: structural process changes need to be designed as deliberately as the product itself.
How the Dashboard Felt to Use
The production dashboard UI is client-confidential. Below is an interactive recreation built for this portfolio, using the same interaction pattern but with generic product names and fictional data.
Illustrative recreation: interface rebuilt from memory in plain HTML/CSS/JS. Product name, brand names, and data are all fictional.
| Report | Region | Cadence | Status |
|---|---|---|---|
| Weekly Share Recap | Total US | Weekly | Sent |
| Distribution Tracker | Region 1 | Monthly | Pending |