Redesigning Team Dashboards for a Project Management Tool
Overview
StackBoard is a project management platform used by cross-functional teams to track work across sprints, backlogs, and roadmaps. The existing dashboard was data-dense but poorly organized, which made it hard for managers to get a quick read on project health without digging through multiple views.
I redesigned the team dashboard to surface the most important signals at a glance, reduce clicks to key actions, and make the layout flexible enough for different team sizes and workflows. The result was a cleaner, faster overview that teams actually used as their daily starting point.
+35%
Dashboard Adoption
-21%
Time to Status Update
+19%
Team Satisfaction
Team dashboard with status strip and modular widget cards
Challenge
The dashboard showed everything but highlighted nothing. Sprint progress, blockers, workload distribution, and recent activity were all visible, but they competed for attention equally. Managers had to mentally filter through dense tables to figure out what actually needed their attention.
As a result, most team leads stopped using the dashboard altogether. They relied on standups and Slack threads to get status updates, which defeated the purpose of the tool.
Problem Statement
How might we redesign the team dashboard so managers can assess project health in under 30 seconds, without losing access to the detail they need when they want to dig deeper?
Original dashboard where every data type competed for attention
Approach
I treated the dashboard redesign as an information hierarchy problem first and a visual design problem second. The question was not what to show, but what to show first.
What I found
Through interviews with team leads and PMs, I identified three things they checked first every morning: blockers, sprint progress, and workload balance. Everything else was secondary. But in the old layout, these signals were buried between charts and tables that rarely got read.
Interview findings identifying the three daily priority checks
What I changed
I reorganized the dashboard into a priority-based layout. A compact status strip at the top shows blockers, velocity, and progress at a glance. Detailed views expand on click. Widgets below are customizable, so teams can configure what else appears based on their own workflow.
Three layout iterations from flat grid to status-strip design
Why it worked
The new layout gave managers what they needed in the first few seconds, and let them drill down only when something looked off. That made the dashboard useful enough to replace the Slack check-ins it was competing with.
Before-and-after of manager behavior with the new dashboard
Solution
The redesigned dashboard separated at-a-glance signals from deep-dive data, giving teams a fast overview without sacrificing access to detail.
Status strip: Project health in one row
A compact, always-visible status strip at the top of the dashboard shows blocker count, sprint progress, and velocity trend. Color-coded indicators make it possible to assess health without reading a single number.
Status strip in healthy, at-risk, and behind states
Modular widgets: Teams choose what matters to them
Below the status strip, the dashboard uses a modular card system. Teams can add, remove, and rearrange widgets for workload, activity feed, burndown, or upcoming deadlines based on what matters to their workflow.
Four different team configurations using the modular widget system
Drill-down panels: Detail on demand, not by default
Clicking any summary card opens a side panel with full context, filters, and historical data. This keeps the main view clean while still giving power users everything they need without leaving the dashboard.
Drill-down panel showing blocker details without leaving the dashboard
Results
The new dashboard replaced standups as the first thing most team leads checked each morning, and satisfaction scores improved across all pilot teams.
+35% dashboard adoption
More team leads used the dashboard daily after the redesign
-21% time to status update
Managers could assess project health faster without extra context-gathering
+19% team satisfaction
Survey scores improved on clarity of project visibility and team alignment
Dashboard adoption and status-update time improvements post-launch
Reflection
Dashboards fail when they try to answer every question at once. The most useful dashboards answer one question fast: is everything on track, or do I need to dig in?
The biggest lesson here was that adoption is not a design problem or a feature problem. It is a relevance problem. If the first thing people see is useful, they come back.
Next Project
