Skip to content
Published on

Divide and Conquer, No Procrastination — You Can Do It All

🇰🇷KO🇺🇸EN🇯🇵JA
Split View필사 모드
Authors

Opening — The Wall of Overwhelm

When a task is too big, oddly, our hands won't move. We freeze before the sentence "I have to finish the project this week." We don't know where to start, the end isn't visible, and so we do something else. We check email, brew coffee, and postpone — "I'll really start in a bit."

I was the same. Given a big assignment, I would spend days just staring at it, unable to begin. Then, as the deadline loomed, I would finally pull an all-nighter and somehow get it done. And every time I thought the same thing: "I finished it after all. I should have started sooner."

There is a strange irony in this pattern. The task that felt so overwhelming suddenly unlocks right before the deadline. Why? Because the deadline breaks the task small for me. The giant goal "finish this week" shrinks, in the face of the deadline, into a concrete single piece: "this one screen, right now." What moved me was not the pressure but the small concreteness the pressure created. So we needn't wait for the deadline; we can break the task small ourselves first.

Here is what I realized. A task feels overwhelming not because it is big, but because I'm seeing it as one giant lump. Break the lump into small pieces, and each piece isn't scary at all. And as you knock off the small pieces one by one, the big task quietly finishes.

The message of this essay is simple: break it small, and you can do it all.

Why Overwhelm Arises

Before discussing how to split, let's look at the nature of overwhelm. That heaviness we feel before a big task — where does it come from?

First, vagueness. "Finish the project" contains no concrete first action. Not knowing where to start, the brain receives no signal to begin acting. Our brains respond to concrete next moves more than to abstract goals. "Finish" is not an action; "open the file" is.

Second, bulk. Load the whole size of the task into your head at once and you're crushed under its weight. Look at the whole mountain and you can't fathom climbing; but the single step in front of you, anyone can take. The problem isn't the task but the view that takes it in all at once.

Third, fear. We fear doing it badly, running out of time, a bad result. And this fear is usually largest when the task is seen vaguely. The instant you split it concretely and gauge "this piece is about thirty minutes," the vague dread shrinks to a manageable size.

Three causes of overwhelm and their remedies
Vagueness -> set a concrete first move ("open the file")
Bulk      -> hold only one piece in view at a time
Fear      -> split and gauge the size of each piece

One interesting fact: all three causes arise from "seeing big," and all three dissolve through "breaking small." So divide and conquer is not merely a work technique but a tool for governing the emotion of overwhelm itself.

Divide and Conquer — Life Wisdom From Computer Science

"Divide and conquer" is originally an algorithm-design technique. Split a big problem into smaller problems of the same kind, solve each small one, then combine the answers to solve the whole. Merge sort, quicksort, binary search — the most elegant algorithms in computer science stand on this principle.

The core insight: a big problem looks unsolvable as-is, but split it small enough and each piece solves itself.

Why is this possible? The difficulty of a big problem usually comes from "having to hold the whole thing in your head at once." Human working memory is so small that gripping a huge problem whole quickly overloads it. But a single small piece slips right into working memory. The essence of divide and conquer is shrinking the problem's size to fit our head's small capacity.

This principle applies to nearly every big task in life, not just code.

  • "Write a book" is daunting. "Sketch the outline of one chapter today" is doable.
  • "Move houses" is enormous. "Sort one shelf today" takes thirty minutes.
  • "Refactor the whole service" is frightening. "Clean up just this one function" finishes before lunch.
[Big task]                 [Split tasks]
finish project  ──split──> design feature A
                           build feature A
                           test feature A
                           design feature B
                           ...
              <──conquer──  finish each piece, one by one
              <──combine──  when each is done, the whole is done

There is one important criterion here: how small should you split? The answer is "small enough that you no longer want to put it off." If "design the database" still feels overwhelming, go down to "just list the columns of the user table." The size at which the urge to procrastinate disappears — that is the right size.

Split Recursively — If a Piece Is Still Big, Split Again

The real charm of divide and conquer is in "recursion." You split a big problem into smaller ones, but what if a small one is still big? Simple: split again. Repeat the same move until it's small enough.

In algorithms, merge sort halves the array, halves those halves, and keeps halving until each element stands alone. A single element is already sorted, with nothing left to solve. Split until it's self-evident, then combine back up and the whole becomes sorted.

