• Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Additional menu

MindManager Blog

What is problem-solving? And why is it important in the workplace?

September 28, 2023 by MindManager Blog

If there’s one thing you can count on as a business professional, it’s that you’ll never run short of new problems to solve. Thankfully, whether it includes handling difficult or unexpected situations in the workplace, or resolving complex organizational challenges, we all have the capacity to develop our business problem-solving skills.

The best way to get better at tackling problems productively is to start at the beginning. After all, the better you understand what problem-solving is – and the significant role it plays in every organization – the easier you’ll find it to improve on problem-solving skills in the workplace.

Let’s dive in!

What is problem-solving?

Problem-solving refers to the act of find solutions to difficult or complex issues.

A good problem-solving definition might be finding solutions to difficult or complex issues . In practice, however, solving problems in the workplace is a little more immersive than that.

In the workplace, problem-solving includes a variety of tools, resources, and techniques to:

  • Identify what’s not working.
  • Figure out why it’s broken.
  • Determine the best course of action to fix it.

Whether you know them as obstacles, glitches, or setbacks, problems are a part of our everyday lives. The good news is that our brains excel at reasoning out intricate scenarios and making calculations in situations we’ve never experienced before. That means every one of us is hard-wired to be an adept problem-solver.

The trick is to learn how to take that innate ability and apply it in a deliberate and practiced way.

However, one thing is certain: successfully resolving business and workplace issues is essential.

Not only does effective problem-solving create value that encourages growth, it goes hand-in-hand with impactful decision making.

What are the benefits of problem-solving in business?

Practically speaking, problem-solving provides a golden opportunity to improve your processes, products, and systems – especially when you work through those challenges with others.

Learning to face difficulties calmly, and deal with them intentionally, can also:

  • Ramp up your confidence.
  • Increase your resilience.
  • Help you develop valuable critical thinking skills.

Applying problem-solving skills in the face of an obstacle that seems insurmountable trains you to shift your perspective and look at potential hurdles in a different way.

It also gets you used to examining multiple options for dealing with a problem, which can help you feel more confident in the direction you take.

Solving problems as a team

Business problem solving as a team offers an even wider range of benefits since active collaboration tends to make good things happen at both the individual and group level.

For example:

  • Team-based problem-solving is akin to having a built-in sounding board when you explore new approaches and ideas.
  • As each team member’s critical thinking skills evolve, they bring fresh insights to the collective problem-solving process, bearing out the old adage that many heads are better than one.
  • Solving problems as a team also reduces the feeling of personal risk and exposure that’s common when one person is tasked with solving a puzzle. When that same problem is shared, the sense of risk gets dispersed, and individual team members are less likely to feel singled out.

Not only is there less chance of arriving at an unreasonable or biased solution when you problem-solve as a group, team members assigned to carry that solution out will feel more invested in its success.

Examples of problem solving skills in the workplace

Improving on your problem-solving skills helps you make the most of your brain’s natural capacity to analyze and reason things out.

There are dozens of problem-solving skills that play out in the average workplace – all of which can contribute to your ability to correct oversights, resolve conflict , and work around unexpected obstructions.

Here are a few common examples of problem-solving skills in the workplace, and tips on how to improve them.

1. Data gathering

Figuring out the cause of a problem hinges on collecting relevant data. Consulting efficiently with colleagues, conducting online research, and brainstorming with your team are all valuable data gathering skills.

2. Active listening

As opposed to listening in a purely supportive or empathetic way, active listening involves concentrating fully on what the other person is saying so you can understand the content, respond accordingly, and remember what was said later.

3. Troubleshooting

The ability to analyze and troubleshoot a situation with the help of any data and human input you’ve gathered is essential for drilling down into the core of a problem, and scrutinizing potential solutions.

4. Brainstorming

Brainstorming has become synonymous with creative thinking, innovative idea generation, and problem-solving. The more productive your brainstorming sessions, the more likely you and your group are to put together a list of quality, workable solutions.

It’s interesting to note that effective decision making is both a contributor to, and a by-product of, effective problem-solving.

