Where the work lives between reviews.
Free to use · No credit card required
Structure is not the same as clarity
Given enough fields, statuses, and custom views, a team will build a beautiful model of its process and then stop maintaining it, because keeping the model accurate costs more than the model returns. What survives is the smallest structure that still answers the questions people ask: who owns this, what state is it in, and is it moving.
Scan in a list, compare in a table
- Sortable table with owner, status, priority, and due date
- Filter by any combination, including linked objective
- Team colour-coding for team versus personal work
- Click any row to open the full task
Every task has one owner and an explicit yes
- One owner per task — no ambiguous group assignment
- Assigned work waits for acceptance before it counts as underway
- Push back with a reason and it returns to the assigner
- Activity feed records who changed what, and when
What you can do with a task
List and table views
Read down a list when you are scanning, switch to the table when you need to sort and compare. Same tasks either way.
Filters that answer questions
By owner, status, priority, due date, or objective. "What is Jake blocked on" should take one interaction, not a saved search.
Private personal tasks
Personal work is colour-coded blue and visible only to you. One list to review, two levels of visibility.
Discussion on the task
Comments and mentions live with the work. The decision about a task is findable from the task, not from a Slack search.
Links to anywhere
Attach a Jira ticket, a Google Doc, a PR, or any URL. The task points at the artefact rather than duplicating it.
Templates for repeat work
Save a set of tasks once and reuse it. Release checklists and onboarding stop being rebuilt from memory each time.