"My team and I rarely have a single network issue to address. Typically issues occur concurrently or in clusters, and we need to prioritize which are more serious and have a greater impact on the organization. Criteria I use to do this include the degree of impact the issue has on the organization, the amount of time and resources it will take to resolve it, and how postponing addressing the issue would either increase its severity or require additional resources. Here is a list of issues my team and I commonly encounter in the order of their priority:

Total network failure - this impacts the entire organization -Severe
Partial network failure - impacts only select users - Severe, but less so
Small network failure - impacts even fewer users - Critical
Single Node failure - impacts a single user - Important
Partial Node loss of connectivity - impacts a single user, but not completely - Routine
Minor issues - recur frequently, but small impacts - Address when time permits"