How much change a business can carry: capacity, capability and too many projects

A familiar pattern in growing businesses: several worthwhile projects are running at once, and all of them are late. The new software is waiting for someone to test it. The product launch is waiting for production trials. The quality certification is waiting for procedures to be written. Meetings multiply, people switch between tasks all day, and the owner starts wondering whether the team is the problem.

Usually it is not. Each project was sensible on its own, and each was affordable. What nobody checked was whether the business could carry all of them at the same time, alongside serving its customers. A business can have the money for its plans and still lack the capacity to deliver them, because the binding constraint is rarely money. It is a handful of people, a few decisions and the ability of everyone else to absorb new ways of working.

This article explains the different kinds of capacity a business has, why capacity is not the same as capability, how too many simultaneous projects slow everything down, and how to choose a sequence that gets benefits sooner. It is general information for owners and managers deciding what to take on.

Six kinds of capacity

When owners think about whether they can take something on, they usually think about money and headcount. Those are only two of the limits:

Financial: what the business can fund.
Delivery: what the people doing project work can complete.
Decision: how many significant decisions the owner and managers can make well, and how quickly.
Operational: how much project work the business can support while still serving customers.
Change: how much new process, technology and behaviour staff can absorb at once.
Capability: whether the business has the skills and systems the work needs at all.

A set of projects can pass the first test and fail several of the others. The one that binds is usually the one nobody counted.

Capacity is not capability

Capacity is how much work the business can handle. Capability is whether it can do the particular work well. The difference matters because a spreadsheet of available hours can look healthy while the business lacks what the work actually requires.

Suppose next quarter’s projects need 600 hours of technical work and the team has 700 hours available. On paper there is room. But if most of those hours belong to people who have never used the new technology, or only one person can sign off the critical design, or nobody can connect the new system to the old one, the number is correct and misleading.

A useful readiness check looks at five layers:

Volume: enough time, people, money and supply for the expected work.
Competence: the technical, commercial and leadership skills the work needs.
Systems: processes, tools and information good enough for the work.
Integration: someone able to manage the handoffs between people, teams and suppliers.
Endurance: whether the capability can be sustained through the whole job and into operation, rather than depending on one person working late.

The last layer is where optimistic plans most often fail. Look especially for single points of failure: the one person who understands the old control system, the one estimator who prices a certain kind of job. A headcount report never shows these. The question is not only “how many?” but “how replaceable?”. The key person dependence article covers reducing that exposure.

The bottleneck is usually operational attention

In a small business, project teams rarely run short of project managers. They run short of the people who also run the business. A manufacturer upgrading a machine, changing its job management system and redesigning its quality procedures may have reasonable resourcing for each project. All three still depend on the same production supervisor for requirements, trials, sign-off and training. The constrained resource is not project labour. It is that supervisor’s attention, which is also needed to keep orders going out.

The same applies to the owner. Every significant project needs decisions, and an owner sponsoring five projects while running the business gives each one a fraction of the attention it needs. Decisions queue, and the queue looks like slow project work.

Find the bottleneck by watching where work waits: whose approval, whose testing, whose availability. The names that come up in every delay are the business’s real constraints. The mapping dependencies article covers mapping shared people and decisions across projects.

Why too many projects slow everything down

Running more projects at once feels productive. It usually is not:

More work in progress means more switching. People lose time every time they move between tasks, and more handoffs, meetings and status updates are needed.
Benefits arrive later. A project that starts early but keeps waiting for people can finish later than one deliberately started later and done with focus.
Priorities get set informally. If the owner does not decide what comes first, the people at the bottleneck decide, usually in favour of whoever asked loudest or most recently.
Busy people create queues. Someone fully booked has no slack, so any variation, such as a sick day or an urgent customer problem, delays everything waiting on them.
Staff saturate. Even well-designed changes fail if people are asked to learn too many new things at once.

Two common responses do not help. Asking the team to “work smarter” may improve things a little, but it does not create the missing hours. Adding contingency to each project separately does not help either, because if every project relies on the same person, each project’s buffer is competing for the same scarce time.

A capacity review

A practical review takes an afternoon:

Identify the binding constraints. Which people, decisions or approvals genuinely limit how fast work moves?
Estimate demand on each, by period. When does each project need that person or decision, and how much? Monthly totals hide clashes; look week by week or month by month.
Estimate credible supply. Start with their total hours, then subtract normal duties, leave, seasonal peaks and a margin for the unexpected. What remains is the real capacity for projects.
Change commitments until the plan fits.

The fourth step is the one most businesses avoid, and without it the review is just a description of the problem. The responses are:

Sequence when the capability exists but timing clashes.
Build when the constraint will recur, through training, hiring or a second person learning the role.
Buy when outside help can be brought in without creating new handoff problems.
Simplify when scope is creating demand the outcome does not need.
Stop when a project is not worth the capacity it consumes. The stopping projects well article covers doing that cleanly.

Count training and onboarding as capacity costs

