audace.github.io/rejection.html at master · Audace/audace.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
<!DOCTYPE html>
<html lang='en'>
  <head>
    <meta charset="utf-8">
    <title>William Fry</title>
    <meta property='og:title' content='William Fry'>
    <meta property="og:url" content="http://williamrfry.com/">
    <meta property="og:site_name" content="William Fry">
    <script>
      (function (i, s, o, g, r, a, m) {
      i['GoogleAnalyticsObject'] = r; i[r] = i[r] || function () {
        (i[r].q = i[r].q || []).push(arguments)
      }, i[r].l = 1 * new Date(); a = s.createElement(o),
        m = s.getElementsByTagName(o)[0]; a.async = 1; a.src = g; m.parentNode.insertBefore(a, m)
      })(window, document, 'script', '//www.google-analytics.com/analytics.js', 'ga');

      ga('create', 'UA-69618114-1', 'auto');
      ga('send', 'pageview');
    </script>
  </head>
  <body>
    <div style='padding: 50px'>
      <article class="post h-entry" itemscope="" itemtype="http://schema.org/BlogPosting">

        <header class="post-header">
          <h1 class="post-title p-name" itemprop="name headline">Rejection sucks. Decision trees make it suck less.</h1>
          <p class="post-meta">
            <time class="dt-published" datetime="2016-04-05T00:00:00+00:00" itemprop="datePublished">Apr 5, 2016
            </time></p>
        </header>

        <div class="post-content e-content" itemprop="articleBody">
          <p>Today <a href="http://www.solutionloft.com">SolutionLoft</a>, the startup I’m working on, was not chosen as a
            recipient for the Wharton Venture Award – a $10k equity-free grant to work on an idea during the summer. And
            in short, <strong>rejection fucking sucks</strong>.</p>

          <p>Yes, mom, I’m sorry for dropping the f-bomb… but it’s true, especially when it’s the rejection of something
            you’ve poured so much blood, sweat and tears into. But there’s a way to make it easier and more productive.
            The basic ingredients are a decision tree, preparation, and discipline.</p>

          <!--more-->

          <h3 id="decision-trees-101">Decision Trees 101</h3>

          <p>From Wikipedia:</p>

          <blockquote>
            <p>It’s a… “decision support tool that uses a tree-like graph or model of decisions and their possible
              consequences, including chance event outcomes, resource costs, and utility.”</p>
          </blockquote>

          <p>The bottom line is that a decision tree maps down your thought process and the possible end results,
            including your reaction to each.</p>

          <p>In more detail, any decision has a number of options that you can choose. From any option that you choose,
            there are a number of different outcomes. Which outcome occurs is out of your control (whether you get
            accepted or rejected). What is in your control is how you respond to the different outcomes, extending the
            tree further to the next decision.</p>

          <h3 id="rejection-without-decision-trees">Rejection without Decision Trees</h3>

          <p>Without decision trees, the flow of events looks a little like the following:</p>

          <p><img src="assets/without_trees.png" alt="Rejection without trees" class="center-image" style='max-width: 100%;'></p>

          <p>While it’s not a problem if everything goes well (i.e. the events turn out as you would like), if things
            don’t go as planned, the emotional toll is much harder. Rejection sucks much worse. Without having prepared
            for the possibility of failure with the help of a decision tree, you’re left with a much higher cognitive
            load.</p>

          <p>Now you must not only reconcile and reflect on events not playing out in your favor but you must also make a
            decision about what to do next. Do you continue working as you have? Do you pivot to something else? Do you
            give up altogether and send your resume to Goldman?</p>

          <h3 id="rejection-with-decision-trees">Rejection with Decision Trees</h3>

          <p>With decision trees, the decision about what to do next is planned for in advance:</p>

          <p><img src="assets/with_trees.png" alt="Rejection with trees" class="center-image" style='max-width: 100%;'></p>

          <p>As you can see, the decision on whether to quit or keep on has already been made by you. On the chance that
            you get rejected, you don’t have the added burden of deciding what to do next. This allows you to let your
            emotions have an hour or two to vent before immediately moving on to what’s next on the tree. This is where
            discipline becomes key.</p>

          <h3 id="adding-in-discipline">Adding in Discipline</h3>

          <p>The problem with plans is that they’re only that. They’re only as strong as they’re followed. Where your
            preparation for failure leaves off is where your discipline becomes key. The following is how I suggest to
            deal with rejection in a disciplined way:</p>

          <ol>
            <li>Before opening the email, remind yourself what your decision tree dictates that you’re going to do in each
              case.</li>
            <li>Open the email and run through it to understand the end result.</li>
            <li><code class="language-plaintext highlighter-rouge">CMD-Q</code> your email client.</li>
            <li>Give yourself two hours to let it sink in and for your emotions to run through the due course of
              reactions. Go for a walk. Get a milkshake.</li>
            <li>Two hours later: open up your email client and pull up the email.</li>
            <li>Write down the key takeaways of the feedback and what you’ve learned from the process as a whole. Save the
              note so that you can reflect on it later.</li>
            <li>Archive the email.</li>
            <li>Immediately start working on the next step of the decision tree.</li>
          </ol>

          <p>By having a set routine for the outcome combined with a preplanned next step in your decision tree, you allow
            yourself to emotionally discharge without losing your productivity or end vision.</p>

          <h3 id="summary">Summary</h3>

          <p>Ahead of YC interview decisions, rejection for thousands of us is right around the corner, but there’s a way
            to turn it to your favor with some preparation, a decision tree, and a little shake of self-discipline.
            Prepare your decision tree ahead of being notified of the decision, focusing on what you plan to do in each
            possible outcome. Be disciplined at the time of notification. Keep hustling.</p>


        </div><a class="u-url" href="/2016/04/05/Rejection-Sucks.html" hidden=""></a>
      </article>
    </div>
  </body>
</html>