problem and solution in a business

Transition to growth mode

with LivePlan Get 40% off now

0 results have been found for “”

 Return to blog home

10 Step Process for Effective Business Problem Solving

Posted august 3, 2021 by harriet genever.

When you start a small business or launch a startup, the one thing you can count on is the unexpected. No matter how thoroughly you plan, forecast , and test, problems are bound to arise. This is why as an entrepreneur, you need to know how to solve business problems effectively.

What is problem solving in business?

Problem solving in business relates to establishing processes that mitigate or remove obstacles currently preventing you from reaching strategic goals . These are typically complex issues that create a gap between actual results and your desired outcome. They may be present in a single team, operational process, or throughout your entire organization, typically without an immediate or obvious solution. 

To approach problem solving successfully, you need to establish consistent processes that help you evaluate, explore solutions, prioritize execution, and measure success. In many ways, it should be similar to how you review business performance through a monthly plan review . You work through the same documentation, look for gaps, dig deeper to identify the root cause, and hash out options. Without this process, you simply cannot expect to solve problems efficiently or effectively. 

Why problem solving is important for your business

While some would say problem-solving comes naturally, it’s actually a skill you can grow and refine over time. Problem solving skills will help you and your team tackle critical issues and conflicts as they arise. It starts from the top. You as the business owner or CEO needing to display the type of level-headed problem solving that you expect to see from your employees.

Doing so will help you and your staff quickly deal with issues, establish and refine a problem solving process, turn challenges into opportunities, and generally keep a level head. Now, the best business leaders didn’t just find a magic solution to solve their problems, they built processes and leveraged tools to find success. And you can do the same.

By following this 10-step process, you can develop your problem-solving skills and approach any issue that arises with confidence. 

1. Define the problem

When a problem arises, it can be very easy to jump right into creating a solution. However, if you don’t thoroughly examine what led to the problem in the first place, you may create a strategy that doesn’t actually solve it. You may just be treating the symptoms.

For instance, if you realize that your sales from new customers are dropping, your first inclination might be to rush into putting together a marketing plan to increase exposure. But what if decreasing sales are just a symptom of the real problem? 

When you define the problem, you want to be sure you’re not missing the forest for the trees. If you have a large issue on your hands, you’ll want to look at it from several different angles:

Competition 

Is a competitor’s promotion or pricing affecting your sales? Are there new entrants in your market? How are they marketing their product or business?

Business model 

Is your business model sustainable? Is it realistic for how fast you want to grow? Should you explore different pricing or cost strategies?

Market factors

How are world events and the nation’s economy affecting your customers and your sales?

Are there any issues affecting your team? Do they have the tools and resources they need to succeed? 

Goal alignment 

Is everyone on your team working toward the same goal ? Have you communicated your short-term and long-term business goals clearly and often?

There are a lot of ways to approach the issue when you’re facing a serious business problem. The key is to make sure you’re getting a full snapshot of what’s going on so you don’t waste money and resources on band-aid solutions. 

Going back to our example, by looking at every facet of your business, you may discover that you’re spending more on advertising than your competitors already. And instead, there’s a communication gap within your team that’s leading to the mishandling of new customers and therefore lost sales. 

If you jumped into fixing the exposure of your brand, you would have been dumping more money into an area you’re already winning. Potentially leading to greater losses as more and more new customers are dropped due to poor internal communication.

This is why it’s so vital that you explore your blind spots and track the problem to its source.

2. Conduct a SWOT analysis

All good businesses solve some sort of problem for customers. What if your particular business problem is actually an opportunity, or even a strength if considered from a different angle? This is when you’d want to conduct a SWOT analysis to determine if that is in fact the case.

SWOT is a great tool for strategic planning and bringing multiple viewpoints to the table when you’re looking at investing resources to solve a problem. This may even be incorporated in your attempts to identify the source of your problem, as it can quickly outline specific strengths and weaknesses of your business. And then by identifying any potential opportunities or threats, you can utilize your findings to kickstart a solution. 

3. Identify multiple solutions with design thinking

As you approach solving your problem, you may want to consider using the design thinking approach . It’s often used by organizations looking to solve big, community-based problems. One of its strengths is that it requires involving a wide range of people in the problem-solving process. Which leads to multiple perspectives and solutions arising.

This approach—applying your company’s skills and expertise to a problem in the market—is the basis for design thinking.

It’s not about finding the most complex problems to solve, but about finding common needs within the organization and in the real world and coming up with solutions that fit those needs. When you’re solving business problems, this applies in the sense that you’re looking for solutions that address underlying issues—you’re looking at the big picture.

4. Conduct market research and customer outreach

Market research and customer outreach aren’t the sorts of things small business owners and startups can do once and then cross off the list. When you’re facing a roadblock, think back to the last time you did some solid market research or took a deep dive into understanding the competitive landscape .

Market research and the insights you get from customer outreach aren’t a silver bullet. Many companies struggle with what they should do with conflicting data points. But it’s worth struggling through and gathering information that can help you better understand your target market . Plus, your customers can be one of the best sources of criticism. It’s actually a gift if you can avoid taking the negatives personally .

The worst thing you can do when you’re facing challenges is isolating yourself from your customers and ignore your competition. So survey your customers. Put together a competitive matrix . 

5. Seek input from your team and your mentors

Don’t do your SWOT analysis or design thinking work by yourself. The freedom to express concerns, opinions, and ideas will allow people in an organization to speak up. Their feedback is going to help you move faster and more efficiently. If you have a team in place, bring them into the discussion. You hired them to be experts in their area; use their expertise to navigate and dig deeper into underlying causes of problems and potential solutions.

If you’re running your business solo, at least bring in a trusted mentor. SCORE offers a free business mentorship program if you don’t already have one. It can also be helpful to connect with a strategic business advisor , especially if business financials aren’t your strongest suit.

Quoting Stephen Covey, who said that “strength lies in differences, not in similarities,” speaking to the importance of diversity when it comes to problem-solving in business. The more diverse a team is , the more often innovative solutions to the problems faced by the organization appear.

In fact, it has been found that groups that show greater diversity were better at solving problems than groups made up specifically of highly skilled problem solvers. So whoever you bring in to help you problem-solve, resist the urge to surround yourself with people who already agree with you about everything.

