Organizing Team Tasks: List, Board, or Project Plan Compared

Why tasks get lost in a team

In small companies, tasks come up everywhere: in a customer conversation, in an email, in the hallway, in the weekly meeting. Some end up on a note, some in an inbox, some in the head of a single person. As long as the team is small and everyone sits in the same room, this hardly shows. With every new person it becomes harder to say who is working on what and what has been left lying.

The usual reaction is to look for a tool. The choice is then often made by feature list or recommendation, not by the type of work. That is why this article asks a more precise question: which way of organizing tasks, list, board, or project plan, fits which kind of work in a small team? To answer it, we first clarify the three terms, then present a thinking model from coordination research, look at the findings, weigh two perspectives, and finally derive a decision rule.

A team rarely loses tasks because a tool is missing, but because nobody has clarified how the tasks depend on one another.

What are a task list, a board, and a project plan?

A task list is the simplest form: each task is on one line, with a responsible person and a date. It answers the question of who does what by when. It says nothing about how the tasks are connected.

A board arranges tasks as cards in columns that represent the path of the work, such as open, in progress, waiting, done. The best-known form is Kanban. Kanban comes from production control at Toyota. All tasks appear as cards on a board, the columns represent the path of the work, and a limit on parallel work, the WIP limit, ensures that things get finished before new ones start. As the article on OKR, Kanban, and weekly planning shows, Kanban fits ongoing work with many small items above all.

A project plan arranges the steps of a project in time. A project is a one-time undertaking with a fixed result, a beginning, and an end. The plan shows milestones, sequences, and deadlines, often as a bar chart, also called a Gantt chart. A milestone is a verifiable intermediate result, not an activity. What such a plan looks like on one page is described in the article on project planning in small teams.

The thinking model: coordination as managing dependencies

Thomas Malone and Kevin Crowston (1994) brought together insights from computer science, organization theory, economics, and psychology into a coordination theory. Their core statement is: coordination is managing dependencies among activities. Where there is no dependency, there is nothing to coordinate. Where there is one, the right form depends on what kind it is.

The authors distinguish several basic types. Three of them are useful for a small team. First, shared resources: several tasks need the same person, the same vehicle, the same time. Second, handoffs between producer and consumer: the result of one step is the starting point of the next, for example from on-site measurement to costing. Third, sequences and simultaneous deadlines: one step may only begin when another is finished, or several things must come together by the same date.

An everyday analogy makes the difference tangible. A family's shopping list is a list: all that matters is that someone gets each item. A house move is a project: the kitchen can only be taken apart once the van is there, and the van comes on a fixed day. Nobody would plan a move with a shopping list, and nobody needs a bar chart for the weekly groceries.

What studies show about task organization in small companies

There are few studies on how small companies actually plan their projects. Tasevska, Damij, and Damij (2014) surveyed 30 small and medium-sized companies in North Macedonia about their projects for introducing enterprise resource planning systems. The companies did plan: they described the business case, defined the scope, and set a baseline plan. However, they did not use specific planning tools such as bar charts or a breakdown of work packages. Risk planning was the least practiced. The study is small and limited to one type of project. But it fits a pattern many owners know: the plan exists, just not in a place everyone can see.

A case study from Mexico offers a hint about the effect of visible task organization. Jiménez-Martínez, González-Mosqueda, Meza-Ramirez, and colleagues (2026) followed a sports jersey manufacturer with 16 employees that organized its five production stages with elements of Scrum and a digital board. The diagnosis beforehand cited inadequate task planning, poor internal communication, and an uneven distribution of work. After the change, the authors reported 43 percent less downtime and 43.7 percent better internal communication.

Both findings should be read with caution. The Mexican study is a single case study without a comparison group, the data come from a survey of the entire workforce at one point in time, and the board and Scrum were introduced together. Which part of the effect is due to the board cannot be derived from it.

