Stepping Off the Startup Treadmill
[PING!] Got a second to chat?

Letā€™s go back to mid-December. Iā€™m sitting in the hotel lobby trying to get shit done. Iā€™m building a new feature for HelpDocs to help users draft their docs easier.

Itā€™s early days for the feature. Iā€™m really still thinking it through. Making sure we build something powerful enough that it solves our usersā€™ problems. Simple enough that it makes their lives easier.

PING!

Itā€™s a message from my team in Slack. Something innocuous. Probably about payday (hey itā€™s December whatcha gonna do šŸ¤·ā€ā™€ļø). Or a user with an issue.

I shoot off a quick reply and get back to work.

Actually yā€™know what Iā€™ve stopped anyway. Iā€™m gonna grab a coffee.

10 minutes passes.

Ok so about that feature. I just need toā€¦ PING!

šŸ˜©

Journey to Notification Hell

Iā€™ve lost count of the amount of times Iā€™ve been distracted in the last year by instant messages. From my team. From customers. Friends. Family. Across a half dozen platforms.

Itā€™s a sad story. Iā€™ll sit down to do some deep work. Or shallow work. Any work really. Iā€™ll get about 5 minutes in and the dreaded pingā€™ll drag me right back out.

Now Iā€™m no stranger to notification hell. I disabled those annoying pings on my phone years ago. My iPhoneā€™s been on Do Not Disturb since itā€™s glorious debut.

But at work? I have to be available right? I mean thatā€™s my solemn duty as a founder. Right?! šŸ¤”

Reclaiming My Time

I got so used to minimizing my response times and making myself available I never stopped to ask why.

Did I really have to respond to that cat GIF in 20 seconds?

Could the customerā€™s ā€œurgentā€ billing question about their plan that wonā€™t renew for 3 weeks really not wait half hour?

Do I need a notification every time a payment fails given theyā€™ll go through an automated dunning sequence anyway?

Thatā€™s a hard no on all counts.

I was at breaking point. Notification hell was dragging me in a thousand different unimportant directions each day.

Making myself available to everyone all the time was wrecking my productivity. I couldnā€™t remember the last time Iā€™d done any deep work.

Enough was enough. In the now infamous words of Auntie Maxine I had to start reclaiming my time.

Muscle Memoryā€¦Of the Mind?

I did what any sensible person would do. I rage disabled all notifications.

Team communication notifications? Gone. Live chat notifications? No thanks. iMessages from my partner? They can get their own coffee.

I felt an overwhelming sense of relief.

I got back to work.

Things were good.

Until they werenā€™t. Despite having notifications disabled everywhere and that distraction-free environment Iā€™d craved I still found myself checking in.

Because while I wasnā€™t seeing the notifications I knew they were still there.

What if my team needed me? What if a customer knowledge base had a production issue I needed to fix asap? Or my card had been declined for my Spotify subscription? šŸ˜

All Iā€™d managed to do was trade notifications interrupting my day for me interrupting my day. I did more checking in than ever.

I needed a more radical change.

An Easier Way to Team

Now Iā€™ve been a founder long enough to know that switching tools very rarely solves problems.

Sure you might get some incremental improvements. But if you suck at writing blog posts in one editor youā€™ll probably suck at writing them in every editor.

Wary but with resolve I ventured into the world of team communication tools. My goal was to find something less realtime. Less stressful.

After some quick research and testing I settled on Twist by Doist (one of my absolute favorite remote teams). Doist made Twist to solve their own problems with comms across timezones and different working hours.

Itā€™s like the threads you get in Slack but without the realtime firehose of notifications. You can choose who to notify every time you send a message.

Thereā€™s no status indicators. Who cares if several people are typing? Communication becomes fully asynchronous. As it should be.

Honestly I freaking love this thing so much Iā€™m gonna write a whole post about it. But thatā€™s for another day šŸ˜…

Team communication āœ…

