Category: leading geeks

How to get good service from your Help Desk or Support Center

Help Desk
Image by Michael @ NW Lens via Flickr

I was going to make this a snarky post on how to get bad service from IT, but then I realized that it might actually be more useful to write this in a more positive light.  Also, I actually had positive things to say.

So you’re someone who has a computer problem at a company, and you have some sort of computer support/MIS/IT department that you need to help you.  Here’s what to do to get the best service both now and for your problems in the future:

  • Follow the process.  Maybe it seems really silly to call into the Help Desk line rather than just walk up to the systems administrator (since you just did tequila shots with him last night), but I really mean that you should call in instead.  Why do you need to follow the process?
    • If it’s a system-wide problem, having all the calls come into one place will allow it to be diagnosed & fixed faster.  If 4 different people get 4 different calls about the same problem and we’re all in different offices, we’re not aware that it’s system-wide until several minutes or hours later.
    • Your buddy in the IT department might not be the best person to ask about your question.  Your drinking pal the sysadmin usually can’t fix your Word problem, and the IT Director probably doesn’t know her way around common Citrix problems the way the Help Desk does.
    • You can make sure your problem gets documented properly.  When I ran IT departments and had to handle a user’s issue directly, I rarely remembered to document it in the ticket tracking system.  Unfortunately, that meant that the next time that user had that problem, someone else had to take the same troubleshooting steps I did.  If it’s a problem you have all the time, you also WANT your problem to be documented properly, since it’s more likely to be taken very seriously if you can prove a pattern via the documentation trail.
    • Walking straight up to IT & support folks tends to tick them off.  They might be in the middle of a different user’s problem, or they might be held to a certain hold time standard.  Your walk-up interrupts them and probably annoys them as well.
  • Call the support line WHILE you’re having the problem (and you’re at your computer!).  Calling after you’ve already moved on or–even worse–calling when you’re not in front of the computer removes almost all the tools that the support folks will need in order to diagnose and fix the issue.  This is another reason not to walk directly up to the IT folk; we need you to access your computer so we can figure out what’s going on!
  • Call the support line yourself.  Don’t have your boss/secretary/wife/dog call for you.  Maybe you feel like your boss will have more clout & get things done better or faster, but it’s the same as the last point–we still need you to be at your computer.  And if you’re the boss, you should note that your secretary can’t fix it for you if he’s not at your computer.  Your wife will make us laugh but probably won’t help us fix it, either.  And your dog doesn’t have opposable thumbs.
  • Be nice. I know you’re annoyed that your @!#&* document has @#$%^&* frozen yet again, but cursing at the person on the other end of the phone won’t motivate them to fix it any faster.  Please keep in mind that geeks are people, too, and treat them politely and professionally.  If you’re rude, chances are we’ll fix your problem this time, but you might find yourself ringing to voice mail a bit more often, since the support folks will be more likely to jump to answer the calls from the users who are nice to them.  If you did happen to lose your temper, donuts make good apology tools.  Just sayin’…
So what have I missed?  What are other sure-fire ways to get good service from your support geeks?

What a CEO should be thinking about

I had the opportunity recently to meet with the inimitable Donna Payne, CEO of PayneGroup.  I have been a groupie of Donna’s since she changed my world by talking about PowerPoint metadata back in 2000 when I was doing applications at a law firm.  Since then, we’ve been social media buddies and even co-presented on using social media to the vendors at ILTA ’09.  I was pretty thrilled when she made time in her busy day to chat with me.

