In Valid Logic

Endlessly expanding technology

Analogies in customer service

Ok... going to go on a little rant... see if you can find one of my annoyances from today.

Being a developer, one thing I constantly do is analyzing things. Analyze anything from code to things in life. Also like deriving analogies from them.

My latest interest? Restaurants... your lunch and fast food type places.

In terms of how places operate, I see that there are usually two types... those with the assembly line process and those with single person service.

Places like McDonalds, Taco Bell, and Quizno's are all assembly line places. One person takes your order, another puts it together, another finishes it up, a final wraps it, and then someone hands it to you. This system is efficient, but it is impersonal and not dynamic. Try going through a drive through in one of these places and ask for your soda with no ice (I hate ice, dead space). The vast majority of the time, they never remember. I've come the conclusion that when I ask for it, it is more of a hopeful wish than an order, so I never really raise a fuss over it.

And while on this topic, I'll grip about why I despise Quizno's. They can never get my sandwich right. My order is "regular smoked turkey, no lettuce, tomato, or onions". Very simple and easy to remember. The problem? One guy puts the sandwich together, then puts it on the conveyor belt as it goes through the oven, then another guy puts on the veggies, like lettuce. The first guy never talks to the second guy. I always have to be sure to watch for my sandwich to come out and catch the guy before he puts lettuce on. Often times, I'll be in the middle of paying and not catch them in time, and then I don't get what I asked for and have to pick it off.

One time, they had to make my sandwich three times to get it right. Ordered the sandwich to go, came home, took it out, and found they made the wrong sandwich. Some Sierra Turkey sandwich. So I went back up, told them they made the wrong one, retell the guy my order, and he goes and makes another. He brings it back and says "you wanted lettuce, right?" I roll my eyes and say no. He automatically apologizes and goes back to make it a third time... and finally right. Same thing happened at In & Out today... I was craving In & Out... went, ordered, came home, and they gave me the wrong order. Get in my car, drive back, talk to them, wait 10 more minutes, got it right.

The other kind of lunch restaurant is the one with single person service. This is your Togos or your usual deli sandwich place. These places have one person who takes your order, makes it, and often handles paying for it. Deli shops are often even better about being able to handle more complex orders or multiple sandwiches at the same time. They give personal service. If you go there regularly, they often recognize you and will remember what sandwiches you like and how to make them. You don't have to watch them like a hawk, and often they are polite and chat with you. It is an interesting contrast to the assembly line places, where you perhaps don't even see the person who's making your order.

So if you made it this far in my rant, you may be thinking "what the hell does this have to do with the tech industry?" This is where the analogy comes in. Support is a very important part of any business. How do you handle your support? Do you treat it like an assembly line, or do you give personal service? Do you just take in a request and pass it along to the next person, or do you see the problem through to the end? Do your customers get someone else every time, or do they get the same person (or small group of people)? Do you care about your customers issues, or you just want to get it closed an on to the next one?

But what does this have to do with software development? Because all developers are in support. All developers, at one point or another, will have to deal with a customer. A customer is anyone who is paying your company money. And when you deal with them, you are a representative of your company.

Monday, June 19, 2006

blog comments powered by Disqus