Unlocking innovation starts with a clear understanding of the problem. Without a unified grasp of organizational identity and goals, companies risk the high failure rates seen in business transformations—a disconnection that ripples from executives to frontline managers, creating inefficiency and missed opportunities. Clarity enables focused, effective problem-solving.
Challenges with Defining a Problem
1. Premature solutioning. Teams gravitate toward the first feasible solution without exploring better options. Time constraints and high-activity environments can lead to poorly orchestrated planning sessions, risking solutions to ill-defined problems.
2. Varied definitions. A problem looks different through engineering, sales, and product lenses, creating interdepartmental misunderstandings.
3. Collaboration hurdles. The thorniest problems need many cross-functional partners, but the person leading the charge often gets the credit while contributors get overlooked. These recognition imbalances discourage some from giving full effort next time.
A Model for Defining a Problem: The 5 Whys
The 5 Whys is a simple, powerful tool that moves past outward symptoms to a problem's underlying cause, so you can address it once and for all. Toyota refined the method as a core part of its problem-solving training. Sakichi Toyoda, architect of the Toyota Production System, described it as "the basis of Toyota's scientific approach . . . by repeating why five times, the nature of the problem as well as its solution becomes clear." The lineage traces back to Socrates, who probed people's arguments with repeated "why" until they were forced to examine their own assumptions — the Socratic method.
Here's how it can look:
• A new release broke a key feature. Why? A server failed.
• Why did the server fail? An obscure subsystem was misused.
• Why was it misused? The engineer didn't know how to use it properly.
• Why didn't he know? He was never trained.
• Why wasn't he trained? His manager doesn't believe in training new engineers because they're "too busy."
A purely technical fault turns out to be a managerial one. You can fix the server, make the subsystem less error-prone, train the engineer, and address the manager's belief — a proportional investment at each level. In other words, fix the server, make the subsystem less error-prone, train the engineer, and talk with the manager.
Five is just a number; ask why as many times as you need, but not so many that you drift into unrelated complaints.
Advantages and Downsides
• Advantages: offers a structured approach; isn't about blame but root cause; democratizes problem-solving; builds a culture of continuous improvement.
• Downsides: won't work if the cause is genuinely unknown; assumes a single cause when causes are often jointly sufficient; one weak answer can throw off the whole chain; results vary between users.
A Complementary Tool: Reframing
The 5 Whys drills into a known problem well — but what if the problem was misdiagnosed from the start? That's Thomas Wedell-Wedellsborg's focus in What's Your Problem? His finding: leaders routinely solve the wrong problem well, because they fall in love with an initial framing before testing it. His reframing practice: state the problem in one sentence, seek an outsider's view, look for exceptions where the problem doesn't occur, check who actually owns it, and ask what's missing from the definition. Reframe first to make sure you're drilling into the right problem, then apply the 5 Whys.
Process for Defining and Validating Problems
1. Define separately. Gather each department's closest people and run a 5 Whys exercise to produce their own statement.
2. Reconcile. The next stage is to create alignment. If definitions already overlap, great. Otherwise, combine all the problem statements and spend time on one collective definition that encompasses different voices, because each group thinks about the problem differently, through their own lens and expertise. Even if the final version doesn't satisfy everyone, as long as everyone can weigh in and the majority rules, that’s enough. This co-creation process can be messy, but with the right group norms and facilitator, it can be effective.
3. Create buy-in. Some problems have plagued companies for years, and they are so big they outweigh any one individual or team. Instead of one person taking all the credit, frame it as a collective opportunity for the team to get recognition, rather than one person leading the charge.
4. Validate. Once you have the problem statement, spend time with your stakeholders (senior leaders, partners, customers) to get their opinions, confirm it is the right problem, and assess the value it will deliver once solved.
5. Evaluate readiness. Review the team's capability to execute. People often suggest ideas based on their existing skillset rather than the best approach — bring in the right resources, or the team will row hard without the muscle to reach the destination.
A well-defined problem is the foundation of innovation. Structured methods like the 5 Whys and reframing, paired with collaborative clarity, pave the way for impact.
Quote of the Day. "Always the beautiful answer who asks a more beautiful question." — E.E. Cummings
Reflection Question. What problem-solving techniques have proven effective for you and your organization? Comment and share below; we’d love to hear from you!
As an executive, leadership, and team coach, I work with leaders to cultivate a culture of innovation. Contact me to explore this topic further.
The next article in this series (3/6) looks at carving out dedicated time for the deliberate thought innovation requires.
What methods do you use to define a problem?