What became very clear during our conversation was how focused Donna is on what I can only describe as “CEO stuff”.  Even though she has successfully created a premier company in the legal space that writes top-shelf metadata, formatting, and numbering software, does high-level consulting, and provides some of the best training around, she’s not just sitting around and trying to make sales.  Here’s why I think her brain is in the right place:

  • She cares for her team.  A LOT.  She has a yoga instructor come in once a week to help with stress (and it’s just fun!).  She specifically cited my On Burnout post as something she diligently attempts to avoid having anyone on her team experience.  And I think her caring has paid off–most of her senior team has been with her more than a decade.  That’s something like 30,000 years in the software space, I think.
  • She sees her company’s potential weaknesses and attacks them before they become REAL weaknesses.  This goes along with watching her team for burnout; she’s also watching for any potential internal or external weaknesses so that she can address them quickly.  I like to call this “preventive maintenance”, and I’ll bet that it saves her company a ton of cash in the long run.
  • She is constantly thinking about her company’s next steps. Donna is thinking 10+ years into the future of her company, and is taking action right now in order to bring that future about.  She’s not content to just have one of the best companies out there–she’s looking for what’s next, and she’s not afraid to take risks in order to get there.
  • She’s actively thinking about the industry’s next steps.  Even though a lot of law firms are scared of the cloud and might not want to touch non-Microsoft applications for a long time, Donna is actively thinking about them and planning for when the industry becomes less hesitant.
In a nutshell, this is what I think a CEO should be thinking about: her people, preventing potential weaknesses, the company’s next steps, and the industry’s next steps.  I believe that this is why PayneGroup has lasted since 1994, weathering the dot-com bust and the most recent recession.  I look forward to seeing what Donna will do with PayneGroup to take it through the next few decades!

My completely nitpicky pet peeves (humor)

Quotes. Made in notepad
Image via Wikipedia

Dear fellow geeks, geek leaders, and other random people who read this blog:

This is not a useful post.  This post, in fact, will show you how the inside of my brain works.  It can be a scary, scary place sometimes.  Also?  This isn’t a rant.  This is just nitpicky.  Also probably brought on by lack of sleep.  And it’s supposed to be funny, not cranky.  So if you read it as cranky, oops.

Here goes.  I hate it when you…

  • Change the subject line of the email.  I have multiple reasons for this:
    1. I don’t read subject lines.  I also don’t read chapter titles, article titles, etc.  I don’t know why.  It’s weird.  My husband makes fun of me for it.  So I’m not actually going to SEE what you put in there for my cute little eyes to see.
    2. It breaks my email threading.  I have a strange obsessive behavior that makes me adore my threaded email conversations.  I cuddle up with them at night (no, not really.  If you’re like me and don’t read titles, please go back and note the “humor” thing up top.).
  • Make plurals with apostrophes.  Just please don’t do it.  Unless you like watching me twitch.  In which case you should go ahead and do it, but don’t expect me to buy you a beer.  Ever.
  • Misspell Latin phrases.  If you can’t spell it, don’t use it.  You don’t sound erudite, you just make me twitch.  See previous bullet point about twitching.
  • Hug me.  There are a few non-family members who I don’t mind hugs from (Whose first names pretty much always start with “J”.  No, I don’t know why.), but otherwise, there will be twitching.  But this one doesn’t get you exempted from the beer buying, so this one is a lesser evil in the Jenn hierarchy.
  • Correct my order of punctuation and quotation marks.  Yes, I know I do it “wrong” for American English.  No, I don’t care.  Pthththt.
So, gentle readers, what are your completely ridiculous pet peeves?  (Other than being called “gentle readers”, that is.  I think that one’s weird, but I’m still leaving it in there.)

Dear Job Applicant: Your résumé is driving me insane

Un-suckify your resumeDear Job Applicants:

