Slashdot Mirror
Reporting To Executives
chopsuei3 writes "As a System Administrator, I am charged with providing more insight into the functioning of the system. What types of reports and information do other System Administrators submit to executives and on what frequency? Measurements such as uptime and average page latency are useful, but our site is relatively stable and we see minimal downtime, so I'm looking for other important and useful information I can report up to better illustrate my efforts. Our system is also unique in that about 70% of the traffic we see is from devices and not human browsers. I am a lone System Administrator in a 20-person company which specializes in web-based irrigation management. I also simultaneously perform all IT-related tasks in the office, which may also be important to report up to executives on regular basis."
Start out your presentation stating that you're willing to dive as low as the executives ask you to but you're going to give them a high level view. Have slides after the end of your presentation as backup to support this claim. Keep large numbers of systems generalized with figures next to them to let the executives know how many devices or users you're supporting. Include meaningful statistics like 'requests per hour' to give them a good hint of how capable your system is.
If you're briefing one or two executives, see if you can pull up their calendar for the past few months and see what kind of meetings they've been in. If anything overlaps with what you're presenting do not brief the same thing twice. If you have multiple executives, tailor your presentation to the top one or two in importance. Nobody wants their time wasted with something they've already seen.
If they want a low level view, you might put together an example story of the flow of information from the sprinkler A all the way back to your server and the response back with all the challenges faced along the way. Keep it interesting, uncluttered and as simple as possible unless further questions are asked.
If you've got budget, pick up the three Edward Tufte books on The Visual Display of Quantitative Information, Envisioning Information & Visual Explanations. Read them and incorporate that sort of data presentation into your reports.
Another great thing is if you can get interesting metrics established and defined and then develop scripts to ingest this information automatically into weekly reports (think of a perl script that digests very large log files). Have them create a cover sheet with the most general metrics and convert it to PDF or whatever the execs prefer to view them in. If you've got time, tailor them to the specific reader (your CTO is going to be interested in different things than your CEO or marketing director).
My work here is dung.
better illustrate my efforts.
Presenting executives with log files, or web stats is no way to communicate with your boss. This will give him/her an idea of the work the server is doing, but not you. You might want to present your to-do lists. These to-do lists should include completed and incomplete tasks. Since it is a small company and you are the only SA, you might try to attend the companies planning meetings. Be a part of the company instead of just an employee and you won't have to worry about CYA all the time.
Flexible bare-metal recovery for Linux/UNIX
I don't mean to sound flippant or like a cocky IT jerk but they really have no idea what you're talking about. You'll have to translate it into terms they can understand.
In my company, the issue we're looking at is trying to quantify the value of IT. What management does not understand it devalues. So there's a bunch of geeks in a room doing shit. But what does it mean for the bottom line? Just filing reports on trouble tickets doesn't do the job. One ticket could be for showing a person where their start menu disappeared to and another could represent an continuing problem that took a hundred hours of work to resolve.
Staying until 2am to fix a problem in the server room doesn't count for diddly if all anyone sees of you in public is you being rude to a secretary for losing her word icon. That's all that will be remembered.
Kwisatz Haderach
Sell the spice to CHOAM
This Mahdi took Shaddam's Throne
Agreed perfectly, with one big, fat caveat: Have a very good handle on what you have, and can and cannot be done. Also, never, EVER promise anything up-front w/o studying the problem.
Recently, I got one for my own employer, in that our CEO wanted to simply open his cell phone and search all contacts in the group...
Long story short, it's doable, but it eats a lot of resources to get it done (fortunately, we haven't had to spend any real money for it, but it's not quite complete just yet). While I doubt that every request would start getting hairy like that, you'd be amazed at how often the most innocuous of CxO requests can end up eating a mountain of time once you get into the minutiae.
Finally, I'd suggest that no matter the request, you never take your eyes off the prize - keeping existing systems running with as much uptime as possible. ;)
Quo usque tandem abutere, Nimbus, patientia nostra?
Reporting numbers that are from a different department is silly. sysadmin for an airline website? report costs of operation, and current load with a reminder of where you need to upgrade. if you are a sysadmin and you are dipping into the database to look at sales numbers, you are not doing your job, you are doing the accounting departments job.
Website operational costs $xxxx.xx per month we had XXXXXXX visitors in that time period and are operating at 46% capacity. Currently experiencing a 6% growth from last month and a 1% growth from last year at this time. At this growth rate barring any hardware failures, we will not need any capacity upgrades for XX months. We had to replace a hard drive array at a cost of $X,XXX.xx and will be scheduling a 12 hour downtime window later this month for software upgrades to protect the company and site from fraud.
That is what an executive wants to see, distilled down to a small paragraph that gives him everything he wanted in less than 30 seconds. Also if you distill it tightly like that, you end up showing up the other guys that report because you are concise and to the point not wasting any of his time. They REALLLLY appreciate that.
Do not look at laser with remaining good eye.
The numbers could be entirely fictional - as long as the report looks good and seems to trend the right way it will never be read.
All generalizations are false, including this one. Mark Twain