The Problem You Think of versus the Problem You Have

A founder I worked with recently was stuck on a supplier. He needed 100 units of a component. He’d spent weeks hunting for a new supplier, getting quotes, comparing lead times, negotiating minimums. Every conversation was about the supplier. The supplier was the problem.

Except it wasn’t. His team had already hand-built working prototypes. They knew how to make the thing. What they didn’t have was the cash to wait on a perfect production run, and the patience to keep building while revenue stayed at zero. The constraint was sequencing and cash flow. The path forward was obvious. Build the rest the way you built the first, get the units on the ground, prove the concept, and let early revenue tell you when it’s time to scale into real manufacturing.

This situation is more common than most leaders would admit, and the cost is significant. In a survey of senior executives across dozens of companies, the strategist Thomas Wedell-Wedellsborg found that 85% agreed their organizations were bad at diagnosing problems, and 87% agreed that the flaw carried a high cost. Almost no one thought they were unaffected. These are not careless people. They’re capable individuals who jump to a solution before they’ve named the actual problem, because naming it is slow and uncomfortable, and acting feels like leadership.

The trouble is that different problems need different fixes, and the wrong category gets the wrong intervention almost every time.

We diagnose most execution breakdowns across four problem types, because where the problem lives determines what actually moves it. An operational problem is a gap in the process or resources.

The work would happen if the system supported it. A behavioral problem lives in individual habits. People know what to do and don’t do it under pressure. A structural problem is built into incentives and design. The org is quietly rewarding the thing it says it wants to stop. A cultural problem is the set of shared norms that makes any or all three of the above feel normal. Our founder’s situation read as a supplier problem, which sounds operational. The real issue was behavioral and structural. A hesitation to keep building, sitting on top of a cash position that was punished by waiting. A supplier would have solved nothing, because nothing in the supply chain was actually broken.

The part that makes the diagnosis worth the discomfort is in how the fix for one type actively worsens the others. Throw process at a behavioral problem, and you get more rules nobody follows. Throw motivation at a structural problem, and you exhaust good people fighting a system designed to keep them out. Throw training at a cultural problem, and you get a team that can recite the values and ignore them by Tuesday. Misdiagnosis isn’t neutral. It spends your scarcest resources, time and credibility, on the wrong target. And it teaches your people that effort doesn’t change anything.

I learned this version of the action in the infantry, where a misread situation can get people hurt. The most dangerous patterns were never the ones that looked most urgent. It was the quiet thing nobody named because everyone was busy reacting to the loud thing. You slow down for ten seconds, you read the ground for what’s actually there, and then you move hard. The order matters. Diagnose, then act, with everything you’ve got.

That second half is where most diagnoses die anyway. Naming the real problem and doing something about it are different acts, and the gap between them is where good analysis goes to rot. Our founder didn’t need a deeper diagnosis after we found the real constraint. He needed to go build the units that afternoon. A correct read that doesn’t turn into a decision is just a more sophisticated way of being stuck.

A few moves we run with our clients in finding the actual constraints:

• Write the problem three different ways before you propose a single solution. “The supplier won’t run small batches,” “I don’t have cash to wait,” and “I’m afraid to keep building without a guarantee” are three different problems with three different fixes. You’ll usually feel which one is true.
• Ask what would have to be broken for this to be the real problem. If the supply chain were genuinely the issue, the prototypes wouldn’t exist. The evidence in front of you often rules out the problem you’ve named.
• Name the type out loud: operational, behavioral, structural, or cultural. The category points to the intervention. Get the category wrong, and every dollar after that compounds the mistake.
• Then set a deadline measured in days, not quarters. Diagnosis without a hard move date drifts back into analysis, and analysis is the comfortable place to hide.

This is structured judgment, not measurement. We’re not putting a number on your culture or claiming a formula tells you the answer. We’re reading the evidence in front of us, naming the real constraint, and committing to a move before the comfortable wrong answer reasserts itself. Done honestly, that’s most of the work.

Most teams have the capability to solve their actual problem. What they’re missing is the discipline to name it before they reach for the checkbook.

This essay cites sources from Wedell-Wedellsborg (Harvard Business Review), Argyris and Schön (Jossey-Bass), and Pfeffer and Sutton (Harvard Business School Press). Contact us for a complete list of works cited.