A simple project plan for one person
Updated
A simple project plan fits on one page. It says what you are trying to get done, how you will know it is done, what is in and what is out, the first few steps, and what could go wrong. For one person that is enough planning to start, and little enough that you will actually write it.
Why one person needs a plan at all
Team plans exist so that many people can agree on the same thing. Yours has a smaller audience: you, three weeks from now, on a tired Tuesday evening, wondering what this project was supposed to be.
Without a plan, personal projects tend to fail in two predictable ways. They grow, because every good idea gets added. Or they fade, because there is no clear finish line and no obvious next step. A short plan fixes both. It is also the cheapest part of personal project management: ten minutes of writing that saves weeks of drifting.
The five parts
A simple project management plan for one person needs five things. The example running through this guide is a real kind of project with no software in it: turning a pile of family recipes into a small printed book.
1. The outcome
One sentence describing the result, not the activity. "Work on the recipe book" is an activity. "A printed book of thirty family recipes, one copy for each sibling" is an outcome. If you cannot write the sentence, you do not have a project yet. You have an interest.
2. What done means
Two to five checks you could tick off at the end. They turn a vague finish line into a real one.
- Every recipe has been cooked once from the written version.
- The layout is proofread by someone other than you.
- The books are printed and handed out.
3. In and out of scope
Write both lists. The "out" list matters more, because it is where you park the good ideas that would otherwise stretch the project forever. Photos of every dish? Out, for this version. A second volume with desserts? Out. You can always start another project later.
4. The first tickets
Three to seven concrete steps to get moving. Not the whole project, just the beginning. The rest will show up as you work, and trying to list it all up front is how planning turns into procrastination. If a step feels too big to start, it is probably a small project of its own; the guide on project vs task explains how to tell.
5. Risks and open questions
What could stop you, and what you do not know yet. Keep it honest and short. "Grandma's handwriting is hard to read." "No idea what printing costs." Each open question is a candidate for an early ticket, because answering it removes a reason to stall.
A one-page template
Copy this into the first ticket of a new project and fill it in:
PROJECT PLAN Outcome (one sentence): Done means: - - - In scope: - Out of scope (for now): - First tickets: 1. 2. 3. Risks and open questions: - Review on: (a date, or "at the weekly review")
And here is the recipe book, filled in:
Outcome: A printed book of 30 family recipes, one copy per sibling. Done means: - Every recipe cooked once from the written version - Layout proofread by someone else - Books printed and handed out In scope: 30 recipes, simple layout, short note per recipe Out of scope (for now): photos of every dish, desserts volume First tickets: 1. Collect all recipe cards in one box 2. Pick the 30 recipes 3. Type up the first five 4. Ask two print shops for a price Risks and open questions: - Some cards are hard to read - Printing cost unknown
Keeping the plan alive
A plan you never read again is just a nice document. Keep it where the work is, as the first ticket in the project, not in a separate file you have to remember. Then look at it on a schedule. A short weekly review is the natural place: read the outcome, check the done list, and ask whether anything should move from "in" to "out".
When something changes, change the plan. Adding a recipe is fine. Adding a second book is a new project. The plan is not a contract with yourself. It is a note that keeps the project the size you meant it to be.
If an AI agent helps with a project, the plan doubles as its brief. The outcome and the done list tell it what finished looks like, and the out of scope list tells it what to leave alone.
Common mistakes
- Planning every step. List the first few. The plan is a start, not a script.
- No "out" list. Without it, scope only ever grows.
- An outcome that is really an activity. "Learn Spanish" never ends. "Hold a ten-minute conversation in Spanish" does.
- Skipping the risks. The thing you avoided writing down is usually the thing that stalls you.
When you can skip the plan
Not everything needs one. If the whole job fits in a single afternoon, or is really one task with a few steps, just make a ticket and do it. A simple project plan earns its ten minutes when the work stretches over weeks, when you will stop and restart it several times, or when it has more than a handful of moving parts. A good rule: if you would struggle to explain what finished looks like, write the plan first.
Putting it to work
Once the plan exists, the project becomes a list of tickets you can work through. Very Simple Projects is a simple personal project management app built for exactly that: projects, numbered tickets, a star, labels, a thread on every ticket, and six statuses you can add to. Put your plan in the first ticket and the rest follows. It costs $0.99 a month, and the first month is free.