6. Apply lean planning for nimble execution

So you do your SWOT analysis and your design thinking exercise. You come up with a set of strong, data-driven ideas. But implementing them requires you to adjust your budget, or your strategic plan, or even your understanding of your target market.

Are you willing to change course? Can you quickly make adjustments? Well in order to grow, you can’t be afraid to be nimble . 

By adopting the lean business planning method —the process of revising your business strategy regularly—you’ll be able to shift your strategies more fluidly. You don’t want to change course every week, and you don’t want to fall victim to shiny object thinking. But you can strike a balance that allows you to reduce your business’s risk while keeping your team heading in the right direction.

Along the way, you’ll make strategic decisions that don’t pan out the way you hoped. The best thing you can do is test your ideas and iterate often so you’re not wasting money and resources on things that don’t work. That’s Lean Planning .

7. Model different financial scenarios

When you’re trying to solve a serious business problem, one of the best things you can do is build a few different financial forecasts so you can model different scenarios. You might find that the idea that seemed the strongest will take longer than you thought to reverse a negative financial trend. At the very least you’ll have better insight into the financial impact of moving in a different direction.

The real benefit here is looking at different tactical approaches to the same problem. Maybe instead of increasing sales right now, you’re better off in the long run if you adopt a strategy to reduce churn and retain your best customers. You won’t know unless you model a few different scenarios. You can do this by using spreadsheets, and a tool like LivePlan can make it easier and quicker.

8. Watch your cash flow

While you’re working to solve a challenging business problem, pay particular attention to your cash flow and your cash flow forecast . Understanding when your company is at risk of running out of cash in the bank can help you be proactive. It’s a lot easier to get a line of credit while your financials still look good and healthy, than when you’re one pay period away from ruin.

If you’re dealing with a serious issue, it’s easy to start to get tunnel vision. You’ll benefit from maintaining a little breathing room for your business as you figure out what to do next.

9. Use a decision-making framework

Once you’ve gathered all the information you need, generated a number of ideas, and done some financial modeling, you might still feel uncertain. It’s natural—you’re not a fortune-teller. You’re trying to make the best decision you can with the information you have.

This article offers a really useful approach to making decisions. It starts with putting your options into a matrix like this one:

Use this sort of framework to put everything you’ve learned out on the table. If you’re working with a bigger team, this sort of exercise can also bring the rest of your team to the table so they feel some ownership over the outcome.

10. Identify key metrics to track

How will you know your problem is solved? And not just the symptom—how will you know when you’ve addressed the underlying issues? Before you dive into enacting the solution, make sure you know what success looks like.

Decide on a few key performance indicators . Take a baseline measurement, and set a goal and a timeframe. You’re essentially translating your solution into a plan, complete with milestones and goals. Without these, you’ve simply made a blind decision with no way to track success. You need those goals and milestones to make your plan real .

Problem solving skills to improve

As you and your team work through this process, it’s worth keeping in mind specific problem solving skills you should continue to develop. Bolstering your ability, as well as your team, to solve problems effectively will only make this process more useful and efficient. Here are a few key skills to work on.

Emotional intelligence

It can be very easy to make quick, emotional responses in a time of crisis or when discussing something you’re passionate about. To avoid making assumptions and letting your emotions get the best of you, you need to focus on empathizing with others. This involves understanding your own emotional state, reactions and listening carefully to the responses of your team. The more you’re able to listen carefully, the better you’ll be at asking for and taking advice that actually leads to effective problem solving.

Jumping right into a solution can immediately kill the possibility of solving your problem. Just like when you start a business , you need to do the research into what the problem you’re solving actually is. Luckily, you can embed research into your problem solving by holding active reviews of financial performance and team processes. Simply asking “What? Where? When? How?” can lead to more in-depth explorations of potential issues.

The best thing you can do to grow your research abilities is to encourage and practice curiosity. Look at every problem as an opportunity. Something that may be trouble now, but is worth exploring and finding the right solution. You’ll pick up best practices, useful tools and fine-tune your own research process the more you’re willing to explore.

Brainstorming

Creatively brainstorming with your team is somewhat of an art form. There needs to be a willingness to throw everything at the wall and act as if nothing is a bad idea at the start. This style of collaboration encourages participation without fear of rejection. It also helps outline potential solutions outside of your current scope, that you can refine and turn into realistic action.

Work on breaking down problems and try to give everyone in the room a voice. The more input you allow, the greater potential you have for finding the best solution.

Decisiveness

One thing that can drag out acting upon a potential solution, is being indecisive. If you aren’t willing to state when the final cutoff for deliberation is, you simply won’t take steps quickly enough. This is when having a process for problem solving comes in handy, as it purposefully outlines when you should start taking action.

Work on choosing decision-makers, identify necessary results and be prepared to analyze and adjust if necessary. You don’t have to get it right every time, but taking action at the right time, even if it fails, is almost more vital than never taking a step.  

Stemming off failure, you need to learn to be resilient. Again, no one gets it perfect every single time. There are so many factors in play to consider and sometimes even the most well-thought-out solution doesn’t stick. Instead of being down on yourself or your team, look to separate yourself from the problem and continue to think of it as a puzzle worth solving. Every failure is a learning opportunity and it only helps you further refine and eliminate issues in your strategy.

Problem solving is a process

The key to effective problem-solving in business is the ability to adapt. You can waste a lot of resources on staying the wrong course for too long. So make a plan to reduce your risk now. Think about what you’d do if you were faced with a problem large enough to sink your business. Be as proactive as you can.

Editor’s note: This article was originally published in 2016. It was updated in 2021.

Like this post? Share with a friend!

Harriet Genever

Posted in management, join over 1 million entrepreneurs who found success with liveplan, like this content sign up to receive more.

Subscribe for tips and guidance to help you grow a better, smarter business.

You're all set!

Exciting business insights and growth strategies will be coming your way each month.

We care about your privacy. See our privacy policy .

• Business Essentials
• Leadership & Management
• Credential of Leadership, Impact, and Management in Business (CLIMB)
• Entrepreneurship & Innovation
• *New* Digital Transformation
• Finance & Accounting
• Business in Society
• For Organizations
• Support Portal
• Media Coverage
• Founding Donors
• Leadership Team

