Monday morning, three people each know part of what has to happen this week. One task sits in an email, one in a chat thread, one on a sticky note. On Wednesday a customer asks about something promised on Monday, and nobody can say who has it.
Small teams rarely need a project tool for this. They need one short list for today, and three agreements about how it is used. This article describes a version you can start tomorrow with a shared document or a simple board.
Two lists, not one
Most task lists fail because they mix two different things: what we might do someday and what we are doing today.
- The backlog holds everything: ideas, requests, small fixes, things waiting for someone else. It can be long. Nobody is expected to read it every day.
- Today's list holds only what this team commits to finish today. It is short and visible to everyone.
If you keep only one list, it grows until people stop trusting it. Splitting it lets the backlog be messy without making the day messy. For planning beyond a single day, a weekly capacity check is a better tool.
Who adds tasks
Open writing access sounds friendly and quickly becomes a dumping ground. A better rule has two parts.
- Anyone can propose. A task goes into the backlog, or into a shared inbox, with one line: what, for whom, and by when if there is a real date.
- One person decides what lands on today's list. In a team of three to eight, this is usually the owner, the team lead or whoever talks to customers most. Name the person, and name a deputy for days off.
This is not about control. It is about having one place where the question "can this fit today?" gets an answer. Without it, every request is silently accepted by whoever read it first.
Each task on today's list also needs exactly one owner. "Marketing" is not an owner. "Petra" is.
How to rank
Ranking does not need a scoring model. Three questions in a fixed order are enough.
- Is it promised to a customer for today or tomorrow? These go first.
- Is someone else blocked until it is done? These go second, because a small delay for you becomes a larger one for a colleague.
- Everything else. Within this group, pick what removes the most risk or the most repeated work.
Write the rule at the top of the list so it is visible. When two tasks compete, people can apply it without asking.
One practical addition: mark at most one task per person as "first". When everything is urgent, nothing is. If the person deciding cannot say which one comes first, that is a signal that the day is overloaded, not that the ranking rule is wrong.
How long the list should be
Count the realistic working hours, subtract meetings and interruptions, and you will usually find that four to five hours are available for focused work. A common rule of thumb is about three tasks per person. A fourth is allowed only if it is small.
Leave room for the unexpected. A list that is planned to the last minute fails by lunchtime, and a failed list teaches the team to ignore it. If you also protect uninterrupted blocks, as described in protecting focus time in a small team, say which tasks belong in those hours.
When it gets reset
This is the part most teams skip, and it decides whether the list stays honest.
Every morning, in a five-minute check, go through yesterday's list line by line. Each unfinished task gets one of three outcomes:
- Finish today. It stays, and it is ranked again with the rule above.
- Back to the backlog. It is not today's work after all. Note why in a few words.
- Drop. The need disappeared. Remove it, and tell whoever asked.
What must not happen is a silent carry-over. A task that has moved from day to day for a week is not a task, it is a decision that nobody made. When a task returns to the list a third time, ask what is stopping it: unclear scope, missing input, or low priority. Each has a different answer.
Then close the loop at the end of the day with two minutes: tick what is done and tell the person who asked. That is all the "reporting" a small team needs. If you want a record of larger choices made along the way, keep a one-page decision log rather than extending the daily list.
What to avoid
- Sub-tasks and tags in the first week. Start plain. Add structure only when a real problem demands it.
- Using the list as a status report for management. The moment people write for an audience, they stop writing what is true.
- Adding tasks during the day without removing one. If something urgent arrives, ask what moves out. This keeps the cost of interruptions visible.
- Long descriptions. A task title should say what finished looks like, for example "Send revised quote to Novak" rather than "Quote".
A simple start
- Create one shared page called "Today" and one called "Backlog".
- Write the ranking rule at the top of "Today".
- Name the person who decides what goes on the list, and a deputy.
- Hold the five-minute morning reset for two weeks.
- After two weeks, look at how many tasks were finished the same day. If it is fewer than two thirds, the list is too long; shorten it before you change any tool.