Anyway, SHULTZ!
Friday, September 13, 2013
About my last two posts: God what boring posts! Must be middle aged senility starting to kick in. I'm sitting in my office on a Friday afternoon and much of the crew around me are employed in shooting each other with nerf rockets. It's that kind of a day. This is usually about the time the alcohol cart comes swinging around, bottles and glasses clinking together. My friend and colleague, Mark and I have created a little vernacular around this. One Friday around 2pm or so I said I was ready for the clink. Later a signal was borne out of this with a slight nod to Hogan's Heroes: When one of us is ready for a drink, we now just call out "Shultz." Clink = (Col) Klink ergo Shultz. At the old gig it was "Yar," the signal that it was time to go to the pirate (Il Pirata). But when you work for a company that regularly stocks its fridges with alcohol, we haven't bothered to find a pirate in our new surroundings. Also, what's a "pirate" emoticon? For now I've been settled on just a semicolon: ;- but someone with a better brain might help.
Anyway, SHULTZ!
Anyway, SHULTZ!
Wednesday, August 28, 2013
On the subject of support and "relationship management"
While I was digging for some old lyrics, which I couldn't find, I stumbled upon this draft I was asked to submit on behalf of my boss, or more precisely, my boss's boss, at my previous gig. The assignment was to present my thoughts on "four pillars" of relationship management. The pillars were spelled out to me and I ran with them from there. I guess it's my best expression of what I've been doing in one day gig or another for a bit now. And I feel proud to have injected the term "mouse fart" into what otherwise is probably boring reading for the majority of humankind. So for that reason I will submit this to you, dear reader, in all of its glory and splendor:
Effective Relationship Management
Bill Swan – Technical Account Manager, [The previous company I worked for that dare not speak of]
Four pillars:
Responsiveness
Engagement
Prioritization
Follow Through
An organization is only as good as its support, and great support begins with managing relationships with customers effectively. There are many components to this, but today I want to talk about four: Responsiveness, Engagement, Prioritization and Follow Through.
Responsiveness
First and foremost: Show your customers you have a pulse. I think it’s important to respond to requests as quickly as you can, even if it’s only to let them know that you’ll get back to them shortly after you’ve had a chance to review the query. There is the auto-response in the CRM, of course, but I believe it is more important to respond with an additional message suitable to your personal style. First impressions are important, and there’s no reason to keep your customers waiting needlessly, or to allow them any inkling that their question or issue has entered an automated black hole. Yes, there are Service Level Agreements that can dictate the expected time of response based on specific tiered levels of support (As in: How much money they pay for support), and those levels should be set to a realistic target that accounts for spikes in customer activity, resource allocation etc. But then you should do this: Proceed to blow these targets out of the water every time. It is better to undersell the response time and consistently over-deliver than the other way around.
As a member of support, how do you do that, especially if you are getting backed up with customer requests? Consider this: It doesn’t take much to simply let them know you’re there, that you are indeed a living, breathing human being and you will be with them shortly. More often than not, the recipient will thank you for such a quick response. Once you’ve got them hooked, you can reel them in when you’re ready.
Engagement
Responsiveness leads to engagement. And engagement can mean a number of different things. You are essentially at the stage of coming to an agreement with a client to be with them at an agreed upon time to tackle the issue with your undivided attention. And as you are engaged, you are feeling out the customer and getting to know their communication style (this can be written or verbal). You engage in a meaningful conversation about the issue at hand, and the goal should be that, within reason, you can be yourself and not rely on canned responses. Some of this comes more easily as you gain the experience with and knowledge of the products or services you are supporting. There’s nothing like knowing the answer to give you confidence in dealing with customers, especially demanding ones. However, you can still establish a rapport with them by staying relaxed and focused, and being willing to tell the customer if you don’t know a particular answer to an issue or a specific component of the issue, that you will be able to find that answer. This tells that customer you are engaged. If it’s apparent the user has a sense of humor, don’t be afraid to tap into it (assuming you have a sense of humor too). Finally, engagement also means honoring your commitments. If you’ve set a deadline or goal and you think the timeline might slip, engage and let them know. That should be common sense, right?
Prioritization
Tackle the critical issues first, of course. But during your engagement with the critical issues, you can simultaneously cherry pick the low hanging fruit. In other words, if you’re in a long troubleshooting session on a challenging issue, inevitably there will be lulls (such as a re-installation or reboot). And during those lulls you can either sit and watch the paint dry, log onto facebook or you can lop off some easy questions or engage with clients that you know aren’t in a big hurry to let them know you’ll be “on it” soon.
After the critical issues, I usually engage first with any client that hasn’t been in touch for a while. If you’ve been in support for any reasonable length of time, you come to learn that the old adage “No news is good news” ain’t so. No news is no news, and while that could mean anything, it won’t hurt to summon a little paranoia and make sure you keep the quiet clients happy when they re-engage. It may be a client who is perfectly happy or unusually competent and only thinks to contact the vendor when there is an issue of real significance…but it also could be a client who is thinking of switching vendors. Think of these erstwhile quiet clients as a new customer. If you keep the mindset that you want to give this customer a great first impression, then you’ve done your job.
While we are boldly moving into a brave new world of collaboration and communication outlets that purportedly will supplant email, the simple fact of the matter is: Email isn’t going away tomorrow. Manage your inbox. Different people have different styles, but I am a filer. Personally I think it’s much more manageable if you create a system of categorization for incoming messages based by client, priority, product or other topic, whatever makes the most sense. Part of good prioritization involved getting into the habit of being highly organized. Knowledge work is all about organization: It’s what we do! Have some process of categorization, though. You never know when you’re going to need to know your History.
Follow Through
Once you have an engagement, it goes without saying that you need to back up your promise for elaboration or getting back to the client. Use any means necessary to keep yourself to it. Calendars and reminders are there for a reason! Even if there is an issue that you believe to have been resolved with a client, follow up and make sure no other questions have come up and to confirm that the issue is indeed closed. There are processes that can be built for this based on SLA, but I would also add the personal touch here.
Proactive communication is also part of follow through, especially if you are managing a set group of clients. You’ll want such communication to be meaningful and consistent. A new product release announcement is one example, and another is a periodic check in to make sure the client is doing okay, particularly with clients who haven’t been in touch. I would contact these clients individually, based on their communication style. Email is okay for some clients. Others like to chat on the phone, so be mindful of what method best suits each client. Do not send an email blast to all clients in the bcc field or through a canned CRM message all at once. Not only does it lack the personal touch I’ve been talking about, but it might just end up in the recipient’s SPAM filter.
Finally, document everything you do, every message, call or other means of communication should be put into whatever CRM you are using in a clear, organized and easy to read fashion. Even if you think it’s a mouse fart, document it. Think of how you would want to pick up a case where someone else left off, or what would happen if you were suddenly hit by a truck. Document, document, document -- rinse, repeat. You’ll want to cover yourself, too. If anything regarding an interaction with a client ever comes into question, you’ll be able to cite when, where and how the information was originally conveyed. Make sure there is a date and time stamp included in any documentation, such as if you are copying an email message or thread. Including the message header has saved me a number of headaches over the years (Hint: forward the email and then copy/paste from that message so you get the top header. If you were the last one to communicate, go to your sent items and get the header from there). Good documentation is probably the most important element of follow through. You can save this part for down time if things get busy.
Summary
The world of support is often reactive, that is inevitable. It’s human nature for clients to contact you more frequently as a member of support when something bad has happened. You don’t often get a message out of the blue from folks telling you what a great job you’re doing (except maybe during the holiday season), but if you keep these four principles in mind --Responsiveness, engagement, prioritization and follow through—chances are, when your clients get asked about the quality of support they receive, they’ll have nothing but kind words to say. And if they’re still unhappy, they’ll probably blame the product or how much it costs. But you can go home at night and sleep well knowing you’ve done your job.
Effective Relationship Management
Bill Swan – Technical Account Manager, [The previous company I worked for that dare not speak of]
Four pillars:
Responsiveness
Engagement
Prioritization
Follow Through
An organization is only as good as its support, and great support begins with managing relationships with customers effectively. There are many components to this, but today I want to talk about four: Responsiveness, Engagement, Prioritization and Follow Through.
Responsiveness
First and foremost: Show your customers you have a pulse. I think it’s important to respond to requests as quickly as you can, even if it’s only to let them know that you’ll get back to them shortly after you’ve had a chance to review the query. There is the auto-response in the CRM, of course, but I believe it is more important to respond with an additional message suitable to your personal style. First impressions are important, and there’s no reason to keep your customers waiting needlessly, or to allow them any inkling that their question or issue has entered an automated black hole. Yes, there are Service Level Agreements that can dictate the expected time of response based on specific tiered levels of support (As in: How much money they pay for support), and those levels should be set to a realistic target that accounts for spikes in customer activity, resource allocation etc. But then you should do this: Proceed to blow these targets out of the water every time. It is better to undersell the response time and consistently over-deliver than the other way around.
As a member of support, how do you do that, especially if you are getting backed up with customer requests? Consider this: It doesn’t take much to simply let them know you’re there, that you are indeed a living, breathing human being and you will be with them shortly. More often than not, the recipient will thank you for such a quick response. Once you’ve got them hooked, you can reel them in when you’re ready.
Engagement
Responsiveness leads to engagement. And engagement can mean a number of different things. You are essentially at the stage of coming to an agreement with a client to be with them at an agreed upon time to tackle the issue with your undivided attention. And as you are engaged, you are feeling out the customer and getting to know their communication style (this can be written or verbal). You engage in a meaningful conversation about the issue at hand, and the goal should be that, within reason, you can be yourself and not rely on canned responses. Some of this comes more easily as you gain the experience with and knowledge of the products or services you are supporting. There’s nothing like knowing the answer to give you confidence in dealing with customers, especially demanding ones. However, you can still establish a rapport with them by staying relaxed and focused, and being willing to tell the customer if you don’t know a particular answer to an issue or a specific component of the issue, that you will be able to find that answer. This tells that customer you are engaged. If it’s apparent the user has a sense of humor, don’t be afraid to tap into it (assuming you have a sense of humor too). Finally, engagement also means honoring your commitments. If you’ve set a deadline or goal and you think the timeline might slip, engage and let them know. That should be common sense, right?
Prioritization
Tackle the critical issues first, of course. But during your engagement with the critical issues, you can simultaneously cherry pick the low hanging fruit. In other words, if you’re in a long troubleshooting session on a challenging issue, inevitably there will be lulls (such as a re-installation or reboot). And during those lulls you can either sit and watch the paint dry, log onto facebook or you can lop off some easy questions or engage with clients that you know aren’t in a big hurry to let them know you’ll be “on it” soon.
After the critical issues, I usually engage first with any client that hasn’t been in touch for a while. If you’ve been in support for any reasonable length of time, you come to learn that the old adage “No news is good news” ain’t so. No news is no news, and while that could mean anything, it won’t hurt to summon a little paranoia and make sure you keep the quiet clients happy when they re-engage. It may be a client who is perfectly happy or unusually competent and only thinks to contact the vendor when there is an issue of real significance…but it also could be a client who is thinking of switching vendors. Think of these erstwhile quiet clients as a new customer. If you keep the mindset that you want to give this customer a great first impression, then you’ve done your job.
While we are boldly moving into a brave new world of collaboration and communication outlets that purportedly will supplant email, the simple fact of the matter is: Email isn’t going away tomorrow. Manage your inbox. Different people have different styles, but I am a filer. Personally I think it’s much more manageable if you create a system of categorization for incoming messages based by client, priority, product or other topic, whatever makes the most sense. Part of good prioritization involved getting into the habit of being highly organized. Knowledge work is all about organization: It’s what we do! Have some process of categorization, though. You never know when you’re going to need to know your History.
Follow Through
Once you have an engagement, it goes without saying that you need to back up your promise for elaboration or getting back to the client. Use any means necessary to keep yourself to it. Calendars and reminders are there for a reason! Even if there is an issue that you believe to have been resolved with a client, follow up and make sure no other questions have come up and to confirm that the issue is indeed closed. There are processes that can be built for this based on SLA, but I would also add the personal touch here.
Proactive communication is also part of follow through, especially if you are managing a set group of clients. You’ll want such communication to be meaningful and consistent. A new product release announcement is one example, and another is a periodic check in to make sure the client is doing okay, particularly with clients who haven’t been in touch. I would contact these clients individually, based on their communication style. Email is okay for some clients. Others like to chat on the phone, so be mindful of what method best suits each client. Do not send an email blast to all clients in the bcc field or through a canned CRM message all at once. Not only does it lack the personal touch I’ve been talking about, but it might just end up in the recipient’s SPAM filter.
Finally, document everything you do, every message, call or other means of communication should be put into whatever CRM you are using in a clear, organized and easy to read fashion. Even if you think it’s a mouse fart, document it. Think of how you would want to pick up a case where someone else left off, or what would happen if you were suddenly hit by a truck. Document, document, document -- rinse, repeat. You’ll want to cover yourself, too. If anything regarding an interaction with a client ever comes into question, you’ll be able to cite when, where and how the information was originally conveyed. Make sure there is a date and time stamp included in any documentation, such as if you are copying an email message or thread. Including the message header has saved me a number of headaches over the years (Hint: forward the email and then copy/paste from that message so you get the top header. If you were the last one to communicate, go to your sent items and get the header from there). Good documentation is probably the most important element of follow through. You can save this part for down time if things get busy.
Summary
The world of support is often reactive, that is inevitable. It’s human nature for clients to contact you more frequently as a member of support when something bad has happened. You don’t often get a message out of the blue from folks telling you what a great job you’re doing (except maybe during the holiday season), but if you keep these four principles in mind --Responsiveness, engagement, prioritization and follow through—chances are, when your clients get asked about the quality of support they receive, they’ll have nothing but kind words to say. And if they’re still unhappy, they’ll probably blame the product or how much it costs. But you can go home at night and sleep well knowing you’ve done your job.
Wednesday, August 21, 2013
90 days into the new gig
After seven years working for the same company (one that was bi-polar, slowly dying on the vine), I started a new gig at the end of April (a company that is growing lightning fast with maybe an ache or pain or two). The process to get here was long and arduous -- I had to fight a bit for it -- but I landed and I can honestly say I feel invigorated -- mainly because the role I am in now is the first of its kind, and I've long felt that I do best when I am allowed the opportunity to carve my own niche and find and manage work in my own way. Some people have said "I don't envy you, because you get all the problems and then the outcome of some of them are beyond your direct control." Truth is, I see myself as a translator. Not between actual languages but nuances of our own language. Engineers speak in one nuance, salespeople and customers and customer service reps speak in others. And each group has its own repository of information where they log their daily work - and I have access to all of it, a whiff of the omniscient narrator, perhaps, which is a rare position to be in. In some ways, I hope to be a diplomat, to help each group gain a better understanding of the others, and I am learning a ton in the process. Along the way the goal is to help people solve a problem or find a solution (depending on how you view the 1/2 glass). But it's also about managing relationships, helping shape expectations, and also rolling up my sleeves for a little grunt work which I don't mind. I feel lucky to have been given a lot of leeway to do my job as I see fit -- I do not have to spend a lot of time telling people what I'm doing, I can spend that time actually doing it. Although I am among the older side in age in this group, I am not made to feel that way. I don't know if that's because I don't come off as being that much older, or I'm just a late bloomer. I'm feeling this way because I just had my first quarterly review, and there were no negatives except that I may have to be nudged to say no to a few things in due course. I am also just happy to know that even in moments of self doubt, complacency and a fear of advancing age, I can still shake some shit up.
Tuesday, August 20, 2013
Tuesday, January 01, 2013
"Salvage Operation" Oyster Stew
Oyster Stew a la Wixsom via Swan
Ingredients:
-35 Oysters (20 steamed/shucked, 15 raw/shucked, water within the latter 15 strained and set aside)
-1 fennel, fat bit sliced and diced
-3 medium shallots (finely chopped)
-4 cloves of garlic (minced)
-10 medium Yukon Gold potatoes (or so), drawn and quartered to bite-sized pieces
-1 scallion (to be sauteed with the raw Oysters separately)
-1 stick of butter (or a bit more if you're feeling naughty)
-Salt/pepper to taste along the way
-Pinches of Cayenne to taste along the way
-Parsley, finely chopped (for garnish)
-1 QT of Half & Half (not heavy cream, this is for lightness)
Okay, so shucking oysters is a royal pain in the ass! I won't devote too much time to what's supposed to be the proper technique or the fact that you sometimes have to bend the rules a bit to get through the goddamned pile before midnight, and I won't say that was the reason why I steamed some of them beforehand to make the job easier, although the thought did cross my mind. The reason I did that was because my mother in law, Margo Wixsom, bought a boatload of them a couple of days earlier and we ended up with whatever she and a bunch of friends and family couldn't BBQ or eat raw on that first night, and she really wanted to make the stew with the rest of them after having had the dish at the Station Cafe at Point Reyes Station recently, so she called me to steam about half as she was heading to our place. I dutifully complied without knowing what was to come next. Turns out the cold she had kicked in a bit heavy so I took on the whole job of making the stew myself, purportedly as a salvage operation so all those wonderful oysters wouldn't go to waste. There was a period in between where I wasn't sure when she'd arrive so I started looking at online recipes for the stew. It was then that I realized that I should use some of the water from within the remaining oysters to strain and set aside to get that sea-salty deliciousness that you know and love about oysters. This was not as easy to do after steaming them, as the insides of the shells were pretty much dried out with the liquid below in the steamer tainted with all the dirt and crap from the outside of the shells. There were enough raw oysters left to get the good kind of water from within.
So...I had 20 steamed oysters chilling in the fridge, and another 15 raw, with the liquid separated out. Then Margo arrived and clued me in as to the rest of the game plan.
First, I took some butter (I just threw in a whole stick and said "fuck it" without asking exactly how much), and turned on a nice large sauteeing pan to medium low. Once the butter was melted I tossed in the garlic, followed by the shallots and fennel and made 'em sweat til they were kind of limp. I tossed in a bit of salt and pepper at this point before throwing in the potatoes, stirring them up a bit and covering the pan. With the potatoes in the fold, it was about 20 minutes or so of sauteeing time, with a check-in to stir each 5 minutes or thereabouts.
Meanwhile, at this point I thought it would be a good idea to cook the raw oysters a little bit to get them about par with the steamed ones from earlier. So I tossed in about two or three tablespoons of butter, one chopped scallion (aka green onion, without the really white part) and sauteed those for 5 minutes on low. I tossed in a pinch of cayenne to keep them honest. Then I set them aside until the potatoes and whatnot were done.
I then transferred the potatoes and whatnot from the pan to a pot, tossing in a full quart of half & half, warming that up (don't boil it or you'll be sorry, said my wife, Kiera, who stepped in as it started getting bubbly). Just as the potatoes/whatnot and the half and half was starting to feel like it was maybe halfway to the warmth I wanted it to be, I added the raw oyster sautee mixture, the strained water from the shells, and finally the steamed ones. I also added about six or seven grinds of fresh pepper and another pinch of cayenne. Five minutes later, it was ready to serve.
To garnish, I added the chopped parsley and a tiny pinch of cayenne for the finish. We didn't have oyster crackers, but Kiera had made some croutons from a baguette the other night so those got tossed in as well (her suggestion).
What I thought was going to be a salvage operation ended up eliciting the following comment from Margo: "This is better than the Station Cafe's!" I doubt that, but I'll go with it. I was skeptical about how it would turn out, especially after a day of watching Bowl games interspersed with beer and Kiera's world famous chili. I highly recommend topping off such a day with this stew, serving at about 10pm. Try and employ someone else to shuck the oysters if you can. If only I had "The Help...."
Ingredients:
-35 Oysters (20 steamed/shucked, 15 raw/shucked, water within the latter 15 strained and set aside)
-1 fennel, fat bit sliced and diced
-3 medium shallots (finely chopped)
-4 cloves of garlic (minced)
-10 medium Yukon Gold potatoes (or so), drawn and quartered to bite-sized pieces
-1 scallion (to be sauteed with the raw Oysters separately)
-1 stick of butter (or a bit more if you're feeling naughty)
-Salt/pepper to taste along the way
-Pinches of Cayenne to taste along the way
-Parsley, finely chopped (for garnish)
-1 QT of Half & Half (not heavy cream, this is for lightness)
Okay, so shucking oysters is a royal pain in the ass! I won't devote too much time to what's supposed to be the proper technique or the fact that you sometimes have to bend the rules a bit to get through the goddamned pile before midnight, and I won't say that was the reason why I steamed some of them beforehand to make the job easier, although the thought did cross my mind. The reason I did that was because my mother in law, Margo Wixsom, bought a boatload of them a couple of days earlier and we ended up with whatever she and a bunch of friends and family couldn't BBQ or eat raw on that first night, and she really wanted to make the stew with the rest of them after having had the dish at the Station Cafe at Point Reyes Station recently, so she called me to steam about half as she was heading to our place. I dutifully complied without knowing what was to come next. Turns out the cold she had kicked in a bit heavy so I took on the whole job of making the stew myself, purportedly as a salvage operation so all those wonderful oysters wouldn't go to waste. There was a period in between where I wasn't sure when she'd arrive so I started looking at online recipes for the stew. It was then that I realized that I should use some of the water from within the remaining oysters to strain and set aside to get that sea-salty deliciousness that you know and love about oysters. This was not as easy to do after steaming them, as the insides of the shells were pretty much dried out with the liquid below in the steamer tainted with all the dirt and crap from the outside of the shells. There were enough raw oysters left to get the good kind of water from within.
So...I had 20 steamed oysters chilling in the fridge, and another 15 raw, with the liquid separated out. Then Margo arrived and clued me in as to the rest of the game plan.
First, I took some butter (I just threw in a whole stick and said "fuck it" without asking exactly how much), and turned on a nice large sauteeing pan to medium low. Once the butter was melted I tossed in the garlic, followed by the shallots and fennel and made 'em sweat til they were kind of limp. I tossed in a bit of salt and pepper at this point before throwing in the potatoes, stirring them up a bit and covering the pan. With the potatoes in the fold, it was about 20 minutes or so of sauteeing time, with a check-in to stir each 5 minutes or thereabouts.
Meanwhile, at this point I thought it would be a good idea to cook the raw oysters a little bit to get them about par with the steamed ones from earlier. So I tossed in about two or three tablespoons of butter, one chopped scallion (aka green onion, without the really white part) and sauteed those for 5 minutes on low. I tossed in a pinch of cayenne to keep them honest. Then I set them aside until the potatoes and whatnot were done.
I then transferred the potatoes and whatnot from the pan to a pot, tossing in a full quart of half & half, warming that up (don't boil it or you'll be sorry, said my wife, Kiera, who stepped in as it started getting bubbly). Just as the potatoes/whatnot and the half and half was starting to feel like it was maybe halfway to the warmth I wanted it to be, I added the raw oyster sautee mixture, the strained water from the shells, and finally the steamed ones. I also added about six or seven grinds of fresh pepper and another pinch of cayenne. Five minutes later, it was ready to serve.
To garnish, I added the chopped parsley and a tiny pinch of cayenne for the finish. We didn't have oyster crackers, but Kiera had made some croutons from a baguette the other night so those got tossed in as well (her suggestion).
What I thought was going to be a salvage operation ended up eliciting the following comment from Margo: "This is better than the Station Cafe's!" I doubt that, but I'll go with it. I was skeptical about how it would turn out, especially after a day of watching Bowl games interspersed with beer and Kiera's world famous chili. I highly recommend topping off such a day with this stew, serving at about 10pm. Try and employ someone else to shuck the oysters if you can. If only I had "The Help...."
Subscribe to:
Posts (Atom)