Your résumés are driving me nuts.  So nuts that I’ve created a list:

  • You don’t tailor your résumé to my job posting.  If my job posting says you have to know marketing and be able to teach, the word “marketing” should actually SHOW UP on your résumé.  If I specify that you have to know how to administer Compellent SANs, guess what I want to see on your résumé ?
  • For the love of everything, get someone to proofread your résumé.  I read one today that said, “References can be refurbished upon request.”  Seriously?  Seriously!?!?!?!?!
  • I really don’t care about your job responsibilities that much.  Your accomplishments, sure.  Your responsibilities, not really.  I want to know what you did.  Did you manage a network?  Did you manage humans?  Did you manage a budget?  How many?  How much?  How big?  I’m reading to see if you have what it takes to manage my network, humans, and budget.
  • Please tell me why you want to do this job.  Especially if it’s an unusual job.  For example, we hire for a role at HubSpot known as “Inbound Marketing Consultant.”  And, honestly, it’s not a job like any other job.  As a result, if I can’t figure out from your résumé or cover letter WHY you want this job, I have to waste time in the interview figuring out two things (below), and I HATE wasting time.
    1. Do you have any idea what this job is?
    2. Given your understanding of the job, why do you want it?
  • Please have some clue what’s on your résumé.  Seriously, people, if you don’t know what’s there and I’ve only spent 30 seconds skimming it, we’re in a world of hurt.
  • Please put complete information on your résumé.  I can’t tell you how many interviews I’ve had where people say, “It’s not on my résumé, but…”  Well, then, your résumé isn’t complete, now, is it?
I’m sure there are more, but I have to go back to skimming résumés.  Can someone please have mercy on me?

Image courtesy of CharlotWest

I Can’t Keep You Fixed

I can't keep you fixedYeah, I know. Your job sucks sometimes. Servers crash, users complain, you are looking to your next job but haven’t quite gotten there yet, etc. Or maybe you’re having some troubles at home, not sleeping, etc.

I promise you that I will do my best, as your manager/leader/director/chief whatsit officer, to make your job better.

I will shift your workload, give you plum projects, take you out for beer, approve tons of personal time, etc.  I will do everything in my power to make you happy and productive, because I know that happy workers are better at their jobs (except lawyers.  No, really–I don’t have the citation on hand, but I read a study in business school that said so.).

But, honestly, I can’t keep you fixed.

I will protect you from politics, and defend you like a mother bear defending her cubs.  I will fight for your requests even if I don’t necessarily completely agree (but do see the merit).  I will joke with you, cry with you, and get angry alongside you.

But, still, I can’t keep you fixed.

As adults in the workplace, sometimes we need to take responsibility for our own happiness.  Should we fight for what we want? Absolutely.  Should we go to our managers with our complaints/problems? Yes.

But it’s not their job to keep us fixed.  It’s our job to fix ourselves.  If I’m going to my manager with a problem, I should also have some ideas of solutions.  Maybe they’re not tenable solutions, but “I’m not going to do that” isn’t a solution–it’s creation of even more problems.

So yeah, jobs suck sometimes. And as a manager, I do my best to keep my team happy.  But as a team member myself, I need to be cognizant that there is mutual responsibility for the fixing.  I can’t keep you fixed, just like my manager can’t keep me fixed.  But together, I think, we can probably do a decent job of getting through the day.

**Note to fellow grammar geeks: I know I switched personal pronouns, but it sounded really cranky when I didn’t…

Photo Courtesy of DaveOnFlickr.

When You Shouldn’t Hire “The Best”

“We always hire the best.”

“The people who work here are the best people in the world.”

“We never use the phrase ‘good enough’ in our hiring.”

I’ve seen countless companies completely mess themselves up by sticking to some sort of resolve to “hire the best” without thinking it through.  They hire the coolest, brightest, smartest, and quickest people and then have morale and retention problem that they just can’t figure out.  They leave out one essential piece of hiring “the best”–they forget that they need the best for the job.  So they end up with…

  • Brilliant technologists who are miserable working a Help Desk phone
  • Great managers who are lousy consultants
  • Great user support folks who are cranky systems administrators (this one is hard to tell, since systems administrators tend to be cranky anyhow)
  • Great applications people who are bored trainers

I’ve found that behavioral interviewing can really separate the best (in general) from the best for the job.  Here are my favorite questions:

  • In job x, you’ll often experience situation y.  Can you tell me about a time when you were in a similar situation and how you reacted?
  • How do you handle it when you feel like you’re at the end of your rope, and what sorts of situations make you feel like that?
  • I’ve made mistakes that could turn your hair grey to hear them.  Tell me about how you handled one of the worst mistakes you’ve ever made (I don’t make them tell me the details of the mistake).
  • How would you handle <some situation they’ll experience on the job>?
  • What is the coolest thing you’ve ever done in work or in life?  What made it so cool?

