# Team Activity Dashboard UX Research

## Goal
Design a dashboard that is operational first: show the current project, each agent's contribution, token consumption, and the current workflow state without overwhelming the user.

## Recommended status categories
Use a compact fixed vocabulary:
- researching
- backlogging
- progressing
- reviewing
- testing
- waiting for decision
- done

## Best chart choices
- Stacked horizontal bars for project progress by state
- Ranked bars for per-agent contribution
- Small token trend sparklines if/when live history exists
- Status chips for quick scanning
- Table for exact numbers and task text

## Information hierarchy
1. Project banner
2. KPI strip
3. Contribution / token charts
4. Agent activity table
5. Workboard / recent events

## UX notes
- Keep the chart layer readable and operational.
- Use color chips sparingly so status still scans fast.
- Put exact values in the table, not in charts.
- Make the dashboard feel alive by refreshing from a single snapshot JSON.

## V1 recommendation
Start with a static HTML page that fetches `data/team-status.json` and refreshes every 15 seconds. That keeps the implementation simple while leaving room for a live telemetry bridge later.