How to Organize Tasks at Work: A System That Survives Monday

To organize tasks at work, keep every task in one place, sort each one by what kind of work it is and how urgent it is, put it in one of four lanes that say where it stands, and spend fifteen minutes once a week putting the whole thing back in order. That is the entire system. Most task systems fail not because the method is wrong but because tasks leak out of them: a request stays in email, a bug lives in chat, and by Monday the list no longer describes the work. The rules below are about stopping the leaks, and about what to do with the tasks that never seem to move.

Deciding which task comes first is its own skill, covered in how to prioritize tasks at work. This guide is about the system that holds the tasks, so that the prioritizing has something reliable to work on.

Capture everything in one place

The first step of David Allen’s Getting Things Done method↗ (opens in a new tab) is capture: “Write, record, or gather any and everything that has your attention into a collection tool.” The important words are “any and everything” and “a collection tool,” singular. Two lists means you check one and forget the other.

• Pick the one place, and make it the place your team can see too. A personal notebook for work other people are waiting on is a second list in disguise.
• Name the leaks. For most people they are email, chat, meeting notes and hallway requests. Each gets a habit: when a request arrives there, it becomes a task within the day, and the reply says so.
• Capture fast, sort later. A title that starts with a verb is enough at capture time. Deciding what it is and how urgent comes next.
• If a task takes under two minutes, do it instead of writing it down. Everything else goes in.

The first time you do this, the list will be long. That is the list you already had, now visible. A task list template helps if you are starting from nothing.

Sort by kind and priority

Two labels per task are enough to organize almost any list. The first is the kind of work. For most teams that build or run something, three kinds cover it: a feature is something new, an enhancement improves something that exists, and a bug is something broken. Why three is enough, and how to decide between them, is explained in features, enhancements and bugs.

The second label is a priority number. Use a scale with room in it, such as 1 to 10 where 1 is most urgent, and keep only two or three tasks at the top. Kind tells you what sort of attention a task needs; priority tells you when. Resist adding more labels until a real question needs one. Every label is a decision someone has to make each time they add a task.

One board, four lanes

A list tells you what exists. A board also tells you where each thing stands. Four columns, or lanes, are enough for most work:

• To Do: everything captured and not yet planned. It can be long. That is fine.
• Next Up: what you have committed to doing next. Keep it short enough to finish in a week or two, so putting something here means something.
• In Progress: what someone is actually working on today. If a task has not been touched in days, it is not in progress, whatever the board says.
• Completed: finished work, including work you decided not to do, marked with the reason.

One board per team, not one per person or per project. People see each other’s work, dependencies show, and nobody keeps a private list of the “real” priorities. For your own work alongside the team’s, personal kanban shows how the same lanes work for one person, and kanban board vs to-do list covers when a list is still enough.

A 15-minute weekly review

A system that is never tidied decays within a month. The Getting Things Done method calls this step Reflect, and its instruction reads: “Update and review all pertinent system contents to regain control and focus.” Fifteen minutes, same time each week, in this order:

1. Empty the leaks (3 minutes). Scan email, chat and meeting notes from the week and add anything that became a task.
2. Sort the new ones (3 minutes). Give each a kind and a priority. Merge duplicates.
3. Walk In Progress (3 minutes). Anything not touched this week goes back to Next Up or To Do, with a line saying why.
4. Refill Next Up (3 minutes). Pull the highest-priority tasks from To Do until the week is full, and no further.
5. Close what is finished or no longer needed (3 minutes). Move it to Completed with the reason.

If you run a team, do this with the person who owns the priorities, and send the top of the list to whoever needs to know. A weekly status report can come straight from it.

What to do with tasks that sit for weeks

Every list collects tasks that never move. The Kanban Guide↗ (opens in a new tab) names the measure for this, Work Item Age: “The elapsed time between when a work item started and the current date.” A task in progress for three weeks is telling you something. So is one that has sat in To Do for three months. Pick one of four answers for each, at the weekly review:

• Split it. A task that never starts is often three tasks, and the first one is small enough to do on Tuesday.
• Commit to it. Move it to Next Up with a priority that means it will happen this week or next.
• Hand it over. It may belong to someone with more context or more room. Ask them, and put the new owner’s name in the first line of the note.
• Close it, with the reason. “Not doing this: the customer left” is a decision, and writing it down stops it coming back. A task nobody has asked about in three months is a strong candidate.

What you should not do is leave it and feel bad. A list full of guilt is a list people stop opening.

AI assistants adding and updating tasks

An AI assistant connected to your task board can do a lot of the capture and upkeep: turn meeting notes into tasks, file a bug when a test fails, and write what it did on the task when it finishes. That keeps the one place complete without anyone typing. It needs three rules to stay organized rather than noisy:

• Search before adding. An assistant that files the same bug twice doubles the weekly review. Tell it to look for an existing task and comment there instead.
• Let it propose priorities, not set them. Ranking is a judgment about the business, and it belongs to a person.
• Keep its changes visible. You should be able to see which updates an assistant made and on whose behalf.

The Model Context Protocol specification↗ (opens in a new tab), which most assistants use to reach tools like a board, says “there SHOULD always be a human in the loop with the ability to deny tool invocations.” For a task board, that usually means the assistant can add and comment freely, while moving or closing tasks stays with a person until you trust the pattern.

Organizing tasks on fenbs

fenbs is built around this system. Every task is a feature, an enhancement or a bug, with a priority from 1 to 10, on one board with four fixed lanes: To Do, Next Up, In Progress and Completed. There are no sprints, due dates or WIP limits to configure.

• Capture: Add many takes a pasted list, one task per line, and a line starting with bug:, feature: or enhancement: sets that task’s kind. Everything is previewed before anything is created.
• Sort: each lane has its own order. Sort In Progress by Oldest at the weekly review to bring the longest-standing tasks to the top, or by Changed to see what moved recently.
• Close with a reason: a task in Completed is marked Completed, Won’t fix, Duplicate, Cannot reproduce or Obsolete, so only shipped work counts as delivered.
• Report: Copy as Markdown copies the board as text, for a status message.
• Assistants: over MCP, fenbs_create_item holds back a task that looks like an open one and returns the likely match, so the assistant comments instead of filing twice. History records every change under the name of the person or assistant that made it.