Too Many Projects at Work? How to Cut the Load Without Dropping Balls

Count them, rank them, and ask your manager to choose. That is the short version of how to manage too many projects at work. You cannot fix overload with better time management alone, because the problem is not how you spend the hours. It is that the work asked of you does not fit in them. The fix is a conversation, and the conversation goes better with numbers.

Why too many projects hurts more than it should

Every project you hold costs attention even when you are not working on it. Each one has open threads, people waiting, things you are trying to remember.

Switching between them has a cost too. Sophie Leroy's research on attention residue found that when people move from one task to another before finishing, part of their attention stays stuck on the first, and they do worse on the second. Eight projects means lots of half-finished switches.

So five projects is not five-eighths the stress of eight. It is often much less, because each one gets real, unbroken time.

Step 1: do a project load audit

Open a sheet and list every project you are on. All of them, including the "small" ones and the ones nobody has mentioned for a month.

Add up the middle column. In this example that is 30 hours, on top of meetings and email. If your week has 15 hours of real project time, you are asking for double. Now you have a number, not a feeling.

Step 2: rank them yourself first

Before you talk to anyone, put the list in order by what matters most to the business, not to you. Use three questions:

1. What breaks if this slips by a month?
2. Who is waiting on it, and how senior are they?
3. Is there a fixed date set by someone outside the team?

You will not get it perfect. The point is to arrive with a view, not a complaint.

Step 3: the priority conversation

This is the step most people avoid, and it is the one that works. Here is a script.

"I want to make sure the right things move. I'm on six projects that need about 30 hours a week, and I have around 15 hours after meetings. Here's how I'd rank them. Can we agree which three get my time and what happens to the other three?"

Then wait.

Three replies you might hear

"They're all important." Say: "Understood. If they all get a share, each one moves at about half speed. Is that okay for the Q4 report?" Making the cost specific usually forces a choice.

"Just do your best." Say: "I will. So I can do that, I'll put the vendor review and the process doc on hold until November unless you tell me otherwise." Then confirm it in writing.

"Let me think." Say: "Sure. Can we pick it up Thursday?" Put it in the calendar.

Step 4: park the rest properly

A paused project left vague turns into guilt. Park it clearly.

• Write a three-line note: where it stands, what is next, what you would need to restart.
• Tell the people waiting on it, with a rough date.
• Take it off your daily list completely. Keep it on a "parked" page.

There is more on how to handle lists of half-finished work in what to do with years of unfinished to-do lists.

Step 5: give the top projects real time

Agreeing on three projects is only useful if they get blocks on the calendar. Book two-hour slots for the top one, and protect them. If meetings keep eating them, read how to plan your day around a 9 to 5 job, which deals with the hours you actually control.

Try to give each project a theme day or half day. Monday afternoon for the website, Tuesday morning for the report. Fewer switches means less residue.

What if you can't say no?

Some workplaces really do not allow it, or the manager will not choose. The limitation is real. In that case, choose for yourself, quietly, and make the tradeoffs visible in your status updates: "Report on track. Partner deck paused this week to hit the report date." People can disagree, but they cannot say they were not told.

And if every week feels like a fire, look at how to prioritize when everything feels urgent. Overload and fake urgency often travel together.

Signs you are on too many projects

It is not always obvious from inside. Watch for these:

• You open a project and spend the first 15 minutes remembering where you were.
• Status updates are the only thing that moves on half your projects.
• People chase you for things you had forgotten you owned.
• You finish the week busy and cannot name one project that moved meaningfully.

If three of those sound familiar, run the audit above this week, not next month.

What managers often do not know

Many managers have no idea how many projects a person is on. Requests arrive from different directions, and each one sounds small to the person asking. The audit is not a complaint. It is information your manager probably wants. Framed that way, the conversation tends to go far better than people fear.

A worked example: from eight projects to four

Here is a composite example. Dev, an engineer, was on eight projects. His audit showed they needed about 34 hours a week against 14 free hours. He ranked them and took the list to his manager.

The manager kept four active, paused two until next quarter, and moved two to a colleague who had more time. Dev wrote parking notes for the paused ones and told the people waiting.

A month later, two of the four active projects had shipped. Before the audit, none of the eight had shipped in two months. Working on too many projects at once had made all of them slow. Fewer projects made each one fast.

A daily habit that keeps it from creeping back

Each morning, look at your three agreed projects and pick one step for each. Not more. When a new project shows up, add it to the audit sheet and ask the same question: which one does this replace? A planner like Todonado can hold the parked list separately from the day list, so new requests do not quietly join the pile. The sheet works just as well.