What's the difference between many ideas and too many projects?

TL;DR: An idea is a possibility you have written down. A project is a commitment that is already drawing on your time, attention, decisions and sometimes money. Many ideas cost you little. Many active projects compete for the same limited capacity, so the useful move is to filter which ideas become projects and cap how many run at once.^[1][2]

Ideas need time to ripen; they need brainstorming sessions, planning, designing, and steps to get ready before starting. however projects need more commitment, even if they are only experiments. they have a start and finish line.

What counts as an idea, and what counts as a project?

An idea is something you could do. A project is something you have started and expect to keep doing, with work that needs your hours this week.

"Start a newsletter about bike repair" sitting in a notes app asks nothing of you today. Once you have set up the mailing list and told three people the first issue lands on Friday, it has become a project. It now has a deadline, decisions (which platform, which topic first) and dependencies (you can't send it until the list exists).

The practical test is whether the idea has crossed into active work. Writers on project portfolios and on innovation management describe the same pattern: trouble starts when too many ideas are allowed into the active stage at the same time.^[1][3] One puts the root cause in how many ideas get to the point where they become projects.^[1]

Why is having lots of ideas usually fine?

Ideas sit still. A list of forty ideas doesn't send you reminders or need a decision before Thursday.

That makes ideas cheap to keep. You can record them and queue them for later without spending much of your working capacity.^[1][3] Writing one down also means you can stop holding it in your head, which matters if your attention tends to grab every new thing that passes.

People with idea-heavy minds often hear that the ideas themselves are the problem. The sources in this area are more specific. One innovation article places the risk at the point of promotion: letting too many ideas into development at once.^[3]

What goes wrong when too many projects are active?

Active projects compete for the same hours and the same attention, and each move between them costs you time.

A guide on portfolio overload describes the issue as too much work competing for the same capacity.^[2] Your week has a fixed number of open hours. Four live projects don't each get a clean quarter of them. They get a quarter minus the cost of moving between them.

That moving cost is measurable. The American Psychological Association notes that a single switch between tasks may cost only a few tenths of a second, and that these costs add up when people switch back and forth repeatedly.^[4] An older APA summary of lab research found that participants lost time when switching for all types of tasks, and that the time lost grew as the tasks became more complex or unfamiliar.^[5] Most real projects are complex, and a project you haven't touched in a week is partly unfamiliar again.

There is a second cost on top of the switch itself. Repeated interruptions can make you lose track of the original task and spend time rebuilding where you were. One study described by the APA found that students averaged less than 6 minutes of studying before switching tasks.^[6]

In practice it looks like this. You have a two-hour gap on a Tuesday. The thesis chapter, a client invoice and the newsletter draft all want it. You open the chapter, remember the invoice, send it, check the newsletter, return to the chapter and spend fifteen minutes rereading your own notes to find the thread. Two hours pass and no single project moved much.

Is all multitasking harmful?

The evidence is mixed for habitual media multitasking, so be careful with sweeping claims. The stronger evidence is for the time cost of switching between active tasks.

A 2018 review of research on media multitaskers found it hard to see a clear pattern: a few studies showed positive effects, a few showed negative effects and more showed no effect.^[7] A 2025 study found no significant relationship between media multitasking and cognitive performance in the population it examined.^[8]

So the claim this post rests on is narrow. Unmanaged active work competing for your attention costs you time. Having a busy, idea-generating mind is a separate matter, and the research here doesn't say it harms you.

How many projects can one person run at once?

There is no universal number. The right ceiling depends on how complex the projects are, how much they depend on other people or on each other, how many decisions they need, how much time you have and whether they share resources.

The portfolio guide makes this point directly: the issue is capacity, and no magic number of projects fixes it.^[2] The research on switching costs is solid, but it doesn't give a personal limit on concurrent projects.^[4][7]

What follows is advice. No study backs a specific number. A reasonable starting point is to pick a small number of active projects (two or three for many people) and see whether each one moves forward every week. If one sits untouched for two weeks, it is effectively paused, and it's cleaner to pause it on purpose.

How do you decide when an idea becomes a project?

Keep ideas in a backlog, and promote one only when it passes a short test and there is room in your week.

A promotion test with four questions works well:

• Outcome: can you say what done looks like in one sentence?
• Next action: do you know the first job, small enough to start in one sitting?
• Owner: is it clear who does the work, including anyone you depend on?
• Capacity: is there open time in your calendar for it this week without taking hours from an active project?

If any answer is no, the idea stays in the backlog, which is a fine place for it. Review the backlog on a set day, say Friday afternoon, so ideas get a fair look without interrupting active work.

When the active list is full and a new idea passes the test, use a swap rule: one in, one out. Pause an active project before you start the new one. When you pause, write two lines: where you stopped and what the next job is. That note cuts the time you would otherwise spend reconstructing the task later, which is the cost the interruption research describes.^[6]

What does this look like inside a planner?

The structure is two lists and a calendar check. Ideas go into a backlog the moment they appear. Active projects get broken into jobs with time estimates, and those jobs only go into open time on your calendar.

TimeBud is built around this split. Bud files quick captures, so a new idea goes somewhere safe without pulling you off the job in front of you. For active projects, TimeBud breaks a goal like "write the thesis" into jobs with minute estimates and dependencies, fills only the open time in your calendar and runs a focus timer through them one at a time. When you are deciding whether to promote an idea, you can see whether there is room for its first job this week.

Try TimeBud free