Dashboards: Team Hub & Personal Dashboard
Two dashboards on the same platform, one for managers to see their team and one for each person to focus on their own work. I designed both solo, in parallel.
- Role
- Senior Product Designer
- Timeline
- Platform
- Web (Desktop)
- Team
- Solo designer · engineering team
Overview
ecoPortal needed people to understand their workload quickly, both from the manager's side and from the side of the person doing the work. I designed two complementary dashboards. Team Hub is the manager's view of team activity, tasks and performance. Personal Dashboard is each person's own space, with their tasks, actions and active pages.
The problem
ecoPortal is an incident management platform, but incidents don't live alone: they create tasks, actions and assignments that need to be tracked to the end. As the platform matured, two needs appeared that no screen covered.
Team leads and managers wanted their team's workload in one place: how many tasks were open, which actions were overdue, how long tasks took on average and what had been created or assigned lately. The information existed, but it was spread across several screens.
Individual contributors wanted a personal space to see their own tasks and actions at a glance, add items quickly, check their active page and jump to the task and action managers without hunting around.
How do we design two dashboards that feel like one product, with the same visual language and tokens, for such different mental models?
The challenge was scope and parallel work: two dashboards, different goals, one design system and one sprint cadence.
Briefing
The briefing treated both screens as a single initiative. The product team already had user research: managers tracked status in spreadsheets and morning standups because the platform didn't bring team data together, and individual contributors started their day by opening four or five tabs to figure out what needed attention.
Key points from the briefing:
- Team Hub scope: real-time task and action counts, trend charts, duration metrics, overdue flags, recently created items and assigned pages, all filterable by team member (People Filter)
- Personal Dashboard scope: personal task and action counts, quick creation of tasks and actions, active page tracking, shortcuts to the task and action managers, and a comments view
- Shared constraint: both dashboards had to work across several breakpoints (1920, 1200, 800 and a compact one)
- Shared foundation: both screens would use ecoPortal's tokens (Tokens Auto Desktop, Primitives Auto ecoPortal Default) and had to look like siblings, not separate products
Questions set in the briefing:
- What's the minimum widget set for each dashboard, and what waits?
- How does Team Hub's People Filter act on each widget? Do all widgets filter, or only some?
- In the Personal Dashboard, how do the Opt In/Opt Out settings relate to the dashboard itself?
- How do we design empty and loading states per widget instead of per page?
Ideation & brainstorming
With both dashboards in scope at once, exploration focused on two things: information architecture (what goes where, in what order) and widget patterns (how each data block communicates what it shows).
I looked at dashboards in tools like Jira, Asana and Linear, especially how they mix counts, charts, lists and tables on one screen without overwhelming people.
The main hypotheses:
- Team Hub needs a clear reading order: summary numbers first (where do things stand?), then charts and tables (what's the trend, what's the detail?). A widget that answers "how many?" should read in under 3 seconds.
- In the Personal Dashboard, the main job is doing, not reading. Creating a task or action had to be one click away from anywhere on the screen.
- Skeleton loaders and empty states aren't a detail. On a dashboard they're often the first thing people see, especially on first login, so they need to feel designed and tell you something.
- Team Hub's People Filter had to float and stay visible, instead of being a page filter that makes you scroll back to the top.
Before any visual work, I made a flow map for each dashboard, defining widget hierarchy, how filters interact and which states each widget needed.
Lo-fi usability testing
For dashboards, lo-fi testing looks at layout comprehension, widget discoverability and how fast people finish tasks. I tested with two groups: team leads for Team Hub and individual contributors for Personal Dashboard.
In Team Hub, I tested:
- Whether people found the most critical widget within 10 seconds of looking at the screen
- Whether the People Filter was understood as a filter that affects every widget
- Whether the charts (Tasks Chart and Actions Chart) were read correctly without tooltips
- Whether hover on the Avg Task Duration widget and the Overdue Actions Table gave enough context
In Personal Dashboard, I tested:
- Whether people found and used Add New for tasks and actions without instructions
- Whether the Active Page widget made sense (what it shows and why it's there)
- Whether the shortcuts to Action Manager and Task Manager were recognized right away as navigation
What I found:
- Team Hub: the Summary Table needed tabs (Summary, Actions and other views). Without them, people expected all the data at once and got lost.
- Team Hub: hover on Avg Task Duration was the most used element in the test. People wanted more detail there than the first design showed.
- Team Hub: testers noticed and liked the "Loading time too long" state. They were used to dashboards that spin forever, so a clear message that it's taking a while, with a retry option, felt considerate.
- Personal Dashboard: Add New for tasks needed a visible stepper. Not knowing how many steps the flow had made people hesitate.
- Personal Dashboard: Opt In / Opt Out was confusing inside the dashboard. People expected it in settings, not on the home screen.
Flow refinement
With testing done on both dashboards, I revised everything before hi-fi.
Team Hub changes
Summary Table with tabs: I added tabs to the widget (Summary and Actions) so it could show more than one view without growing taller.
Richer Avg Task Duration hover: the hover got more contextual data. The Hovers group in the final design shows every variation used on the widget.
Manager dashboard variations: testing showed that managers with different team sizes needed different widget arrangements, so I added a set of Manager Dashboard Variations to cover them.
Floating People Filter confirmed: the filter stays pinned to the top of the screen while you scroll. I documented two states: Floating toolbar (default) and People filter (open).
Loading per widget: each widget got its own loading state instead of a page spinner: Open Tasks, Actions, Overdue Actions, Assigned Pages, Recently Created and Avg Task Duration.
Personal Dashboard changes
Stepper in Add New: the task and action creation flows got a stepper. It was the change with the biggest effect, because it removed the hesitation and made multi-step creation predictable.
Opt In / Opt Out moved: it left the widget area and got its own section, apart from the personal workspace. I also documented it as an Org Settings item.
Shortcuts to Action Manager and Task Manager: they became shortcut cards with clear affordance, not just links. In testing, people already used them as navigation points.
Hi-fi design
With both sets of flows revised and validated, I moved to hi-fi: every widget, every state and every breakpoint for both dashboards, inside ecoPortal's design system.
Team Hub
Main screens: three states. Default (full dashboard with data), Filtered (People Filter on, widgets filtered) and Release Version 1 (the launch state, documented as a reference for engineering). Manager Dashboard Variations cover the different widget arrangements.
Widgets:
- Floating Bar: the People Filter, always visible at the top. States: Floating toolbar (closed) and People filter (open).
- Summary Table: task and action summaries in tabs (Summary and Actions).
- Avg Task Duration: a metric with a detailed hover.
- Overdue Actions Table: a list of overdue actions with status indicators.
- Team Tasks and Actions: one container holding the Tasks Chart and the Actions Chart.
- Tasks Chart: bar/area chart of open tasks over time.
- Actions Chart: bar/area chart of actions over time.
- Recently Created: a list of the most recently created items.
- Assigned Pages: a list of pages assigned to team members.
States per widget: loaded, loading, skeleton loader, skeleton per breakpoint, its own empty state and "loading time too long."
Breakpoints: 1920, 1200, 800 and a compact one, with widgets reflowing at each size.
Team Hub empty state: two variants, one for a hub with no data yet (first use) and one for filters that return nothing.
Personal Dashboard
Main screen: the Personal Dashboard with data loaded, a donut chart showing how many personal tasks are done and a compact list below.
Widgets and flows:
- Add New, Tasks: multi-step task creation with a stepper, with variants for the different input states and steps.
- Add New, Actions: the matching flow for actions, with progress shown in a donut chart.
- Shortcuts to AM and TM: cards that open Action Manager and Task Manager.
- Comments: a comment stream, with a stepper to move between threads.
- Active Page: shows the currently active page in a compact dark panel.
Empty states: Actions (no actions yet), Comments (no comments) and Active Pages (no active page).
Opt In / Opt Out: a section to turn the Personal Dashboard itself on or off, tied into Org Settings for organization-level configuration.
Breakpoints: several sizes, always with the donut chart and the main widgets adapting to the available width.
Handoff & design QA
Both dashboards were handed off and reviewed alongside the implementation sprints. I owned design QA for both.
The handoff had full Figma annotations for every widget (spacing, tokens, states and interactions), responsive behavior for every breakpoint and a state map per widget with every possible transition. We held three handoff sessions: one for Team Hub, one for Personal Dashboard and one just for the states both share (loading, skeleton and empty).
What QA caught:
- Team Hub: the People Filter scrolled with the page instead of staying fixed
- Team Hub: row hover was missing on the Overdue Actions Table
- Team Hub: Summary Table tabs switched without the specified animation
- Personal Dashboard: the stepper didn't advance correctly on step 2 of Add New for tasks
- Personal Dashboard: donut chart segment colors didn't match the tokens in the loaded state
- Both: skeleton loader animation timing differed between widgets
Everything was fixed before each dashboard went live.
Results & learnings
Both dashboards became the home screen for their audiences. Team Hub is now the default landing page for team leads and managers, and Personal Dashboard is the default for individual contributors.
What worked:
- Designing both at once forced a shared visual language early. They couldn't drift apart, because every decision was made with both screens in view.
- Per-widget loading, skeleton and empty states made the product feel much more polished. A dashboard that fails gracefully earns more trust than one that just spins.
- The floating People Filter was Team Hub's most praised feature after launch, because people could filter without losing their place on the page.
What I'd do differently:
- Test one dashboard at a time. Running both tests together blurred some results and made it harder to tell which screen an insight belonged to.
- Pin down the product definition of Opt In / Opt Out before designing. Not having it caused several avoidable revision rounds.
- Think about mobile from the start. It was out of scope, but requests came in right after launch, and a responsive strategy from day one would have saved a separate design cycle.
Next steps: notifications in Team Hub (an alert when a widget crosses a threshold), customizable widget order in Personal Dashboard and one notification center connecting both screens.