Challenge Negatively Biased Thoughts
Last updated
Last updated
Now that we’ve identified our negatively biased thoughts, we’re going to choose a primary thought to challenge. This is the thought that we believed the MOST and will likely have the highest believability rating. If you have more than one thought at your highest believability rating, choose the one that you believe a teeny bit more or the one that hits you a little harder.
Go ahead and write down the Primary Biased Thought you’ll challenge in your notebook or text editor.
Now that we have our primary thought, we can challenge it! To do this, we’ll first identify which thinking traps we see in our primary negatively biased thought. Thinking traps are known thought patterns that lead to exaggerated, irrational, and unhelpful thoughts. The table below describes several that commonly pop up when we feel anxious:
Using the table above as a guide, write down the thinking traps you see in your primary biased thought. It’s common for thoughts to fall into more than one thinking trap, so feel free to select more than one!
As you start to notice your thinking traps, it may be helpful to keep track of which thinking traps you tend to fall for so that you can quickly check your thoughts based on your tendencies. For example, if you tend to catastrophize, the next time you’re in a code review, you can quickly ask yourself “hold on, am I catastrophizing again?” Take a moment to reflect on which thinking traps you tend to fall into in your notebook or text editor.
Alright, now let’s challenge that primary biased thought! To do this, we’re going to generate some evidence FOR and AGAINST the thought being true. (Why would we consider evidence FOR these thoughts? Well, sometimes our anxieties are created by things or people in our environment, and the resulting thoughts are actually realistic. That said, we’ll want to evaluate the evidence FOR extra carefully). This can be tough to do at first, so below are some guiding questions you might ask to help you generate evidence.
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 ___?
Imagine I had the thought “They regret hiring me because I’m so incompetent.” Here’s what my evidence might look like:
You’ll notice that there is still some evidence for the thought; that’s okay! The point of challenging your thought isn’t to be more positive or to ignore certain kinds of evidence. The point is to take a more balanced and self-compassionate point of view.
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 ___?
Thinking Trap
Definition
Example Thought
Catastrophizing
Predicting something very negative will happen without any evidence
I’m going to introduce a breaking change to production.
Dichotomous Thinking
Considering only the extremes and nothing in between
I’m an incompetent software developer.
Minimizing
Discounting positive experiences, outcomes, or qualities
They only approved my pull request because they feel bad for me.
Mind Reading
Believing you know what others are thinking, failing to consider other, more likely, possibilities
I’m annoying my teammates by asking for a code review.
Negative Filter
Attending to only the negative aspects of a situation
I haven’t thought of all the possible edge cases.
Over- generalizing
Generalizing a single instance as being indicative of all others
I introduced a bug to production last time so I’ll probably do the same this time.
Personalizing
Assuming an action is directed to or because of oneself
They left a bunch of comments because they think I’m incompetent.
Should Statements
Having a fixed idea of what should happen & overestimating how bad it is that these expectations aren’t met
I have years of development experience. I really shouldn’t feel anxious about code reviews.
Catastrophizing
Minimizing
Negative Filter
Personalizing
Dichotomous Thinking
Mind Reading
Overgeneralizing
Should Statements
Evidence FOR:
(The thought is realistic and true)
Evidence AGAINST:
(The thought is unrealistic and false)
What is the worst that could happen? That - they tell me I’m stupid because I’ve made the same coding mistake in multiple pull requests.
Am I blaming myself for a situation outside of my control? It was my mistake, but I don’t need to blame myself so intensely for it!
* If there is evidence in this column, check to see if they are due to thinking errors!
Am I 100% sure they regret hiring me? NO.
Can I read minds? NO.
Could I handle it? YES. I would ultimately be okay.
Am I placing unrealistic and unattainable standards on myself that I wouldn’t expect another person to achieve? YES! Making the same mistake multiple times is actually pretty normal and expected. It’s a part of learning!
Am I overestimating the probability of this? Yes, realistically they probably don’t regret hiring me because I’ve contributed a lot.
Does making a mistake really mean that I’m incompetent? NO. Everyone makes mistakes, including super star coders, and they aren’t considered incompetent!
Evidence FOR:
(The thought is realistic and true)
Evidence AGAINST:
(The thought is unrealistic and false)
* If there is evidence in this column, check to see if they are due to thinking errors!