Task management

What this shelf covers

Keeping track of what has to be done: personal lists, shared boards, recurring work, reminders and the small amount of structure that makes a day legible.

The boundary with project management is genuine. These tools organise work. Project tools coordinate work that depends on other work, with dates, capacity and reporting attached, and that machinery is overhead until the dependencies are real.

Coordinated delivery with schedules belongs in project management. Notes and reference material sit in notes and wiki.

Capture speed is the whole thing

A task system competes with remembering, and it loses whenever it is slower than remembering.

Measure the time from thinking of something to having it recorded. Opening the application, choosing a project, setting a date and typing a title should not take longer than the task deserves. Products that demand structure at capture lose the items that would otherwise have been kept.

Mobile and keyboard access matter for the same reason. Most tasks occur to people away from the place where they will do them.

Views, and why they matter less than they look

Boards, lists, calendars and timelines are the same records displayed differently.

• Boards for work moving through stages.
• Lists for priority within a day or a week.
• Calendars for anything anchored to a date.
• Timelines for sequences with duration.
• Filtered views for one person’s slice of everything.

The useful question is whether one dataset supports several views, so different people can work how they prefer without the team maintaining two versions of the truth. Products where each view is a separate object create exactly that fragmentation.

Recurring work, which is where these tools earn their price

Most of what a person does repeats, and handling repetition well separates good products from note-taking with checkboxes.

Ask how recurrence works after a task is completed late, whether a missed occurrence piles up or is skipped, and whether a recurring item can carry a checklist that resets each time. Those details decide whether the system stays accurate over months.

Reminders belong here too. A reminder attached to a time is useful. A notification that arrives while somebody is doing something else is noise, and the difference is entirely in how the tool handles snoozing and rescheduling.

Shared lists without becoming a project tool

Small teams share tasks long before they need project software.

What they need is ownership, so every item has one name against it, and visibility of what somebody else is waiting on. Comments attached to the task beat a chat thread that scrolls away.

The failure to watch for is accumulation. A shared list grows until it contains four hundred items, at which point it stops being a plan and becomes a reproach. Deleting is the maintenance activity, and no product will do it for you.

What it costs

Per user per month, with free personal tiers that are genuinely usable for one person.

The paid boundaries usually sit at automation, saved views, guests, permissions and history depth rather than at storage. For teams, check what a guest costs, since clients and contractors often need to see a single list rather than the whole workspace.

Export is worth testing early. Tasks and comments generally leave cleanly, while attachments, custom fields and recurrence rules frequently do not, which is the sort of detail examined in what pricing pages hide.

Choosing between the free tier and a paid plan

Most products here have a free tier that genuinely works for one person, which makes the upgrade question worth answering deliberately rather than by drift.

Pay when you need something a list cannot do on its own. Shared ownership across several people, automation that removes a repeated manual step, saved views that different people rely on, or history you would miss if it disappeared.

Do not pay for capacity. Storage and item limits are rarely what a task system runs out of, and a plan bought for its ceiling usually goes unused.

For teams, the seat count is the number to watch rather than the tier. Occasional contributors, clients and reviewers should sit on guest access where the product offers it, and dormant accounts should be removed on a schedule rather than when somebody notices the invoice.