We do the same with work.

Example of recursive decomposition
"Write one blog post"
  - "Decide the topic"          <- still vague? -> split more
      - "List 5 keywords of interest"  <- 5 min. Stop.
  - "Build the outline"
      - "Write 6 section titles"       <- 10 min. Stop.
  - "Write the draft"
      - "Write only the first section" <- an hour. Stop.

The stopping signal is consistent. When you feel "I could start this right now," it's small enough. If that feeling doesn't come, split once more. The five minutes spent splitting prevent the five hours wasted procrastinating.

One caution: splitting itself can become a variant of procrastination — planning elaborately while never actually starting. So set a rule: once you've split, you must start the smallest first piece immediately. A plan is for action, not for postponing action.

Don't Procrastinate — The Art of Starting

The essence of procrastination is not laziness. Psychology research mostly sees it as a problem of emotion regulation. When a task is boring, hard, overwhelming, or carries the fear of failure, we postpone it to avoid that uncomfortable feeling, because the moment we delay, our mind feels briefly lighter. That short relief reinforces the procrastination.

This matters for a reason. See procrastination as laziness and the prescription becomes "be more diligent" — which barely helps. See it as emotional avoidance and the prescription changes: reduce that uncomfortable feeling. And the most effective way to reduce the feeling is precisely to break the task small. A small piece provokes less boredom, less fear, less overwhelm. So divide and conquer is, before it is a time-management technique, an emotion-management technique.

The problem is starting. Once you begin, it's surprisingly manageable; it's the moment before beginning that weighs the most. So the key to beating procrastination is "reducing the friction of starting."

The most famous tool is David Allen's two-minute rule: "If a task takes under two minutes, do it now." Postponing it costs more than just doing it.

James Clear, in Atomic Habits (2018), reshaped the two-minute rule into an art of starting: begin any task with a two-minute version of it. Not "read for thirty minutes" but "read one page"; not "work out" but "put on the running shoes." Once you start, stopping is harder. The law of inertia applies to work too.

I have a phrase I use: "Don't try to do it well; just start." The first line can be terrible. You need a first line before you can fix the second. Wait for a perfect start and you will never start.

Start triggers that beat procrastination
- "Just two minutes" -> usually you pass two minutes
- "The draft can be a mess" -> unlocks perfectionist paralysis
- "Set up the environment in advance" -> removes start friction
- "Make the first move within five seconds" -> no room to hesitate

Build Momentum by Reviewing Yesterday

When a big task spans several days, the hardest part is starting the engine each morning by re-deriving "where was I?" Crank from zero every time, and you face the overwhelm afresh every day.

Here is a powerful habit: at the start of the day, spend five minutes reviewing what you did yesterday.

Reread yesterday's code, skim yesterday's notes, find the point where you stopped. Two things happen. First, context recovers quickly; yesterday's flow comes back to mind. Second, "oh, I did this much yesterday" gives a small sense of achievement that eases today's engine into gear.

This touches a writing trick attributed to Hemingway: he stopped writing while he still knew what came next. That way, the next day he wouldn't freeze before a blank page but could pick right up. When you stop, jot one line about "where to start tomorrow" — it's the kindest gift to your future self.

Momentum isn't grand. It's small continuity. The feeling that yesterday and today connect without a break — that is the force that carries a big task to the end.

Energy Management — Allocate Focus, Not Just Time

Even after beating procrastination and starting, you can't work at the same intensity all day. What we truly lack is not time but focus energy. So to carry a big task to the end, you must place pieces along your energy curve, not just your schedule.

Everyone's clearest hours differ. For some it's morning, for others late night. Find your golden window and place the hardest, most important piece there. Conversely, in low-energy hours put light, mechanical pieces — tidying, formatting, replies.

Placing pieces by energy
High energy (golden window) -> hardest, most important piece (MIT)
Medium energy               -> ordinary work, meetings
Low energy                  -> tidying, replies, mechanical work

Another key is recovery. Focus doesn't run forever. A widely used method is the Pomodoro: a rhythm of twenty-five minutes of focus and five of rest. The crux is seeing rest not as "waste" but as "charging for the next focus." Alternating focus and rest gets more done, more deeply, than enduring five hours straight.

