If you work on a team, you probably have two places where tasks live: the team's project tracker and some personal list of your own. The trouble starts when you treat them as the same tool. Put everything in the tracker and your own small tasks drown in other people's tickets. Keep everything in your personal list and the team loses sight of what you're doing. This article gives you one rule for sorting tasks between the two, a way to link them without maintaining two copies, and a short checklist for noticing when the line has drifted.
The rule
A task belongs in the team tracker when someone else is waiting on it or needs to see its status. Everything else is personal.
That's the whole decision. The rest of this article is about applying it, because the edge cases are where the mess comes from.
Why the two extremes fail
Everything in the tracker. The tracker becomes a mix of real deliverables and personal reminders: "reply to Sam", "clean up my branch", "read the onboarding doc". Teammates scanning the board have to filter out your notes-to-self to find the work that affects them. You, meanwhile, get the friction of a shared tool (fields, statuses, assignees) for tasks that only needed a line of text. Small items pile up unclosed because closing them feels like ceremony, and the board slowly stops reflecting reality.
Everything in your personal list. You stay organized, but only you can see it. A teammate who depends on your piece of the work has to ask you for status in chat, and your manager reconstructs your progress from standups. When you're out, nobody can pick up where you left off, because the state of the work lives in an app on your laptop.
Both failures come from the same mistake: sorting by where you happen to be when the task shows up, rather than by who needs to know about it.
The test question
For each task, ask: if I finished this and told no one, who would be affected?
- If a person or a downstream step is blocked until it's done, it goes in the tracker.
- If someone would reasonably check on it before it's done, it goes in the tracker.
- If the honest answer is "no one would notice except me," it stays personal.
Note the second condition. Some tasks don't block anyone right now but still need visibility: a piece of work a lead is planning around, a fix a customer was told is coming. Those belong in the tracker even though nothing is strictly waiting today. The rule is "waiting on it or needs to see its status", and dropping the second half is how work goes quietly invisible.
Quick sort
| Signal | Where it goes |
|---|---|
| Someone is blocked until it's done | Team tracker |
| Someone will check its status | Team tracker |
| Has a deadline set by others | Team tracker |
| Only you would notice if it slipped | Personal list |
| Prep work for a tracker item | Personal list |
| Reminder, habit, or note-to-self | Personal list |
What lives in the tracker
The tracker holds commitments to other people: deliverables, handoffs, bugs someone reported, anything with a status a teammate might look up. Each item there should be legible to someone who isn't you. That means a title that describes the outcome, not your private shorthand, and a status that's accurate at the moment anyone reads it.
It does not need to hold your process. "Draft the spec" can be one tracker item; the six sub-steps you'll take to draft it don't need to be tickets unless someone else is doing one of them.
What stays personal
The personal list holds everything you need to remember that no one else needs to see: the micro-steps behind a tracker item, follow-ups you owe yourself, things to read, small maintenance, errands. It can be as messy and abbreviated as you like, because you're the only reader.
It also holds the one thing the tracker is bad at: what you're doing next. A tracker shows what's in progress. It rarely shows the concrete next physical action, like "open the PR and reply to the review comment about naming". That level of detail is yours.
How the two connect without duplicate work
The failure to avoid here is keeping two statuses for one task. Once an item exists in both places, one copy goes stale, and you stop trusting whichever one you looked at last. Three habits prevent that.
Point, don't copy. When a tracker item is yours, add a single line to your personal list that references it, with the next action and nothing else. "TRK-231 — write the migration script" is enough. Your personal list is a set of pointers into the tracker, not a second copy of it.
Status lives in one place. Progress, blockers, and done/not-done get recorded in the tracker, because that's what other people read. Your personal list only ever says what you are doing next. When the next action is done, you update the tracker and rewrite the pointer with the new next action. You never have to reconcile two statuses, because only one exists.
Pull, don't push. Start the day by looking at the tracker and pulling the items you'll touch into your personal list as pointers. Don't do it the other way around, where personal items get pushed into the tracker "just in case". Pulling keeps the tracker as the source of truth and your list as a working view of it.
If your team's tracker and your personal tool can link to each other, use that. If not, an item ID or a short slug in the title does the same job.
Signs you've drawn the line in the wrong place
Watch for these. Each one points at a specific fix.
Teammates ask you for status in chat. The work they're asking about is a tracker item living in your personal list. Move it.
Your board has items only you would ever read. Notes-to-self in the tracker. Move them out, and close the ones that were really just reminders.
You close tracker items in bulk right before a review. The tracker isn't where status actually lives for you; you're back-filling it. Adopt the pull habit so status gets updated as you go.
The same task exists in both tools with different states. You copied instead of pointed. Delete the status from the personal copy and leave only the next action.
Your personal list has deadlines someone else set. A date set by another person means that person is waiting. That's a tracker item by definition.
A tracker item has been "in progress" so long you've forgotten what's left. The next action is missing. Add a pointer to your personal list with the concrete next step, and the item will start moving again.
Who this isn't for
If you work alone, the rule collapses: no one else is waiting, so a single list is enough. You can still borrow the pointer-and-next-action idea if your list gets long, but you don't need two tools.
If your team requires that every unit of work be logged for billing, compliance, or audit reasons, the tracker is the system of record and you don't get to choose what goes in it. The rule still helps in a narrower way: your personal list becomes a pure view of next actions, and it should hold nothing that isn't a pointer into the tracker.
If your team tracker is effectively a manager's status report that nobody else reads, treat "needs to see its status" as "the manager needs to see its status" and apply the rule as written. The fix for a tracker nobody reads is a team conversation, not a personal filing system.
The next action
Open whatever list you're working from today. For each item, ask who would be affected if you finished it and told no one. Anything with a name attached goes to the tracker, with a one-line pointer left behind. Everything else stays where it is. Do that once, and the sorting habit tends to take care of itself from there.