BlueprintIs it a project or a habit? Decide before you plan it
A project ends. A habit repeats. That is the whole distinction, and it matters because the two are planned, measured and finished in different ways. Before you write a single task, ask the question: when this is done, will I stop? If yes, it is a project. If the honest answer is "I hope I never stop", it is a habit, and a project app is the wrong place for it.
The test
Three questions settle almost every case.
Does it have an end state you could describe in one sentence? "The spare room is an office with a desk, a chair, and a working lamp." That is a project. "I want to keep the flat tidy" has no end state. Habit.
Would you be disappointed if it kept going? A project that runs past its end is late. A habit that keeps going is working. If continuing feels like failure, it is a project.
Is the work the same each time or different each time? Projects are made of different tasks that add up: measure the room, order the desk, build the desk, run the cable. Habits are made of the same task again: walk, write, stretch, cook. Same work, repeated, is a habit even if you have given it a fancy name.
Three examples that fool people
"Learn Spanish." Sounds like a habit, because it never really ends. But "reach the point where I can order a meal and ask directions" is a project with an end state, and it is a much better thing to plan. Set that as the finish line, put milestones under it, and close it when you get there. Then daily practice becomes a habit with its own tracker, and the project's success is real rather than permanently deferred.
"Get fit." This one hides a project inside a habit. The habit is training three times a week. The project is the first eight weeks in which you find a routine you can keep. Plan those eight weeks as a project, and let the habit take over at the end. Our sister site Aura's habit ROI calculator is a fair way to check whether the daily version is worth the time before you commit to it.
"Do 75 Hard." A named challenge with fixed rules and a fixed length is a project, whatever it looks like from the inside. It has an end date, a definition of done, and a clear failure condition. Track the daily rules as repetitions, but plan the whole thing as a project with a start and an end. The team's other site, Unbroken, keeps a free 75 Hard tracker that treats it exactly that way, day count and rules in one place.
How planning changes once you know
A project gets milestones, owners, and time tracked against it. The question you ask each week is "what is the next action, and is the end date still true?" You expect the list of tasks to shrink to zero. When it does, you close it, and closing it is a real event. That is what Blueprint is for: projects with an end, each with milestones and time logged, so you can see what a thing actually cost once it is done.
A habit gets a streak, a rhythm, and a very small definition of a rep. The question each week is "did it happen, and how often?" You do not expect the list to shrink. You expect the count to grow. The measure of a good habit week is that nothing interesting happened.
Mixing the two is where plans rot. A habit filed as a project sits open for a year with no milestone ever reached, which feels like failure even though the habit is working. A project filed as a habit gets "worked on" every day without a definition of done, and never ends.
When a project produces a habit
The usual path is project first, habit after. The project builds the thing: the office, the routine, the ten dinners you can cook without a recipe. The habit maintains it. Plan the build with an end. On the day you close it, decide what the maintenance rep is, how often, and where you will count it.
That handover is worth doing on purpose. Write it as the last task of the project: "Set up the daily version and close this." Then the project ends cleanly and the habit starts with a definition rather than a vague intention.
Small wins live in both
One thing both kinds share: the day feels better when something got finished, however small. A project gives you that when a milestone closes. A habit gives you it when the rep is done. On days when neither happens, it helps to have a place to write down the one thing that did. Aura's free daily wins page exists for that: a line a day, no streak to protect, no scoring. It is the anti-shame end of the same idea, and it pairs well with a project board that only shows what is left.
FAQ
Can something start as a project and become a habit?
Yes, and that is the usual path. Learning to cook ten dinners is a project. Cooking on weeknights afterwards is a habit. Plan the learning as a project with an end, then hand the repetition to a habit tracker and close the project.
What about a goal like running a marathon?
The race is a project: it has a date and a finish line. The training is a habit with a deadline attached. Track the runs as repetitions and the race as a milestone. When the race is done the project closes, and you decide separately whether the running habit continues.
Why does it matter which one I call it?
Because they fail differently. A project fails when it never ends. A habit fails when it stops repeating. If you treat a habit like a project you will look for a finish line that does not exist and give up. If you treat a project like a habit you will keep it open for years.