Building a case

Evidence is your best friend when you're persuading someone to help you fix a network problem. More evidence means more effective persuasion. Use these tips and our troubleshooting worksheet to help build your case.

What makes a compelling case?

A convincing case includes (at least most of) these attributes.

Clarity

PingPlotter data is meaningless unless it's associated with a story. Be sure to describe how the problem impacts your experience with the network.

Evidence

The more PingPlotter evidence you can show about the problem the stronger case you make. This is where timelines at the bottom of the program become useful. They help you show how long and how often problems occur.

As tempting as it may be, don't only provide the "worst-case scenario" examples of your data. Results like this are easily dismissed as something that wouldn't normally happen. Provide consistent data. Show them what you've been seeing on a regular basis.

Correlation

You can show a relationship between your problem description and PingPlotter data. For example, "When my online game lags, PingPlotter shows packet loss."

Objectivity

A good case presents the facts and does not exaggerate. Provide a realistic picture of the problem instead of focusing on the worst part of your data. Be as non-argumentative as possible. A collaborative approach helps get technicians on your side, but a combative approach does the opposite.

When you've assembled your case, the next step is reaching out. Continue for tips on making effective contact.