The Most Expensive Mistake Leaders Make
Imagine spending months—sometimes years—building a solution, assembling a team, investing capital, and burning through energy, only to discover that you were solving the wrong problem all along. It happens more often than most organizations want to admit. The real culprit is rarely a lack of resources or talent. It is almost always a failure to ask the right question before sprinting toward an answer.
This is not a new insight. It sits at the very heart of design thinking, one of the most influential frameworks in modern business strategy. And yet, despite its widespread adoption, the most foundational principle of design thinking remains the most frequently skipped step: problem definition. Before you explore solutions, you must be absolutely certain you have correctly identified the problem you are actually trying to solve.
What Design Thinking Actually Teaches Us
Design thinking is often described as a creative, human-centered approach to innovation. But at its core, it is a structured problem-solving process built on two equally important pillars: rigorous qualitative research and the disciplined application of design principles such as data visualization, iterative prototyping, and systems thinking.
The ratio matters. Roughly 80% of the design thinking process is dedicated to understanding the problem deeply before a single solution is proposed. That means most of the work happens before a whiteboard gets touched or a prototype gets built. It means talking to real people, observing real behaviors, mapping real pain points, and resisting the temptation to jump ahead.
The process begins not with answers but with questions—and not just any questions. Great problem-solving demands great questions. Open-ended, curious, assumption-challenging questions that peel back the surface of what appears obvious to reveal what is actually true. Only once you have done that hard, sometimes uncomfortable work of inquiry can you reliably identify the actual problem worth solving.
A Lesson Learned Twice: From Steel Mills to AI Presentations
Jim Szafranski, CEO of Prezi, learned this lesson not once but twice, through two very different professional chapters. His first encounter came as an MIT graduate student in the late 1980s, when he was applying early artificial intelligence techniques to optimize production in steel mills. His second came decades later, as he steered Prezi—a global visual presentation platform—into the era of generative AI.
In both cases, the critical breakthrough did not arrive through better algorithms or more sophisticated technology. It came from stepping back and asking a better question. This is a pattern worth paying close attention to, precisely because it runs counter to the dominant instinct in technology-driven environments, where the reflex is to reach for a more powerful tool rather than to interrogate the problem itself more carefully.
Szafranski's experience confirms what design thinkers have long argued: the quality of your solution is fundamentally constrained by the quality of your question. Upgrade the question, and you upgrade everything that follows.
Why We Default to the Wrong Questions
If asking better questions is so obviously valuable, why do so many organizations skip this step? Several forces push leaders and teams toward premature solution mode.
- Urgency bias: When pressure is high, moving fast feels responsible. Pausing to question the question can feel like delay, even when it is actually the highest-leverage activity available.
- Expertise traps: The more experienced someone is in a domain, the more quickly they pattern-match to familiar problems. This can cause them to misidentify novel challenges as variations of problems they have solved before.
- Organizational incentives: Many companies reward action and output over reflection and inquiry. Questions that challenge assumptions can be perceived as disruptive or as a sign of uncertainty rather than intellectual rigor.
- Technology seduction: In an age of generative AI and rapid prototyping tools, the ability to produce solutions has never been faster or cheaper. This ease of production can accelerate the rush toward answers before the problem is properly understood.
How to Apply This in Practice: A Framework for Better Questions
Whether you are a founder navigating a product pivot, a team leader working through an operational challenge, or an executive steering organizational strategy, the following practices can help you slow down enough to ask the right question before you run toward an answer.
Start with "What problem are we actually trying to solve?"
This sounds deceptively simple. It is not. Ask this question in your next meeting and pay attention to how many different answers surface. Misalignment at the problem definition level is one of the most common and costly sources of organizational friction. Getting everyone in the room to agree on what the real problem is—before discussing solutions—can save enormous time and resources downstream.
Use qualitative research before quantitative analysis
Data tells you what is happening. Conversations tell you why. Before you dive into dashboards and metrics, invest time in direct qualitative inquiry. Interview customers, observe users in context, map the experience of the people most affected by the problem. Qualitative research does not replace quantitative analysis; it gives that analysis meaning and direction.
Challenge your assumptions explicitly
List the assumptions embedded in the way you have framed the problem. Then ask: what if the opposite were true? What if the constraint we take for granted is actually optional? This kind of assumption inversion often reveals that the real problem is upstream of where the team has been looking.
Prototype the problem, not just the solution
One of the most underused tools in design thinking is problem prototyping—creating visual representations of the problem space, including stakeholder maps, journey maps, and causal loop diagrams. Visualizing the problem often surfaces dimensions that were invisible in a purely verbal or analytical description.
The Competitive Advantage of Asking Better Questions
In a world where generative AI can produce solutions at remarkable speed and scale, the human ability to ask the right question is becoming a more valuable differentiator, not less. Anyone with access to a language model can generate answers. Fewer people have cultivated the discipline, the curiosity, and the methodological rigor to generate the right questions first.
Design thinking, applied seriously and not just as a workshop exercise, offers a proven path to developing that capacity. It reframes intelligence not as the speed of solution generation, but as the depth of problem understanding. And as Jim Szafranski's story illustrates, that reframing can transform outcomes—whether you are optimizing production in a 1980s steel mill or building the next generation of AI-powered communication tools.
The next time you find yourself racing toward a solution, pause. Ask yourself: am I solving the right problem? The answer to that question may be the most valuable thing you produce all year.