• Harvard Business School →
• HBS Online →
• Business Insights →

Business Insights

Harvard Business School Online's Business Insights Blog provides the career insights you need to achieve your goals and gain confidence in your business skills.

• Career Development
• Communication
• Decision-Making
• Earning Your MBA
• Negotiation
• News & Events
• Productivity
• Staff Spotlight
• Student Profiles
• Work-Life Balance
• Alternative Investments
• Business Analytics
• Business Strategy
• Business and Climate Change
• Design Thinking and Innovation
• Digital Marketing Strategy
• Disruptive Strategy
• Economics for Managers
• Entrepreneurship Essentials
• Financial Accounting
• Global Business
• Launching Tech Ventures
• Leadership Principles
• Leadership, Ethics, and Corporate Accountability
• Leading with Finance
• Management Essentials
• Negotiation Mastery
• Organizational Leadership
• Power and Influence for Positive Impact
• Strategy Execution
• Sustainable Business Strategy
• Sustainable Investing
• Winning with Digital Platforms

Why Problem-Solving Skills Are Essential for Leaders in Any Industry

• 17 Jan 2023

Any organization offering a product or service is in the business of solving problems.

Whether providing medical care to address health issues or quick convenience to those hungry for dinner, a business’s purpose is to satisfy customer needs .

In addition to solving customers’ problems, you’ll undoubtedly encounter challenges within your organization as it evolves to meet customer needs. You’re likely to experience growing pains in the form of missed targets, unattained goals, and team disagreements.

Yet, the ubiquity of problems doesn’t have to be discouraging; with the right frameworks and tools, you can build the skills to solve consumers' and your organization’s most challenging issues.

Here’s a primer on problem-solving in business, why it’s important, the skills you need, and how to build them.

Access your free e-book today.

What Is Problem-Solving in Business?

Problem-solving is the process of systematically removing barriers that prevent you or others from reaching goals.

Your business removes obstacles in customers’ lives through its products or services, just as you can remove obstacles that keep your team from achieving business goals.

Design Thinking

Design thinking , as described by Harvard Business School Dean Srikant Datar in the online course Design Thinking and Innovation , is a human-centered , solutions-based approach to problem-solving and innovation. Originally created for product design, design thinking’s use case has evolved . It’s now used to solve internal business problems, too.

The design thinking process has four stages :

• Clarify: Clarify a problem through research and feedback from those impacted.
• Ideate: Armed with new insights, generate as many solutions as possible.
• Develop: Combine and cull your ideas into a short list of viable, feasible, and desirable options before building prototypes (if making physical products) and creating a plan of action (if solving an intangible problem).
• Implement: Execute the strongest idea, ensuring clear communication with all stakeholders about its potential value and deliberate reasoning.

Using this framework, you can generate innovative ideas that wouldn’t have surfaced otherwise.

Creative Problem-Solving

Another, less structured approach to challenges is creative problem-solving , which employs a series of exercises to explore open-ended solutions and develop new perspectives. This is especially useful when a problem’s root cause has yet to be defined.

You can use creative problem-solving tools in design thinking’s “ideate” stage, which include:

• Brainstorming: Instruct everyone to develop as many ideas as possible in an allotted time frame without passing judgment.
• Divergent thinking exercises: Rather than arriving at the same conclusion (convergent thinking), instruct everyone to come up with a unique idea for a given prompt (divergent thinking). This type of exercise helps avoid the tendency to agree with others’ ideas without considering alternatives.
• Alternate worlds: Ask your team to consider how various personas would manage the problem. For instance, how would a pilot approach it? What about a young child? What about a seasoned engineer?

It can be tempting to fall back on how problems have been solved before, especially if they worked well. However, if you’re striving for innovation, relying on existing systems can stunt your company’s growth.

Related: How to Be a More Creative Problem-Solver at Work: 8 Tips

Why Is Problem-Solving Important for Leaders?

While obstacles’ specifics vary between industries, strong problem-solving skills are crucial for leaders in any field.

Whether building a new product or dealing with internal issues, you’re bound to come up against challenges. Having frameworks and tools at your disposal when they arise can turn issues into opportunities.

As a leader, it’s rarely your responsibility to solve a problem single-handedly, so it’s crucial to know how to empower employees to work together to find the best solution.

Your job is to guide them through each step of the framework and set the parameters and prompts within which they can be creative. Then, you can develop a list of ideas together, test the best ones, and implement the chosen solution.

Related: 5 Design Thinking Skills for Business Professionals

4 Problem-Solving Skills All Leaders Need

1. problem framing.

One key skill for any leader is framing problems in a way that makes sense for their organization. Problem framing is defined in Design Thinking and Innovation as determining the scope, context, and perspective of the problem you’re trying to solve.

“Before you begin to generate solutions for your problem, you must always think hard about how you’re going to frame that problem,” Datar says in the course.

For instance, imagine you work for a company that sells children’s sneakers, and sales have plummeted. When framing the problem, consider:

• What is the children’s sneaker market like right now?
• Should we improve the quality of our sneakers?
• Should we assess all children’s footwear?
• Is this a marketing issue for children’s sneakers specifically?
• Is this a bigger issue that impacts how we should market or produce all footwear?

While there’s no one right way to frame a problem, how you do can impact the solutions you generate. It’s imperative to accurately frame problems to align with organizational priorities and ensure your team generates useful ideas for your firm.

To solve a problem, you need to empathize with those impacted by it. Empathy is the ability to understand others’ emotions and experiences. While many believe empathy is a fixed trait, it’s a skill you can strengthen through practice.

When confronted with a problem, consider whom it impacts. Returning to the children’s sneaker example, think of who’s affected:

• Your organization’s employees, because sales are down
• The customers who typically buy your sneakers
• The children who typically wear your sneakers

Empathy is required to get to the problem’s root and consider each group’s perspective. Assuming someone’s perspective often isn’t accurate, so the best way to get that information is by collecting user feedback.

For instance, if you asked customers who typically buy your children’s sneakers why they’ve stopped, they could say, “A new brand of children’s sneakers came onto the market that have soles with more traction. I want my child to be as safe as possible, so I bought those instead.”

