Master the Art of Problem-Solving: 3 Steps to Tackle Any Challenge

“The problem is not that there are problems. The problem is expecting otherwise and thinking that having problems is a problem.” – Theodore Rubin

Every business has problems. That’s not a diagnosis of dysfunction — it’s just what running a real company looks like. The difference between businesses that solve problems and businesses that keep fighting the same fires is rarely effort or intelligence. It’s whether the owner is solving the actual problem or repeatedly patching its symptoms.

That distinction matters more than it sounds. A team member who keeps missing deadlines, a recurring client complaint, a process that breaks every few months in a slightly different way — these often get treated as one-off issues requiring a quick fix, when they’re actually the same underlying problem resurfacing in different clothes. Solve the symptom enough times and you’ll be solving it forever. Solve the root cause once and it stops coming back.

This is genuinely different from decision-making — choosing between known paths forward is a different skill than diagnosing what’s actually broken in the first place. Here’s the three-step process for the diagnostic work.

Step 1: Identify the Root Cause — Not Just the Symptom in Front of You

The first and most important discipline in problem-solving is resisting the urge to fix what’s visible before understanding what’s actually generating it. The visible issue — a missed deadline, an unhappy client, a process breakdown — is almost always a symptom. The root cause is usually a layer or two beneath it.

A structured way to dig past the surface:

• What’s actually happening here, specifically? Not the general pattern — the precise sequence of events in this instance.
• Why is this happening? Ask it once, then ask it again about your own answer. Most root causes require asking “why” three to five times before reaching something genuinely structural rather than circumstantial.
• Has this happened before, in a different form? If the same underlying issue has shown up multiple times with different surface details, that’s strong evidence you’re looking at a systemic gap rather than an isolated incident.
• What would have to be true for this to never happen again? This question often reveals the root cause faster than asking why it happened, because it forces you to name the missing structural element directly.

This process — root cause analysis — is what separates a fix from a patch. A patch addresses the symptom you can see today. A fix addresses the structural gap that’s been producing symptoms in different forms over time. The investment in digging deeper at this stage pays for itself many times over by preventing the same problem from recurring next quarter in a new costume. root cause analysis, ensures that you’re addressing the actual problem instead of wasting time on superficial fixes.

Step 2: Brainstorm Solutions to the Real Problem — With the Right People in the Room

Once the root cause is genuinely clear, the solution-generation phase becomes far more productive, because you’re solving the actual problem instead of guessing at fixes for a symptom. This is where creativity and diverse perspective matter most.

What makes this phase produce better solutions:

• Include people who see the problem differently than you do. A team member closer to the day-to-day operation often has context the owner doesn’t. An outside advisor unfamiliar with “how things have always been done” often sees options that insiders have stopped noticing.
• Generate volume before judgment. Solutions assessed and dismissed too quickly rarely get a fair hearing. Generate a genuine range of options — conventional and unconventional — before evaluating any of them.
• Explicitly ask what resources already exist that could be leveraged. Often the most efficient solution uses something already available — a team member’s underused skill, an existing tool, a process that could be adapted — rather than requiring something entirely new.
• Push past the first idea that sounds reasonable. The first solution that comes to mind is rarely the best one; it’s just the most available. A few additional minutes of generation frequently surfaces a meaningfully better option.

The goal of this step is genuine optionality — a real set of choices to evaluate, not a single idea rushed into action because it arrived first.

Step 3: Evaluate Against the Root Cause, Then Execute Without Delay

With several real options on the table, the evaluation criterion that matters most is simple: does this solution address the root cause identified in Step 1, or does it just make the current symptom less visible?

Three questions that filter effectively:

• Does this solve the actual problem, or does it just buy time? A solution that addresses only the symptom will need to be repeated. A solution that addresses the root cause shouldn’t need to be revisited for the same underlying issue.
• Do we have the resources and authority to execute this well? The best solution on paper is worthless if it requires capacity, budget, or buy-in that doesn’t exist. Choose the best solution that’s actually executable, not the theoretically ideal one that will stall.
• What’s the risk if this doesn’t fully work? Most solutions to real business problems are imperfect on the first attempt. Understanding the downside if the chosen approach needs adjustment helps you commit confidently rather than hesitating indefinitely.

Once a solution is chosen, commit and execute. A well-diagnosed problem with no action behind it produces no different outcome than no diagnosis at all. Take the first concrete step this week, observe what happens, and adjust based on real information rather than further analysis.d adapt as needed.

What Root-Cause Thinking Looks Like in Practice

One of the best examples of creative problem-solving comes from the early months of the COVID-19 pandemic. Angie Dobransky shared a story about her housekeeper, who faced a unique challenge.

Clients were concerned about cleaning supplies being brought into their homes from other locations, potentially carrying germs. Instead of ignoring the issue, she listened and identified the root cause: clients wanted to feel safe. Her solution? She purchased a mop for each client and stored it in their homes.

This simple, cost-effective fix not only addressed the problem but also strengthened her relationships with clients by showing that she cared. It’s a powerful reminder that great solutions often come from empathy and listening.

Notice what made this solution work: she didn’t address the surface request (use different supplies, prove the equipment was clean) — she identified what clients actually needed, which was reassurance and a sense of control over what entered their homes. That’s root-cause thinking: the presenting complaint and the underlying need are often two different things, and the best solutions address the second one.

Best Practices for Effective Problem-Solving

To become a master problem-solver, keep these best practices in mind:

• Stay Calm Under Pressure: Resist the urge to react immediately. Take a moment to breathe and assess the situation.
• Engage Your Team: Collaboration leads to better solutions. Involve people with diverse perspectives.
• Focus on Solutions, Not Blame: Avoid the temptation to point fingers. Direct your energy toward finding answers.
• Be Flexible: If your first solution doesn’t work, pivot and try something new. Problem-solving is often an iterative process.

Common Challenges in Problem-Solving

Even seasoned problem-solvers face challenges, such as:

• Tunnel Vision: When you’re fixated on one solution, you might miss better options. Step back and reassess the problem from different angles.
• Analysis Paralysis: Too many options can be overwhelming. To overcome this, start with one small step and adjust as needed.

A third common challenge worth naming: treating every problem as novel. When a problem feels unfamiliar, it’s tempting to start the diagnostic process from scratch every time. But many recurring business problems are variations on a small number of structural gaps — undocumented processes, unclear decision authority, a missing system. Building the SOPs and structure that prevent the most common root causes from recurring is often more valuable than getting faster at solving each new instance.

RADical Action Step: Diagnose Before You Fix

Think of a problem that keeps recurring in your business — not a one-time event, but something that shows up repeatedly in different forms. Take 15 minutes to run it through the framework:

Ask “why” at least three times until you reach something structural rather than circumstantial. Generate three to five real solution options, including at least one you initially dismiss too quickly. Choose the option that addresses the root cause, not just the current symptom, and commit to one concrete action this week.

If the problem you’re examining touches on team accountability, decision bottlenecks, or systems that don’t yet exist, the Structural Independence Assessment™ can help you see whether it’s an isolated issue or a symptom of a broader structural gap.

Or if you’re working through a problem that needs an outside perspective to properly diagnose, book a discovery call and let’s get to the actual root of it together.solving isn’t just about fixing what’s broken—it’s about creating opportunities and driving progress.

Watch the Full Video

For a deeper dive into these principles, watch Angie Dobransky’s video on mastering problem-solving:

Frequently Asked Questions