How do we decide what goes on the /noc page?

The other day someone asked how do we decide what goes on the Network Operations page, which is due for a big overhaul in the month of March based on everything we have learned so far. How do we figure out if something is important enough to put something there you ask? Very simple:

If an issue is affecting more than 10 customers, or more than one server, it gets posted.

If an issue is likely to affect more than 10 customers, or more than one server, it gets posted.

Simple enough. We are a partner company, we are an extension of their business that provides essential Internet services. As that extention, our duty is to communicate to our partners and our clients when things are different than usual. We have found that it is more effective in terms of providing timely support, that it is far easier for the clients to be aware of what may be going on so when they are asked for support they can be fully informed of any service issues.

The site has been very successful, it has contributed to a huge decrease in support requests and consequently savings for everyone involved because we are all that much more efficient. There has been only one negative comment so far, “I want all my information on one page, I don’t want to have to look at three pages to find all my Own Web Now information!” While we can understand the concern, this is a problem that technology has already fixed, people no longer surf the Internet. People subscribe to the data feeds that go on their desktop, portal, SharePoint, you name it. If you are actively seeking out information, instead of letting information come to you in the fastest and most efficient way possible, it’s time to learn about blog aggregators.