When someone shares their feelings and experiences, you have an opportunity to empathize with them. This can yield solutions to their problem that directly address its root and shows you care. In this case, you may design a new line of children’s sneakers with extremely grippy soles for added safety, knowing that’s what your customers care most about.

Related: 3 Effective Methods for Assessing Customer Needs

3. Breaking Cognitive Fixedness

Cognitive fixedness is a state of mind in which you examine situations through the lens of past experiences. This locks you into one mindset rather than allowing you to consider alternative possibilities.

For instance, your cognitive fixedness may make you think rubber is the only material for sneaker treads. What else could you use? Is there a grippier alternative you haven’t considered?

Problem-solving is all about overcoming cognitive fixedness. You not only need to foster this skill in yourself but among your team.

4. Creating a Psychologically Safe Environment

As a leader, it’s your job to create an environment conducive to problem-solving. In a psychologically safe environment, all team members feel comfortable bringing ideas to the table, which are likely influenced by their personal opinions and experiences.

If employees are penalized for “bad” ideas or chastised for questioning long-held procedures and systems, innovation has no place to take root.

By employing the design thinking framework and creative problem-solving exercises, you can foster a setting in which your team feels comfortable sharing ideas and new, innovative solutions can grow.

How to Build Problem-Solving Skills

The most obvious answer to how to build your problem-solving skills is perhaps the most intimidating: You must practice.

Again and again, you’ll encounter challenges, use creative problem-solving tools and design thinking frameworks, and assess results to learn what to do differently next time.

While most of your practice will occur within your organization, you can learn in a lower-stakes setting by taking an online course, such as Design Thinking and Innovation . Datar guides you through each tool and framework, presenting real-world business examples to help you envision how you would approach the same types of problems in your organization.

Are you interested in uncovering innovative solutions for your organization’s business problems? Explore Design Thinking and Innovation —one of our online entrepreneurship and innovation courses —to learn how to leverage proven frameworks and tools to solve challenges. Not sure which course is right for you? Download our free flowchart .

About the Author

• SUGGESTED TOPICS
• The Magazine
• Newsletters
• Managing Yourself
• Managing Teams
• Work-life Balance
• The Big Idea
• Data & Visuals
• Reading Lists
• Case Selections
• HBR Learning
• Topic Feeds
• Account Settings
• Email Preferences

How to Solve Problems

• Laura Amico

To bring the best ideas forward, teams must build psychological safety.

Teams today aren’t just asked to execute tasks: They’re called upon to solve problems. You’d think that many brains working together would mean better solutions, but the reality is that too often problem-solving teams fall victim to inefficiency, conflict, and cautious conclusions. The two charts below will help your team think about how to collaborate better and come up with the best solutions for the thorniest challenges.

• Laura Amico is a former senior editor at Harvard Business Review.

Partner Center

How to master the seven-step problem-solving process

In this episode of the McKinsey Podcast , Simon London speaks with Charles Conn, CEO of venture-capital firm Oxford Sciences Innovation, and McKinsey senior partner Hugo Sarrazin about the complexities of different problem-solving strategies.

Podcast transcript

Simon London: Hello, and welcome to this episode of the McKinsey Podcast , with me, Simon London. What’s the number-one skill you need to succeed professionally? Salesmanship, perhaps? Or a facility with statistics? Or maybe the ability to communicate crisply and clearly? Many would argue that at the very top of the list comes problem solving: that is, the ability to think through and come up with an optimal course of action to address any complex challenge—in business, in public policy, or indeed in life.

Looked at this way, it’s no surprise that McKinsey takes problem solving very seriously, testing for it during the recruiting process and then honing it, in McKinsey consultants, through immersion in a structured seven-step method. To discuss the art of problem solving, I sat down in California with McKinsey senior partner Hugo Sarrazin and also with Charles Conn. Charles is a former McKinsey partner, entrepreneur, executive, and coauthor of the book Bulletproof Problem Solving: The One Skill That Changes Everything [John Wiley & Sons, 2018].

Charles and Hugo, welcome to the podcast. Thank you for being here.

Hugo Sarrazin: Our pleasure.

Charles Conn: It’s terrific to be here.

Simon London: Problem solving is a really interesting piece of terminology. It could mean so many different things. I have a son who’s a teenage climber. They talk about solving problems. Climbing is problem solving. Charles, when you talk about problem solving, what are you talking about?

Charles Conn: For me, problem solving is the answer to the question “What should I do?” It’s interesting when there’s uncertainty and complexity, and when it’s meaningful because there are consequences. Your son’s climbing is a perfect example. There are consequences, and it’s complicated, and there’s uncertainty—can he make that grab? I think we can apply that same frame almost at any level. You can think about questions like “What town would I like to live in?” or “Should I put solar panels on my roof?”

You might think that’s a funny thing to apply problem solving to, but in my mind it’s not fundamentally different from business problem solving, which answers the question “What should my strategy be?” Or problem solving at the policy level: “How do we combat climate change?” “Should I support the local school bond?” I think these are all part and parcel of the same type of question, “What should I do?”

I’m a big fan of structured problem solving. By following steps, we can more clearly understand what problem it is we’re solving, what are the components of the problem that we’re solving, which components are the most important ones for us to pay attention to, which analytic techniques we should apply to those, and how we can synthesize what we’ve learned back into a compelling story. That’s all it is, at its heart.

I think sometimes when people think about seven steps, they assume that there’s a rigidity to this. That’s not it at all. It’s actually to give you the scope for creativity, which often doesn’t exist when your problem solving is muddled.

Simon London: You were just talking about the seven-step process. That’s what’s written down in the book, but it’s a very McKinsey process as well. Without getting too deep into the weeds, let’s go through the steps, one by one. You were just talking about problem definition as being a particularly important thing to get right first. That’s the first step. Hugo, tell us about that.

Hugo Sarrazin: It is surprising how often people jump past this step and make a bunch of assumptions. The most powerful thing is to step back and ask the basic questions—“What are we trying to solve? What are the constraints that exist? What are the dependencies?” Let’s make those explicit and really push the thinking and defining. At McKinsey, we spend an enormous amount of time in writing that little statement, and the statement, if you’re a logic purist, is great. You debate. “Is it an ‘or’? Is it an ‘and’? What’s the action verb?” Because all these specific words help you get to the heart of what matters.

