Month: June 2012

The pace of support

A story

A while back my Google Apps email broke. I could still send and receive email through the web interface but all application-specific passwords were not functioning. I spent most of a Monday trying various steps. Nothing worked.

I remembered that Google offers phone support to its Apps for Business users. I only have one user account so this was $5 a month. Five dollars for dedicated phone and email support? I will take that deal every time.

I called Google and after a relatively painless phone tree I got a wonderfully helpful Googler on the line. He immediately spent 55 minutes on the phone with me. It totally blew me away. Phenomenal experience.

A problem

After 55 minutes, though, the Googler could not fix things. I had the luck of running in to an IMAP authentication error that was not supposed to happen. No worries, I told the Googler, some things take time and I will be patient. We ended the call and that evening he sent me a follow-up email with some steps to try. I gave them a shot (no luck) and replied the next morning. Then I waited. For 3 days.

I followed up via email to see what the status was. Shortly after that message my email was back up and running. Despite fixing my original issue, it left me with a bad experience. This showed me that sometimes the pacing of support is the most important aspect.

A lesson

First impressions matter. While that is no secret, I think last impressions are just as crucial. My first interaction with Google was brilliant. Fifty-five minutes of 1-to-1 help. That is unheard of and I was ecstatic.

Then, I waited. Three days. With no word on what was happening. Did someone forget? Did my email get lost? Do I have to contact them again? Will I have to start at square one with a new support engineer? As a company, those are not questions you want your customers asking. They cause thoughts of doubt. They make it harder to believe you care. When your customers wonder where you went it means you have paced your support poorly.

There are benefits to offering support across multiple channels. Phone support and live chat provide immediate gratification. Email allows for the delay in troubleshooting that can be necessary for more complex issues. The trick is in handling people who start in one medium and end in another. A support team must prepare to handle the inevitable follow-up emails from phone calls and live chats quickly. It is not because the questions are any more important. It is because your first contact with those users set certain expectations. Your job is to see things through.

A phone call sets certain expectations for the pacing of support. That call was my first experience with Google. It was great. The Googler was responsive, caring, and quick to help. All of that was lost after we moved to email. I went from feeling like I had that Googler’s full attention to feeling forgotten.

The medium of support is not important. Consistency and follow through are. The standard you set in phone support should follow every user through every interaction with your support team. First experiences set expectations. Proper pacing ensures they are met. Allowing for each mode of support to move at its own pace irrespective of where the user has been before creates a terribly disjointed and unsatisfying experience. Google may have fixed my issue but they left me far from happy.

I’m really excited to see Reeder 3 go live tonight in the App Store. Shawn Blanc and Ben Brooks wrote great reviews of it. I just set it up on my iPhone to sync with my Fever install. No more Google Reader. Pretty slick update to an already great app.

Productivity is about your life, not just your work

Most people measure productivity in terms of work, what they’re paid to do.

I prefer a different measure.

Productivity is the measure of how effectively you get done the things you rationally, explicitly want to do (including work when necessary). Productivity is the output of the exercise of free will. This isn’t a new generalization, adherents of GTD and other productivity systems know that productivity is about your life, not just your work.

Tantek Çelik – The Acceleration of Addictiveness vs Willpower, Productivity, and Flow.

When Friction is Fiction

Sometimes our lizard brains build mountains where only roads exist — mainly so we have an excuse not to venture down them. One side of our brain is naturally built to warn of danger and the other is all too apt to believe it. It is in this tension that even fiction can become friction that slows us down and keeps us from tackling the task at hand. Overcoming the challenges of our lives often comes from staring this friction in its face and seeing it for what it really is — the fear of what we are fully capable of…

Patrick Rhone – When Friction is Fiction.

Great day of hiking with @simpledream and friends

Triple Falls

Took advantage of the nice weather today and hit 3 waterfalls in 5 miles through the Columbia Gorge. The aperture on that photo is off, but pictured is Triple Falls.

As the online editor, I s…

As the online editor, I sometimes feel like my job is to make something beautiful, just to hack it apart for kindling. Here’s the way I (mostly) think about it instead: any link to a fragment of LQ is a breadcrumb that can bring you back to the whole. Every magazine wants to lead you back to the mothership, but when you finally pick up an issue of Lapham’s Quarterly, what you have isn’t the end of your own curation and the beginning of our vision. It’s the start of a new reading in a closed-off sphere that also resembles the web you came from: a rabbit hole of thought that you’ll gladly fall into.

Michelle Legro – History and Its Contents.

Mount Defiance, in the mist

Spent the first half of yesterday hiking Mount Defiance with Leah, Luke, and Luke’s sister who’s in town for the week. It was a decent day of weather in Portland but the mountain ended up surrounded by clouds and mist. Still a great hike but we missed out on what should have been great views of Mount Hood.