I once walked into my manager’s office with a problem. Not a complaint — a real scenario, laid out straight: here’s what’s happening, here’s the tension, here’s what happens if we don’t deal with it. I wasn’t looking for someone to fix it for me. I was looking for a steer, because the call wasn’t mine to make.
He didn’t see it that way. “Don’t bring me problems. Bring me solutions. I already know what the problem is.”
I got it, in a way — that’s the version of leadership everyone’s taught to admire. But sitting on the other side of that desk, I also did some quiet math. If I bring him a solution, he approves it, I execute it, and it backfires — I’m still the one who gets to explain the failure. “He authorized it” doesn’t appear in my performance review. The instruction to “bring solutions, not problems” sounds like empowerment. From where I was sitting, it just moved the risk downhill.
Which is the thing about that line — it’s usually right. Most problems that land on someone’s desk are exactly what they look like: the report’s late, the client’s annoyed, the invoice is wrong. Fix it, move on. Our brains are built for this — fast, automatic, System 1 thinking that hands you an answer before you’ve finished reading the email. It feels efficient. It feels like leadership. And more than anything, it makes the anxiety of not knowing go away, fast.
Which is exactly why it’s so easy to apply the same instinct to the problems that aren’t like that at all.
Because some problems aren’t obvious. They’re gnarly, they’re tangled, and the person handing them to you doesn’t actually know what they’re asking for — they just know something’s wrong. Treat that kind of problem the same way you’d treat a broken invoice, and you get a very specific, very expensive kind of failure: flawlessly executing the wrong solution.
Stockholm found this out the hard way, sort of by accident. The city was drowning in traffic, jammed across its bridges into the inner city. The obvious fix — the one that “solving the problem” would’ve handed you — was more roads. Bigger bridges. A multi-year, multi-billion-krona engineering project. Instead, in 2006, someone paused long enough to ask a different question: is this actually a roads problem, or is it a supply-and-demand problem? Turned out to be the second one. A toll — a few dollars, charged only at peak hours — did in months what a new bridge would’ve taken years and a fortune to attempt, and traffic dropped by a fifth almost overnight.
Same problem. Completely different question. That’s the whole fault line, right there.
Not every problem needs framing. Some genuinely just need solving — the invoice, the late report, the thing you’ve seen a hundred times before. But some problems only look like the thing you’ve seen before, and the only way to find out which one you’re standing in front of is to pause long enough to ask. Which is, itself, the hard part. Because in the moment, you rarely know if you’re looking at a fire that needs putting out or a question that hasn’t been asked yet.