Want to subscribe to The McKinsey Podcast ?

Simon London: So this is a concise problem statement.

Hugo Sarrazin: Yeah. It’s not like “Can we grow in Japan?” That’s interesting, but it is “What, specifically, are we trying to uncover in the growth of a product in Japan? Or a segment in Japan? Or a channel in Japan?” When you spend an enormous amount of time, in the first meeting of the different stakeholders, debating this and having different people put forward what they think the problem definition is, you realize that people have completely different views of why they’re here. That, to me, is the most important step.

Charles Conn: I would agree with that. For me, the problem context is critical. When we understand “What are the forces acting upon your decision maker? How quickly is the answer needed? With what precision is the answer needed? Are there areas that are off limits or areas where we would particularly like to find our solution? Is the decision maker open to exploring other areas?” then you not only become more efficient, and move toward what we call the critical path in problem solving, but you also make it so much more likely that you’re not going to waste your time or your decision maker’s time.

How often do especially bright young people run off with half of the idea about what the problem is and start collecting data and start building models—only to discover that they’ve really gone off half-cocked.

Hugo Sarrazin: Yeah.

Charles Conn: And in the wrong direction.

Simon London: OK. So step one—and there is a real art and a structure to it—is define the problem. Step two, Charles?

Charles Conn: My favorite step is step two, which is to use logic trees to disaggregate the problem. Every problem we’re solving has some complexity and some uncertainty in it. The only way that we can really get our team working on the problem is to take the problem apart into logical pieces.

What we find, of course, is that the way to disaggregate the problem often gives you an insight into the answer to the problem quite quickly. I love to do two or three different cuts at it, each one giving a bit of a different insight into what might be going wrong. By doing sensible disaggregations, using logic trees, we can figure out which parts of the problem we should be looking at, and we can assign those different parts to team members.

Simon London: What’s a good example of a logic tree on a sort of ratable problem?

Charles Conn: Maybe the easiest one is the classic profit tree. Almost in every business that I would take a look at, I would start with a profit or return-on-assets tree. In its simplest form, you have the components of revenue, which are price and quantity, and the components of cost, which are cost and quantity. Each of those can be broken out. Cost can be broken into variable cost and fixed cost. The components of price can be broken into what your pricing scheme is. That simple tree often provides insight into what’s going on in a business or what the difference is between that business and the competitors.

If we add the leg, which is “What’s the asset base or investment element?”—so profit divided by assets—then we can ask the question “Is the business using its investments sensibly?” whether that’s in stores or in manufacturing or in transportation assets. I hope we can see just how simple this is, even though we’re describing it in words.

When I went to work with Gordon Moore at the Moore Foundation, the problem that he asked us to look at was “How can we save Pacific salmon?” Now, that sounds like an impossible question, but it was amenable to precisely the same type of disaggregation and allowed us to organize what became a 15-year effort to improve the likelihood of good outcomes for Pacific salmon.

Simon London: Now, is there a danger that your logic tree can be impossibly large? This, I think, brings us onto the third step in the process, which is that you have to prioritize.

Charles Conn: Absolutely. The third step, which we also emphasize, along with good problem definition, is rigorous prioritization—we ask the questions “How important is this lever or this branch of the tree in the overall outcome that we seek to achieve? How much can I move that lever?” Obviously, we try and focus our efforts on ones that have a big impact on the problem and the ones that we have the ability to change. With salmon, ocean conditions turned out to be a big lever, but not one that we could adjust. We focused our attention on fish habitats and fish-harvesting practices, which were big levers that we could affect.

People spend a lot of time arguing about branches that are either not important or that none of us can change. We see it in the public square. When we deal with questions at the policy level—“Should you support the death penalty?” “How do we affect climate change?” “How can we uncover the causes and address homelessness?”—it’s even more important that we’re focusing on levers that are big and movable.

Would you like to learn more about our Strategy & Corporate Finance Practice ?

Simon London: Let’s move swiftly on to step four. You’ve defined your problem, you disaggregate it, you prioritize where you want to analyze—what you want to really look at hard. Then you got to the work plan. Now, what does that mean in practice?

Hugo Sarrazin: Depending on what you’ve prioritized, there are many things you could do. It could be breaking the work among the team members so that people have a clear piece of the work to do. It could be defining the specific analyses that need to get done and executed, and being clear on time lines. There’s always a level-one answer, there’s a level-two answer, there’s a level-three answer. Without being too flippant, I can solve any problem during a good dinner with wine. It won’t have a whole lot of backing.

Simon London: Not going to have a lot of depth to it.

Hugo Sarrazin: No, but it may be useful as a starting point. If the stakes are not that high, that could be OK. If it’s really high stakes, you may need level three and have the whole model validated in three different ways. You need to find a work plan that reflects the level of precision, the time frame you have, and the stakeholders you need to bring along in the exercise.

Charles Conn: I love the way you’ve described that, because, again, some people think of problem solving as a linear thing, but of course what’s critical is that it’s iterative. As you say, you can solve the problem in one day or even one hour.

Charles Conn: We encourage our teams everywhere to do that. We call it the one-day answer or the one-hour answer. In work planning, we’re always iterating. Every time you see a 50-page work plan that stretches out to three months, you know it’s wrong. It will be outmoded very quickly by that learning process that you described. Iterative problem solving is a critical part of this. Sometimes, people think work planning sounds dull, but it isn’t. It’s how we know what’s expected of us and when we need to deliver it and how we’re progressing toward the answer. It’s also the place where we can deal with biases. Bias is a feature of every human decision-making process. If we design our team interactions intelligently, we can avoid the worst sort of biases.

Simon London: Here we’re talking about cognitive biases primarily, right? It’s not that I’m biased against you because of your accent or something. These are the cognitive biases that behavioral sciences have shown we all carry around, things like anchoring, overoptimism—these kinds of things.

Both: Yeah.

