Most team leads have lived through this. You set up a Kanban board because everyone says boards make work visible. Three weeks later, one column holds forty cards, nobody drags anything, and the real plan lives in someone's head.

Or the opposite happens. You keep a long task list, and the urgent work hides between update footer copyright and decide next quarter's roadmap. Nobody can tell what is actually moving.

The problem is rarely the tool. One view is being asked to serve every kind of work. Boards and lists answer different questions. If you pick the view based on the question your team asks most often, both become useful again.

Why one view stops working

A board answers one question well: where is each piece of work right now? A list answers a different one: what is there to do, and in what order?

Trouble starts when the work doesn't match the question the view is built to answer. Each mismatch produces its own symptoms.

A board is the wrong fit when:

  • Most cards sit in To do for weeks, so the board is really a list turned sideways.
  • Items don't share the same steps, so people invent extra columns or ignore the ones that exist.
  • The order in which things must happen matters more than their status, and the board can't show that sequence.

A list is the wrong fit when:

  • Work passes between people, and you keep asking who has it now.
  • Things get stuck waiting for review or approval, and the list doesn't make the waiting visible.
  • Your weekly check-in turns into reading every line aloud to find out what changed.

If you recognise these patterns, the view isn't broken. It is simply the wrong view for that kind of work.

Work that flows: use the board

A board fits best when items repeat the same journey. Each piece of work passes through the same steps, hands over between people, and finishes. The useful information is how many items sit at each step and where they pile up.

Typical examples include:

  • Content production, from draft to edit to publish.
  • Bug fixing, from reported to fixed to verified.
  • Design or creative requests that go through a client review.
  • Support or change requests from an ongoing client.

In Tilvin, the Kanban board shows a project's tasks as columns, one for each step in the project's workflow. Moving a card between columns changes its status. The columns come from the process the project uses, which administrators set up as ordered steps. Before you open the board, make sure the workflow describes how the work really moves.

Take a six-person design agency handling a stream of client requests. Its steps might be Brief, In design, Client review, Revisions and Done. When five cards gather in Client review, the board tells the team lead something a list wouldn't: the bottleneck is waiting on the client, not the designers. The right move is to chase feedback, not push the team harder.

A few habits keep a board honest:

  • Keep the steps few. Four to six columns is usually enough. Every column should mean that a specific person does something.
  • Watch the piles, not the cards. Look for columns that grow from one week to the next.
  • Move cards when the work moves. If dragging a card feels like admin, you probably have too many columns.

Work that is planned or varied: use the list

A list fits best when sequence and dates matter more than status. It also suits projects made of many small, one-off items that don't share a process. You don't need to know what stage book the venue is at. You need to know it happens before send invitations.

Typical examples include:

  • A website launch with a run of pre-launch checks.
  • Onboarding a new client.
  • Preparing an event or a workshop.
  • Internal admin and housekeeping.

In Tilvin, tasks live in task lists. Each task carries a type, priority, assignees, a status, start and end dates, an estimate and progress. Group the lists by phase or by area, such as Discovery, Build and Launch, so that each list reads as a short, ordered plan. If dates and estimates feel like overhead, this guide to minimum planning for small projects covers how little you need to add for the list to be useful.

When you want to see those dates laid out over time, the project Gantt chart in Reports turns the same start and end dates into a timeline. That view helps when you are checking whether phases overlap or a deadline is realistic.

When a project needs both

Many real projects mix both kinds of work. A website build has planned phases that suit a list. Once testing starts, it also produces a stream of bugs that suit a board. A retainer client sends ad-hoc requests that flow, but also books a quarterly campaign that needs a plan.

The board shows the project's own tasks, so you are not keeping two copies of the work. You are choosing which lens to look through. Some practical ways to handle the mix:

  • Use task types. Marking items as a task, a bug or a future item lets you tell the planned work apart from the incoming stream, even when they sit in the same project.
  • Park future items deliberately. Ideas that aren't committed yet don't belong in the first column of your board, where they make it look busier than it is.
  • Break down big cards. If one card on the board hides a week of work, split it into sub-tasks with their own assignees and status. This article on sub-tasks and checklists explains when that helps and when it only adds noise.

A quick test for any project

If you're unsure which view to lead with, ask yourself three questions:

  1. Do most items go through the same steps? If yes, lean towards the board.
  2. Does the order or the date of items matter more than where they are? If yes, lean towards the list.
  3. What will you ask at the weekly check-in: what's stuck? or what's next? The first suggests the board, the second the list.

Choose one primary view per project and tell the team which one it is. Everyone can still open the other view. The point is that status updates and conversations start from the same place.

Practical next steps

You don't need to reorganise everything at once. Try this over the next fortnight:

  1. List your active projects and write down, for each one, the question you most often need answered.
  2. Pick a primary view for each project using the test above, and tell the team which view to update.
  3. Trim the workflow for any project that leads with the board, so every column means someone acts.
  4. Agree one rule for updates. For example, cards move when the work moves, or task status and progress get updated before the weekly check-in.
  5. Review after two weeks. If a board has a stagnant first column, or a list keeps prompting who has this?, switch the primary view.

If you're setting this up in Tilvin, the features overview shows how task lists, workflows and the Kanban board fit together within a project. Start with one project, get the view right, and let the team feel the difference before rolling it out further.