Task management for small teams: a practical guide
In this article
On a small team, everyone does a bit of everything. Tasks arrive through chat, email and meetings, and it is easy for something to slip. At the same time, tools built for large companies ask for setup and process that a team of five does not need.
This guide collects simple practices for managing the tasks of a team of two to ten people, without adding bureaucracy.
The most common problems
- Work is spread across many places. Some of it in chat, some in a doc and some in someone's head.
- Nobody is sure who owns what. Two people do the same thing or, worse, nobody does it.
- Priorities change without warning. The team finds out late that something urgent pushed another task aside.
- Nobody knows how much is left. Without a shared view, it is hard to tell a client or partner when something will be ready.
Principle 1: one place for all work
Every agreed task should live in one place the whole team can see. It can be a board, a list or a spreadsheet, as long as there is only one. When someone asks for something in chat, the first step is to turn it into a task in that place.
A Kanban board works well for small teams because it shows the status of every task without a meeting. If you have never used one, start with what a Kanban board is.
Principle 2: one owner per task
Every task needs one owner, even when several people work on it. The owner does not have to do everything, but they make sure the task moves and speak up when it gets stuck.
Write concrete tasks that start with a verb and that someone can finish in a few days. "Prepare the proposal for client X" works better than "Client X".
Principle 3: visible priorities
On a small team, the order of work changes often. To keep everyone aligned on what comes first:
- Sort the to-do column by priority. Whatever is at the top gets done first.
- Use a priority label only for exceptions. When every task is marked urgent, the label stops helping anyone decide.
- Add dates only when they exist. A real deadline, like a launch or a client meeting, helps. A made-up date adds noise.
Principle 4: less work in parallel
With few people, every open task weighs more. If each person has five tasks in progress, all of them move slowly. Limiting work in progress to one or two tasks per person helps you finish sooner. We explain it in detail in our guide to WIP limits.
Principle 5: a short weekly review
A fifteen to thirty minute meeting each week is enough to keep the board current. A simple agenda:
- Review what is done. Move finished work to "Done" and close what no longer applies.
- Review what is stuck. Talk about tasks that have not moved for many days.
- Order what comes next. Agree on next week's priorities and assign owners.
How to share progress with clients
Many small teams work for clients who want to know how their project is going. Instead of writing email updates, you can give them read-only access to the board. They see progress whenever they need to, without being able to move or edit cards.
A tool sized for a small team
Onion is a free Kanban board built for small teams. It keeps work on boards with assignees, dates and tags; it has a My tasks page with what is on your plate across your boards; and it lets you invite your team as editors and clients as viewers. If you use Trello or Notion today, see how Onion compares with Trello and Notion.
Create your first board for free at app.getonion.app.