compare
There is a version of this search that has a clean answer. One person, one list, everything in it, reviewed on Sunday evening. For that, the roundups are reliable: pick whichever of the well known apps has the keyboard shortcuts that suit you, use it for two weeks, and stop shopping.
This article is for the other version. The list started as one person's, then a colleague was invited to a project, then two more, and now five people are assigning each other tasks inside an app that was designed around one owner. It still mostly works. The parts that do not work fail quietly, which is what makes them expensive.
It is worth being precise about the strength, because the strength is real and easy to throw away.
A to do list app optimises for two moments. Capture, meaning the two seconds between remembering something and it being written down somewhere trusted. And review, meaning the daily pass where a person decides what today looks like.
Everything good about these apps serves those two moments. Typing a line with a date inside it and having the date parsed out. A global shortcut that opens an input box over whatever is on screen. A Today screen that hides everything not due. A Sunday review that takes six minutes. None of this is decoration. A person who captures reliably and reviews daily is more effective than a person with a better system and no habit.
This also explains why these apps feel so much lighter than project tools. They are not managing the work. They are managing one person's attention, which is a smaller problem with a cleaner solution.
The failure is not that the app is weak. It is that shared work asks a different question, and the app has no way to answer it.
A personal task has two states: open and done. That is sufficient when the only person who can act on it is the person reading the list.
Shared work has states in between that matter to somebody else. Written but not reviewed. Reviewed but not approved. Sent to the client and waiting. Blocked on a file that has not arrived. In a list app, all four of those look identical, which is to say they look open. So the question "is this actually moving" cannot be answered from the list, and it gets asked in chat instead.
This is the failure that shows up first and gets excused the longest, usually by adding labels that mean stages. Labels work until there are eleven of them and three mean nearly the same thing.
Most list apps added sharing by allowing an assignee on a task. This looks like the same feature a team tool has and behaves differently in one important way.
In a personal list app, a task assigned to someone appears in their list, and their list is private. Nobody can see whether it is progressing, whether it was opened, or whether they have thirty other things that week. Assignment becomes a send operation, like email. The sender's list is now clean and they have no idea what happened next.
The result is a team where five people each believe they have handed work off and nothing has arrived.
A list app can show what is due today. What it cannot show is next Tuesday from the team's point of view: three deliverables, two of them depending on one person, one of them waiting on a client who has not replied.
So somebody builds that picture by hand, in a spreadsheet or a document, and updates it on Friday afternoons. Within a month the spreadsheet is the real plan and the list app holds a subset of it. Two records that disagree are worse than one record that is incomplete, because now nobody knows which to trust.
On a shared task, the question "why is this the way it is" gets asked repeatedly. The answer lives in a chat thread from three weeks ago, or in a reply inside an email thread that only two people were on.
List apps have comments, but they are thin by design, because a personal task does not need a discussion. When shared work needs one, the discussion happens somewhere else, and the task becomes a title pointing at nothing. This is the failure that costs the most over a year and is the hardest to notice, because each individual instance is just one person asking one question.
Free tiers are worth reading before a team adopts anything, because they encode what each vendor thinks the product is for. These figures come from each vendor's own pricing page in September 2026.
| Tool | What the free plan gives | What the next step up is for |
|---|---|---|
| Todoist | Beginner plan: 5 personal projects, 3 filter views, 1 week of activity history, 5 MB per file upload | Pro raises personal projects to 300, filter views to 150, and gives full reporting history. A shared team workspace and team projects are on the Business plan |
| Trello | Up to 10 collaborators per Workspace, up to 10 boards per Workspace, unlimited cards, unlimited activity log | Standard removes the board limit and adds custom fields. Timeline and calendar views are on Premium |
| Asana | Personal plan: 2 users, unlimited tasks and projects, list, board and calendar views | Starter raises the seat count and adds the timeline view and reporting |
| Slack | 90 days of message history, up to ten apps | Pro removes the history limit. Slack holds conversation rather than tasks, so it sits beside a task tool rather than replacing one |
Prices exclude tax and plan contents change, so the vendor's page is the only reliable source.
The Asana row is the odd one and worth understanding, because it caps people at two while giving away projects and views without limit. That is a free tier designed to be outgrown on the first day a third person joins, which is a legitimate choice and a very different bet from a board tool handing out ten collaborators. Read together, the three rows show that the word free means a restriction on people, on containers, or on memory, and the only useful question is which of the three the team will hit first.
Two things are visible in that table. The list app's free tier limits how much one person can organise, and puts shared team space behind its top plan. The board tool's free tier limits how many boards exist and hands out collaborators freely. That difference is the product philosophy, stated in pricing. A list app expects to be bought by a person. A board tool expects to be adopted by a team.
The activity history row is worth a second look. One week of history means that in eight days there is no record of what changed. For a personal list that is irrelevant, since the person remembers. For shared work it is the difference between a record and a rumour.
The instinct at this point is to replace the list app. That is usually the wrong move, and it is why so many teams cycle through tools without improving anything.
The arrangement that holds is two layers with one rule.
The bottom layer is the shared board. One place where every piece of work that involves more than one person exists as a card, with a stage, an owner and a date. This is the only record anybody else is allowed to rely on. Stages are agreed once and not negotiated per project.
The top layer is each person's own list. Whatever app they already like. It holds their own reminders, their errands, the follow ups that belong to nobody else, and their plan for today.
The rule is that nothing lives only in the top layer if someone else is waiting for it. A personal list can hold a copy, a note, a nudge. It cannot hold the truth.
This sounds like duplication and is not, because the two layers answer different questions. The board answers "where does this stand", which is a question other people ask. The personal list answers "what comes next for me today", which is a question only the owner asks. One record per question is the right number.
Setting the bottom layer up is a smaller job than it sounds, and it goes wrong when it is treated as a migration. Nothing from the personal lists needs to be imported. The only items that belong on the board on day one are the things currently in flight that somebody else is waiting on, which for a team of five is typically fifteen to thirty cards and an hour of work. Anything finished stays where it is, and anything nobody else depends on stays where it is too. Teams that try to move a year of history first spend a weekend on it and then abandon the board, because the first thing anyone sees on opening it is a wall of dead cards.
Making the bottom layer work needs three things and no more than three. Stages that mean the same thing on every board. One owner per card, never two. A date on anything in progress. Teams that add more conventions than that end up with a process nobody follows.
Choosing the bottom layer is where the earlier table matters. A board where the timeline and calendar are views of the same cards removes the hand built spreadsheet, which was the third failure above. A board where comments sit on the card removes the missing context, which was the fourth. Comparisons such as Pinateca vs Trello and All comparisons are more useful read against those two criteria than against a feature list, and the Features page is the place to check which board types are included rather than sold as an upgrade.
None of this means the to do list app was a mistake. Capture and daily review are the habits everything else depends on, and the app that makes them effortless has earned its place.
What changes is the boundary. The personal list stops being where shared commitments are stored and goes back to being where one person plans a day. The moment a second person is waiting on something, it belongs on the board, and the personal list holds a pointer to it at most.
The test for whether the boundary is holding is a question anybody on the team can answer in ten seconds: if you were away tomorrow, could a colleague find out what you are in the middle of without messaging you. If the answer is no, the commitments are still in the top layer.
Write down every task currently sitting only in a private list that somebody else is waiting on. That list is usually shorter than expected and more alarming than expected. Move those onto one shared board with a stage, an owner and a date, and leave everything else exactly where it is. If the shared layer needs a board, a timeline and a place for the conversation without an upgrade step, Pinateca is free for up to five people and ten boards.
For two or three people with mostly separate work, yes, and switching tools would cost more than it saves. It stops working when tasks routinely pass between people, because a personal list has no stage between open and done and no shared view of what is coming. The point of failure is usually the first time someone has to ask whether a handed off task was started.
Not if each answers a different question. The shared board answers where a piece of work stands, which other people need. The personal list answers what one person is doing next, which only that person needs. It becomes waste when the same commitment is maintained in both places as a source of truth rather than a pointer.
Sometimes, yes. Shared team workspaces in list apps are frequently placed on the highest plan, while board tools tend to hand out collaborators on the free tier and charge for size or advanced views instead. Compare the specific plan that contains the feature the team needs, not the entry price.
Between four and six, and the same ones everywhere. A common set is To do, In progress, Review, Waiting on someone else, and Done. The two most often left out are review and waiting on someone else, and they are the two that explain most delays.
Give them an owner anyway, even if the owner's job is only to chase it. A card with no owner is a card nobody starts, and a card with two owners behaves the same way. If genuinely no one can own it, that is useful information about whether it should be on the board at all.