Cut the list with a weekly shrink, not a new app
Task lists grow when everything enters at the same urgency and nothing leaves except by accident. Meetings spawn nouns. Chat spawns "look into." Good intentions spawn "someday organize." None of those are tasks. They are inventory without a checkout lane. Remote work makes the pile worse because capture is frictionless and completion is invisible. Adding a line feels like progress. Finishing requires choosing what not to do.
The fix is triage on the way in (verb + location or delete), two-list discipline (daily plan vs backlog vs parking lot), and a fifteen-to-thirty-minute weekly shrink with delete/merge/rewrite rules. Cap active WIP at three. Celebrate removals. Four drivers of growth: topic-shaped lines with no first move (clear next action); missing decisions parked as tasks; no weekly cut; fantasy capacity that loads eight hours of tasks onto an eight-hour calendar (planning eight hours).
Triage on the way in
When something new arrives, ask once:
- Is this mine?
- If yes, what is the first visible action (verb + location)?
- If no, who owns it - and did I tell them?
- Does this need a date, or does it die?
If you cannot answer in two minutes, the item is a project, not a task. Put it in a project list with one next action on the daily plan. During composition blocks, capture interrupts on a side sheet and process them in a message window - "quick" additions mid-block are list growth in disguise (structure a remote workday).
Capture is not commitment. Inboxes feel responsible when they grow. Most growth is uncaptured "maybe later" without owners or finish lines.
Two-list discipline + parking lot
Daily plan: one primary, two to three secondary max, all startable today. Use structure a remote workday.
Backlog: everything else, sorted by project, explicitly not "today." Never let the backlog live in the same view as today's primary. Choice fatigue grows lists psychologically even when count stays flat.
Parking lot (someday): not a task list. Reviewed monthly, not daily. Items enter only with a note about why they are not today. If the parking lot exceeds one screen, delete half without reading twice - real priorities fight their way back. Quarterly, delete half again; if an item survived four reviews untouched, it was never real.
One visible next action should sit at the top when you sit down - the line that passes a two-minute start test. The backlog can be messy behind that line. The morning only needs the line. Priority labels without finish lines become astrology: rewrite until the primary names an artifact ("PR merged," "email sent," "section drafted for review"). Score with busy versus finishing.
Weekly shrink rules (fifteen to thirty minutes)
Schedule the cut. Without it, capture systems become storage. GetToWork shrink rules:
- Delete duplicates, obsolete items, and anything without a next action and a date (or explicit parking-lot reason).
- Merge related lines into one project with one next action.
- Rewrite topics into verb + location or delete them.
- Assign decisions to owners with dates in writing - decisions are not tasks.
- Cap active WIP at three for solo work. New urgent work requires finishing or explicitly parking something else with a stakeholder note: "Pulling PAY-200 ahead; FAQ slice moves to next week."
- One in, one out for the daily plan: a new secondary displaces another or waits until tomorrow.
- Celebrate removals. Deleting twenty lines is progress: "Removed stale items; three primaries left for the week." Deletion must feel like winning, not giving up.
If the cut takes an hour, capture is too loose. Capture less, file faster (useful notes without a second Notion).
Deferred needs a date or a "won't do" line. Hidden no is how lists grow: items linger as passive aggression toward yourself.
Worked example: eighty lines to twelve
Example: Every chat message that might need action becomes a line - "look at design," "follow up with Sam," "invoice thing," "read thread about API." By Friday there are eighty items and zero starts.
Triage once: delete anything without a date or owner, merge duplicates, rewrite five lines as physical next actions. The list drops to twelve. Pick one primary for tomorrow from the twelve, not from the eighty. The lesson is not better software. It is capture discipline: if it is not worth a verb and a location, it is not worth a line.
Client drip: client adds "small" requests daily until forty items sit open. Fix: batch tweaks into a Friday window; primary stays the feature milestone; new asks go to backlog with a date. Without batching, the list becomes the client's infinite free bucket.
Team board swamp: you assign yourself every interesting ticket until WIP hits twelve. Fix: three active max; rest unassigned or scheduled next sprint. Shared household or team lists need an owner per line or deletion - "we should fix the garage" without an owner is wallpaper. One person owns weekly triage even if everyone can add.
Emotional items and dual systems
"Think about career" and "figure out health insurance" are projects requiring a first action or a calendar appointment with yourself. Therapy-sized worries on a work list create static - move them to the right container or schedule the call that moves them.
Do not copy Jira into a personal app and maintain two lists. Pick one system of record for work items. Personal app holds only private next actions tied to tickets. Duplication creates the illusion of progress when you are only syncing.
New list hygiene feels great for seven days, then a crunch week arrives and capture reverts to panic. Plan for crunch: shorter weekly cut, harder delete rule, primary so small it survives bad weeks (why productivity systems fail after the first week).
Lists grow when capture is easier than completion. Tighten entry, park someday honestly, cut weekly, and measure finished artifacts instead of line count.
Weekly cut script (print and run)
Open the backlog. Set a fifteen-minute timer. For each line, do exactly one:
- Done already → delete
- Not mine → reassign or delete after telling the owner
- No verb → rewrite to verb + location or delete
- No date and not parking-lot → delete or give a date
- Duplicate → merge
- Someday → move to parking lot with one-line why, or delete
- Active → keep only if under WIP cap of three; otherwise park with stakeholder note
When the timer ends, stop. Leftovers wait until next week. A perfect cut that never happens loses to a blunt cut that happens every Friday. If crunch week arrives, shrink to ten minutes and a harder delete rule - continuity of the cut matters more than thoroughness (why productivity systems fail after the first week).
Primary fights the list: the daily plan names one primary outcome; the list serves the primary, not the reverse. If the list keeps growing while the current-action field stays empty, you are collecting, not working.