Short answer: A good task list is one source of truth, ranked top to bottom, time-boxed, and shaped to move items OUT. Paper beats most apps for personal daily work; apps earn their keep for team lists, shared context, and anything repeatable. Lists stop working when they become inboxes — when adding is easier than finishing. The fix is not a better app; it is a smaller list and a weekly cull.
Everyone maintains a list of tasks. The majority of them malfunction.
Usually, it is not wrong that the list was wrong. The list is correct. It includes everything you need to do. The content is distributed in a progressively increasing order, which is not accurate. There are fourteen items from last Tuesday which you haven’t looked at since. The list includes “write Q3 strategy doc” next to “reply to Dave” It is precise and useless.
This article is directed at the individual who has experimented with four task management applications, maintained a physical list for a month, and subsequently witnessed the resurgence of the same disorder. Basically we will cover what a task list is actually for, the four things every good task list has, when paper beats digital, when a team list beats a personal one and when a task list stops working so you know to kill it rather than reorganise it.
The accumulated knowledge base of twenty years of shipping software, extensive Pivotal/Tanzu Labs heritage and the engineering practice of running teams off a ranked backlog that can only prioritise a single thing at one time.
What a task list is for
The reason a list of tasks exists is because it allows you to stop worrying about what to do next and do the thing. Job done. This is not that status report. Your productivity is not captured through this. It is not a scheduler. This is a tool to help delegate the decision of what comes next, so you can focus on your work.
This means a to-do list has succeeded if you have clarity on the first task in the list and start working on it. All that is below is an accessory. Your list is broken if you find at least one item that you have to think hard about where to start. Either the ranking is incorrect, the items are too large, or the list is performing a function it was not designed for.
This explains why teams feel better for three weeks when they switch task apps, after which they are back to the same mess. The application is not the issue. No matter where it is, the list has four things in common and if those four things are not present the app does not add them. We address the other end of the spectrum teams that outgrow personal lists and require something more structured in the task tracker piece.
The four things every good list has
A functioning task list possesses four qualities. By installing them, most task-list issues will get resolved. If you skip any of them, no app will save you.
The ultimate truth comes from a single source. You do not need two or three lists. Say “the yellow sticky note on my monitor” not “the sticky note on my monitor plus the Jira board plus the Slack reminder”. All in one. The second category contains matters of considerable significance that are slowly erased from memory, as one tends to forget to look at it on Tuesdays. The real issue is not in the list management, but rather in the fact that you have a list of things you don’t really intend to do. Recognize it and erase it.
Everything is organized according to its level of importance. No "P0 and P1 at the same time". Refrain from using a quadrant for important versus urgent that has ties. Something is highest on the list. If two items seem equally important, flip a coin and start one of them with it. The five minutes you waste ranking these is five minutes you don’t ship. We explain why ranked backlogs are better than prioritised buckets in the problems in project management breakdown.
All activities or tasks in your working list that fulfil your project must fit within a time-bounded envelope. "Reply to Dave" takes ten minutes. Creating the building design document will take two hours. Having “Rewrite the auth layer” in six days on a daily list is just wrong, it is supposed to be on the backlog with a plan. If an item cannot be sized, then it is too big. Size it first before you start it.
An effective list has an integrated exit as it is shaped to move things OUT. Things that are done are crossed off, archived or deleted. Not kept as trophies like in a restaurant. If it’s easier to ADD to your list than to FINISH things on it, then your list is becoming an INBOX. And inboxes grow without limit. Working lists remain “working” only because of the weekly cull (we shall cover that below.)
In a quarter, teams that run on ranked backlogs with the four properties highlighted rarely want to go back. Refer to task and project management to see how this scales from the individual to the team.
Paper vs digital vs app
The most honest answer to “which task app should I use” is: for personal daily work, start with paper. Use an app to enforce ranking for teamwork. The conflicts between application ecosystems don’t matter as much as the 4 characteristics actually do the right performance of the software.
The three reasons why paper wins for personal daily lists. First, the left-to-right writing and crossing off loop is tactile and a superior finishing of the item than an animation. the length of a paper which will not fit on a page is too long. So paper has a natural cap on size Another thing is that you cannot search paper which is by design; Tuesday list does not pollute Friday’s.
A digital note in your preferred editor or a markdown file in git wins when you need search, archive or sync across devices. Be careful with beautifully designed lists in rich-text apps. They reward you for adding stuff like bold headers, nested bullets, and coloured tags. The shipping tax gets consumed by decoration tax.
The App is designed to help the team with coordination, reactions, notifications, and anything else you cannot keep in your head. The proper application ensures ranking is observed, predicts delivery based on throughput, and doesn’t let the backlog indicate both things are priority one at the same time. With the wrong application, you can apply “P0” tags for 40 items. We address the tool fit at the team level in the task management dashboard article.
For a two-person team of individual contributors, a couple of common lists on Trello and a daily paper list beats any richer tool. For engineering teams from 6 to 20 running iterations, using a backlog with Fibonacci points and forecasting based on velocity wins by a country mile and the paper list remains for the daily personal cut.
The team task list is a different animal
Your personal task list and your team’s task list look very similar on the face of it items, ranks, due dates, etc. But it is exactly this similarity where teams run into trouble. The team list comes with three restrictions not found in the personal list.
People who were not a part of the writing of the team list will read it. In other words, we need items that have sufficient context so that a second engineer, picking one up at 9am on Monday, knows what the goal is without having to have a meeting. A personal note might say, “Fix the login bug.” But a task for the team would be, “Login fails for users with apostrophe in email address. Repro at /example/apostrophe-email. See acceptance criterial below.”
The team list is assessed by capability, not intent. A team has a known velocity defined as the average number of accepted stories per iteration over the last three iterations. The subsequent iteration list should consist of backlog items starting from the top until the item points sum aligns with the velocity. If an iteration requires more than the allocated time, it steps out of projected limits. Refer to the link provided for instructions on measuring this without formality.
The prioritization of teams takes business value into consideration, not personal preference. When two engineers think that a different item is "most important", the list will reconcile this in one place with one DRI. A reconciliation often proves to be a difficult meeting. Having two engineers working quietly on different "most important" things is actually worse.
When teams treat their task list as a shared backlog with these three properties, they ship more and argue less. Teams who treat it as a shared to-do app (with no rules) end up with the custom Jira sprawl everybody pretends is normal.
When a list stops working
There are three ways lists fail. Detect the indicators beforehand and the resolution is affordable.
The list becomes an inbox when adding is easier than finishing. The catalog increases in items by twenty percent on a weekly basis. You pass by objects that you have ignored for a month. To keep you on track, delete any items you haven’t completed in the last two weeks at the end of every week. The act of removing the email elicits anxiety because that’s the signal it would never get done. Your anxiety is the feedback.
The highest point on the list is not the item you’re working on. The rank either needs to be fixed or y is the real top, so promote y and demote x. Because when the first item is no longer believable, no subsequent item will be trustworthy. The entire list becomes advisory. Attention drifts back to whatever ‘feels urgent’. And that’s where the chaos begins.
All the things on the list grow larger in size. Create the control panel, compose the note, overhaul enrollment. In the case of big items, the start time is never Tuesday morning; they get rescheduled. The solution involves breaking down every item that cannot be initiated within the next 30 minutes. If the item is to "build the dashboard," what you actually want is "sketch the three charts the dashboard needs."
The three types of failures have an identical root: All stop “what we are working on today”, all start “everything else” The solution is to downsize the list, not make it more elaborate.
Templates and formats worth copying
There’s no design difference that distinguishes a good task list from a bad one. The framework that is effective for most engineering teams.
- Top of the list. The single next item. Enough context that starting it is obvious.
- Next three items. Ranked. Enough context that whoever finishes the top can start the next without a meeting.
- Backlog. Everything else. Ordered, but not necessarily reviewed daily. Reviewed weekly.
- Done. Items crossed off since the last cull. Reviewed in the retrospective, then archived.
That's everything for the template The LiteTracker kanban planning walkthrough explains how this visual board is used by teams not using sprints.
Try jotting down the following three lines in your personal notebook on a daily basis. Top of the day, two next up (what you’re doing next) and done (what you’ve accomplished). If the day’s biggest item can still be seen in Wednesday’s rank-ordering, it means it is too big or the ranking was wrong. Please do not add a fourth line in the future.
Still stuck
A task list works best if it is a single source of truth, always in strict rank order, time-boxed, and has a weekly cull. All other aspects are secondary. Use a notebook to write down three items in order of priority if your personal backlog is broken; the whole problem usually resolves in about a week. When your team list is broken, it is usually the ranking (2 x P0s, no DRI) or the sizing (everything is big), not the tool.
If assessing and prioritizing items using a shared backlog with Fibonacci capped-at-8 estimating and forecast based on accepted stories only sounds like the team needs, try LiteTracker free - no credit card, no time limit, no demo call. If a common Trello board and a retro on Friday is sufficient, do it. Either way, it’s time to stop treating the list like a filing cabinet. Use it to transform your approach – don’t think about what to do next and go do the next thing.
Frequently asked
What is a task list?
A task list is a single, ranked list of the next things you plan to do. It is built so you can stop thinking about what to do next and instead go do the top one. Essentially, it is a spreadsheet and it should only be used for this purpose. Your sole task is to make the upcoming move clear.
What makes a good task list?
The four essential characteristics of an effective backlog are: one source of truth if implemented correctly (not three lists), ranked top to bottom (with no ties and no ‘P0 and P1’), time-box items (so every item fits in a known envelope) and shaped to move items OUT (so that if done properly the items will not become an inbox – weekly cull).
Is paper or an app better for a task list?
According to our experience, a paper wins for personal daily lists because the write-cross-off loop finishes stuff, the medium caps the size, and old lists do not pollute today. Applications are best-suited for work alongside teams, repeatable workflows, and anything involving reminders that wouldn’t fit in your head. Whether the four properties above are present matters more than the medium.
How do you keep a task list from becoming an inbox?
Weekly purge Weekly, eliminate things that haven’t been accomplished in the last two weeks. If the thought of deletion induces anxiety in you, it’s a sign that you were never going to go through with it anyway. Anxiety is user feedback; requesting deletion is developer feedback.
How is a team task list different from a personal one?
We need a team task list that is readable, scoping against known capacity not energy, and ranking against business value with one DRI per conflict. When a team list is treated like a shared to-do app without these constraints, Jira sprawl appears.
How many items should a task list have?
A page is sufficient for a daily personal list. A team’s iteration list matches with a rolling three-iteration velocity. Anything beyond that goes to a separate record that is reviewed every week, not every day. If the daily list doesn’t fit on a sheet or the iteration list is bigger than velocity, the list is lying about what will get done.
When should I switch task management apps?
Seldom When teams switch apps, they get a three week honeymoon before they experience the same chaos. Because problems were usually due to the list structure, not the tool. If the platform is actively hindering (ranking, time-boxing, culling, single source), and you can rule out your own behaviour as the cause, then switch.