2014-02-11

Co.Labs

How To Stop Overthinking Your Startup's New Feature

After weeks of stressing over my writing app's new feature, the solution came to me in a TV show.



I recently needed to update how Draft, an online word processor I created, supports comments. When I originally added comments, I kept them very simple; a list with a text box beneath—reminiscent of comments on a blog. To help people understand the context of the comment, you could hover your mouse over a comment, and if it contained any quoted text, it became highlighted in Draft, like this:

It did its job, but with room for improvement. For example, the context awareness wasn't very good. Also, users wanted to reply to a single comment.

So I broke up comments on the page and aligned them with the text. It wasn't super easy, but I had it ready in a couple of days.

The ability to reply to a single comment was ready in hours. But after I was done, I wanted to see if I could improve the "hover over a comment and highlight the text" bit.

I realized the main editor technology would need to be changed to support better highlighting. So I spent weeks changing a core piece of my product, and even came close to releasing something, until I realized I broke the browser's native spell-check capabilities.

I spent even more time learning how to incorporate a spell-check service—even brushed up on my probability theory and learned to derive Bayes' Theorem trying to write my own.

Eventually I got an English spell-check system in place. But then, I looked at a map of Draft's users: Half of them are outside of the United States in non-English-speaking countries.

After weeks of effort, Draft's improvements still weren't ready.

You Can Learn A Lot From A Terrible Drummer

As I was worrying how I was going to fix my problems now with spell check, I watched the pilot episode of The Tim Ferriss Experiment, a show starring Ferriss, the best-selling author who teaches people how to do impactful things in less time.

Tim's entire method can be boiled down to the Pareto principle: For many events, 80% of the effects come from 20% of the causes. You want 80% of the benefit from exercise? Figure out the 20% of what's most important to get you there. Want to learn to be a great chef? Determine the 20% of what great chefs learn that has the most impact.

Tim now has an entire TV show teaching people what can be done in as little as four days: learning a foreign language or building a business. But does he always succeed?

In the pilot, Tim is challenged with learning to play the drums in just four days. On day 5, he'll be up on stage at a rock concert to play drums for the band Foreigner during one of their songs.

So Tim starts learning how to play the drums. Intensely. He has the best tools and education money can buy. He's practicing all day and night. But it's not working. Doubt sets in:

I'm effectively having an anxiety attack.

With only about a day left, Foreigner came for a sneak peek at Tim's progress. Tim was awful. Kelly Hansen, the band's front man, scolds Tim:

This is no joke, man.

But the visit from Foreigner also brought this advice from the band's drummer:

Play the song. Don't play the drums.

You saw the light bulb turn on. Tim realized he had complicated his true goal. He was learning how to read music, play different types of drums, improvise, and use flourishes during the main heartbeat of the song. But none of those things mattered for the task at hand, which was playing a single song he had already picked out.

With just a day left, Tim focused on just what he needed to learn the main heartbeat of the song, ignoring everything else. He was on stage a day later successfully rocking with the band: If that was possible, what other impossibles do I have in my life that I should really question?

How Starting Over Solved My Problem

That night after watching Tim, I walked the dog with my wife and talked with her about the episode. Had I just done the same thing with this new comments feature? The original goal was to improve comments, and now I'm creating my own spell check.

So, I started all over again with a new focus and constrained to only the task at hand. The main editor technology in Draft would not change. I had to find a way to work around it. And, sure enough, I did.

In just a few hours, I improved highlighting without replacing core parts of Draft. In a fraction of the time I had already spent, I was done. I shipped the new comments feature a few days later, and without all the complexity and risk of the path I was pursuing.

http://t.co/pKWTjfZ11I leaped ahead of any other writing software with recent feature additions. @natekontny LOVE the in-line comments

— JAVIER SANDOVAL (@SpanishCurls) December 14, 2013

I don't know why we are so good at making what could be a small problem so much more complex. It's easy to fall prey to letting our dreams and projects snowball into things we can't accomplish. And just like that, more of our time vanishes.

The great news is that the solution is simple—constant self-reflection: What's the smallest possible thing I could do to accomplish my true goal? Have I made this much more complicated than it needs to be? Is there a way to do a fifth of what I'm doing right now?

Or, in other words:

Am I learning to play the drums, or could I just learn to play the song?

Nate Kontny is the creator of Draft, a collaborative platform to help make you a better writer. He’d love to meet you on Twitter.

[Image: Flickr user Eugene Kim]






Add New Comment

1 Comments

  • Tim Ferriss is a complete charlatan though. As your article shows, he didn't learn to play the drums - he learned how to muddle through one song. Same as his dreadful book "The 4-Hour Chef" features recipes using cans of concentrated soup.