Not gonna lie I was pretty pleased with myself by this point. My time was now finally my own. No more intense checking in. No more distractions. Now where did I leave that feature? Oh yeah!

PING!

Goddammit.

Danteā€™s 10th Circle of Live Chat

At HelpDocs we make pretty great knowledge base software. But if you asked our customers Iā€™d like to think what they really love about us is our support.

We try to make the support experience as fabulous as we can. Weā€™ve always had low response times. Fast times to resolution. High quality answers.

Human, friendly, engaging support. The kind we wanna see when we reach out to other companies.

Weā€™ve had live chat since day 1. It seemed like a no brainer. People want answers quick right?

As we grew from 1 to 100 to 1000 to now, well, significantly more users the strain started to show.

Iā€™m proud to say our response time barely slipped. If anything we continued to improve. Most chats were completely resolved in minutes. Almost all within a single working hour.

What Iā€™m less proud about is the toll that took on the team. The toll it took on me.

We were wrong. Customers donā€™t want quick responses to their live chat messages. They want instant responses.

In practical terms that meant one of us had to have our chat software open at all times.

I was clearing the ticket queue at 8am and still chatting away at midnight. I spoke to customers while I was working out. At dinner with my family. Doing my makeup. Watching Netflix.

My mind was always half focused on live chat. Iā€™d have half conversations with Jarratt each day. While we were supposed to be spending time together as a couple I wasnā€™t really there.

I was a ghost.

I know the rest of the team was feeling the strain too. Work was bleeding into life. And thatā€™s not a good place to be.

Trading Live Chat for Being a Live Person

So I turned live chat off. Not just the notifications this time. The whole damn thing.

We no longer offer chat support as a company. Customers reach out to us through a contact form built into our in-app help widget Lighthouse. Lighthouse suggests knowledge base articles as users type their query. If they donā€™t find anything we get sent their message by email.

I switched everything over and waited for the influx of angry ā€œWHERE IS MY CHAT GONE I CANā€™T EVEN SPEAK TO YOU NOWā€œ messages.

Thenā€¦nothing. Nobody cared. Customers are still getting their responses quickly. They just get them by email rather than chat.

The messages we get are less ā€œHello?ā€ and more ā€œthis is my specific problem. Can you help?ā€.

Our reply timeā€™s slipped but our time to resolutionā€™s pretty much the same. If not quicker in most cases.

All while focussing on our mental health as a small team.

Editorā€™s note: if you also do your best remote work when you can unplug from distractions weā€™re hiring a bunch of roles. Come work with us šŸŒˆ

Nobodyā€™s expecting a reply to their email in 5 seconds. Itā€™s easy to surprise and delight a customer when their expectations are so low.

Itā€™s no secret that most companies suck at email support. Weā€™ve all had experiences where you fire off an email and hear back a week later. Or worse not at all. Iā€™m still waiting on a reply from a vendor I emailed in June šŸ˜†

But when companies donā€™t suck at email itā€™s a magical experience. A one hour response time is great when the expectation is 24 hours or more. Thatā€™s opposed to live chat where 30 seconds feels slow and disappointing.

As a company leader I know which experience Iā€™d prefer to give.

Happier Team === Happier Customers

My search for an exit from notification hell was a purely selfish endeavor. I wanted to feel whole again and not get constantly dragged away from my work.

I spent a lot of last year doing 16 hour days. Most of the time in retrospect was spent context switching. I wanted to have some time to myself. To spend with my spouse. I wanted to not kill myself working.

Fast forward to now and Iā€™ve been working fully asynchronously for three weeks.

That feature Iā€™d been distracted working on for weeks? After finding my balance in a distraction-free work environment I had it built and shipped to staging in 2 hours.

Iā€™ve replied to a higher volume of customers than ever.

Our customers are as happy as ever. Iā€™m less stressed. My code quality and quantity are both way up.

Iā€™m more productive in a 30-40 hour focused week than I ever was in my 100+ hour weeks of distraction hell. And I feel better than ever.

PING!

Oh.