Kanban or list? Choosing the right view for every team

Same work, different views

One reason new work tools fail to take hold is the expectation that everyone will work the same way. Sales, engineering and finance have different rhythms, habits and needs, and forcing the same view on all of them means frustrating nearly everyone.

The good news is that a view is just a way of looking at the data. The tasks stay the same, with their owner, deadline and status; only the way they are presented changes. Choosing the right view for each context is simpler than it looks, if you start from what you need to see.

A view is just a way of looking at the data: the tasks stay the same.

When kanban works best

Kanban shows work as a flow moving through successive stages, from pick-up to completion. It is particularly well suited when tasks follow a recurring path, such as support requests, product development or order handling, and when you want to see where work is piling up.

Its great strength is making bottlenecks visible. If one column fills up while the others stay empty, the problem is obvious to everyone without any need for reports. To get the most out of it, limit the columns to genuinely distinct stages and, where possible, set a work-in-progress limit for each stage, nudging the team to finish before starting new tasks.

The most common mistake is turning the board into an archive. Tasks completed long ago should be archived; otherwise the final column grows endlessly and makes everything else harder to read.

When a list is the right choice

A list is less eye-catching but often more practical. It works well for personal work, for tasks that don’t follow a defined flow and for anyone juggling lots of short items sorted by deadline or priority. Anyone who starts the day by looking at their list knows right away where to begin.

It is also the best view when tasks have many attributes to compare, such as amounts, customers or cost centers. Sorting, filtering and grouping a list is instant, whereas on a board the same job becomes awkward.

The limitation of a list is that it hides the flow. Looking at a list sorted by deadline, it is hard to tell whether work is piling up at a particular stage or whether some tasks have been stuck for a while waiting on someone else. That is why many teams use the list for day-to-day work and the board for progress meetings.

Kanban

• Shows the flow
• Highlights bottlenecks
• Ideal for meetings

List

• Sorts by due date
• Filters and groups
• Ideal for personal work

Calendar and management views

There is also a third family of views, based on time. A calendar is indispensable for anyone managing fixed deadlines, appointments or recurring tasks, because it shows how work is spread across days and weeks and brings the crunch periods to light.

Management, finally, needs an overview more than detail: how many projects are running late, which teams are overloaded, where overdue tasks are concentrated. A progress dashboard answers these questions without forcing anyone to dig into individual teams’ boards.

A good executive dashboard shows a handful of indicators, always the same ones, and lets you drill down only when something doesn’t add up. Rather than policing individual tasks, it helps you see where to step in with more resources or different priorities.

Let teams choose

The rule of thumb is simple: define the essential data of a task in the same way for everyone, and give each team the freedom to choose how to display it. Owner, deadline, status and priority must mean the same thing to everyone; the layout on screen can vary.

In Task every team can switch from list to kanban to calendar without losing any information, and the same tasks feed the progress dashboard for those who need the big picture. That way sales can work by deadline, engineering by stage and management can see the whole, without anyone having to adapt to someone else’s method.