Look closely at when procrastination worsens and it's usually the moment energy bottoms out. Then, rather than forcing it by willpower, it's wiser to rest briefly or drop to the smallest piece. Respecting your rhythm instead of berating yourself is also a skill for finishing.

And the foundation of energy is, in the end, the body. When sleep runs short, focus and self-control are the first to collapse. Sleeping enough, moving lightly, not skipping meals — it doesn't sound like a productivity secret, but it is the foundation beneath all productivity. No divide-and-conquer strategy beats a sleep-deprived brain. So if you want to work well, paradoxically, start by resting well.

One at a Time, Deeply — The Illusion of Multitasking

Facing the small pieces, ambition kicks in. You want to do several at once. But here lies a trap.

Cognitive-psychology research is consistent: humans are bad at multitasking. What we call multitasking is actually rapid "task switching," and each switch costs the price of reloading context. According to Gloria Mark's research, fully returning to a task after a single interruption takes more than twenty minutes on average.

So after splitting small, you must do one at a time, deeply. Focus on a single piece until it's done.

  • Open only one piece at a time. Keep the rest closed in the list.
  • Until that piece is done, don't look at other tabs or notifications.
  • When it's done, check it off the list, then open the next piece.

Paradoxically, finishing one at a time is faster overall than clutching several at once. A finished task vanishes from your head; only unfinished tasks impose cognitive load. Each time you fully finish one, your mind gets one notch lighter.

Let me also touch the word "deeply." Splitting small does not mean working shallowly. Quite the opposite. Focus wholly on one piece and you can dig into it all the way, not just its surface. One thing done properly is far sturdier in the end than several touched sloppily. Breaking small isn't giving up depth — it is the condition that makes depth possible.

Don't Drop the Other Tasks — A Tracking System

Doing one thing deeply does not mean you may forget the others. Quite the opposite. So that other tasks don't leak away while you focus, you need a tracking system that holds everything externally.

The core principle is simple: write every to-do in one place, not in your head. Only then can you focus on this one thing with peace of mind: "the other tasks are all recorded over there; for now I just do this."

My tracking system has three layers.

[Three-layer tracking system]
Inbox    : where everything that surfaces gets dumped (no sorting)
   v sorted daily
Today    : 3-5 small pieces to finish today (more is greed)
   v one at a time
Done      : where finished items move (a record of achievement)

One important detail: the "Today" list must be short. List twenty to-dos and you won't finish them; the sixteen unfinished ones guilt you daily. Pick only the 3-5 you will truly finish today. Let the rest wait in the inbox.

And at each day's end, tidy the system. Move today's unfinished items to tomorrow, drop newly surfaced items into the inbox, send finished ones to Done. This short tidy-up keeps the system alive.

The real effect of a tracking system lies in an unexpected place: peace of mind. Believe that everything is written in one place and your head no longer needs to clutch the other tasks. Only then can you sink fully into this one piece. As the tool remembers in your stead, your head is freed to do only the thinking.

Priorities — Which Piece to Split First

When pieces multiply, the question comes: "so which do I do first?" Without priorities, doing whatever's at hand means you only do the easy things and postpone what actually matters.

The simplest, most powerful tool is the Eisenhower Matrix. Sort tasks along two axes: urgent and important.

            Urgent           Not urgent
Important  | Do now        | Schedule it     |
           | (deadline)    | (highest value) |
Not imp.   | Delegate/fast | Reduce or drop  |

The trap is the "urgent but not important" box. Ringing notifications, messages demanding a quick reply — these eat the whole day. Meanwhile the "important but not urgent" work, the kind that changes the future, gets postponed daily precisely because it isn't urgent. Good prioritization defends exactly this box.

Here divide and conquer meets prioritization. After splitting a big task, you have many pieces, and this matrix guides which to do first. Not all pieces matter equally. Some are prerequisites for others (do them first); some are side branches you needn't finish at all. After splitting, decide once "in what order to conquer," and you won't deliberate each time what's next.

And don't be fooled by false urgency. Merely distinguishing deadlines others set from deadlines you set changes who controls your day. Not every notification needs an answer right now. The order is to first carve out time to finish the truly important piece, then arrange the rest around it.

One practical tip: at the start of the day, set the single task you could call "if I finish only this, the day is a success" — the MIT, Most Important Task — and place it in your clearest hours. Even if the rest scatters, finishing that one means the day moved forward.

