A Project Slot Is Not a Unit of Capacity
A project-count limit can protect attention, but it cannot show which resource is overloaded. Test the next commitment against its actual demands.
Limiting the number of active projects can be a sensible way to protect attention. It is easy to understand and difficult to disguise.
But a count is a proxy. It does not tell you how much engineering time, plant access, management attention, or working capital the next project requires.
That distinction matters when deciding what to start, sequence, or stop.
Look at the next commitment
A supplier-pricing review and a line installation may each occupy one project slot. Their immediate demands can be very different.
Compare the work needed in the next decision window, not just the total project scope. A project awaiting a supplier response may consume little engineering time today, yet require substantial qualification work later.
Record the next milestone, the people and facilities required, and the period in which that demand occurs. A rough, explicit estimate is more useful than pretending all projects are equal.
Include the shared load
Different project teams do not prove that projects are independent.
They may share a sponsor, a quality reviewer, a capital budget, a maintenance shutdown, or a production trial window. They may also ask the same operating team to absorb several changes at once.
Look for those shared demands before adding work. Otherwise a portfolio can appear well staffed while every consequential decision waits for the same person.
Make the tradeoff visible
When a new opportunity appears, ask what it would displace.
If it uses an already constrained resource, the choice may be to delay it, narrow its scope, or stop lower-value work. If it does not, a bounded discovery step may be reasonable without authorizing the entire implementation.
Define that boundary clearly. Permission to investigate is not a promise of plant access, capital, or a production slot.
Keep the project limit when it is serving a purpose. Revise it when resource evidence shows that it is blocking worthwhile work or allowing overload.
Use the portfolio meeting to decide
For each proposed start, bring the expected value, the next commitment, the shared dependencies, and the work that would move as a result.
Then leave with a start, sequence, narrow, or stop decision and an owner.
The aim is not to run more projects. It is to put limited attention and operating capacity behind the work most likely to produce a useful result.