Project governance
Which Projects Should You Pause When Your Team Is Overloaded?
Every project has a sponsor, every deadline sounds important, and the same few people appear on every plan. Asking everyone to work harder does not resolve which commitments should receive their time first. Leaders need a shared view of the work and an explicit choice about what can wait.
This guide proposes a practical portfolio review for a small or growing organization. The fields and decision rules below are suggested working practices, not an industry standard or a formula that guarantees delivery.
Start with commitments, not a fresh priority survey
List the initiatives already drawing on the team. Include work that began informally, improvement projects, system changes, and initiatives described as almost finished. Ask what remains to complete each one. A project that is mostly done can still depend on a substantial amount of scarce specialist time.
Keep normal service responsibilities visible alongside the project list. Customer support, recurring reporting, maintenance, and people management still need capacity. An employee's entire working week should not be assumed available for project assignments.
Choose a planning window that matches the decisions you can realistically make. A short upcoming period can be more useful than attempting precise allocations for the entire year. Record uncertainty rather than presenting tentative estimates as fixed commitments.
Create a capacity-and-commitment register
Use one shared table with these fields for each initiative:
- Intended outcome: What result is the organization trying to deliver, and who needs it?
- Next meaningful milestone: What evidence will show the next stage is complete?
- Date and reason: Is the date tied to an external obligation, a dependency, or an internal preference? Identify the person who can verify it.
- Remaining effort: Estimate the work in the planning window, grouped by the specific roles or people needed.
- Dependencies: Which decisions, inputs, or other initiatives must be ready first?
- Cost of pausing: What would be delayed, lost, or difficult to restart? Separate known consequences from assumptions.
- Proposed disposition: Continue, narrow, pause, sequence later, or stop, with an authorized decision owner.
A project count alone is insufficient for this discussion. Three initiatives that each require the same system administrator next week need a different response from three initiatives using separate teams over several months.
Validate capacity with the people doing the work
Ask contributors to review the remaining effort and timing. Identify time already committed to routine operations, planned absences, and approved work. Discuss whether estimates include preparation, testing, training, and follow-up rather than only the visible implementation step.
Use consistent units and label estimates. If the team cannot estimate reliably yet, begin with rough ranges and identify the largest conflicts. Do not turn an uncertain allocation into a precise individual performance target.
Where assignments overlap, confirm the actual timing before adding the numbers together. A specialist required for one review late in the period may not constrain the same work as a specialist needed throughout it. Name the bottleneck and the period affected.
Illustrative example: three projects, one specialist
Imagine a fictional service business considering work for the next two weeks. After routine support and existing commitments, its system administrator estimates 24 hours available for these initiatives. An access-control update needs 16 hours, a reporting redesign needs 12, and an intranet refresh needs 8. These figures are illustrative estimates, not ADH client data or recommended staffing ratios.
The requested 36 hours exceed the estimated 24 available. Leadership first verifies the consequences and deadlines. Suppose the access update has a confirmed external deadline, the reporting redesign supports a later management review, and the intranet date is an internal preference.
One feasible proposal is to continue the 16-hour update, use 8 hours to define reporting requirements, and pause the intranet refresh. That proposal also changes the reporting milestone: requirements readiness is different from a completed dashboard. Leadership must approve the revised outcome rather than leaving the original delivery promise in place.
Before deciding, check dependencies and restart costs. If another team has already booked intranet training, pausing may require coordination. If a mandatory requirement is uncertain, verify it with the responsible authority. A simple arithmetic comparison identifies a conflict; it does not decide which obligation the business may change.
Make a real pause decision
A paused project needs more than a lower priority label. Record what work stops, what limited preservation work remains, who communicates the change, and what event permits reconsideration. Preserve necessary records and access controls. Identify any contractual, operational, or policy approvals needed before changing a commitment.
Do not call a project paused while continuing to expect its original deadline. Update plans, task assignments, and affected stakeholders together. Capture the choice and resulting actions in a decision log.
Set a rule for new work
For each new request, ask what capacity it requires and which existing commitment would move if it starts now. The answer may be to narrow the request, change its sequence, approve additional support, or decline it. Avoid implying that additional headcount is available before it is authorized.
Review the register when circumstances change and at an agreed cadence. Compare estimates with what actually remained to be done, investigate recurring conflicts, and refine the next planning window. Keep the process proportionate: its purpose is to support choices, not create a second project-reporting burden.
Your first review
Bring the delivery owners and authorized priority decision-maker together. Select the shared role under the greatest pressure, list the commitments that depend on it, and choose one concrete adjustment. Finish with named owners, revised milestones, and a date to review the consequences.
ADH Enterprises supports project governance and execution, including intake, prioritization, decision ownership, and leadership reviews. Describe where your projects compete for capacity to discuss a focused engagement.