Their answers to behavioral questions will help you rapidly see that sometimes a completely awesome candidate just isn’t the best for the job.  And honestly, one of the biggest mistakes you can make as a hiring manager is to let someone’s degrees/qualifications/personality blind you to a bad fit.

So how about you?  How do you distinguish between to “the best” and “the best for the job”?

Photo courtesy of Rachael Voorhees

Leading Geeks through Disasters

Some of you have read this blog for a while might already know that I have some experience with technology disasters. Specifically, two back-to-back disasters involving many gallons of water and a server room, thereby earning me the nickname “Waterfall Girl” a few years back. (Which didn’t really stick, luckily.)

Here are some lessons I’ve learned:

  • Geeks surprise you. You never know what they’ll do in high-stress situations.
  • Communication is key. No change? Tell people that. During stressful situations, people just want INFORMATION (dammit!), and sometimes telling them that there’s been no change and you’re still working on it still actually helps them.
  • Apologies help. Folks know the disaster isn’t your fault, but apologizing anyhow somehow helps them. I’m going to guess that it’s because it addresses how they feel and demonstrates that you realize the crisis has caused them no small inconvenience.
  • You can’t please everyone. Did you make an announcement via the PA system? Well, some people would really rather have email. Did you send email? Well, prepare for responses vilifying you for not walking the floors or making an announcement Did you and your team walk the floors? Well, they’re not doing it fast enough. All you can do is your best.
  • You can’t do everything right. Maybe you didn’t communicate fast enough. Maybe you didn’t figure out the problem in time to prevent a cascade event (or maybe the cascading events were inevitable). Maybe you estimated that things would be back in two hours but it took two days. You’re not infallible, and you will probably make even more mistakes in crisis situations. Forgive yourself, pick up the pieces, apologize, and move on.
  • Acknowledge emotion. If you’ve already worked 70 hours by Thursday, you will be a bit, uh, grumpier than usual. Once when I took a post-disaster phone call, I said something to the effect of, “I realize that I haven’t slept and that you’re very stressed as well because of the disaster. My goal is to get through this conversation without either of us getting too testy or angry.” The caller laughed (as people will when you do or say something unexpected), and we got through a 12-minute conversation without excess grumpiness. Realize that your geeks will feel stress and get upset easily as well.

I’m sure there are more things to add. What have your experiences been?
Photo courtesy of Maciej Szczepaniak

Customer Service vs. Accuracy

Customer service vs. accuracyI recently had two customer service experiences with a company that sent me a defective DVD and then sent me the wrong disk as replacement.  The discussions were nearly identical (both took place via online chat), but they left me feeling very different.  During the first discussion, I was confident that I had done everything I needed to do.  During the second one, I was unsure.

That uncertainty led me to examine the conversations in order to see the differences.  Interestingly, there was no real difference in what the service rep said would happen next.  Instead, what I found was that the first rep put it this way:

We will absolutely take care of that for you.  I’ll escalate it now, and you’ll get the replacement DVD.

But the second rep put it this way:

I don’t have the authority to replace DVDs.  I’ll escalate this to support and they will be in touch with you.

Which one was more accurate?  Probably the second.  Which one made me feel better?  The first.

I personally have the tendency to be overly accurate and not reassuring enough–something that I’ll now be working on.  And as I think about it, the geeks I’ve worked with who excel at customer service tend to leave some of the exact details out (like the first rep above did) in the interest of making the user/customer/client feel like they have been both heard and taken care of.

So what do you think?  Which do you value more–customer service or accuracy?

Photo courtesy of Roman Pinzon-Soto.

What do you do with needy geeks?

Most geeks tend to fall into one of two categories: The “leave me alone.  I can figure this out by myself” geek, and the “I need to understand ABSOLUTELY EVERYTHING about this situation before I can be expected to even think about doing it” geek.  I find the former type fairly easy to manage; just swing by for regular check-ins, make sure you know what they’re doing, and let them go.  The latter, however, can be very difficult for a busy manager to handle.