Two further findings from other articles help put this into context. Research on parallel project work shows, as described in the article on Kanban in sales: up to a point it increases performance, beyond that the switching costs more than it brings. That argues for a limit on parallel work, as a board allows. And Masicampo and Baumeister (2011) showed that a specific plan for an unfinished task is enough to end the intrusive thoughts about it. A task that is recorded with a person and a date in a shared place therefore also relieves the mind.

One tool for everything or one form per kind of work? Two perspectives

There are two readings of how a small team should organize its tasks. The first says: one place for everything. All tasks, whether day-to-day work or projects, are in a single list or on a single board. Simplicity speaks for this. Nobody has to think about where a task belongs, and nobody misses anything because it sits in another system.

The second says: one form per kind of work. Day-to-day work runs on a board, projects get their own plan, small personal items stay on one's own list. Coordination theory speaks for this: a board shows bottlenecks but not sequences. A project plan shows sequences but not bottlenecks.

I consider a combination of both readings the most sustainable solution: one shared place, but several views. The tasks are in one location; the board and the project plan are two perspectives on the same entries. Many current tools allow this. Where that is not possible, a clear rule is better than a second system without a rule. This matches the recommendation from the article on OKR, Kanban, and weekly planning: teams of up to ten people usually manage with weekly planning and one shared board. Projects with fixed deadlines are added as a separate view.

Decision rule: which form for which team

A simple sequence follows from the thinking model and the findings. Here it is called the dependency test, and it takes a team less than an hour.

1. Collect one week of tasks

   Write down all the tasks the team completed or started last week. Twenty to forty entries are typical for a small team.

2. Determine the dependency of each task

   Mark each task: independent, handoff to another person, or part of a project with a deadline.

3. Read the main emphasis

   If handoffs dominate, a board is the basic form. If independent tasks dominate, a shared list is enough. If there are a few projects with deadlines, only these get a project plan.

4. Set one place

   All forms are in one place that the team opens every day. Tasks given verbally or by email are entered there before anyone works on them.

5. Check after four weeks

   Count how often someone had to ask about the status of a task. This number should fall.

The status question is a useful measure because it can be counted without effort and measures exactly what good task organization is supposed to prevent. Who is responsible for a task and who is only informed can be clarified for handoffs across several areas with the RACI matrix. For choosing a specific tool, the framework from the article on project management tools compared helps.

One example of a platform that combines tasks, knowledge, and goals in one place is quik OS, a tool from a business partner of Owners Council. Whether this or another tool fits, you check with the same questions: does the team open it every day? Can list, board, and project plan be shown as views of the same tasks? Can a new colleague find within a minute what they are working on this week?

Where the forms reach their limits

None of the three forms replaces the decision about what takes priority. A board shows that twelve items are piling up in front of costing. It does not say which one gets processed first. A project plan shows that the trade fair deadline is shaky. Whether a customer order has to wait for it is decided by a person. If you want to set priorities in the team deliberately, the article on weekly team planning provides a fixed meeting for it.

The evidence also has limits. The studies cited look at few companies or laboratory situations. They do not prove that a particular tool increases revenue.

Conclusion: which way of organizing tasks fits which team?

The opening question was
way of organizing tasks fits which kind of work. The answer follows from the type of dependency. Independent individual tasks need a shared list with a person and a date. Work with many handoffs needs a board that makes bottlenecks visible and limits parallel work. One-time projects with fixed deadlines need a project plan with milestones. Most small teams have all three kinds, but in very different proportions.

As shown, the few studies mainly show that visibility and a shared place help, not that one particular form is superior. For the small company this means: one place, a board as the basic form for day-to-day work, and a project plan only where a deadline requires it. The right tool is then the one that reflects this order without detours.

The next step

1. Collect all of last week's tasks with the team on one page.
2. Mark each task as independent, handoff, or part of a project with a deadline.
3. Use the main emphasis to set the basic form and choose a single place for it.
4. Agree on the rule that tasks given verbally are entered there before anyone works on them.
5. Starting Monday, count the status questions about tasks for four weeks.

After four weeks, the tally shows whether the new order holds.