Teamboard for Transparent Collaboration

Why it matters: in a 12-person engineering team, Kanban shows "28 tasks in progress", but it hides that 14 of them sit on one person. Teamboard exposes that asymmetry in 2 seconds — you can literally see whose column is short and whose runs off the screen.

A separate Unassigned column holds tasks without an owner. Treat it as your visual penalty bar: the longer something rots there, the longer the manager hasn't decided who owns it. A healthy team keeps Unassigned at 0-3 cards. If it's 20+, you're hoarding work instead of planning it.

Rule of thumb: if the gap between the most-loaded and least-loaded person is ≥3 tasks, intervene. Not necessarily by reassigning — sometimes asking "Ivan, are all 14 actually active, or are 5 waiting on something?" is enough. Often half flip to "Waiting" status and the column shrinks without anyone moving a card.

The "84% capacity" footer indicator aggregates the whole team: total active tasks vs declared capacity (e.g. 2 tasks per person). If your team consistently runs at 110%, you're planning more than the team can deliver and deadlines will slip.

If you care more about where the task is in the process (Backlog → Review → Done) than who's pulling it, teamboard is worse than Kanban. Don't swap one for the other; add teamboard as a second view on the same task set.

Management overview across many projects isn't teamboard, it's a dashboard with a "workload per assignee" widget. Dashboards aggregate numbers across projects, teamboard shows the detail inside one. Dependencies and deadlines (who's blocking whom, when something ships) → Gantt, not teamboard.

Larger teams often run all three: Kanban for daily work, teamboard for rebalancing and 1-1s, dashboard for management reviews. In Easylim it's the same task set, three views — no migration.