One Task Per Day: A Scoring System to Beat Overwhelm and Actually Ship Work

Most developers have thirty tasks on the list and zero completed by end of day. The fix is counterintuitive: do less.

Picking one task per day sounds lazy. It is not. According to Todoist's planning guide, finishing one big task daily means five to seven significant completions per week. That beats the alternative — juggling twelve things and finishing none.

The problem is not willpower. The problem is selection. Which one task? A simple scoring system removes the guesswork.

Why One Task Works

The Ivy Lee method, over a century old, enforces strict limits: six tasks max, worked in order, one at a time. Workflowy's breakdown of the method explains why — it forces focus and eliminates task-switching. No jumping ahead. Finish the current item or move it to tomorrow.

Key point: the constraint is the feature. A list of thirty tasks is not a plan. It is a wish list.

Forbes reports that psychologists view overwhelm as structurally identical to flow. The difference is whether the person treats activation as a stop signal or a launch condition. High performers in military and surgical contexts train deliberately to enter pressure states. The technique is called stress inoculation.

In plain terms: overwhelm means the work matters. Use that energy on one thing instead of scattering it across twenty.

The Scoring System: Impact, Urgency, Resistance

Every evening, list tomorrow's candidate tasks. Score each on three dimensions, 1 to 5:

Impact — What changes if this gets done? A shipped feature scores 5. Reorganizing bookmarks scores 1.

Urgency — What breaks if this waits another day? A deadline tomorrow scores 5. A "someday" refactor scores 1.

Resistance — How much do you want to avoid it? The task you dread most scores 5. The comfortable busywork scores 1.

The formula:

Score = Impact + Urgency + (Resistance × 1.5)

Resistance gets a multiplier. The task with the highest avoidance is almost always the one that matters most. The "Eat the Frog" method from Todoist's guide formalizes the same idea — identify the task you most want to avoid and do it first.

Example scoring

Task	Impact	Urgency	Resistance	Score
Fix auth bug in staging	4	5	2	12.0
Write migration script	5	3	5	15.5
Update README	2	1	1	4.5
Refactor payment module	4	2	4	12.0

The migration script wins. It has the highest impact and the highest resistance. The README update — comfortable, low-stakes — drops to the bottom.

Common mistake: picking the urgent-but-low-impact task because it feels productive. Answering emails all day feels busy. It does not move the needle.

How to Execute the One Task

Once scored, the winning task gets a time block. Research on ultradian rhythms supports 90-minute focused sessions, as noted in the Forbes article on overwhelm and productivity. One to two blocks of 90 minutes usually covers a single meaningful task.

The daily routine looks like this:

1. Previous evening: list candidates, score them, pick one winner
2. Morning: open only what the task requires — close Slack, email, everything else
3. First 90-minute block: work on the task. No switching
4. Break: 15 minutes. Walk, not scroll
5. Second 90-minute block if needed: finish or get to a clear stopping point
6. Afternoon: handle smaller items, communication, planning for tomorrow

Tested in production. Three hours on one thing consistently beats eight hours split across six things. Asana's time management research found that 29% of knowledge workers experiencing burnout cited unclear priorities as a contributing factor. One task eliminates that ambiguity.

What about the other tasks?

They wait. Some become irrelevant by the time their turn comes. That is a feature, not a bug. Practice shows that half the "urgent" items on any given list resolve themselves or get handled by someone else within 48 hours.

The Ivy Lee approach handles overflow simply: unfinished tasks move to tomorrow's list and get re-scored. Context changes daily. Yesterday's priority-two task might score highest tomorrow.

Handling Ties and Interruptions

Two tasks score identically. Pick the one with higher resistance. If resistance is also equal, pick the one that unblocks other work. A completed migration script unblocks three downstream tasks. A refactored module unblocks none.

Genuine emergencies — production is down, a client deadline moved up — override the system. Handle the emergency, then return to the scored task. The system is a default, not a cage. Colter Reed's daily planning framework emphasizes flexibility: be prepared for estimates to be wrong, and adapt without guilt.

Key point: the scoring system is not about rigidity. It is about making a decision once, in the evening, instead of re-deciding every thirty minutes throughout the day.

Sizing Tasks for a Single Day

A task that takes eight hours is not a daily task. It is a project. Break it into pieces that fit within two to three hours of focused work.

"Build user dashboard" is not a task. These are:

• Design dashboard data schema
• Implement API endpoint for dashboard stats
• Build dashboard UI skeleton
• Wire up real-time data to dashboard components

Each is completable in one session. Each delivers visible progress.

Full Focus's task management guide recommends never scheduling more than six hours of task work per day. Estimates are consistently too optimistic. Leave margin for the unexpected.

Try it: take your biggest current project. Split it into chunks no larger than three hours each. Score those chunks. The highest-scoring chunk is tomorrow's one task.

Tracking Results

The scoring system generates data over time. After two weeks, review:

• Completion rate: how many daily tasks actually got finished? Below 70% means tasks are too large or the scoring is off
• Resistance correlation: did high-resistance tasks produce the most meaningful outcomes? Usually, yes
• Estimate accuracy: did three-hour tasks actually take three hours? Adjust future scoring if consistently off

No special tool is required. A plain text file works:

2026-03-10 | Migration script | Score: 15.5 | Done | 2.5h
2026-03-11 | Auth bug fix     | Score: 12.0 | Done | 1.5h
2026-03-12 | Payment refactor | Score: 12.0 | WIP  | 3h → carry to 03-13

If it works — it is correct. Fancy apps are optional. The decision process is what matters.

Frequently Asked Questions

How do you decide which task is most important when everything feels equally urgent?

Score them. The formula removes emotion from the decision. When everything "feels" urgent, most items actually score low on impact. Write the numbers down — the ranking usually becomes obvious within two minutes.

How do you prevent yourself from switching to other tasks mid-day?

Close every application not required for the current task. Notifications are the primary enemy of single-tasking. The Forbes research on flow states confirms that task-switching under stress is precisely what prevents sustained focus. One browser tab, one editor window, one task.

What happens when a genuinely urgent task appears after you have already started?

Handle it if production is down or a hard deadline is at risk. Otherwise, write it down and score it for tomorrow. Most "emergencies" are not emergencies — they are someone else's poor planning arriving in your inbox.

How do you break large projects into daily-sized tasks?

Each chunk should produce a visible, testable result within two to three hours. If a task description starts with "work on" rather than a specific verb like "implement," "fix," or "write," it is too vague. Rewrite until each piece has a clear done state.