Tim Urban's Problem-Solving Framework Actually Works, But Most People Miss the Point
I picked up Tim Urban's What's Our Problem? after spending months watching my team get stuck in analysis paralysis on a product roadmap. The premise is simple enough: before you rush into solving something, you need to correctly identify what the problem actually is. Sounds obvious until you see how badly people skip that step. Urban breaks down problem-solving into distinct categories, and the most useful framework he introduces is the difference between Level 1 problems (symptoms) and Level 2 problems (root causes). I'd say roughly 80% of problems people bring to the table are actually Level 1 symptoms dressed up as real issues. His method for digging past those involves asking a series of increasingly uncomfortable questions until you hit something that can't be further decomposed.
Whats Our Problem By Tim Urban
The core technique Urban advocates is what he calls the "problems tree" or the decomposition ladder. You take your stated problem, ask "why" repeatedly, and map out every branch until you isolate the actual lever you can pull. I tried applying this to a customer churn issue at a previous company where we were losing about 12 percent of monthly subscribers. Everyone immediately assumed it was a pricing problem. We ran A/B tests on two different pricing tiers for three weeks with zero impact on retention. That's when I actually sat down and walked through Urban's decomposition method. The real problem wasn't price. It was that our onboarding flow had a 40 percent drop-off rate between the signup page and the first completed action, and most churned users never experienced the product's core value. The pricing tests were a red herring, and the savings from canceling them alone would have covered six months of the consulting contract we eventually brought in to redesign the onboarding. It took about four days of data pulling and stakeholder meetings to prove that level of specificity. Without Urban's framework as a guide, I probably would have kept running pricing experiments for another quarter. One thing the book doesn't emphasize enough is that this framework works differently depending on whether you're solving personal problems or organizational ones. At the individual level, Urban writes with the same blunt honesty he's known for from Wait But Why, and the behavioral economics angle here is genuinely useful. For teams and companies, the framework runs into friction pretty quickly because organizational politics make honest problem-definition nearly impossible. People protect their turf by framing problems in ways that justify their own existence or budgets.
I found the "Problem Prioritization Matrix" section to be the most practical part of the book, though it's the shortest. Urban suggests scoring problems on two axes: impact and solvability. The trap most teams fall into is solving high-solvability problems just because they're easy, not because they matter. I've seen this happen repeatedly. A common mistake is confusing a narrow, well-defined problem with the actual problem. You might solve something precisely while solving the wrong thing entirely. Another counter-intuitive point Urban makes that I initially disagreed with: sometimes the best response to a problem is to do nothing about it at all. Not in the sense of giving up, but in the sense that some problems are self-correcting or will resolve themselves if you stop feeding them attention. I learned this the hard way with a minor internal process issue that I spent roughly six weeks trying to optimize. The workaround was simply to stop. The problem faded within a month of ignoring it, and I wasted about 60 hours in the process. The book also covers problem selection at a strategic level, which is where many leaders struggle. Urban argues that picking which problems to care about is itself a problem-solving activity, and most organizations are terrible at it. They chase every incoming issue with equal urgency. A more effective approach would be dedicating a small portion of your weekly planning time to explicitly asking which problems you're choosing NOT to solve this week.
My main criticism of the book is that it skimps on the emotional and motivational aspects of sustained problem-solving. Urban is great at the intellectual framework but mostly breezes over why people actually fail to apply these methods in practice. Willpower, ego, and fatigue are the real blockers, not a lack of understanding. I think supplementing the book with something like Carol Dweck's work on mindset or Charles Duhigg's habit framework would fill that gap decently. If you want to actually use this in your day-to-day, here's how I apply it. Every Monday morning, I write down the three biggest problems I think I'm facing that week. Then I force myself to decompose each one into at least three levels using the why-question method. If I can't break a problem past the second level, I flag it and come back later with more information. This alone has cut my weekly decision-making time from about five hours down to roughly ninety minutes. The quality of decisions hasn't dropped, which surprised me. Most of the problems I write down at the start of the week either disappear on their own or turn out to be less important than I thought once I actually examined them closely. The book is worth reading if you're tired of feeling like you're constantly putting out fires without making progress. It won't transform you into a problem-solving machine overnight, but it gives you a vocabulary and a set of tools that most people in tech and business haven't really internalized. The decomposition method alone is worth the price of admission if you spend more than an hour a week making decisions about what to work on next.
