How many projects can my team run at once?

Your team can run as many Jobs as its real capacity can cover, which is almost always fewer than the calendar suggests. Start with the weekly capacity of the people doing the work, subtract meetings, admin, reviews, and revisions, then compare what remains with the effort your active Jobs demand. The next Job either fits or it quietly pushes everything else into overtime.

Why concurrency is really a capacity question

Owners want a clean answer: five projects, ten projects, maybe twenty if everyone drinks enough coffee. The count means very little without the team and effort behind it. Three light Jobs may fit comfortably while two heavy ones overload the same designer, developer, or lead in the same week.

That is why concurrency is not mainly a project-count problem. It is a workload problem. When owners judge capacity by how many job names they think the team should be able to juggle, they usually miss the overlap that creates pressure. What matters is whether the required hours for this week and next week actually fit inside the hours your team can deliver without constant spillover.

Measure your team’s real deliverable hours

Start with the people who deliver the work and calculate what they can realistically contribute in a normal week. A forty-hour week does not create forty hours of Deliverable work. Leads answer questions, designers prep files, developers review work, and writers revise. Real capacity is lower than the tidy number on the staffing plan.

This is where many firms first realize why they feel overcommitted. They have been mentally planning from a theoretical number instead of the hours that are truly available for production. Once you calculate that real weekly capacity, you have the ceiling the rest of the planning has to respect. Without that number, every new project discussion is mostly guesswork.

Subtract meetings, admin, and revisions

Capacity gets inflated when every hour is treated as Deliverable time. Internal check-ins, client calls, admin, reviews, and small corrections still consume the week, even when the calendar does not give them their own colorful project bar. Ignore them and the team looks free right until the work lands.

Revisions are especially easy to undercount because they arrive inside existing jobs and feel smaller than they are. But they still compete for the same weekly hours as new work. The same goes for handoff packaging, QA, and coordination. A firm that subtracts those recurring obligations gets a far truer picture of what remains available for active jobs than one that plans from raw hours alone.

Weigh active jobs against the effort left

Once you know the weekly capacity left after the usual overhead, compare it with what current Jobs still demand over the next few weeks. Use the real work owed, not the effort you wish it needed or the reassuring amount of white space on the calendar. If the team has sixty hours of delivery capacity and active Jobs need ninety in the same period, you are already full.

This is where workflow management software earns its keep. You need to see the effort load across Jobs, not just milestone dates. Compare the team’s remaining capacity with what active work still needs, and “Can we take one more?” becomes a workload question instead of an optimism contest.

Decide the next job against the ceiling, not optimism

When a new project appears, the question is not whether the team wants it or whether there is a blank start date on the calendar. The question is whether the work fits beneath the delivery ceiling without forcing everything else to spill. If it does not fit, the honest options are to delay the start, reduce scope, add capacity, or pass it on. What does not work is pretending the team will somehow absorb the extra load because the opportunity feels important.

Protect some slack on purpose. A team booked to the absolute limit has no room for revisions, surprises, sick days, or the ordinary interruption that eats half an afternoon. A little breathing room keeps one late Job from turning the rest of the schedule into overlapping emergencies.

Review concurrency this way often enough and the project count stops fooling you. Clearer capacity and utilization shows the ceiling, while better habits around protecting delivery capacity keep one exciting new intake from overwhelming the Jobs already moving.

FAQ

Why does my team feel maxed out when the schedule looks open?

Because a calendar shows dates, not effort. Two projects can each look small on the timeline while together demanding more hours in the same week than your team actually has, and that overlap is what makes people feel underwater.

Should everyone be booked to 100 percent?

No. Planning to full capacity leaves nothing for revisions, sick days, and the work that always runs long, so most firms plan delivery people to somewhere around 70 to 80 percent of their raw hours. The slack is what absorbs reality.

How do I know when to stop taking projects?

When the effort your committed jobs demand starts exceeding your realistic weekly capacity, you are full, regardless of how many logos are on the roster. That is the point to either delay the next start date, add capacity, or hand it on.