A personal project has one thing a work project never has: nobody is waiting for it. No manager asks how it is going, no team is blocked by your part, and the deadline, if there is one, was set by you and can be moved by you. That freedom is why people start them. It is also why so many of them end quietly somewhere in the middle.
This is a way to plan one that borrows what works from project management and leaves out the parts that only exist to coordinate a team. It is written for an adult with a job and a few hours a week, not for a school assignment.
Why the middle is where projects die
Two things usually go wrong, and neither is laziness.
First, the plan measures the wrong thing. A list of twenty tasks with eight ticked reads as 40% done. If the eight were the quick ones, sign up for a domain, pick a name, buy the running shoes, the real work has barely started. Research on how people choose tasks under load found exactly this pattern: given the choice, people clear the easy tasks first, which raises the number completed while the hard work waits. That study looked at emergency-room doctors over six years, not hobbyists, but the pull is familiar to anyone with a to-do list.
Second, the first bad week gets read as a verdict. Relapse research calls it the abstinence-violation effect: one slip is taken as proof that the whole attempt has failed, so the person stops instead of restarting. It was described for addiction, and the same all-or-nothing reaction shows up in dieting and in anything else people try to keep up.
A good plan removes both traps. It counts hours, not boxes, and it expects missed weeks.
Step 1: write the finish line and the date
Not “learn Spanish” but “hold a 15-minute conversation with my Spanish neighbour by 1 March”. Not “launch the app” but “ten paying customers by the end of June”. A finish line you could photograph. Then a date.
If you get to pick the start, pick a landmark. Dai, Milkman and Riis found that people are more likely to start on a goal at the beginning of a week, a month or a year, or just after a birthday, and that “a new week” is enough. Monday is a fresh start; you do not have to wait for January.
Step 2: break it into three to five milestones
A milestone is a checkpoint you would notice passing: the lease is signed, the first long run is done, the beta is in someone else’s hands. Give each one a date that adds up to the finish line. Three to five is enough. More than that and the milestones become a task list with better formatting.
Step 3: turn each milestone into steps with hours
Under each milestone, list the steps, and put an honest hour estimate on every one. This is the part most planning skips, and it is the part that makes the rest work.
With hours on the steps you can answer the only question that matters in week six: am I on pace? Add up the hours done, compare them with the hours the plan has, and compare that with how much of the time has passed. If you have used 60% of the time and done 30% of the hours, you know now, while there is still time to change something. A box count cannot tell you this, because it does not know that “fit out the counter” is 25 hours and “order the sign” is one.
A rule of thumb for estimates: if you have never done the step before, write down your guess, then add half again. You will still be under. The point is not to be right; it is to make the hard steps visible next to the easy ones.
Step 4: put the steps in order
Some steps cannot start until another is done. You cannot hire baristas before the counter exists; you cannot taper before the long runs are in. Mark those. Everything else can be done in whatever order suits the week you are having, which is a freedom worth keeping.
What you do not need: a board with columns, a Gantt chart, a critical path. Those are tools for keeping several people from tripping over each other. You are one person.
Step 5: attach the daily habit that feeds it
Most personal projects are really a habit wearing a project’s clothes. The 10K is forty training runs. The book is a hundred writing sessions. The product is a few hundred hours of evenings.
So write the habit down next to the goal, and count its time toward the goal’s hours. A morning run that is “45 minutes, four times a week” is three hours a week toward the race. When the habit is linked to the project, a streak stops being decoration and becomes progress you can see.
Step 6: write the if-then plan for the obstacle
Name the most likely thing to get in the way. Then write one sentence in this shape: if that happens, then I will do this. “If I get home after 8pm, then I will do the 20-minute version instead of skipping.” “If a week goes by with no progress, then I will book two hours on Sunday and do the smallest step on the list.”
This is the best-evidenced trick in planning research. Gollwitzer and Sheeran’s meta-analysis of 94 tests found a medium-to-large effect on reaching goals, and a 2025 update across 642 tests confirmed it holds, with the size depending on how motivated you are and how the plan is worded. There is a longer piece on it here: the if-then plan.
Step 7: check the pace weekly, and plan the comeback in advance
Once a week, look at three numbers: hours done, hours planned, time used. That is the whole review. If the pace is behind, you have three honest moves: put in more hours, move the date, or cut scope. Pick one on purpose. Drifting is the fourth option, and it is the one that ends projects.
And decide now what a missed week means. It means the plan has one more data point, not that you are the kind of person who does not finish things. Write the comeback into the plan the way you wrote the obstacle: if I miss a week, then the next session is the smallest step, not the biggest. If you want the research behind that, it is in a missed day is data, not defeat.
What a personal project does not need
- A team tool. Boards, assignees, comments and permissions solve problems you do not have. They also add a layer of upkeep that competes with the project for your hours.
- Reminders every hour. A plan you look at once a week with honest numbers beats a phone that nags. If you need a nudge, make it the daily habit, not a notification.
- A perfect estimate. The estimates will be wrong. The pace check exists so that being wrong is visible in week three rather than week eleven.
How MileStone does this
MileStone is built for exactly this shape of project and nothing else. A goal holds milestones with dates; each milestone holds steps with hour estimates, costs and a “do this after” order; a daily habit can be linked to the goal so its time counts toward the pace. Progress is weighted by hours done, not steps ticked, and the goal page tells you whether the current pace reaches the date. When you create a goal it asks what could get in the way and what you will do when it does, and keeps the answer where you will see it. If you would rather not type the plan out, it writes a prompt for the AI you already use, and you paste the reply back as milestones, steps and hours.
It has no teams, no sharing, no boards and no calendar integration. That is on purpose. It is a planner for one person with a job and a project they mean to finish.
Questions people ask
How is a personal project different from a work project? Nobody is waiting for it. There is no manager, no team and no deadline set by someone else, so the plan has to supply the finish line, the checkpoints and the honest pace check that a workplace would otherwise provide. It also runs in the hours around a job, which is why estimating hours matters more than listing tasks.
Do I need project management software for a personal project? Not the team kind. Boards, assignees, comments and Gantt charts solve coordination problems you do not have when you are the only person. You need five things: a finish line with a date, three to five milestones, steps with hour estimates, the order they must happen in, and a way to see whether your pace still reaches the date. A notebook can do it; a planner built for one person does it with less bookkeeping.
Why do personal projects stall halfway? The most common pattern is that the easy steps get done first and the count of ticked boxes looks healthy while the hours that remain are the hard ones. When the plan then slips, one bad week gets read as proof the whole thing has failed. A plan that counts hours instead of boxes, and treats a missed week as data rather than a verdict, removes both traps.
Sources
- KC, D. S., Staats, B. R., Kouchaki, M., & Gino, F. (2020). Task selection and workload: A focus on completing easy tasks hurts performance. Management Science, 66(10), 4397–4416. (Emergency-department physicians plus a lab replication, not consumers.)
- Marlatt, G. A., & Gordon, J. R. (Eds.). (1985). Relapse Prevention: Maintenance Strategies in the Treatment of Addictive Behaviors. Guilford Press.
- Dai, H., Milkman, K. L., & Riis, J. (2014). The fresh start effect: Temporal landmarks motivate aspirational behavior. Management Science, 60(10), 2563–2582.
- Gollwitzer, P. M., & Sheeran, P. (2006). Implementation intentions and goal achievement: A meta-analysis of effects and processes. Advances in Experimental Social Psychology, 38, 69–119.
- Sheeran, P., Listrom, O., & Gollwitzer, P. M. (2025). The when and how of planning: Meta-analysis of the scope and components of implementation intentions in 642 tests. European Review of Social Psychology, 36(1), 162–194.