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

A Work Breakdown Structure (WBS) organizes a project’s scope into smaller components. NASA’s handbook describes a product-oriented hierarchy. For a personal application project, begin with the completed application package and break it into the research record, required documents, essays, recommendations, and submission evidence. Add tasks beneath those components.

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 early, and submit and verify (1 week). These are example planning allowances; actual requirements and lead times come from the selected programs.

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 the resume, obtain required transcripts, and check whether each program requires a test, accepts an existing result, or offers a waiver
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). Check each program’s current requirements before planning tests or documents; test requirements and submission rules differ by program.

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 can proceed independently. While waiting for a required transcript, you can draft essays using the published prompts and request recommendation letters. Identify which tasks are ready and whether your available sessions can accommodate them.

Estimating Time

For each task, estimate the effort and identify the source of uncertainty. Use your experience with comparable work where available. Add specific waiting periods for external documents or responses instead of applying one multiplier to every task.

If drafting an essay is expected to take six hours, reserve separate time for reviewing the prompt, obtaining feedback, and revising. Record which steps you can do while waiting for another person. Revisit the estimate after the first complete draft gives you better evidence.

Plot the estimates and any explicit contingency 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: Testing requirements resolved and any necessary preparation scheduled

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

Begin with a notebook, list, or spreadsheet. Add a more detailed scheduling tool when dependencies or coordination make it useful.

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. Place milestones and work sessions beside existing commitments. Link them to the relevant files and keep fixed external deadlines distinct from dates you can change.

Avoid the temptation to spend two hours setting up a project management tool when the project itself will only take 20 hours. Keep setup and maintenance proportionate to the work the tool helps you organize.

When Projects Stall

If progress stops, identify the obstacle before adding more tasks. Possible causes include:

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 priority. Other commitments took the available time. Decide whether the project still matters, then reserve a realistic session or change the deadline.

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.

A plan becomes useful when it makes the next action and the conditions for completion clear. The planning structure described here exists to move you from planning into doing — and to keep you doing until the project is done.

Keep an application requirements table

Create one row per program with the official application link, deadline and time zone, required documents, test policy, recommendation process, and submission confirmation method. Record the date you checked each requirement. Use the actual program page rather than assuming every application follows the same sequence.

Separate your actions from external responses. “Request transcript” can be completed today; “transcript received” is a later checkpoint. Add a follow-up date and preserve the confirmation number or receipt. Request recommendations early enough for the referee to make an informed commitment.

Check the final handoff

Before submitting, compare the finished materials with the requirement list. Verify names, word limits, file formats, and the selected program. Leave enough time to resolve a missing document or upload problem. After submission, save the confirmation and check whether the portal reports any outstanding items.

For a different personal project, keep the same structure: requirements, tasks, dependencies, completion evidence, and follow-up. A home archive might end with backed-up files and an index; a portfolio might end with working pages and a saved export. Define that endpoint before filling the calendar with activity.