Types of Hard Problems
We self-destructively tell ourselves that challenges are “hard,” without further qualifying them, giving our brains permission to stop…
We self-destructively tell ourselves that challenges are “hard,” without further qualifying them, giving our brains permission to stop thinking when we should push ahead. In this brief post, we will examine what “hard” really means and simple tactics for breaking the different cycles. Note: this post is concerned with traditional notions of difficulty, not with computational complexity theory.
It’s Hard Because We Don’t Know How to Do It
The most common type of difficulty is when the problem is solvable but we don’t personally have the knowledge to solve it. A great example is an app my brother built called HotPaws that helps a dog owner determine the temperature of the pavement based on the local weather. The app itself was not “hard” to build, but neither of us knew the calculations or principles necessary to determine how heat would transfer from the sun to the pavement in different climate conditions with different pavement materials. These problems are easy to solve: you have to find an expert who knows the content or you have to learn the content.
It’s Hard Because It’s Slow, Painful, or Undesirable
Perhaps more frequently we substitute “hard” for challenges we can solve but for which the process of solving them is monotonous, long, or laborious. Building a team from scratch is “hard” because we have to search, vet, and hire numerous candidates, train, and develop culture. Getting a home mortgage is hard because we have to maintain constant vigilance, find numerous documents, and answer an inordinate number of clarification questions and remain organized, which tests our patience for a prolonged period of time. Unsticking this category of problem also is easy — we have to buckle up and just do it or find someone to help share some of the load. Jocko Willink, retired Navy SEAL, says it best when describing how he wakes up early every morning when he says “Don’t think. Just execute the plan. The plan is the alarm clock goes off, you get up, you go work out. Get some.”
It’s Hard Because The End State Is Far Away
Building a startup fits into this category of “hard.” We perceive difficulty when we know we are on a long journey that has steps A through Z but when we are only cognitively aware of steps A and B. We know that we need A, an idea, and B a team, and then probably C a prototype or some investment, and we know that Z is an IPO/DPO or an acquisition, but what is F, M or P? We cannot see around the corners we have not yet encountered. I’d argue that this is the most challenging type of “hard” because effort can help alleviate the difficulty but returns can also be diminishing. To work through these challenges, we can take a three part approach:
Visualize and plan for the end states X, Y, and Z, but not overly so. Paint a compelling and plausible picture but don’t obsess over detail. Defining these will inspire and motivate, but it won’t be a roadmap for actual execution. Once you are ready to achieve X, Y, and Z, you will likely decide to move the goal post farther out or X, Y, and Z won’t be relevant due to how much has changed since A. Still, if one is to sail from San Francisco to Australia, one must first point the boat toward Sydney.
Work on A and B and begin to crystallize options for C.
Regularly check that B, C, and D are still on the path to Z and repeat.
It’s Hard Because No One Knows
Finally we have problems that are hard because no one knows the answer. Examples include big picture challenges such as “Does life exist on other planets?” but also more mundane or operational challenges like “Should we offer subscription pricing on our app or pay as you go options?” While no one person can answer these questions with authority (at least not today with regards to life on other planets), we can tackle them like a scientist by testing our hypotheses in the field. If life exists or does not exist, what indicators should we see? If we test a subscription program and a pay as you go model in an A/B fashion, which one do users flock to and avoid and why?
Taken together, it’s easy to see that what feels “hard” generally is not so hard if we are patient with ourselves and demand precision from our minds about what the blockers truly are.