Charles Conn: Availability bias is the one that I’m always alert to. You think you’ve seen the problem before, and therefore what’s available is your previous conception of it—and we have to be most careful about that. In any human setting, we also have to be careful about biases that are based on hierarchies, sometimes called sunflower bias. I’m sure, Hugo, with your teams, you make sure that the youngest team members speak first. Not the oldest team members, because it’s easy for people to look at who’s senior and alter their own creative approaches.

Hugo Sarrazin: It’s helpful, at that moment—if someone is asserting a point of view—to ask the question “This was true in what context?” You’re trying to apply something that worked in one context to a different one. That can be deadly if the context has changed, and that’s why organizations struggle to change. You promote all these people because they did something that worked well in the past, and then there’s a disruption in the industry, and they keep doing what got them promoted even though the context has changed.

Simon London: Right. Right.

Hugo Sarrazin: So it’s the same thing in problem solving.

Charles Conn: And it’s why diversity in our teams is so important. It’s one of the best things about the world that we’re in now. We’re likely to have people from different socioeconomic, ethnic, and national backgrounds, each of whom sees problems from a slightly different perspective. It is therefore much more likely that the team will uncover a truly creative and clever approach to problem solving.

Simon London: Let’s move on to step five. You’ve done your work plan. Now you’ve actually got to do the analysis. The thing that strikes me here is that the range of tools that we have at our disposal now, of course, is just huge, particularly with advances in computation, advanced analytics. There’s so many things that you can apply here. Just talk about the analysis stage. How do you pick the right tools?

Charles Conn: For me, the most important thing is that we start with simple heuristics and explanatory statistics before we go off and use the big-gun tools. We need to understand the shape and scope of our problem before we start applying these massive and complex analytical approaches.

Simon London: Would you agree with that?

Hugo Sarrazin: I agree. I think there are so many wonderful heuristics. You need to start there before you go deep into the modeling exercise. There’s an interesting dynamic that’s happening, though. In some cases, for some types of problems, it is even better to set yourself up to maximize your learning. Your problem-solving methodology is test and learn, test and learn, test and learn, and iterate. That is a heuristic in itself, the A/B testing that is used in many parts of the world. So that’s a problem-solving methodology. It’s nothing different. It just uses technology and feedback loops in a fast way. The other one is exploratory data analysis. When you’re dealing with a large-scale problem, and there’s so much data, I can get to the heuristics that Charles was talking about through very clever visualization of data.

You test with your data. You need to set up an environment to do so, but don’t get caught up in neural-network modeling immediately. You’re testing, you’re checking—“Is the data right? Is it sound? Does it make sense?”—before you launch too far.

Simon London: You do hear these ideas—that if you have a big enough data set and enough algorithms, they’re going to find things that you just wouldn’t have spotted, find solutions that maybe you wouldn’t have thought of. Does machine learning sort of revolutionize the problem-solving process? Or are these actually just other tools in the toolbox for structured problem solving?

Charles Conn: It can be revolutionary. There are some areas in which the pattern recognition of large data sets and good algorithms can help us see things that we otherwise couldn’t see. But I do think it’s terribly important we don’t think that this particular technique is a substitute for superb problem solving, starting with good problem definition. Many people use machine learning without understanding algorithms that themselves can have biases built into them. Just as 20 years ago, when we were doing statistical analysis, we knew that we needed good model definition, we still need a good understanding of our algorithms and really good problem definition before we launch off into big data sets and unknown algorithms.

Simon London: Step six. You’ve done your analysis.

Charles Conn: I take six and seven together, and this is the place where young problem solvers often make a mistake. They’ve got their analysis, and they assume that’s the answer, and of course it isn’t the answer. The ability to synthesize the pieces that came out of the analysis and begin to weave those into a story that helps people answer the question “What should I do?” This is back to where we started. If we can’t synthesize, and we can’t tell a story, then our decision maker can’t find the answer to “What should I do?”

Simon London: But, again, these final steps are about motivating people to action, right?

Charles Conn: Yeah.

Simon London: I am slightly torn about the nomenclature of problem solving because it’s on paper, right? Until you motivate people to action, you actually haven’t solved anything.

Charles Conn: I love this question because I think decision-making theory, without a bias to action, is a waste of time. Everything in how I approach this is to help people take action that makes the world better.

Simon London: Hence, these are absolutely critical steps. If you don’t do this well, you’ve just got a bunch of analysis.

Charles Conn: We end up in exactly the same place where we started, which is people speaking across each other, past each other in the public square, rather than actually working together, shoulder to shoulder, to crack these important problems.

Simon London: In the real world, we have a lot of uncertainty—arguably, increasing uncertainty. How do good problem solvers deal with that?

Hugo Sarrazin: At every step of the process. In the problem definition, when you’re defining the context, you need to understand those sources of uncertainty and whether they’re important or not important. It becomes important in the definition of the tree.

You need to think carefully about the branches of the tree that are more certain and less certain as you define them. They don’t have equal weight just because they’ve got equal space on the page. Then, when you’re prioritizing, your prioritization approach may put more emphasis on things that have low probability but huge impact—or, vice versa, may put a lot of priority on things that are very likely and, hopefully, have a reasonable impact. You can introduce that along the way. When you come back to the synthesis, you just need to be nuanced about what you’re understanding, the likelihood.

Often, people lack humility in the way they make their recommendations: “This is the answer.” They’re very precise, and I think we would all be well-served to say, “This is a likely answer under the following sets of conditions” and then make the level of uncertainty clearer, if that is appropriate. It doesn’t mean you’re always in the gray zone; it doesn’t mean you don’t have a point of view. It just means that you can be explicit about the certainty of your answer when you make that recommendation.

Simon London: So it sounds like there is an underlying principle: “Acknowledge and embrace the uncertainty. Don’t pretend that it isn’t there. Be very clear about what the uncertainties are up front, and then build that into every step of the process.”

Hugo Sarrazin: Every step of the process.

Simon London: Yeah. We have just walked through a particular structured methodology for problem solving. But, of course, this is not the only structured methodology for problem solving. One that is also very well-known is design thinking, which comes at things very differently. So, Hugo, I know you have worked with a lot of designers. Just give us a very quick summary. Design thinking—what is it, and how does it relate?

