# Mini Toolkit

## CREATE AWARENESS

1. Rate your anxiety using the SUDS scale (below):

<table data-header-hidden><thead><tr><th width="66"></th><th></th></tr></thead><tbody><tr><td><strong>10</strong> </td><td>Highest anxiety/distress that you have ever felt </td></tr><tr><td><strong>9</strong> </td><td>Extremely anxious/distressed </td></tr><tr><td><strong>8</strong> </td><td>Very anxious/distressed; can’t concentrate. Physiological signs present (e.g. racing heart, sweating, stomach distress, shortness of breath). </td></tr><tr><td><strong>7</strong> </td><td>Quite anxious/distressed; interfering with functioning. Physiological signs may be present (e.g. racing heart, sweating, stomach distress, shortness of breath). </td></tr><tr><td><strong>6</strong> </td><td>Moderate-to-strong anxiety or distress </td></tr><tr><td><strong>5</strong> </td><td>Moderate anxiety/distress; uncomfortable, but can continue to function </td></tr><tr><td><strong>4</strong> </td><td>Mild-to-moderate anxiety or distress </td></tr><tr><td><strong>3</strong> </td><td>Mild anxiety/distress; no interference with functioning </td></tr><tr><td><strong>2</strong> </td><td>Minimal anxiety/distress </td></tr><tr><td><strong>1</strong> </td><td>Alert and awake; concentrating well </td></tr><tr><td><strong>0</strong> </td><td>No distress; total relaxation </td></tr></tbody></table>

***

## REDUCE PHYSIOLOGICAL AROUSAL\*

*Optional if anxiety rating is under 7*

1. Put one of the TIPP skills into practice. Mark which skill you used below:
   * **Temperature**: splashing cold water on your face
   * **Intense Exercise**: exercising for 20-30 min
   * **Paced Breathing**: slowing breathing, taking care to take longer out breaths
   * **Progressive Muscle Relaxation**: tensing then releasing muscle groups
2. Re-rate your anxiety using the SUDS scale: \_\_\_\_\_\_\_\_

{% hint style="info" %}
\*Repeat this step up to one more time if your score did not go down. Remember, we don't want to get trapped in a cycle of avoidance!
{% endhint %}

***

## CHALLENGE BIASED THINKING

1. Briefly describe the code review situation.<br>
2. Write down your biased thoughts in table format.

Guiding questions:&#x20;

1. *How am I doubting my abilities as an engineer?*
2. *How am I doubting my abilities to manage my anxiety?*
3. *What am I worried will happen?*
4. *What do I think are the consequences of that outcome happening?*
5. *What am I afraid it means to / about me if that outcome were to happen?*

<table data-header-hidden><thead><tr><th width="493"></th><th width="127"></th><th></th></tr></thead><tbody><tr><td><strong>Thought</strong></td><td><strong>Pre- Believability (0-100)</strong></td><td><strong>Post- Believability (0-100)</strong></td></tr><tr><td>Example: Everyone will think I’m bad at coding</td><td>73</td><td>30<br></td></tr><tr><td><br><br></td><td><br></td><td><br></td></tr><tr><td><br><br></td><td><br></td><td><br></td></tr><tr><td><br><br></td><td><br></td><td><br></td></tr><tr><td><br><br></td><td><br></td><td><br></td></tr></tbody></table>

3. For each biased thought, rate how strongly you believe each to be true on a 0-100 scale in the “pre-believability” column of the table.
4. Write down the thought you most strongly believe to be true.
5. Write down any thinking traps you see in the thought you most strongly believe to be true:
6. Evaluate the evidence for and against this thought:

<table data-header-hidden><thead><tr><th width="221"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Thinking Trap</strong> </td><td><strong>Definition</strong> </td><td><strong>Example Thought</strong> </td></tr><tr><td><strong>Catastrophizing</strong> </td><td>Predicting something very negative will happen without any evidence </td><td>I’m going to introduce a breaking change to production. </td></tr><tr><td><strong>Dichotomous Thinking</strong> </td><td>Considering only the extremes and nothing in between </td><td>I’m an incompetent software developer. </td></tr><tr><td><strong>Minimizing</strong> </td><td>Discounting positive experiences, outcomes, or qualities </td><td>They only approved my pull request because they feel bad for me. </td></tr><tr><td><strong>Mind Reading</strong> </td><td>Believing you know what others are thinking, failing to consider other, more likely, possibilities </td><td>I’m annoying my teammates by asking for a code review. </td></tr><tr><td><strong>Negative Filter</strong> </td><td>Attending to only the negative aspects of a situation </td><td>I haven’t thought of all the possible edge cases.</td></tr><tr><td><strong>Over- generalizing</strong> </td><td>Generalizing a single instance as being indicative of all others </td><td>I introduced a bug to production last time so I’ll probably do the same this time. </td></tr><tr><td><strong>Personalizing</strong> </td><td>Assuming an action is directed to or because of oneself </td><td>They left a bunch of comments because they think I’m incompetent. </td></tr><tr><td><strong>Should Statements</strong> </td><td>Having a fixed idea of what should happen &#x26; overestimating how bad it is that these expectations aren’t met </td><td>I have years of development experience. I really shouldn’t feel anxious about code reviews. </td></tr></tbody></table>

Guiding Questions:

* *Am I 100% sure of this? Can I tell the future, or read minds?*
* *What is the worst that could happen? Could I handle it?*
* *Is there another explanation/ way of looking at this situation?*
* *Am I placing unrealistic and unattainable standards on myself that I wouldn’t expect another person to achieve?*
* *Am I overestimating the probability of this?*
* *Am I blaming myself for a situation outside of my control?*
* *Does \_\_\_ really mean that I am \_\_\_?*

| <p><strong>Evidence FOR</strong>: </p><p>(The thought is realistic and true) </p> | <p><strong>Evidence AGAINST</strong>: </p><p>(The thought is unrealistic and false) </p> |
| --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|                                                                                   | <p><br></p><p></p><p><br></p>                                                            |

7. Write down a rational response in response to your biased thought and rate its believability below:

*Guiding Questions*

1. *What is a more balanced view of the situation?*
2. *What would you say if this were your best friend/partner/child?*
3. *What was the strongest piece of evidence against your thought?*
4. Go back to the table of biased thoughts and re-rate how strongly you believe each to be true on a 0-100 scale in the “post-believability” column of the table.&#x20;
5. Rate your current anxiety using the SUDS scale: \_\_\_\_\_\_\_\_\_\_\_

|                   |                              |
| ----------------- | ---------------------------- |
| Rational Response | Believability Rating (0-100) |
|                   |                              |

***

## PROACTIVELY ENGAGE

If you are about to **ask for a review**, plan ahead and write down how you will ask for a review like a **DEAR**.

* **D**escribe the request
* **E**xpress how you feel about it
* **A**sk for specific feedback
* **R**einforce with gratitude and responsiveness

Write down a practice review request below:

*Example: “Could I get a review? I’m not feeling confident about the way I did XYZ* ��*, so could you pay extra attention to that section? Thanks! I appreciate you!”*

***

If you are about to **give a review**, plan ahead and write down how you will **GIVE**.

* **G**entle
* **I**nterested&#x20;
* **V**alidate
* **E**asy manner

Write down a practice review below:

*Example: “I can see a lot of effort and dedication went into this and I appreciate the approach you took. The code looks really solid, and it lays a good foundation for the new feature. I think you could move a couple constants created here to the settings file, but otherwise this code is very DRY. Great work!”*