For example, honing your analytical abilities and other problem-solving skills will inevitably help you make better decisions. The more efficient your decision-making process becomes, meanwhile, the better you’ll get at uncovering and acting on the most promising solution to any dilemma.

A simple problem-solving scenario

It’s clear that we can all benefit from getting more comfortable with problem-solving in the workplace.

Examples of situations where your problem-solving skills will come in handy aren’t difficult to find, and might include:

  • Fixing a technical issue for your customer.
  • Improving your student’s test performance.
  • Reducing the theft of your in-store merchandise.
  • Bumping up your marketing reach.

But, here’s the interesting thing. While it’s evident in each of these situations that there’s a problem to be solved, the exact nature of that problem isn’t so obvious.

In the student’s case, for example, you’d need additional input to help you figure out why they’re performing poorly. Only then would you be able to take steps to find the best-fit solution and achieve the desired learning outcome.

Here’s a simple scenario to help demonstrate that idea:

Bringing new customers onboard in a timely manner is an important part of your client relations strategy. Since hiring Alex a few weeks ago, however, your onboarding process has been taking longer than it should and team members are beginning to complain.

While you can see that the problem in this scenario is the fact that your team isn’t meeting their client onboarding goals, the key is to get clear on exactly what’s causing the hold-up.

You could jump to the conclusion that Alex has time management issues and that it’s time to start looking for a replacement. But, since one of the most common mistakes in business problem-solving is attempting to seize on a solution right away, that might cause you to waste time and resources on a remedy that ultimately proves unnecessary, or that doesn’t provide a viable fix.

Instead, it’s time to put your problem-solving skills to work.

Using data gathering and troubleshooting to pinpoint and clarify the bottleneck in your onboarding process – and active listening to interpret the situation from Alex’s perspective – you soon determine that the real cause of the problem is not what you thought.

In truth, an administrative oversight during the hiring process (yet another problem to be solved!) left Alex unaware of, and without access to, the business process map that’s so vital to efficiently onboarding new customers. Once you provide the necessary resources, it doesn’t take Alex long to get up to speed – and your client onboarding process to revert back to the well-oiled machine that it was.

Even with a team of eager problem-solvers by your side, the truth is that it’s often necessary to have the right problem-solving tools in place to achieve your desired results. That’s where versatile mind mapping software can help.

Not only does MindManager® provide a visual framework that fully supports the problem-solving process, it improves comprehension, inspires more creative solutions, and boosts your ability to make the best possible decisions.

Ready to take the next step?

MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.

what does problem solving team do

Why choose MindManager?

MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.

Explore MindManager

