Project Planning Basics for Personal Goals

Most personal goals are actually projects in disguise. “Write a novel” is not a single task — it is a multi-month project with research, outlining, drafting, revising, and editing phases. “Renovate the kitchen” involves budgeting, planning, sourcing materials, hiring contractors, and managing timelines. Treating projects like tasks is why people stall: the goal feels too large to start.

The fix is borrowed from professional project management: break the project into phases, the phases into milestones, and the milestones into individual tasks that fit into a single work session.

The Work Breakdown Structure

Professional project managers use a tool called a Work Breakdown Structure (WBS) — a hierarchical decomposition of everything that needs to happen. For personal goals, a simplified version works perfectly.

Level 1: The goal. “Complete an online MBA application by November 15.”

Level 2: Phases. Research schools (2 weeks), prepare application materials (4 weeks), write essays (3 weeks), request recommendations (2 weeks), submit and verify (1 week).

Level 3: Tasks within each phase.

• Research schools: identify 8 target programs, compare tuition and requirements, attend 3 virtual info sessions, narrow to 4 schools
• Prepare materials: update resume, order transcripts, take GMAT practice test, schedule and take GMAT
• Write essays: outline each school’s required essays, draft all essays, revise with feedback, final polish

Level 4: Actions within each task. “Identify 8 target programs” becomes: search MBA ranking sites for 30 minutes, read program pages for top 12 schools, create comparison spreadsheet, narrow to 8 based on criteria.

Each Level 4 action fits into a single sitting — typically 30 to 90 minutes. These are the items that appear on your daily plan.

Sequencing and Dependencies

Not all tasks can happen simultaneously. You cannot write application essays before you know each school’s essay prompts (which come from the research phase). You cannot submit the application before you have GMAT scores.

Map these dependencies by asking: “What must be complete before I can start this task?” Draw arrows between dependent tasks or simply list them in the order they must happen.

Some tasks are independent and can run in parallel. While waiting for GMAT scores, you can draft essays and request recommendation letters. Identifying parallel tracks lets you make progress on multiple fronts without being blocked by a single dependency.

Estimating Time

For each task, estimate how long it will take. Personal project estimates are notoriously optimistic, so apply the planning fallacy buffer: take your honest estimate and multiply by 1.5.

If you think drafting your MBA essays will take 6 hours, budget 9. If you think the GMAT study plan is a 40-hour investment, budget 60. This buffer absorbs the unexpected complications that always arise — a school changes its essay prompts, the transcript office is slow, you bomb the first practice test and need more study time.

Plot the buffered estimates against your available time using reverse engineering. If the math does not work — if you need 120 hours but only have 80 hours available before the deadline — either extend the timeline, reduce the scope, or increase the weekly hours dedicated to the project.

Weekly Milestones

Convert your task timeline into weekly checkpoints. Each week should have a clear deliverable:

• Week 1: Research complete, 8 schools identified
• Week 2: Comparison spreadsheet done, 4 schools selected
• Week 3: Resume updated, transcripts ordered
• Week 4: GMAT practice test taken, study plan created

These milestones become the items you review during your Sunday weekly review. If you miss a milestone, you know immediately and can adjust the following week — either catching up or accepting a delay and rescheduling downstream milestones.

Tools for Personal Project Planning

You do not need professional project management software for personal goals. The complexity does not warrant it, and the overhead of maintaining a Gantt chart for a personal project is demoralizing.

Notebook method. Write the project breakdown on two to three pages. One page for the phases and milestones, one page for the current week’s tasks, and one page for notes and ideas. Update weekly.

Simple digital list. A note-taking app with nested lists (Notion, Apple Notes, Google Docs) provides enough hierarchy for a personal project. Indent tasks under milestones under phases.

Calendar blocking. For time-sensitive projects, place each milestone on your calendar as a deadline event. This makes deadlines visible alongside your regular commitments and prevents the “I forgot about my project” problem.

Avoid the temptation to spend two hours setting up a project management tool when the project itself will only take 20 hours. The tool should take less than 15 minutes to set up and less than 5 minutes per week to maintain.

When Projects Stall

Every personal project hits a stall point — a phase where progress stops and the project sits untouched for days or weeks. Common stall triggers:

Ambiguity. The next task is not clear enough to start. Fix by breaking it down further until the next action is a single, concrete step you can complete in 30 minutes.

A daunting task. One large task blocks the entire project because you keep avoiding it. Fix by breaking the daunting task into smaller pieces and starting with the smallest, easiest piece.

Lost momentum. You got busy with other things and the project lost priority. Fix by re-engaging with one small task during your next Power Hour to rebuild momentum.

Scope creep. The project keeps expanding with new ideas and additions. Fix by writing all new ideas on a “later” list and sticking to the original scope until the core project is complete.

Personal projects completed are worth infinitely more than personal projects planned. The planning structure described here exists to move you from planning into doing — and to keep you doing until the project is done.