A resource-constrained operation cannot absorb a staffing constraint and a capability constraint indefinitely. My first boundary is safe, qualified operation: stop or isolate work that cannot meet safety or quality requirements. Within that boundary, sequence the available resources to protect healthy production, restore usable capability, and complete deeper repair.
Run first.
Protect the tools that are healthy and producing. Keep work moving, protect WIP and priority lots, and avoid creating secondary problems while the organization is already constrained.
This is not ignoring broken equipment. It is preserving the operating base that gives the team room to recover.
Recover to run.
Respond quickly to the interruptions that are holding production back. Restore the fastest reliable path to operation, verify the return, and minimize avoidable lost output.
Recovery is a specific objective: regain usable capability safely. It should not quietly expand into every improvement the equipment may eventually need.
Plan and staff deeper repairs.
Once safe flow and usable capability are protected, assign the deeper corrective work: root cause, reliability improvement, recurring-failure elimination, and long-duration repair. Required repairs, release criteria, and approved operating limits remain binding; staffing pressure does not waive them.
Leaders must also know when to escalate. When local resources can no longer protect flow and restore capability, the wider organization has to engage.
Protect safe production. Restore qualified capability. Plan and staff deeper repairs.