10 Ideas to Navigate the Politics of Prioritizing Network Traffic

Solving network technical issues can be a walk in the park when compared to dealing with user politics about whose traffic should be prioritized. Here are 10 survival tips.

Picture of Mary E. Shacklett, President, Transworld Data

Mary E. Shacklett, President, Transworld Data

July 31, 2025

4 Min Read

Conceptual illustration of network traffic flowing in different directions, in bright colors

CREDIT: SCIENCE PHOTO LIBRARY / ALAMY

It's a straightforward task for network managers to decide which traffic gets priority when networks are busy. But it can be daunting to get the needed support from users -- especially when they all argue that their data should be first. What steps can network managers take to ward off political storms?

Here are 10 strategies to consider.

1. Explain Network Traffic Prioritization and its Role

A helpful step is to explain to senior management how network traffic prioritization works and its effect on business outcomes. Most senior management don't hold network traffic control as their foremost concern. But these execs will listen to dispassionate explanations that detail how network traffic prioritization affects the goals and efficiency of the business. For example, if your business is a healthcare clinic where 50% of clients reside in rural areas, then top-level QoS is required for doctor-patient telehealth appointments. A possible tradeoff in this case: internal administrative communications must run at slower speeds.

2. Meet with Users to Define Network Traffic Priorities

Sharing information with users about network traffic priorities is the bane of network managers. Yet, ignoring this step to make traffic prioritization decisions by yourself yields even more trouble.

As long as top management supports your prioritization strategies, user meetings can be productive. First, state what upper management says about the business' top priorities. After that, it's a matter of arriving at a user consensus. It might take multiple meetings, but it's well worth it if everyone understands upfront the strategies that shape the organization's network traffic priorities and goals.

3. Review Network Traffic Prioritization Annually or as Needed

Business priorities change, and network traffic prioritizations should reflect that. If change is continuous in your company, review traffic prioritizations more often. As a general rule, review traffic prioritization goals annually, preferably at corporate strategy setting and budget time.

4. Make Service Guarantees so Users Know What to Expect

All users should know how traffic speeds, uptime and other network factors affect their network activities. In the earlier telehealth example, for instance, it might only be necessary to operate at full QoS strength between the hours of 9 a.m. and 5 p.m. Outside those hours, network managers could commit resources used for telehealth to other functions.

5. Continuously Improve Network Performance

Every network manager wants to provide the best network service for each user. Yet, resource limitations can make this goal difficult to attain. The key is to continuously improve the network with technologies -- among them private 5G and Wi-Fi 6 -- that can upgrade service levels.

6. Segment Networks

As more companies move into edge computing, carving network service into mini networks -- or segments -- can reap prioritization benefits. With this approach, a remote manufacturing plant, for example, could run its own internal network without having to compete for resources on the larger corporate network. Enterprise networks can also be segmented so only certain user subsets can transact with certain systems.

7. Use CDNs

Commercially available content delivery networks let users connect to nearby servers to access frequently requested websites and resources. User requests don't have to be transmitted to distant central services, which improves network traffic flows. CDNs enable organizations to offload nonessential traffic from their core networks, freeing up bandwidth for business-critical applications. CDNs also help absorb traffic spikes and can subsequently decrease congestion and latency.

8. Use Store and Forward Techniques Where Applicable

Every company has large batch jobs that require daily or weekly processing. But this processing doesn't necessarily have to occur in real time during peak business hours. A huge payload of data will bog down network traffic. Store these data files at their locations and only forward them to their ultimate network destinations during off-hours. Everyone's network service will benefit.

9. Use Multiple ISPs

It's never a good idea to rely on a single ISP for your internet traffic. Use at least two different providers and load balance network traffic between both to provide the best possible throughput for all users. If one ISP goes down or experiences a technical issue, you can fail over to the alternate provider without incurring a service interruption.

10. Develop a Network Service Culture

Technical glitches happen, and there will always be users who feel their traffic prioritizations should be higher. Deal calmly and constructively with users. Focus on addressing the issues you can solve . When the network staff develops a reputation for providing excellent service, users notice.