How many projects can one person realistically run at once?

TL;DR: For most people, two or three meaningful projects at once is a realistic ceiling. Three to five can work when the projects are small and mostly in execution. The more reliable answer comes from your hours: add up what each project needs per week, keep about 20% of your time unplanned, and see how many fit.

It depends; life itself is a project, I think, as many as they want, but there is a trade-off: the more projects you start, the slower you would go.

Is there a research-backed number?

The closest thing to one is two. A 2015 study of concurrent projects concluded that in R&D organisations "two projects are optimal" and that people "should not work simultaneously on four or more projects"^[1].

That finding has limits. The study focused largely on project managers in high-technology environments^[1], so treat it as good evidence for complex, demanding work. It doesn't settle the question for a student, a freelancer or someone running small personal projects.

Practitioner guidance is looser. One guide says most project managers can handle two to five projects at a time, depending on complexity, team size and available tools^[2]. Another puts the range at three to five and says the number depends more on decision cost than on project size^[3]. A third cautions that more than three to four significant projects at once may limit how well one person can manage them^[4].

These are rules of thumb from people who work in the field. They overlap, and the overlap sits around two to four.

Why do the estimates disagree so much?

Because "one project" can mean almost anything. A thesis and a monthly newsletter both count as one project, and they cost very different amounts of attention.

Role matters too. Someone coordinating a team can carry more projects than someone doing most of the hands-on work^[1][5]. If you write every chapter or answer every client email yourself, each project takes a bigger share of your week.

This is why counting projects on its own misleads. Project-management effort scales with scope and duration^[5]. A small, stable project might take two hours a week. A large one that's early-stage or behind schedule can take your whole week.

What about surveys showing people with ten or more projects?

Those figures describe the workloads people are assigned. They say nothing about how well those projects get finished.

One survey reported that 59% of respondents manage between two and five projects, 11% handle six to ten, and 15% oversee ten or more^[6]. Another found that 85% of project managers work on at least two projects at once, with 15% saying they have more than ten on the go^[7].

It's tempting to read that as permission. If 15% of people run ten projects, maybe you can too. The surveys don't say whether those people deliver on time, how many of the projects are stalled, or what it costs them. Use these numbers as context about how common heavy workloads are, and leave them out of your target.

How do you work out your own number?

Start from hours, and count projects afterwards. The steps:

1. List every project you consider active. Be honest: if it's on your mind every week, it counts.
2. Estimate the weekly hours each one needs to move at the pace you've promised.
3. Add overhead for coordination: emails, check-ins, planning, picking the work back up.
4. Compare the total with the time you have, minus a buffer.

For the overhead step, one worked example assumes project management takes 15% of a project's effort hours, so a 1,000-hour project needs about 150 hours of the manager's time^[5]. The same example then checks whether those hours fit within a 32-hour workweek^[5]. You can use the same method on your own week, even if you're the only person on the project.

For the buffer, one project-management guide recommends scheduling yourself to no more than 80% of capacity^[8]. The remaining 20% is there for interruptions and unplanned work.

Here is a made-up example to show the arithmetic. Say you have 30 hours a week for project work. At 80%, you plan 24. A thesis chapter needs 12 hours a week. A client project needs 8. A side project needs 4. That's 24, and you're full. A fourth project means one of the others slows down, whether you decide that or it happens on its own.

When should one project count as two?

When it demands frequent decisions or recovery work. Practitioner ranges are meant to shrink when projects are complex, early-stage, politically sensitive or off track^[2][3].

In practice, give extra weight to:

• A project you're starting from scratch, where every week involves choices about scope and direction.
• A project that has slipped and needs rescuing.
• A project with a difficult stakeholder, where every update takes thought.
• A project that keeps waking you at 2am.

A project in steady execution, where you know the next ten tasks, is cheap by comparison. Two of those can cost less than one project in its first month.

What if your attention is hard to steer, as with ADHD?

The research in this area doesn't look at ADHD, so there's no evidence-based number to give you. What follows is practical advice.

Each active project is another thing your brain checks on. If switching between tasks is costly for you, extra projects cost more than their hours suggest, because each switch means rebuilding context. Two projects with long, protected blocks often go further than four projects squeezed into the same week.

It helps to keep two lists: active and parked. Active projects get time on the calendar this week. Parked projects get a single line describing where you stopped and what the next step is. That line lets you put a project down without the worry that you'll lose it. If attention or workload is affecting your health, a clinician is the right person to talk to.

How do you keep the active list small?

Make each active project concrete enough that the next step is obvious. Vague projects feel bigger and pull at you more. "Work on the thesis" sits in your head all day. "Draft the methods section intro, 45 minutes" can be started and finished.

TimeBud is built around this. It breaks a goal into jobs with minute estimates and dependencies, then plans today around your calendar, filling only open time and leaving breathing room after events. When the hours don't fit, you see it in the plan before the week gets away from you.

When a new project arrives, decide on the spot whether it's active or parked. If it's active, something else has to slow down or pause. Write down which one. A short capture beats holding it in your head, and Bud in TimeBud can file quick captures like that so they stop competing for attention while you work through your current queue.

If you run the hours test and land on two, that's a normal result. Plenty of people do their best work with two projects moving and the rest written down and waiting.

Try TimeBud free