Hugo Sarrazin: It starts with an incredible amount of empathy for the user and uses that to define the problem. It does pause and go out in the wild and spend an enormous amount of time seeing how people interact with objects, seeing the experience they’re getting, seeing the pain points or joy—and uses that to infer and define the problem.

Simon London: Problem definition, but out in the world.

Hugo Sarrazin: With an enormous amount of empathy. There’s a huge emphasis on empathy. Traditional, more classic problem solving is you define the problem based on an understanding of the situation. This one almost presupposes that we don’t know the problem until we go see it. The second thing is you need to come up with multiple scenarios or answers or ideas or concepts, and there’s a lot of divergent thinking initially. That’s slightly different, versus the prioritization, but not for long. Eventually, you need to kind of say, “OK, I’m going to converge again.” Then you go and you bring things back to the customer and get feedback and iterate. Then you rinse and repeat, rinse and repeat. There’s a lot of tactile building, along the way, of prototypes and things like that. It’s very iterative.

Simon London: So, Charles, are these complements or are these alternatives?

Charles Conn: I think they’re entirely complementary, and I think Hugo’s description is perfect. When we do problem definition well in classic problem solving, we are demonstrating the kind of empathy, at the very beginning of our problem, that design thinking asks us to approach. When we ideate—and that’s very similar to the disaggregation, prioritization, and work-planning steps—we do precisely the same thing, and often we use contrasting teams, so that we do have divergent thinking. The best teams allow divergent thinking to bump them off whatever their initial biases in problem solving are. For me, design thinking gives us a constant reminder of creativity, empathy, and the tactile nature of problem solving, but it’s absolutely complementary, not alternative.

Simon London: I think, in a world of cross-functional teams, an interesting question is do people with design-thinking backgrounds really work well together with classical problem solvers? How do you make that chemistry happen?

Hugo Sarrazin: Yeah, it is not easy when people have spent an enormous amount of time seeped in design thinking or user-centric design, whichever word you want to use. If the person who’s applying classic problem-solving methodology is very rigid and mechanical in the way they’re doing it, there could be an enormous amount of tension. If there’s not clarity in the role and not clarity in the process, I think having the two together can be, sometimes, problematic.

The second thing that happens often is that the artifacts the two methodologies try to gravitate toward can be different. Classic problem solving often gravitates toward a model; design thinking migrates toward a prototype. Rather than writing a big deck with all my supporting evidence, they’ll bring an example, a thing, and that feels different. Then you spend your time differently to achieve those two end products, so that’s another source of friction.

Now, I still think it can be an incredibly powerful thing to have the two—if there are the right people with the right mind-set, if there is a team that is explicit about the roles, if we’re clear about the kind of outcomes we are attempting to bring forward. There’s an enormous amount of collaborativeness and respect.

Simon London: But they have to respect each other’s methodology and be prepared to flex, maybe, a little bit, in how this process is going to work.

Hugo Sarrazin: Absolutely.

Simon London: The other area where, it strikes me, there could be a little bit of a different sort of friction is this whole concept of the day-one answer, which is what we were just talking about in classical problem solving. Now, you know that this is probably not going to be your final answer, but that’s how you begin to structure the problem. Whereas I would imagine your design thinkers—no, they’re going off to do their ethnographic research and get out into the field, potentially for a long time, before they come back with at least an initial hypothesis.

Want better strategies? Become a bulletproof problem solver

Hugo Sarrazin: That is a great callout, and that’s another difference. Designers typically will like to soak into the situation and avoid converging too quickly. There’s optionality and exploring different options. There’s a strong belief that keeps the solution space wide enough that you can come up with more radical ideas. If there’s a large design team or many designers on the team, and you come on Friday and say, “What’s our week-one answer?” they’re going to struggle. They’re not going to be comfortable, naturally, to give that answer. It doesn’t mean they don’t have an answer; it’s just not where they are in their thinking process.

Simon London: I think we are, sadly, out of time for today. But Charles and Hugo, thank you so much.

Charles Conn: It was a pleasure to be here, Simon.

Hugo Sarrazin: It was a pleasure. Thank you.

Simon London: And thanks, as always, to you, our listeners, for tuning into this episode of the McKinsey Podcast . If you want to learn more about problem solving, you can find the book, Bulletproof Problem Solving: The One Skill That Changes Everything , online or order it through your local bookstore. To learn more about McKinsey, you can of course find us at McKinsey.com.

Charles Conn is CEO of Oxford Sciences Innovation and an alumnus of McKinsey’s Sydney office. Hugo Sarrazin is a senior partner in the Silicon Valley office, where Simon London, a member of McKinsey Publishing, is also based.

Explore a career with us

Related articles.

Strategy to beat the odds

Five routes to more innovative problem solving

