You have said it. I have said it. Everyone has said it at some point, “this is just hard,” as if that settles something. As if difficulty is a fixed quality baked into the task itself, the way a rock is heavy or water is wet. Here is the problem: that belief is factually wrong, and it is quietly costing us.
Difficulty is not a property of anything. It is relational. It lives in the space between you and the task and is shaped by your experience, your confidence, your mood on a given Tuesday, and a dozen other factors that have nothing to do with the work itself. The same piece of code that stumps a junior developer gets solved in minutes by someone who has seen the pattern before. Same task. Entirely different experience. The task did not change. The person did.
Here is what I mean when I say difficulty is a perception: your brain does not wait for you to start before it forms a judgment. Before you open the document, before you make the call, before you sit down to write, your brain has already run its own simulation. It has taken your history, your current confidence level, your beliefs about what you can do, and it has generated a prediction about how this is going to go. That prediction is what you feel as “hard.” You have already decided, before you have tried anything.
I noticed this in myself when I kept delaying a particular kind of analysis I needed to do for a project, one that involved a method I had not used in years. I told myself it was hard and that I needed more time to prepare. What was actually happening was that my brain had predicted failure based on old evidence, and I was honoring that prediction as if it were fact. When I finally started, twenty minutes in, I realized I had been protecting myself from a problem that existed entirely in my anticipation of it.
Let me be clear about one more thing, because this part is easy to miss: complexity and difficulty are not the same. A task can have many steps, many unknowns, many moving parts, and still not feel hard if you have the resources to meet it. Complexity is objective. Difficulty is perceived. And perception can shift. We often do not perceive complex tasks as hard and we often make the mistake of thinking, when we do perceive something as hard, that it’s because of the complexity. For example, protocol analysis is complex, but people who’ve done it again and again do not perceive it as hard.
Here is the most important thing to know: the default interpretation most people land on when something feels hard is wrong. Research consistently shows that people experiencing difficulty tend to read it as a signal that they are not capable of doing the thing. As if “hard” means “not for me.” That is not a reasonable conclusion. It is a systematic error. The tragedy is that difficulty often signals the opposite: that the thing in front of you is worth doing, that it has real weight, that effort is required because the stakes are real. The signal is accurate. The interpretation is broken.
Imagine a scenario where an SNMP trap is fired based on a device showing data throughput above a threshold and 20 percent higher than normal. What does this signal mean? Is there an attack? Is someone backing up a large amount of data to network storage? Are thirteen machines that pass communications through the device all doing a network-based installation at the same time? The point is that the signal does not always mean an attack is under way. In the same way, complexity as a signal does not mean hard. Additionally, the existence of the feeling of difficulty or “hard” does not mean “can’t.” It means that measurement is in order.
So what do you do with this? A few things, and none of them require overhauling your personality.
Write down or at least conceptualize and verbalize what is hard about it. Externalizing the difficulty, getting it out of your head and onto a page or out of your mouth and into your ears, interrupts the automatic avoidance that makes hard things feel worse. Ask yourself why it matters. Reframing the difficulty as evidence of importance, rather than evidence of your limitation, changes what the feeling means. And find the smallest possible first step you can actually complete. Not the project, the next action. One real success lowers the perceived difficulty of everything that follows it.
The wall you are staring at is not a stop sign. It is the exact spot where growth happens. The discomfort of hard work is not danger. It is the sensation of your capability expanding. Which means the only mistake you can actually make is deciding the wall is the destination.
In the end, based on the research, I discovered a 7-factor protocol that can be used to change hard into valuable:
- Name and externalize: Notice the “this is hard” framing, write down why. This is about interruption.
- Audit the demand-resource gap: Distinguish complexity from difficulty. Identify specific missing resources and challenges.
- Reframe difficulty as importance: Ask, “Why does this matter?” Use difficulty as evidence of value, not impossibility.
- Reappraise arousal as readiness: Relabel physiological arousal: “My body is preparing me.” Shift from threat to challenge physiology.
- Activate growth orientation: Frame engagement as development, not validation. What will I be able to do after this challenge that I haven’t done before?
- Build a proximal success architecture: Decompose into small, achievable sub-goals with immediate feedback. This is creating mastery experiences.
- Embrace productive struggle: Recognize the impasse as the learning activity. Partial attempts build cognitive scaffolding.
This post is based on a literature review I conducted while developing and testing these ideas. The more I looked, the more the evidence pointed in the same direction. Nothing “is” hard. We either perceive it as that or we don’t and changing our perception can, well, not to sound overly dramatic, but changing our perceptions can change our lives.