A big project on your list feels less like a task and more like a weather system. You know it matters. You also know opening it means an hour of planning you do not have tonight. So you scroll instead. Tomorrow the project is still there, still huge, still vague.

You do not need a perfect plan. You need a small map and one step for tomorrow morning. Three questions. Five minutes on your phone. Done.

What project-breakdown guides usually miss

After reading the top results on breaking big projects into smaller tasks, the same gaps show up:

  • They teach corporate jargon. Work breakdown structures, deliverable matrices, stakeholder maps. Helpful in a conference room. Overkill when your project is "study for midterm" or "launch Etsy shop."
  • They assume a desktop and a whiteboard. Miro boards, Notion templates, sticky notes on a wall. Real beginners plan on a phone between classes, shifts, or bedtime.
  • They generate too many subtasks on day one. Twenty bullet points feel productive for ten minutes. Then you stare at the list, pick none of them, and call it "planning."
  • They never hide the rest. Every subtask stays visible forever. Your brain treats a forty-item project like forty separate fires.
  • They stop at the breakdown. Great, you have chunks. Nobody tells you which single task goes on Today and which chunks stay in the parking lot until next week.

This guide is the opposite: Outcome, Chunks, First Move. Three questions, three to five chunks max, one task promoted to Tomorrow.

The 3-question system (Outcome, Chunks, First Move)

Open a blank note on your phone. Answer these in order. Do not open five apps. One note is enough.

  1. Outcome (one sentence). What does "done" look like? Not vibes. A finish line. "Portfolio site live with three case studies and a contact form." "Midterm studied enough to explain chapters 4-7 out loud." If you cannot picture done, the project is still too fuzzy. Shrink the scope until you can.
  2. Chunks (three to five items). List the big phases between here and done. Not micro-steps. Chunks. "Gather screenshots, write case study copy, build pages, test on phone, publish." Five lines max. If you hit six, combine two. Chunks are chapters, not paragraphs.
  3. First Move (two minutes). Look at chunk one only. What is the smallest physical action you could finish in two minutes? "Screenshot three old projects from camera roll." "Open study guide and highlight chapter 4 headers." That move becomes tomorrow's only project task on Today. Everything else stays in the note until chunk one is done.

Full example on screen: Outcome at the top, five chunks in the middle, one starred first move at the bottom. Ten minutes. The project is still big. But tomorrow you are not doing the project. You are doing one two-minute move.

The "one chunk visible" rule

Breakdown fails when every chunk fights for attention at once. After you list chunks, hide all but chunk one. Move chunks two through five to a "Later" note, a Someday list, or the bottom of the same doc behind a line that says "not yet."

When chunk one is done, promote chunk two. Rewrite its first move. One new task on Today. Repeat.

This is the phone version of a kanban board with one card in Doing. Your brain can carry one active phase. It cannot carry five while also answering texts and making dinner.

Example: a student with "finish research paper"

Jae has had "research paper" on the list for two weeks. Every breakdown attempt turned into twelve micro-tasks and zero writing. Here is the three-question pass:

  • Outcome: "Eight-page draft submitted on Canvas by March 14 with bibliography."
  • Chunks: (1) Pick thesis and sources, (2) Outline, (3) Rough draft, (4) Revise, (5) Format and submit.
  • First Move: "Open library database and save three PDFs to Files." Two minutes. Starred on Today.

Chunks two through five stay in the note, out of sight. Jae's Today list shows one task, not a wall of guilt. After three PDFs are saved, chunk one gets a new first move: "Paste three quotes into outline doc." Motion beats another planning session.

Five-minute phone drill (do this tonight)

  1. Minute 1: Pick the scariest project on your list. Say its name out loud.
  2. Minutes 2-3: Answer Outcome and Chunks in one note. Stop at five chunks even if your brain wants twelve.
  3. Minute 4: Write the First Move for chunk one. Must be physical and under two minutes.
  4. Minute 5: Add only the First Move to Tomorrow or Today. Hide every other chunk. Close the note.

Run this drill once per scary project. Not every task on your list needs a breakdown. Groceries do not. "Launch side business" does.

Where Divux fits (chunks in notes, one task on Today)

Breakdown breaks when your chunks live in Notes, your tasks live in Reminders, and your calendar never saw the deadline. You planned beautifully and still forgot to do the two-minute move.

Divux keeps notes, tasks, calendar, and a focus timer on one daily view. Dump Outcome and Chunks in a quick note. Promote the First Move to Today. Block thirty minutes on the calendar if chunk one needs a longer push. Everything stays on one screen so planning turns into doing.

That combo, hidden chunks plus one visible task, is what Divux is built for. Break the project down once. Execute it one chunk at a time.

When the first move still feels impossible, pair this system with our guide on starting tasks when you feel stuck. Outcome-Chunks-First Move picks the step. Name-Shrink-Start gets your hands moving.

Common mistakes (and quick fixes)

  • Writing micro-tasks on day one. "Email professor," "buy highlighters," "fix typo on page 3" belong inside chunks later. Day one is phases only.
  • Leaving all chunks on Today. One chunk visible. The rest are not today's problem.
  • Vague outcomes. "Do better on paper" is not done. "Submit eight pages" is. Rewrite until a stranger could check the box.
  • Re-planning instead of finishing chunk one. If you have replanned the same project three times, your first move is too big. Shrink it again.
  • Breaking down every little task. Reserve this system for projects that span days or weeks. "Call dentist" does not need five chunks.

Frequently asked questions

How many subtasks should a big project have?

Start with three to five chunks, not twenty micro-tasks. Each chunk should be a phase you could explain in one sentence. Hide the rest until the active chunk is done. More detail comes later, not on day one.

What is the fastest way to break down a project on your phone?

Ask three questions: What does done look like in one sentence? What are three to five chunks between here and done? What is the first two-minute move inside chunk one? Write the answers in a note, promote one move to your Today list, and hide the other chunks.

Why do I break projects into tasks but still never start?

You probably built a beautiful map and left every road visible at once. Your brain needs one active chunk and one first move on Today, not a wall of subtasks. Breakdown is for clarity. Your daily list is for motion.