Project vs task: what is the difference?

Project vs task sounds like a question for a textbook, but getting it wrong is the most common reason a personal system stops working. A project has an outcome and an end. A task, or a ticket, is one step toward it, or one problem inside it. Mix the two up and you get tasks that never finish and projects that never start.

The short definitions

• A project is a result you want, that takes more than one step, and that can be finished. "Move the blog to a new host." "Ship version 2 of the app." "Renovate the bathroom."
• A task is one piece of work you can do and then call done. "Export the old posts." "Fix the login bug on Android." "Choose tiles."

In ticket-based tools, a task is usually called a ticket or an issue. The difference in naming does not matter much. What matters is the size, and whether it ends.

Four tests to tell them apart

When you are unsure whether something is a project or a task, ask:

1. Can I do it in one sitting? If yes, it is almost certainly a task. If it takes many sittings with different kinds of work, it is probably a project.
2. Do I know the first step? If you can start right now without thinking, it is a task. If you first have to figure out what to do, you are looking at a project, or at least a task that needs splitting.
3. Can I say when it is finished? Both projects and tasks should pass this test. If neither answer is clear, it is an area of responsibility, not a project. More on that below.
4. Would it contain other things I need to track? If you can already imagine five sub-steps you will want to tick off, make it a project.

Mistake one: a project called "Work"

"Work", "Health", "House" and "Side projects" are not projects. They never finish. They are areas of your life, and they are useful as a way to think, but they make bad containers for tickets.

The problem shows up over time. A project called "House" collects every idea you have ever had about the house. It never gets shorter, nothing ever feels done, and after a few months you stop opening it. Compare that with "Fix the leaking gutter" or "Paint the hallway", which you can finish and close.

A good project name describes the outcome. If you cannot imagine the day you close it, rename it until you can.

Mistake two: a ticket that is really a project

The opposite mistake is just as common. A ticket titled "Build the new website" or "Launch the app" sits in the list for weeks. It is always in progress, it never gets done, and it quietly makes the rest of the list feel stuck.

Signs a ticket is really a project:

• It has been in progress for more than two weeks.
• Its thread has turned into a long to-do list.
• You feel slightly tired every time you read the title.
• You could not say what "done" means for it without a paragraph.

How to split a ticket that is too big

When a ticket turns out to be a project, you have two options. Promote it to its own project, or split it into smaller tickets inside the project you already have.

A simple way to split:

1. Write down what done looks like. One or two sentences. "The new site is live on the real domain and the old one redirects."
2. List the steps that lead there. Do not order them yet. Just write them as short titles.
3. Check each step with the one-sitting test. If a step still fails it, split it again.
4. Create a ticket per step. One problem or one piece of work each.
5. Close or cancel the original. Leave a note in its thread listing the new tickets, so the history makes sense later.

If you use ticket numbers, the note is easy to write: "Split into 14, 15, 16 and 17."

Why the difference matters more with an agent

If an AI agent works on your project, the project vs task question becomes practical, not academic. An agent does good work on a clear, bounded ticket: one bug, one change, one question. Handed a ticket that is really a project, it tends to either do too much at once or stop and ask what you meant.

So keep tickets small enough that "done" is obvious, and ask the agent to file one ticket per problem it finds rather than one big ticket for everything. More on handing work over in managing AI agents when you work alone.

Project vs task, in one line each

• Project: an outcome with an end. It holds tickets.
• Task or ticket: one step or one problem. You can finish it in a sitting.
• Area: a part of your life that never ends. Useful to think with, not a place to put tickets.

For the bigger picture of running your own projects this way, start with what personal project management is. And if you want a tool that follows the same shape, Very Simple Projects is a simple personal project management app: projects you can finish, numbered tickets inside each one, a few statuses, and a thread per ticket. It costs $0.99 a month, with the first month free.