Perfectionism — Procrastination Wearing a Mask

The most cunning form of procrastination is perfectionism. On the surface it looks like delaying "because I want to do it well," but look inside and it's often avoidance: "rather than do it imperfectly, I won't start." If you don't start, there's no failure, so perfectionism becomes a safe refuge for protecting one's pride.

Here divide and conquer shines again. Imagine one perfect deliverable and you're overwhelmed; but "a first piece that's allowed to be rough" carries no burden. So the way to beat perfectionism is not to lower the standard but to delay when the standard is applied.

  • First make a draft by sheer quantity. Don't judge quality at this stage.
  • Once a draft exists, refine it. Refining is far easier than a blank page.
  • Perfection is not a condition for starting but a result of iteration.

Writers have a saying: "Write a shitty first draft." Good writing comes not from a well-written first line but from fixing a terrible first line again and again. The same goes for code, design, slides. Make it exist first, then make it good.

When perfectionism rears up, tell yourself: "Now is not the time to be perfect but the time to make it exist." A rough draft that exists always beats a perfection that doesn't.

A Case — How I Finished an Overwhelming Project

Let me unpack the abstract principle with one experience of mine. Once I took on a multi-week task, and for the first few days I just kept the screen up, doing nothing. It was too big and I didn't know where to start.

Then I changed the approach. Instead of building a grand plan, I wrote on paper "every piece needed to finish this," just as they came to mind. No order, no priority — I just got them all out. About twenty came out. In that instant, strangely, the overwhelm halved. The fog in my head had turned into a list on paper.

The order that rolled an overwhelming project
1. Get every piece out onto paper (ignore order)
2. Pick the smallest piece "doable in 30 minutes"
3. Finish only that one today
4. Next day, review yesterday for 5 min, pick the next piece
5. Repeat. Before long the list is all crossed out

After that, every day I thought only "today, this one piece." I no longer carried the weight of the whole project. I looked only at the one piece in front of me. Two weeks passed that way, and the big task I once couldn't even touch was finished. Not grand willpower but a small daily piece carried me to the end.

The lesson this gave is clear. Big tasks don't end with big resolutions. They end with the steady repetition of small pieces.

The Joy of Completion — Stacking Small Wins

Splitting small has a hidden bonus: you can finish often.

One big task won't finish for days or weeks. During that time we never once feel "done." Split small, though, and you experience "done" several times a day. And that sense of completion isn't just pleasant — it stimulates the brain's reward circuitry and supplies the motivation to start the next thing.

Teresa Amabile, in her Harvard Business Review research "The Progress Principle," found that the moment people feel the most motivation and happiness at work is not grand success but a day on which they made meaningful small progress. The feeling of small progress accumulating is what keeps people moving.

So I don't delete finished tasks; I gather them in "Done." On a draining day, looking at Done — "I've come this far" — gives strength back. Each checkmark is a small cheer.

Let me add one more small psychological device. At day's end, make a habit of looking first at "what I did today" rather than "what I didn't." We instinctively fix our gaze on the unfinished — the Zeigarnik effect. But deliberately turn that gaze toward what's finished, and the day closes on progress rather than lack. The same day ending in "I didn't finish" versus "I did this much" produces entirely different motivation the next morning.

Savoring small wins is not self-consolation. It is an utterly practical act of refueling for the next step.

How to grow the joy of completion
- Split tasks to a finishable size (within half a day)
- Mark them done immediately and savor it for a moment
- Don't erase completion records; collect them
- At day's end, skim what you finished

Beating the Three-Day Resolution — Not Three Days, a System

A new resolution that doesn't last three days — in Korean we call it "jaksim samil." But this isn't weak willpower. It's that the plan relies on motivation. Motivation, by nature, surges and dips like waves. A plan that works only on high-motivation days collapses on the low-motivation ones.

The fix is to lean on systems and small size instead of motivation. Motivation is good as a starting spark, but rely on it alone and you collapse when the spark dies. A system keeps you rolling even on days without motivation.

  • Assume a low-motivation day and define the minimum unit you can still do. ("Even on the worst day, I write one line.")
  • Lower the intensity of the resolution. "Two minutes a day" lasts far longer than "an hour a day." Once it continues, it naturally grows.
  • When you break the streak, don't self-flagellate; return the very next day. Missing once isn't the problem; missing twice in a row is.

