How To Be Productive + Avoid “Analysis Paralysis”
Tags: agile, motivation, productivity, programming
Published: 2019-08-07 20:14:13

---
title: How To Be Productive + Avoid “Analysis Paralysis”
published: true
tags: agile, motivation, productivity, programming
cover_image: https://thepracticaldev.s3.amazonaws.com/i/kfap1tpcptm5j73h7wpd.jpg
canonical_url: https://cubiclebuddha.com/how-to-be-productive-avoid-analysis-paralysis/
---

You’re staring at the blank screen and you have no idea what to write. Or maybe you’re staring at a bug in some software you have to fix. Every career has these moments where you have no idea where to start. You’re overwhelmed by the options, and you’ve found yourself firmly in a state of “analysis paralysis.” So how do you get productive when you can’t even begin?

We’ll share a wonderful tip from a surprising place: Hollywood.

Inspiration can be found anywhere, and I often learn a lot from hearing about other careers. They call this “multidisciplinary learning.” It’s largely the reason why Leonardo DaVinci was so successful– he grabbed as much knowledge as he could from engineering, art, anatomy and more.

## How Hollywood Deals With Writer’s Block

Today’s discovery came to me while listening to the podcast Armchair Expert, where Dax Shepard was interviewing Mike Schur (the show-runner and head writer of NBC’s hit comedy, “The Good Place”). Dax Shepard was shocked to discover that a writer is only allowed 3 days to write an entire episode, saying “[that’s] not a lot of time for writer’s block!”

Dax Shepard and Mike Schur then share their secret:

> **Dax Shepard:** “My technique as a writer, to get over writer’s block is to give myself permission to write something shitty.”

> “Don’t you think it’s own of the greatest assets you can have?”

> **Mike Schur:** “Of course.”

> **Dax Shepard:** “You become paralyzed with trying to write something perfect, and you’ll just never write.”

It turns out that there’s a term in Hollywood for this process of iterating: “The Vomit Draft.”

## The Vomit Draft

The idea is that you just vomit something out. Maybe there are some good chunks in there (forgive me), but ultimately you are most likely going to throw away the whole draft.

So how does that even help?

Well, once you’ve started creating you have effectively removed the roadblocks. You have become un-paralyzed. Now you’re free to write a second draft that will almost certainly be better than the first. As I’ve heard it said before, “there’s only one direction to go from here: up!”

## How To Apply It

So if you’re working on a software bug, make a guess about the cause the bug and investigate it even if it’s wildly wrong. Just by getting into the motion of investigating will help you find the real root cause sooner.

If you’re trying to write an email to your boss about a promotion… write a very bad one first. After you’re done, you’ll know what not to say. Just be sure to avoid adding an email address first so you don’t accidentally send it! We believe in [impermanence](https://dev.to/cubiclebuddha/your-code-is-not-pretty-your-code-is-already-dead-code-glp), but some things are not as easily undone.

Those are just a few practical examples of how to get in the motion. What we’re really talking about here is iterating. You start small and you build on it. More importantly, don’t be afraid to chuck things out if they aren’t working. But you can’t throw away pages if you haven’t written any. So get started with something crappy!

## Other Examples Of How Iterating Solves Quality And Productivity Problems

It’s clear that iteratively developing a product can help to refine the idea into it’s best version over time. Here are some other examples from other careers that prove that “vomit drafts” or prototypes can help immensely.

- **Software:** The software development world introduced a concept called Agile that has recently been applied to all types of careers. You can read more about it [here](https://dev.to/cubiclebuddha/samsara-5-agile-techniques-to-end-suffering-and-increase-learning-4a76).
{% link https://dev.to/cubiclebuddha/samsara-5-agile-techniques-to-end-suffering-and-increase-learning-4a76 %}

- **Novel Writing:** Charles Dickens was famous for writing his novels in sections. And if you look at how prolific he was, you’ll see that he was onto something. Read more about his iterative novels [here](https://dev.to/cubiclebuddha/how-charles-dickens-wrote-like-an-agile-programmer-f51).
{% link https://dev.to/cubiclebuddha/how-charles-dickens-wrote-like-an-agile-programmer-f51 %}

- **Visual Design** : We discussed “design thinking” recently, and [how this lesson from User Experience (UX) Design can help you to move past perfectionism](https://dev.to/cubiclebuddha/using-self-affirmation-to-fake-it-till-you-make-it-34l6)and to improve yourself iteratively.
{% link https://dev.to/cubiclebuddha/using-self-affirmation-to-fake-it-till-you-make-it-34l6 %}

## But What’s Worked For You?

I’d love to hear how you’re learning to overcome the paralysis that comes from a blank white canvas. How are you getting started?