The needy geek (as I will call her) also tends to fall into one of two categories: the “tell me everything” geek, and the “tell me stuff and I will take it away and over-analyze it and pepper you with questions” geek.  I have to be honest–both of these geeks drive me absolutely nuts.  When I have to deal with either of these geeks, my thoughts go something like this:

  • Why can’t you just figure this out?  Part of the project is to figure it out.
  • Sigh.  I hate repeating myself.
  • Go away.
  • Can’t you just figure this out yourself?
  • Please go away?
  • If I already knew everything about it, I would just do the damn thing myself.
  • Now go away.

Obviously, not a good train of thoughts for a manager.  I personally don’t like wishing that any of my reports would go away–I try to be more of a help and resource than that.  Honestly, my lack of patience with “needy” geeks probably reveals some of my own shortcomings.  I tend to lack patience.  I tend to under-explain projects.  I tend to expect everyone to understand everything I say the first time I say it.  So I had to train myself.  What works for me  is:

  • Take a deep breath
  • Realize that people need varying levels of resources to complete tasks
  • Try to gently suggest to the geek whatever path I want him to take
  • Be honest about my expectations–do I expect her to figure it out herself?  Tell her that.
  • Be more detailed about projects in the future

So what works for you?  How do you handle needy geeks?

Image courtesy of Tony Unruh.

Work-Home-Life Balance (Balance in the IT World)

Go to work…

Work…

Get home, work some more…

Try to sleep, worry about work…

Wake up…

Repeat…

Sound like you?

We all attempt to achieve the allusive work-life balance, and in some professions balance is especially difficult. Working in IT is a demanding profession. Mostly, you’ll find it’s demanding of your time, all of the time, anytime. An IT professional is expected to work at home, at night, and on weekends. These hours are considered (by sane people) as home time, therefore it should (and in many cases is) acceptable to handle some personal tasks during what is generally considered work time.

To be fair, the odd hours we keep are necessary, and in most cases unavoidable. The users and companies we work for get twitchy if the system(s) are maintained during the day. The good news is that most IT managers recognize that the job forces us to keep an unorthodox schedule.

This schedule is, however, less accepted at home. Be prepared to field comments such as; “Are you working again!” or “Why are they calling you on your day off”. Children are particularly sensitive this odd work schedule. “Daddy, are working today?”

Officially we work nine to five, forty hours a week. Most of us know this is a fantasy, we work 9-5, then logon from home and work again from 8-11. This is assuming everything is stable. User requests can (and do) come at any time, requiring prompt attention. During an upgrade, or outage all bets are off. We will be working (as we should) around the clock until the issue is resolved. Employers don’t usually have an officially policy to handle these odd working requirements. The “policy” is to turn a blind eye and let the department deal with it internally.

This schedule can cause undue stress at home. Spouses become frustrated with the excessive attention devoted to work, and lack of attention directed to home and your relationship. Children don’t understand why daddy’s always busy. Lastly let’s not forget about the toll it takes on you. It’s unhealthy to live a monolithic life focused solely on your job. Are you living to work, or working to live? Don’t let your career consume you. While your job is certainly a part of who you are, it should not be your defining property.

The only way (I see) to balance work, home and life is by disregarding the traditional work / home boundaries. What does this mean? It essentially means to try working a very flexible schedule. If know you’re going to be working at home tonight, go home early, and pick up the kids at school. If you’ll be working late tonight, meet your spouse someplace nice for a two hour lunch.

Now for the hard part, following my own advice.

Editor’s note: Mark, when he worked for me, worked insane hours.  He pulled all-nighters multiple times, and we would spell each other when we were into a long slog (he’d take the midnight hours, usually), including that one time I pulled 5 all-nighters in 8 days.  I’ve never encountered such a dedicated work ethic, and I’d LOVE to see him take his own advice!