To borrow James Clear's words, what matters is not "keeping it perfectly" but "the speed of getting back on track." Wobbled after three days? Start again on the fourth. Repeat your three-day resolution a hundred times and that's three hundred days.

A Dialogue Example — The Moment You Split the Overwhelm

Let me turn the principle into a concrete scene: a short dialogue with the overwhelmed self.

Stuck in overwhelm

Me (A): This project is so big I don't know where to start.
Me (B): Shouldn't I grasp the whole thing and make a perfect plan first?
Me (A): Right... but that's daunting too. I'll really do it tomorrow.
(Tomorrow comes and the same dialogue repeats)

Splitting it

Me (A): This project is so big I don't know where to start.
Me (B): Forget the whole for a second. What's the smallest thing
        you could finish in the next thirty minutes?
Me (A): Hmm... maybe listing the features I'll need?
Me (B): Good. Then just do that now. Think about the rest after.
Me (A): That much I can do. Let me start.

The difference is clear. The first is trapped in "the whole" and "perfect," and can't take a single step. The second sets the whole down for a moment and narrows its gaze to the one "smallest thing I can do now." Once that step is taken, the next is far easier.

The magic question to ask yourself is this: "Right now, what is the smallest piece I could finish within thirty minutes?" This question is the fastest switch for turning overwhelm into action.

A Practice Routine — A Frame That Rolls the Day

Let me bundle the principles into a daily routine.

[A routine that rolls the day]
Morning (10 min)
  - 5-min review of yesterday -> context recovery, momentum
  - Pick one MIT + 3-4 small pieces for today
Late morning (focus block)
  - Start with the MIT, one at a time, deeply
  - Any other task that surfaces goes to the inbox (not now)
Afternoon (focus block)
  - Conquer the remaining pieces one by one
  - Stuck? "Just two minutes," or split it smaller
Evening (10 min)
  - Move finished items to Done, savor the wins
  - Move unfinished to tomorrow, write one line for tomorrow's start

The key to this routine is that no single step is grand. Everything is small and unintimidating. Yet when these small things connect every day, the big tasks end up finished. Not a flashy explosion but a quiet continuity goes farther in the end.

Closing — You Can Do It All

Let's return to the beginning. The overwhelm before a big task is a lie. The task isn't hard; you're just seeing it as one giant lump.

Break it small. Break it until the urge to procrastinate disappears. Then move forward one at a time, deeply, connected to yesterday, savoring what you finish — small enough that even a low-motivation day can't topple you.

Let's recall what we covered, one line each. Overwhelm arises from seeing big, and divide and conquer splits the big into self-evident pieces. Procrastination is emotional avoidance, and the two-minute rule and a small start disarm it. Momentum comes from connecting yesterday to today, and perfectionism dissolves into "making it exist." A tracking system gives a place to set other tasks down with peace of mind, and priorities defend what matters. The joy of completion fuels the next step, and the three-day resolution is overcome by the speed of returning. It all runs along one grain: don't see big; break it small; don't stop.

Then you really can do it all. Not grand willpower but small pieces and an unbroken continuity carry us to the end. Keep at it today too. When overwhelmed, just start with the single smallest piece. Starting isn't half the battle — starting is almost the whole of it.

Finally, be gentle with yourself. Some days you'll finish not even one piece. That's fine. What matters is not never wavering but returning to the smallest piece after you waver. If you can repeat that small return, you're already someone who can do it all.

Checklist — Finishing Without Procrastinating

Divide and Conquer self-check
[ ] Did I split the overwhelming task small enough that I don't want to put it off?
[ ] Can I start the smallest first piece within two minutes?
[ ] When stopping, did I write one line for "tomorrow's start"?
[ ] Did I do a 5-min review of yesterday this morning?
[ ] Am I focused on only one piece at a time right now?
[ ] Is every to-do in a tracking system rather than my head?
[ ] Did I keep the Today list short, 3-5 items?
[ ] Did I set one MIT (most important task) for today?
[ ] Did I mark finished items and savor the achievement?
[ ] When I broke the streak, did I return the next day instead of blaming myself?

References

Discuss on Twitter • View on GitHub