.css-s5s6ko{margin-right:42px;color:#F5F4F3;}@media (max-width: 1120px){.css-s5s6ko{margin-right:12px;}} AI that works. Coming June 5, Asana redefines work management—again. .css-1ixh9fn{display:inline-block;}@media (max-width: 480px){.css-1ixh9fn{display:block;margin-top:12px;}} .css-1uaoevr-heading-6{font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-1uaoevr-heading-6:hover{color:#F5F4F3;} .css-ora5nu-heading-6{display:-webkit-box;display:-webkit-flex;display:-ms-flexbox;display:flex;-webkit-align-items:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:start;-ms-flex-pack:start;-webkit-justify-content:flex-start;justify-content:flex-start;color:#0D0E10;-webkit-transition:all 0.3s;transition:all 0.3s;position:relative;font-size:16px;line-height:28px;padding:0;font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-ora5nu-heading-6:hover{border-bottom:0;color:#CD4848;}.css-ora5nu-heading-6:hover path{fill:#CD4848;}.css-ora5nu-heading-6:hover div{border-color:#CD4848;}.css-ora5nu-heading-6:hover div:before{border-left-color:#CD4848;}.css-ora5nu-heading-6:active{border-bottom:0;background-color:#EBE8E8;color:#0D0E10;}.css-ora5nu-heading-6:active path{fill:#0D0E10;}.css-ora5nu-heading-6:active div{border-color:#0D0E10;}.css-ora5nu-heading-6:active div:before{border-left-color:#0D0E10;}.css-ora5nu-heading-6:hover{color:#F5F4F3;} Get early access .css-1k6cidy{width:11px;height:11px;margin-left:8px;}.css-1k6cidy path{fill:currentColor;}

  • Product overview
  • All features
  • App integrations

CAPABILITIES

  • project icon Project management
  • Project views
  • Custom fields
  • Status updates
  • goal icon Goals and reporting
  • Reporting dashboards
  • workflow icon Workflows and automation
  • portfolio icon Resource management
  • Time tracking
  • my-task icon Admin and security
  • Admin console
  • asana-intelligence icon Asana Intelligence
  • list icon Personal
  • premium icon Starter
  • briefcase icon Advanced
  • Goal management
  • Organizational planning
  • Campaign management
  • Creative production
  • Marketing strategic planning
  • Request tracking
  • Resource planning
  • Project intake
  • View all uses arrow-right icon
  • Project plans
  • Team goals & objectives
  • Team continuity
  • Meeting agenda
  • View all templates arrow-right icon
  • Work management resources Discover best practices, watch webinars, get insights
  • What's new Learn about the latest and greatest from Asana
  • Customer stories See how the world's best organizations drive work innovation with Asana
  • Help Center Get lots of tips, tricks, and advice to get the most from Asana
  • Asana Academy Sign up for interactive courses and webinars to learn Asana
  • Developers Learn more about building apps on the Asana platform
  • Community programs Connect with and learn from Asana customers around the world
  • Events Find out about upcoming events near you
  • Partners Learn more about our partner programs
  • Support Need help? Contact the Asana support team
  • Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

what does problem solving team do

  • Business strategy |
  • Problem management: 8 steps to better p ...

Problem management: 8 steps to better problem solving

Alicia Raeburn contributor headshot

Problem management is an 8 step framework most commonly used by IT teams. You can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Solving the root cause prevents recurrence and creates a repeatable solution to use on similar errors in the future.

In an IT department, errors and mishaps are part of the job. You can't always control these problems, but you can control how you respond to them with problem management. Problem management helps you solve larger problems and reduce the risk that they’ll happen again by identifying all connected problems, solving them, and planning for the future.

What is problem management?

Problem management is an 8 step framework most commonly used by IT teams. Your team can use problem management to solve for repeating major incidents. By organizing and structuring your problem solving, you can more effectively get to the root cause of high-impact problems—and devise a solution. Problem management is a process—used mostly by IT teams—to identify, react, and respond to issues. It’s not for every problem, but it’s a useful response when multiple major incidents occur that cause large work interruptions. Unlike problem solving, problem management goes beyond the initial incident to discover and dissect the root causes, preventing future incidents with permanent solutions.

The goals of problem management are to:

Prevent problems before they start.

Solve for repetitive errors.

Lessen each incident’s impact. 

Problem management vs. incident management 

Example: Someone leaves their unprotected laptop in a coffee shop, causing a security breach. The security team can use incident management to solve for this one, isolated event. In this case, the team could manually shut down the accounts connected to that laptop. If this continues to happen, IT would use problem management to solve the root of this issue—perhaps installing more security features on each company laptop so that if employees lose them, no one else can access the information.

Problem management vs. problem solving

While similar in name, problem management differs slightly from problem-solving. Problem management focuses on every aspect of the incident—identifying the root cause of the problem, solving it, and prevention. Problem solving is, as the name implies, focused solely on the solution step. 

Example: You’re launching a new password management system when it crashes—again. You don’t know if anything leaked, but you know it could contain confidential information. Plus, it’s happened before. You start the problem management process to ensure it doesn’t happen again. In that process, you’ll use problem solving as a step to fix the issue. In this case, perhaps securing confidential information before you try to launch a new software.

Problem management vs. change management 

Change management targets large transitions within your workplace, good and bad. These inevitable changes aren’t always negative, so you can’t always apply problem management as a solution. That’s where change management comes in—a framework that helps you adjust to any new scenario.

Example: Your company is transitioning to a new cloud platform. The transition happens incident-free—meaning you won’t need problem management—but you can ease the transition by implementing some change management best practices. Preparing and training team members in the new software is a good place to start.

Problem management vs. project management

Project management is the framework for larger collections of work. It’s the overarching method for how you work on any project, hit goals, and get results. You can use project management to help you with problem management, but they are not the same thing. Problem management and project management work together to solve issues as part of your problem management process.

Example: During problem management, you uncover a backend security issue that needs to be addressed—employees are using storage software with outdated security measures. To solve this, you create a project and outline the tasks from start to finish. In this case, you might need to alert senior executives, get approval to remove the software, and alert employees. You create a project schedule with a defined timeline and assign the tasks to relevant teams. In this process, you identified a desired outcome—remove the unsafe software—and solved it. That’s project management.

The 8 steps of problem management

It’s easy to get upset when problems occur. In fact, it’s totally normal. But an emotional response is not always the best response when faced with new incidents. Having a reliable system—such as problem management—removes the temptation to respond emotionally. Proactive project management gives your team a framework for problem solving. It’s an iterative process —the more you use it, the more likely you are to have fewer problems, faster response times, and better outputs. 

1. Identify the problem

During problem identification, you’re looking at the present—what’s happening right now? Here, you’ll define what the incident is and its scale. Is this a small, quick-fix, or a full overhaul? Consider using problem framing to define, prioritize, and understand the obstacles involved with these more complex problems. 

2. Diagnose the cause

Use problem analysis or root cause analysis to strategically look at the cause of a problem. Follow the trail of issues all the way back to its beginnings.

To diagnose the underlying cause, you’ll want to answer:

What factors or conditions led to the incident?

Do you see related incidents? Could those be coming from the same source?

Did someone miss a step? Are processes responsible for this problem?

3. Organize and prioritize

Now it’s time to build out your framework. Use an IT project plan to organize information in a space where everyone can make and see updates in real time. The easiest way to do this is with a project management tool where you can input ‌tasks, assign deadlines, and add dependencies to ensure nothing gets missed. To better organize your process, define:

What needs to be done? 

Who’s responsible for each aspect? If no one is, can we assign someone? 

When does each piece need to be completed?

What is the final number of incidents related to this problem?

Are any of these tasks dependent on another one? Do you need to set up dependencies ?

What are your highest priorities? How do they affect our larger business goals ? 

How should you plan for this in the future?

4. Create a workaround

If the incident has stopped work or altered it, you might need to create a workaround. This is not always necessary, but temporary workarounds can keep work on track and avoid backlog while you go through the problem management steps. When these workarounds are especially effective, you can make them permanent processes.

5. Update your known error database

Every time an incident occurs, create a known error record and add it to your known error database (KEDB). Recording incidents helps you catch recurrences and logs the solution, so you know how to solve similar errors in the future. 

[product ui] Incident log example (lists)

6. Pause for change management (if necessary)

Larger, high-impact problems might require change management. For example, if you realize the problem’s root cause is a lack of staff, you might dedicate team members to help. You can use change management to help them transition their responsibilities, see how these new roles fit in with the entire team, and determine how they will collaborate moving forward.

7. Solve the problem

This is the fun part—you get to resolve problems. At this stage, you should know exactly what you’re dealing with and the steps you need to take. But remember—with problem management, it’s not enough to solve the current problem. You’ll want to take any steps to prevent this from happening again in the future. That could mean hiring a new role to cover gaps in workflows , investing in new softwares and tools, or training staff on best practices to prevent these types of incidents.

Read: Turn your team into skilled problem solvers with these problem-solving strategies

8. Reflect on the process

The problem management process has the added benefit of recording the process in its entirety, so you can review it in the future. Once you’ve solved the problem, take the time to review each step and reflect on the lessons learned during this process. Make note of who was involved, what you needed, and any opportunities to improve your response to the next incident. After you go through the problem management process a few times and understand the basic steps, stakeholders, workload, and resources you need, create a template to make the kickoff process easier in the future.

5 benefits of problem management

Problem management helps you discover every piece of the problem—from the current scenario down to its root cause. Not only does this have an immediate positive impact on the current issue at hand, it also promotes collaboration and helps to build a better product overall. 

Here are five other ways ‌problem management can benefit your team:

Avoids repeat incidents. When you manage the entire incident from start to finish, you will address the foundational problems that caused it. This leads to fewer repeat incidents.

Boosts cross-functional collaboration. Problem management is a collaborative process. One incident might require collaboration from IT, the security team, and legal. Depending on the level of the problem, it might trickle all the way back down to the product or service team, where core changes need to be made.

Creates a better user experience. It’s simple—the fewer incidents you have, the better your customer’s experience will be. Reducing incidents means fewer delays, downtime, and frustrations for your users, and a higher rate of customer satisfaction.

Improves response time. As you develop a flow and framework with a project management process, you’ll be better equipped to handle future incidents—even if they’re different scenarios.

Organizes problem solving. Problem management provides a structured, thoughtful approach to solving problems. This reduces impulsive responses and helps you keep a better problem record of incidents and solutions.

Problem management leads to better, faster solutions

IT teams will always have to deal with incidents, but they don’t have to be bogged down by them. That’s because problem management works. Whether you employ a full problem management team or choose to apply these practices to your current IT infrastructure, problem management—especially when combined with a project management tool—saves you time and effort down the road.

With IT project plans, we’ve made it easier than ever to track your problem management work in a shared tool. Try our free IT project template to see your work come together, effortlessly.

Related resources

what does problem solving team do

Grant management: A nonprofit’s guide

what does problem solving team do

How Asana uses work management to optimize resource planning

what does problem solving team do

How Asana uses work management for organizational planning

what does problem solving team do

Solve your tech overload with an intelligent transformation

Bruce Tulgan, JD

How Managers Can Improve Team Problem-Solving

Teaching good problem-solving means learning from previous solutions..

Posted March 28, 2024 | Reviewed by Ray Parker

  • What Is a Career
  • Find a career counselor near me
  • We can access vast information online, but critical thinking skills are still essential.
  • The key to improving team problem-solving is providing reliable resources you trust.
  • Build a library of problem-solving resources, including creating step-by-step instructions and checklists.

TA Design/Shutterstock

By now, it is a hackneyed truth about today’s world that we all have endless amounts of information at our fingertips, available instantly, all the time. We have multiple competing answers to any question on any subject—more answers than an entire team, let alone an individual, could possibly master in a lifetime. The not quite as obvious punchline is this: There has been a radical change in how much information a person needs to keep inside their head versus accessible through their fingertips.

Nobody should be so short-sighted or so old-fashioned as to write off the power of being able to fill knowledge gaps on demand. Yet this phenomenon is often attributed to a growing critical thinking skills gap experienced in many organizations today.

Many people today are simply not in the habit of really thinking on their feet. Without a lot of experience puzzling through problems, it should be no surprise that so many people are often puzzled when they encounter unanticipated problems.

Here’s the thing: Nine out of ten times, you don’t need to make important decisions on the basis of your own judgment at the moment. You are much better off if you can rely on the accumulated experience of the organization in which you are working, much like we rely on the accumulated information available online.

The key is ensuring that your direct reports are pulling from sources of information and experience they and the organization can trust.

The first step to teaching anybody the basics of problem-solving is to anticipate the most common recurring problems and prepare with ready-made solutions. It may seem counterintuitive, but problem-solving skills aren’t built by reinventing the wheel: From learning and implementing ready-made solutions, employees will learn a lot about the anatomy of a good solution. This will put them in a much better position to improvise when they encounter a truly unanticipated problem.

The trick is to capture best practices, turn them into standard operating procedures, and deploy them to your team for use as job aids. This can be as simple as an “if, then” checklist:

  • If A happens, then do B.
  • If C happens, then do D.
  • If E happens, then do F.

Here are seven tips to help you build a library of problem-solving resources for your team:

1. Break things down and write them out. Start with what you know. Break down the task or project into a list of step-by-step instructions, incorporating any resources or job aids you currently use. Then, take each step further by breaking it down into a series of concrete actions. Get as granular as you possibly can—maybe even go overboard a little. It will always be easier to remove unnecessary steps from your checklist than to add in necessary steps later.

2. Follow your instructions as if you were a newbie. Once you have a detailed, step-by-step outline, try using it as though you were totally new to the task or project. Follow the instructions exactly as you have written them: Avoid subconsciously filling in any gaps with your own expertise. Don't assume that anything goes without saying, especially if the task or project is especially technical or complex. As you follow your instructions, make corrections and additions as you go. Don't make the mistake of assuming you will remember to make necessary corrections or additions later.

3. Make final edits. Follow your updated and improved instructions one final time. Make any further corrections or additions as necessary. Include as many details as possible for and between each step.

4. Turn it into a checklist. Now, it's time to translate your instructions into a checklist format. Checklists are primarily tools of mindfulness : They slow us down and focus us on the present actions under our control. Consider whether the checklist will be more helpful if it is phrased in past or present tense. Who will be using the checklist? What information do they need to know? How much of the checklist can be understood at a glance?

5. Get outside input. Ask someone to try and use your checklist to see if it works for them. Get their feedback about what was clear, what was unclear, and why it was clear or unclear. Ask about any questions they had that weren't answered by the checklist. Solicit other suggestions, thoughts, or improvements you may not have considered. Incorporate their input and then repeat the process with another tester.

what does problem solving team do

6. Use your checklist. Don't simply create your checklist for others and then abandon it. Use it in your own work going forward, and treat it as a living document. Make clarifying notes, additions, and improvements as the work naturally changes over time. Remember, checklists are tools of mindfulness. Use them to tune in to the work you already do and identify opportunities for growth and improvement.

7. Establish a system for saving drafts, templates, and examples of work that can be shared with others . Of course, checklists are just one type of shareable job aid. Sharing examples of your previous work or another team member is another useful way to help someone jumpstart a new task or project. This can be anything from final products to drafts, sketches, templates, or even videos.

Bruce Tulgan, JD

Bruce Tulgan, JD, is the founder and CEO of RainmakerThinking and the author of The Art of Being Indispensable at Work.

  • Find a Therapist
  • Find a Treatment Center
  • Find a Psychiatrist
  • Find a Support Group
  • Find Online Therapy
  • United States
  • Brooklyn, NY
  • Chicago, IL
  • Houston, TX
  • Los Angeles, CA
  • New York, NY
  • Portland, OR
  • San Diego, CA
  • San Francisco, CA
  • Seattle, WA
  • Washington, DC
  • Asperger's
  • Bipolar Disorder
  • Chronic Pain
  • Eating Disorders
  • Passive Aggression
  • Personality
  • Goal Setting
  • Positive Psychology
  • Stopping Smoking
  • Low Sexual Desire
  • Relationships
  • Child Development
  • Therapy Center NEW
  • Diagnosis Dictionary
  • Types of Therapy

March 2024 magazine cover

Understanding what emotional intelligence looks like and the steps needed to improve it could light a path to a more emotionally adept world.

  • Emotional Intelligence
  • Gaslighting
  • Affective Forecasting
  • Neuroscience
  • Coach Portal

Stewart Leadership

  • Executive Coaching
  • Leadership Training
  • Executive Presence
  • Manager Development
  • Team Assessment & Alignment
  • Executive Team Development
  • New Leader Assimilation
  • Presentation & Orals Coaching
  • Change Strategy & Training
  • Strategic Planning & Board Services
  • Culture Assessment & Integration
  • Organizational Design
  • Employee Experience
  • Succession & Workforce Planning
  • Career Management
  • Promote Diversity Equity & Inclusion
  • Competency Modeling
  • LEAD NOW! Model
  • LEAD NOW! All Access
  • Teaming For Success Model
  • Assessments
  • Certifications
  • Facilitation
  • Client Success Stories
  • Clients & Partners
  • Join Our Team
  • Ask A Coach
  • Blog Articles
  • Leadership Lessons
  • LEAD NOW! Videos
  • White Papers
  • Leadership Growth Hour
  • LEAD NOW! Certifications
  • Teaming For Success Certifications
  • Connect With Us
  • Assessment Center

7 Advantages of Team Problem-Solving

--> Team Performance ,--> Teaming ,--> Problem Solving -->