Skip to main content

Service - what does it mean to you?

Recently our little company has been very busy and while it has been tricky to maintain a high level of service, it's something we are managing very carefully. Interestingly though, we have had clients ask us to do things quickly, easily or cheaply. Generally there is no difference in the service provided, however, as our time becomes more precious, it's easy to take the client's request and act on it in the manner they have requested.

For example - "Can you quickly wipe these computers and then roll them out to be sold?"

"Sure - how much time and effort do you want us to put in to this?" (read: how much money do you want to spend on using our valuable time).

"Not much, just make sure our data's wiped and then get them out the door."

OK, so we clear the data, wipe the free space or re-install after a Darik's Boot And Nuke (DBAN) and then roll them out.

Now our client says to us that it hasn't been done properly and they want an explanation. For the first time ever, I reckon, I pointed at the email trail and said to them "You wanted fast, easy and cheap. You got it. If you want well done, comprehensive and completely satisfying, that does not fall into the fast/easy/cheap categories".

Interestingly the client sat back for a moment, said "You've got a point there. Can you sort this out properly?" Well sure I can and I have, but the cost in my time is there.

There's a line in the movie Tango and Cash where Jack Palance replies to two of his underlings telling them "Quick and Easy. Quick and Easy is how you make a cake." and then goes on to talk about killing Tango and Cash. My point to the client today was "Quick and Easy is how you make a cake - not have a well thought, solid and reliable IT infrastructure." Wake up peeps - spend some money and do it right the first time and stop being disappointed when you pay minimal dollar and get minimal effort.

Comments

Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( www.openkm.com ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the stuff in there I knew the general theory of, but not the specifics of how to perform. As I thought about it, it occurred to me that Systems Administration is such a vast field. There is no way I can know all of this stuff. I made a list of the software and operating systems I currently manage. They include: - Windows Server 2003, Standard and Enterprise - Exchange 2003 - Windows XP - Windows Vista - Windows 2000 - Ubuntu Linux - OpenSuSE Linux - Mac OSX (10.3 and 10.4) - Solaris 8 - SQL 2005 - Various specialised software for the transport industry I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I have no clue about SQL 2005 and I need to make it work with another bit of software. All complicated and nothing straightforward. Irritating doesn&

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&