Priya runs operations for a twenty-five-person agency, and every Monday she needs the same nine tasks to answer three different questions. In standup, the team needs to see what's stuck, so she wants a board. For the client update at noon, she needs a clean, sortable list she can scan top to bottom by due date. And for her own planning, she needs to see the whole week laid out so she can tell if Thursday is overloaded. On most teams that means three exports, three copies, and three chances for one of them to go stale before the day is over.
The mistake is treating "which view" as a permanent choice
A lot of teams pick one view for a project and stick with it, usually a board, because it's the one that photographs well in a deck. But a board answers one specific question well — what's stuck, and where — and answers most other questions badly. The fix isn't finding the one perfect view, it's not having to choose, because the underlying task list doesn't change depending on how you're looking at it.
Board: for "what's stuck"
A Kanban board is built for a status conversation. Columns are stages, cards move left to right, and a glance tells you where the pile-up is. It's the right view for a standup, a client review column, or any moment where the question is about flow rather than detail. A work-in-progress cap on a column turns "we're behind" from a feeling into a visible, counted fact.
Table: for "scan, sort, compare"
The same list as a table is built for a different question: which fifty rows match this filter, sorted by this column. It's the view for a client report, a QA pass, or anything where you need to compare fields across many tasks at once — due date, priority, a custom currency field tracking budget. A board makes that kind of scanning slow because it hides most of a task's fields behind a card face; a table puts them all in a row.
Calendar: for "what's due, and when"
Neither a board nor a table answers "what does this week actually look like," because neither one is organized by date. Calendar view is. Drag a task to a new day and it's rescheduled, no separate step, no risk of the calendar and the tracker disagreeing because they're the same data rendered two ways.
Timeline and workload, for the bigger questions
Zoom out further and two more lenses answer questions a single week can't: a timeline lays tasks against real dates and lets you draw a dependency between two of them, so you can see what slips when something upstream slips. Workload does the same for people instead of tasks — group by person, priority, status or tag, set a weekly capacity, and see who's overloaded over the next 7, 14 or 30 days, before it becomes a missed deadline instead of a heads-up.
The point isn't the view, it's that switching is free
What actually saves Priya's Monday isn't that a board or a table or a calendar exists, it's that they're all the same nine tasks, one click apart. Nothing gets rebuilt, re-filtered from scratch, or re-exported to get from the standup view to the client-report view to the planning view. The underlying question — what's true about this work right now — has one answer; the view is just which part of that answer a given hour needs to see.