New capability takes time before it adds capacity. Training someone in a new system, onboarding a contractor or learning a new process all consume hours from the very people who are already scarce. A plan that assumes a new hire or a trained employee will be productive from day one creates an illusion of capacity and quietly overloads everyone else. Include the learning period in the plan.

When choosing who does the work, also ask what the assignment leaves behind. Giving every urgent job to the one expert maximises short-term output and deepens the dependence on them. Pairing that expert with someone learning the work costs some speed now and reduces the risk later.

Decide where each capability should sit

When the review shows a gap, the choice between building and buying is also a choice about what the business will be able to do in future. A capability is a candidate to keep in-house when it sets the business apart from competitors, is needed again and again, depends heavily on knowing how the business works, or involves sensitive information. Buying it in makes more sense when the need is temporary, the skill is scarce, speed matters, an independent view is valuable, or keeping the skill in-house would cost more than it returns.

Often the best answer is a mix. An outside specialist adds capacity for a peak, while someone inside the business keeps the final say on design decisions and learns enough to run and maintain what is built. Two costs are easy to miss. Internal people look cheap because their wages are already in the budget, but the work they stop doing has a cost too. External specialists can look expensive while saving months of delay. Compare the whole cost of each option, including the work that would otherwise wait.

A worked example

This is an illustration. A 30-person manufacturer plans three projects for the year: a new job management system, a new product line and quality certification. Each has its own budget, and the business can afford all three. Each also needs about 120 hours of the production manager’s time for requirements, trials, procedures and training.

The production manager works 38 hours a week, of which about 30 go on running production. That leaves about 8 hours a week for projects.

If all three projects run at once, the 360 hours of demand are spread across the 8 available hours each week. All three advance slowly, and all three finish around week 45. In practice they finish later, because the production manager loses time switching between three sets of meetings, suppliers and decisions.

If they run one after another, each gets the full 8 hours a week and takes about 15 weeks. The job management system finishes around week 15, the product line around week 30 and certification around week 45.

The last project finishes at roughly the same time either way, but two of the three deliver their benefits much earlier: 30 weeks earlier for the first and 15 weeks earlier for the second. Less switching also makes the sequenced plan more likely to hold.

The owner chooses the job management system first, because it reduces the production manager’s own admin time and so frees capacity for the later projects. The owner also brings in a part-time consultant to draft the certification procedures, reducing that project’s demand on the production manager from 120 hours to about 50, with the consultant handing over editable procedures and a walkthrough so the business can maintain them itself. Finally, a senior operator is assigned to learn trial and testing work alongside the production manager, so the next round of projects is less dependent on one person.

How this applies to a small Australian business

List all current and planned projects in one place.
Name the people and decisions every project depends on.
Estimate demand on those people by month, not by year.
Subtract normal duties and leave before counting availability.
Sequence projects so the bottleneck works on one thing at a time where possible.
Check capability as well as hours, especially single points of failure.
Plan for learning time when adding people or skills.
Decide what to stop or defer, and say so.

Signals worth watching

The same few names appear in every project delay.
Projects that are all “nearly there” for months.
Staff saying they spend their days switching between tasks.
Decisions waiting for the owner.
New projects approved because there is money, without asking who will do the work.
Training scheduled with no reduction in other duties.

Common mistakes

Treating funding as the only constraint.
Counting people as interchangeable.
Planning on the assumption that key people are fully free.
Starting everything at once to show progress.
Adding contingency to each project when they share one bottleneck.
Never deciding what to stop.

Frequently asked questions

How many projects should a small business run at once? There is no fixed number. It depends on the bottleneck. If one person is critical to all of them, fewer at a time usually finishes more, sooner.

Isn’t sequencing slower? For the last project, about the same. For the others, it is faster, because they finish and deliver benefits earlier.

What if every project is urgent? Urgency is not priority. Priority is the order in which scarce people are committed. Someone has to set it, ideally the owner.

Should we just hire more people? Sometimes. But new people need time to become productive, and hiring generalists will not fix a shortage of a specific skill or of the owner’s decision time.

How do we measure change saturation? Ask staff how many new processes or systems they are learning at once, and watch for slipping basics. If routine work quality falls during a change, the business is near its limit.

Questions to ask

Which people and decisions does every current project depend on?
How much of their time is genuinely free after normal duties?
Where does work wait most often?
Do we have the skills each project needs, or just the hours?
Which projects would deliver benefits sooner if we did them one at a time?
What are we prepared to stop or defer?

Bringing it together

A business can afford its projects and still be unable to deliver them. Count all the kinds of capacity, not just money and headcount, and separate capacity from capability. Find the people and decisions everything waits on, estimate the real time they have after running the business, and change commitments until the plan fits: sequence, build, buy, simplify or stop. Doing fewer things at once usually means finishing more things sooner.

Source: KEVOS notes, drawing on teaching material on portfolio capacity and capability management, project human resource planning and an EY paper on portfolio management challenges. Examples and figures in this article are illustrations. This article is general information.