Rope bridge crossing a misty canyon toward a stairway, representing how hard can it be as a mindset of curiosity

Thoughts

How Hard Can It Be?

“How hard can it be?” is not denial. It is a mindset. It is the choice to meet the unknown with curiosity instead of hesitation, and to treat barriers as problems to understand rather than excuses to stop.

The Attitude Behind the Phrase

“How hard can it be?” is probably my favorite phrase because it shows up in almost everything I do.

When I say, “How hard can it be?” I am not pretending something is easy. Instead, I am choosing how I want to approach it. I can meet a challenge with negativity, hesitation, and self-imposed limits, or I can meet it with curiosity, patience, and the assumption that there is an answer if I am willing to go looking for it. I choose the second one.

That matters because attitude shapes momentum long before results show up. If the first thing I tell myself is, “I can’t do that,” I have already closed the door before I even checked whether it was locked. If I say, “How hard can it be?” I am giving myself a different starting point. I am leaving room for exploration, questions, learning, and progress.

Why How Hard Can It Be Works

A lot of people give up surprisingly early.

They hear that a project is vague, a skill is missing, or a system is unfamiliar, and they stop themselves before they have even started asking the right questions. I have never been comfortable living there. Part of that probably comes from having to figure a lot of things out on my own. Over time, that turns into a different kind of confidence. Not the confidence of knowing everything in advance, but the confidence of trusting that if I can get clarity, I can usually find a way forward.

That is the real point of the phrase. It is not about ego. It is about refusing to let the unknown act bigger than it is.

If a project is vague, get clarity. When the work needs a skill I do not have yet, go get the skill. And when a system is broken and I do not understand it yet, ask better questions until I do. That is not recklessness. That is problem-solving.

It Is Not Arrogance, It Is Curiosity

I think this phrase gets misunderstood because people hear it as bravado.

They assume it means I think everything is simple, or that I believe I can muscle through anything without help. That is not what I mean. The phrase only works when it is paired with humility. I still need to be willing to fail, ask questions, slow down, pay attention, and bring in help when the situation calls for it. The point is not to pretend I already know. The point is to refuse the idea that not knowing is the end of the story.

That is where curiosity comes in.

If I do not understand something, my next question is usually, “Why can’t I just do it?” That question pushes me to look under the surface. It shifts the problem from being some vague source of resistance into something I can investigate. Once I can see how the thing works, the barrier usually starts shrinking.

How This Changes the Way I Learn

This mindset has shaped how I learn almost everything.

A lot of the skills I use now were not things I started with. WordPress development, CRM management, prepress, marketing automation, AI, photography, videography, all of those required a moment where I could have said, “That’s not really my thing,” and walked away. Instead, I treated each one as something I could explore, understand, and eventually use well.

That approach compounds over time.

Once you spend enough years learning new systems, solving unfamiliar problems, and seeing patterns repeat across different tools and disciplines, you start to trust your ability to figure things out. You realize that many problems are not unique in the way they first appear. They are variations of logic, structure, communication, sequence, and understanding. Once you start recognizing those patterns, the unknown becomes less threatening.

That is one reason this mindset works in both creative and technical spaces. Whether I am designing something I have never designed before or troubleshooting a system I have never touched before, I am still doing the same kind of work underneath it all. I am asking questions, looking for logic, identifying what is missing, and moving toward understanding instead of away from it.

What Happens When You Refuse to Try

There is a cost to shutting yourself down too early.

When people decide something is too hard before they have really engaged with it, they are not just avoiding difficulty. They are cutting themselves off from growth. Comfort becomes a ceiling. The unknown becomes something to avoid instead of something to learn from. Over time, that kind of thinking makes a person smaller than they need to be.

I do not think real growth happens inside the part of your life where everything already makes sense. This tracks with what Stanford psychologist Carol Dweck found in her research on growth mindset, the idea that treating challenges as chances to learn changes how far people are willing to go. You can read more about her growth mindset research here.

Growth shows up when you get outside your comfort zone, push into something unfamiliar, and stay with it long enough to understand it. Sometimes that process is frustrating. Other times it is slower than you want, or it reminds you very quickly that you are not as good at something as you hoped. None of that is a reason to stop.

The Risk In Thinking This Way

There are risks to this mindset, and I think it is worth being honest about them.

If I am not careful, I can come across like a know-it-all, or I can spend time figuring something out that another person could help accelerate much faster. Ego can get in the way if I let it. That is why this phrase only works when it stays connected to learning. The goal is not to prove I can do everything alone. The goal is to stay open enough to learn what the problem requires, and wise enough to recognize when collaboration will get the work further, faster, or better.

That is an important distinction.

“How hard can it be?” should expand capability, not isolate it.

How This Shows Up in My Work

This attitude runs through almost everything I do.

It shows up when I step into a vague project and start asking the questions that create clarity. It shows up when I have to learn a new tool to do the job well, or when a technical problem needs solving before it can be fixed. And it shows up when a creative challenge requires me to push past what I already know how to do.

As a designer, I do not want to be limited to the small circle of things I already know. If I want to become a better designer, then I need to be willing to expand the technical side of my understanding too. The same works in reverse. If I want to become better technically, I need enough creative range to imagine better ways of solving problems. The moment I tell myself something is too hard, I block my own progress before the work even starts.

That is why I say this out loud around other people too. I want teams to hear it. I want them to adopt the posture behind it. When people stop acting like a barrier is permanent, they start looking for ways through it.

The Shift

Most roadblocks are not final. They are temporary distractions, missing information, unfamiliar tools, or problems waiting for someone patient enough to work through them.

That is how I try to see them.

“How hard can it be?” is not about minimizing the work. It is about choosing a mindset that leaves room for answers. It is a way of reminding myself, and the people around me, that the unknown is often less of a wall than it first appears.

Sometimes the answer is that it is hard. Fine. Then go learn, ask, test, adapt, and solve it anyway.

That is where the growth is.

If the answer is not obvious yet, that does not mean stop. It usually means ask better questions, learn faster, and keep going until it makes sense.