• Coaching Skills Training
• Coaching TIPS²™
• Continuous Improvement Coaching
• Courageous Conversations Workshop
• Executive Coaching Program
• Feedback 360
• Safety Coaching
• Sales Coaching Training Program
• Free Consultation
• Applied Strategic Thinking®
• Strategic Leadership Course
• Strategic Teaming
• Strategy Development Processes and Services
• Communication Training for Managers
• Conflict and Collaboration
• Confronting Racism Workshop
• Delegation & Accountability
• Diversity, Equity, and Inclusion Workshop
• Flexible Leadership
• Leading Change
• Leading Groups to Solutions
• Leading Innovation
• Mid-Level Management Training
• Qualities of Leadership
• Bottom Line Leadership
• Customized Leadership Development Programs
• Leadership Development Program Design
• Mini-MBA & Operational Finance
• Problem Solving and Decision Making in the Workplace
• Transition to Leadership
• Virtual Leadership
• High-Performance Teamwork
• Leadership Team Alignment Workshop
• Orienteering
• Corporate Outdoor Training and Team Building
• Retreats for Teams
• Innovation Skills Training
• Personal Impact Workshop
• Supervisor Training Programs
• Customization of CMOE’s Learning Library
• Full Curriculum Development and Design
• Learning & Development Advisory Services
• Bottom Line Leadership Training
• Consulting Services
• Leadership Retreats
• Learning and Development Consulting Services
• Needs Analysis and Organization Assessments
• Transformation & Change Solutions
• Facilitator Training Workshop
• Empathic Leadership
• Supervisor Development Series
• All Courses
• Digital Learning
• Books and Publications
• Assessments and Surveys
• Clients Served
• History and Experience
• Meet the CMOE Team
• Testimonials
• Articles & Tools
• Scenario Templates
• Certified Partners
• Event Resources
• Industry Insights
• Resource Library
• Video Library
• News and Events
• Professional Accreditation and Continuing Education Units
• Surveys & Assessments
• Problem Solving in Business
• 360-Degree Leadership Assessment
• Adaptive Communication
• Adaptive Leadership
• Authentic Leadership Style
• Boundary Spanning Leadership
• Business Change Strategies
• Business-Strategy Principles
• Capacity Building
• Cascading Strategy
• Change Management
• Coaching Framework
• Coaching in the Workplace
• Coaching Leadership Style
• Collaborative Coaching
• Competency Assessment
• Conflict Resolution in the Workplace
• Core Competence
• Corporate Strategic Planning
• Crisis Leadership
• Critical Success Factors
• DEI in the Workplace
• Directive Leader
• Empathetic Leadership Definition
• Horizontal Leadership
• Inclusive Leadership
• Innovation Strategy
• Leadership Competency Framework
• Leadership Model
• Management Succession Planning
• Operational Excellence
• Organizational Alignment
• Participative Leadership Style
• Performance Deficiency Coaching
• Persuasive Leadership Style
• Servant Leadership Style
• Strategic Agility
• Strategic Alignment
• Strategic Audit
• Strategic Framework
• Strategic Management
• Strategic Mindset Competency
• Strategic Thinking
• Strategy Committee
• Strategy Issues
• Strategy Maps
• Supportive Leadership Style: Definition and Qualities
• Team Building Interventions
• Team Environment
• Team Performance Assessment
• Teamwork Atmosphere
• Total Employee Involvement
• Training Needs Analysis (TNA) Definition
• Transformational Leadership
• Visionary Leadership Style
• What Are Strategic Initiatives: Examples and Development

What Is Problem Solving in Business?

Problem-solving in business is defined as implementing processes that reduce or remove obstacles that are preventing you or others from accomplishing operational and strategic business goals.

In business, a problem is a situation that creates a gap between the desired and actual outcomes. In addition, a true problem typically does not have an immediately obvious resolution.

Business problem-solving works best when it is approached through a consistent system in which individuals:

• Identify and define the problem
• Prioritize the problem based on size, potential impact, and urgency
• Complete a root-cause analysis
• Develop a variety of possible solutions
• Evaluate possible solutions and decide which is most effective
• Plan and implement the solution

Why Problem Solving Is Important in Business

Understanding the importance of problem-solving skills in the workplace will help you develop as a leader. Problem-solving skills will help you resolve critical issues and conflicts that you come across. Problem-solving is a valued skill in the workplace because it allows you to:

• Apply a standard problem-solving system to all challenges
• Find the root causes of problems
• Quickly deal with short-term business interruptions
• Form plans to deal with long-term problems and improve the organization
• See challenges as opportunities
• Keep your cool during challenges

How to Solve Business Problems Effectively

There are many different problem-solving skills, but most can be broken into general steps. Here is a four-step method for business problem solving:

1) Identify the Details of the Problem: Gather enough information to accurately define the problem. This can include data on procedures being used, employee actions, relevant workplace rules, and so on. Write down the specific outcome that is needed, but don’t assume what the solution should be.

2) Creatively Brainstorm Solutions: Alone or with a team, state every solution you can think of. You’ll often need to write them down. To get more solutions, brainstorm with the employees who have the greatest knowledge of the issue.

3) Evaluate Solutions and Make a Decision: Compare and contrast alternative solutions based on the feasibility of each one, including the resources needed to implement it and the return on investment of each one. Finally, make a firm decision on one solution that clearly addresses the root cause of the problem.

4) Take Action: Write up a detailed plan for implementing the solution, get the necessary approvals, and put it into action.

What Are Problem-Solving Skills?

Problem-solving skills are specific procedures that can be used to complete one or more of the four general steps of problem-solving (discussed above). Here are five important examples:

Using Emotional Intelligence: You’ll solve problems more calmly when you learn to recognize your own emotional patterns and to empathize with and guide the emotions of others. Avoid knee-jerk responses and making assumptions.

Researching Problems: An effective solution requires an accurate description of the problem. Define simple problems using quick research methods such as asking, “What? Where? When? and How much?.” Difficult problems require more in-depth research, such as data exploration, surveys, and interviews.

Creative Brainstorming: When brainstorming with a group, encourage idea creation by listening attentively to everyone, and recognizing everyone’s unique contributions.

Logical Reasoning: Develop standard logical steps for analyzing possible solutions to problems. Study and apply ideas about logical fallacies, deductive reasoning, and other areas of analytical thought.

Decisiveness: Use an agreed-upon system for choosing a solution, which can include assigning pros and cons to solutions, identifying mandatory results, getting feedback about solutions, choosing the decision-maker(s), and finishing or repeating the process.

How to Improve Problem-Solving Skills

Learning how to solve business problems takes time and effort. Though some people appear to have been born with superior problem-solving skills, great problem solvers usually have practiced and refined their abilities. You can develop high-level skills for solving problems too, through the following methods:

Ask and Listen: Don’t expect to solve every problem alone. Ask for advice, and listen to it carefully.

Practice Curiosity: Any time you’re involved in solving a problem, practice researching and defining the problem just a little longer than you would naturally.

Break Down Problems: Whenever possible, break large problems into their smallest units. Then, search for solutions to one unit at a time.

Don’t Label Yourself Negatively: Don’t allow a problem to mean something negative about you personally. Separate yourself from it. Look at it objectively and be part of the solution.

Clients We’ve Worked With

Contact form.

Need More Information? Please fill out the following form and we will be in contact with you with more information.

" * " indicates required fields

As Featured In:

The Better Business Bureau has determined that CMOE meets accreditation standards. These standards verify that CMOE’s product quality and competence enhance customer trust and confidence.

©2023 Center for Management & Organization Effectiveness. All rights reserved.