How to manage multiple projects at once, on your own
Updated
Most advice on how to manage multiple projects is written for a manager with a team, a portfolio and a status meeting. This guide is for one person. A job, two side projects, a website that needs fixing, and a bathroom that has been almost finished since spring. Nobody reports to you, and nobody will notice if a project quietly stops. That is exactly the problem.
Why several projects feel harder than one big one
One big project is heavy, but it is clear. You know what you are working on. Several smaller projects are lighter each, but together they create a different kind of load: switching. Every time you move from one to another you have to remember where you were, what you decided, and what you were waiting for.
So when you work out how to manage multiple projects at once, the goal is not to squeeze more hours out of the week. It is to make each switch cheap. You should be able to open a project after three weeks away and know within a minute what to do next.
Keep one list of projects
Start with a single list of everything you consider a project. Not a list per area of life, and not projects scattered across a notes app, a whiteboard and your email. One list, in one place.
A project belongs on the list if it has an outcome and can be finished. "Launch the new portfolio site" is a project. "Work" is not. If you are unsure where the line goes, project vs task covers it in more detail.
Seeing the whole list is useful on its own. It is often the first time you admit that there are eleven projects, not four.
Limit how many are active
This is the part that does the most work. Decide how many projects can be active at the same time, and keep to it. For most people with a full-time job, two or three is plenty. Everything else is parked.
An active project is one you intend to move forward this week. A parked project still exists, keeps all its tickets and notes, and waits. Parking is not failure. It is a decision you made on purpose, which is better than a project that stalls by accident and makes you feel bad every time you see it.
The limit feels strict for about a week. After that it feels like relief, because you stop carrying the parked projects around in your head.
Give every active project one next ticket
Inside each active project, keep a list of tickets: one per problem or piece of work, each with a short title. Then make sure exactly one of them is the obvious next thing. Mark it in progress, or give it a star.
The next ticket should be small enough to start in a spare hour. "Redesign the site" is not a next ticket. "Pick a font for headings" is. When the next ticket is concrete, starting costs nothing, and that is what keeps a project alive between busy weeks.
A few habits help:
- Write tickets the moment you think of them. A title and two lines is enough. Polish later, or never.
- Leave a note when you stop. One line in the ticket's thread about where you left off saves ten minutes of rereading next time.
- Mark what you are waiting for. If a ticket is blocked on a reply, a delivery or a decision, say so. That is the first thing to check when you come back.
Park projects without guilt
Some projects will not happen this year. Some will never happen. Both are fine, as long as you decide it. When you park a project, write one line about why and what would make it worth picking up again. When you give up on one, close its open tickets as cancelled rather than deleting them, so the history is still there if you change your mind.
A project list with honest statuses is far more useful than one where everything is technically active and nothing moves.
Do a short weekly pass
Once a week, go through the list. It does not need to take long. For each active project, read the open tickets, close what is done, and check that there is a clear next ticket. Look at the parked projects and ask if one of them should swap places with an active one.
The weekly review guide has a checklist you can copy. The point is that the decisions about what is active happen once a week, calmly, and not every evening in a panic.
If an AI agent helps with some of the work
Many people now run one or more of their projects with help from an AI agent, for example a coding assistant that fixes bugs on a side project. That adds a second source of work, and it needs the same structure.
Give the agent one project, not access to everything. Let it file a ticket per problem it finds and write what it did in the ticket's thread. Then your weekly pass covers the agent's work as well: you read what it reported, reply where it is waiting on you, and decide what matters. The agent helps you move a project forward. It does not get to decide how many projects you run.
A short version
- Put every project in one list.
- Choose two or three active projects. Park the rest on purpose.
- Keep one small, obvious next ticket in each active project.
- Leave a note when you stop, and mark what you are waiting for.
- Once a week, review the list and swap projects if needed.
That is most of how to manage multiple projects on your own. It is one part of personal project management, and the method matters more than the tool, but the tool should not get in the way. Very Simple Projects is a simple personal project management app built for this: a list of projects, numbered tickets with a handful of statuses, a thread on every ticket, and room for an agent if you use one. It costs $0.99 a month, with the first month free.