problem solving team definition in management

Members-only Content

• Monthly Member Events
• Event Session Videos
• Experience Reports
• Research Papers
• Share a Community Event
• Submit an Article to the Blog
• Submit a Member Initiative
• Promote a Training Event

Become an Agile Alliance member!

Your membership enables us to offer a wealth of resources, present renowned international events, support global community groups, and so much more! And, while you’re supporting our non-profit mission, you’ll also gain access to a range of valuable member benefits. Learn more

• Join Us Today
• Member Portal
• Membership FAQs
• Terms and Conditions
• Corporate Members

Agile Conferences

• Agile en Chile 2024
• Agile Executive Forum
• Agile2024 European Experience
• All Agile Alliance Events
• Past Conferences
• Become an Event Sponsor

Virtual Events

• Member Events Calendar
• Agile MiniCon
• BYOC Lean Coffee
• Agile Tech Talks
• Member Meet & Greet
• Agile Coaching Network
• Full Events Calendar
• Community Events
• Non-profit Events
• Agile Training
• Sponsored Meetup Groups
• Submit a Non-profit Event
• Submit a For-profit Training
• Event Funding Request
• Global Events Calendars

Agile en Chile – 2024

• Events Calendar
• BYOC – Lean Coffee
• Member Meet & Greet
• View All Events
• Submit an Event
• Meetup Groups
• Past Conferences & Events

Agile Essentials is designed to bring you up to speed on the basic concepts and principles of Agile with articles, videos, glossary terms, and more.

Agile Essentials

Download the Agile Manifesto

To download a free PDF copy of the Agile Manifesto and 12 Principles of Agile, simply sign-up for our newsletter. Agile Alliance members can download it for free.

• Agile Essentials Overview
• Agile Manifesto
• 12 Principles Behind the Manifesto
• A Short History of Agile
• Subway Map to Agile Practices
• Agile Glossary
• Introductory Videos

Recent Blog Posts

Agile Coach Camp Worldwide is going to Costa Rica

Agile Alliance Call for Nominations for the Board of Directors

Agile Alliance Launches Young Professionals Committee

View all blog posts

Agile Resources

The new agile resource guide.

Find Agile services and products from our member companies in our new Agile Resource Guide . Many listings in the guide feature exclusive offers just for Agile Alliance members. View the guide 

• Remote Working Guide
• Event Sessions
• Content Library

Sustainability Manifesto

The  Agile Sustainability Initiative has created the Agile Sustainability Manifesto in an effort to grow awareness about sustainability within the Agile community and inspire a more sustainable way of working. Read and sign now

MEMBER INITIATIVES

• Agile Sustainability Initiative
• Principle 12 Initiative
• Agile in Color Initiative
• Agile Coach Camp Worldwide
• Agile Coaching Ethics

View all initiatives

Your Community

Global development.

• LATAM Community
• India Community

Global Affiliates

• Community Groups
• Community Services
• Member Initiatives
• LATAM Community Development
• India Community Development
• Volunteer Signup

OUR POLICIES

Become a sponsor.

Being an Agile Alliance sponsor is a great way to introduce your company to our members to build awareness around your products and services. The Call for Agile2024 Sponsorships is now open, and there are great options and opportunities still available! Learn more >

• About Agile Alliance
• Code of Conduct
• Board of Directors
• Agile Alliance Brazil
• Agile Alliance New Zealand
• Policies, Reports & Bylaws
• Logo and Media Files
• Become a Sponsor

Agile Event Session

Problem solving teams: creating resilient organisations through managing complexity, this video content is for agile alliance members only.

If you’re already an active member, please log in now .

To view this content, and gain access to many more valuable resources, conference discounts, and invitations to exclusive networking and learning events, please consider becoming an Agile Alliance member .

Abstract/Description

One reason many of us came to the field of software engineering or software development is because we enjoy solving problems. It exercises out mental muscles, and gives us a feeling of satisfaction to know we can add value to our organizations and customers by solving tough problems. However, as the organizations we work for get bigger, and the scope of work gets bigger, so too do the problems we need to solve. There comes a point where we can’t solve them alone, or even with the immediate team we work with. Some problems require a cross-organization, multi-function approach. When our goal is to be a more agile, lean-thinking organization, we need to develop approaches to solving these types of problems.

This is where Problem Solving Teams come into play. Problem Solving Teams are temporary structures that bring together leaders and team members from across the organization to focus on solving a specific problem. The benefits are many, including not just a solved problem, but also a more resilient organization, a stronger social network and a growing cohort of problem solvers with increased skills and abilities.

This approach draws from many influences, including complexity science, social network theory, military doctrine, flight crews, and emergency responders. We have been experimenting with this approach across several areas that involve multiple geographies and multiple functions.

Additional Resources

Speaker(s) may be willing to present this session at local group meetings and other events.

• Conference or Event
• Session Type
• Audience Levels

More Agile Event Session Videos

Agile – 5 key points for managers

Hacking Culture for Change Management

Have a comment join the conversation, discover the many benefits of membership.

Your membership enables Agile Alliance to offer a wealth of first-rate resources, present renowned international events, support global community groups, and more — all geared toward helping Agile practitioners reach their full potential and deliver innovative, Agile solutions.

Thank you to our valued Agile Alliance Annual Partners

Our new Annual Partner Program offers a new and exciting level of engagement beyond event sponsorship.

Our Cornerstone Corporate Supporting Members

Our Corporate Supporting Members are vital to the mission of Agile Alliance.  Click here to view all corporate members.

©2024 Agile Alliance  |  All Rights Reserved  |  Privacy Policy

©2024 Agile Alliance All Rights Reserved  |  Privacy Policy

• Welcome back!

Not yet a member? Sign up now

• Renew Membership
• Agile Alliance Events
• Agile en Español
• Agile en Chile
• Resources Overview
• Agile Books
• Content Library by Category
• Content Standards
• Privacy Policy
• Cookie Policy

Privacy Overview

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

Additional menu

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.

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

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

This textbook covers content relevant to COMS342 Problem Solving in Teams and Groups at the University of Kansas. Content in this textbook is adapted from The Open University , OpenStax , The Noba Project , and Wikipedia. Each chapter presents the source in the top header and each chapter has its own version of the Creative Commons (CC) license, noted at the bottom of the chapter.

This book (commonly called an Open Educational Resource, OER) was made possible through a generous grant through the KU Libraries. Special thanks to Karna Younger, Josh Bollick, and William Hoffman for helping with this project. The most recent revision (2021) includes several chapters from Dr. Jasmine Linabary’s OER, Small Group Communication: Forming and Sustaining Teams . Special thanks to Dr. Linabary for her exceptional work and willingness to share.

This textbook is designed with several purposes:

• The primary purpose is to save students money.
• Additionally this book is designed to cater the class reading content to the students’ needs.
• Finally this book was created as a text that can easily change based on the needs of the course.

To begin using the book, click on “Contents” in the top-left corner of the screen or use the arrow navigation buttons at the bottom to flip through chapters.

Please submit any revisions via comments on any chapter or email them directly to Dr. Cameron Piercy ([email protected]).

Cameron W. Piercy, Ph.D.

Problem Solving in Teams and Groups Copyright © 2021 by Cameron W. Piercy, Ph.D. is licensed under a Creative Commons Attribution 4.0 International License , except where otherwise noted.

Share This Book

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

A step-by-step guide to planning a workshop, how to create an unforgettable training session in 8 simple steps, 47 useful online tools for workshop planning and meeting facilitation.

All teams and organizations encounter challenges as they grow. There are problems that might occur for teams when it comes to miscommunication or resolving business-critical issues . You may face challenges around growth , design , user engagement, and even team culture and happiness. In short, problem-solving techniques should be part of every team’s skillset.

Problem-solving methods are primarily designed to help a group or team through a process of first identifying problems and challenges , ideating possible solutions , and then evaluating the most suitable .

Finding effective solutions to complex problems isn’t easy, but by using the right process and techniques, you can help your team be more efficient in the process.

So how do you develop strategies that are engaging, and empower your team to solve problems effectively?

In this blog post, we share a series of problem-solving tools you can use in your next workshop or team meeting. You’ll also find some tips for facilitating the process and how to enable others to solve complex problems.

Let’s get started! 

How do you identify problems?

How do you identify the right solution.

• Tips for more effective problem-solving

Complete problem-solving methods

• Problem-solving techniques to identify and analyze problems
• Problem-solving techniques for developing solutions

Problem-solving warm-up activities

Closing activities for a problem-solving process.

Before you can move towards finding the right solution for a given problem, you first need to identify and define the problem you wish to solve. 

Here, you want to clearly articulate what the problem is and allow your group to do the same. Remember that everyone in a group is likely to have differing perspectives and alignment is necessary in order to help the group move forward. 

Identifying a problem accurately also requires that all members of a group are able to contribute their views in an open and safe manner. It can be scary for people to stand up and contribute, especially if the problems or challenges are emotive or personal in nature. Be sure to try and create a psychologically safe space for these kinds of discussions.

Remember that problem analysis and further discussion are also important. Not taking the time to fully analyze and discuss a challenge can result in the development of solutions that are not fit for purpose or do not address the underlying issue.

Successfully identifying and then analyzing a problem means facilitating a group through activities designed to help them clearly and honestly articulate their thoughts and produce usable insight.

With this data, you might then produce a problem statement that clearly describes the problem you wish to be addressed and also state the goal of any process you undertake to tackle this issue.  

Finding solutions is the end goal of any process. Complex organizational challenges can only be solved with an appropriate solution but discovering them requires using the right problem-solving tool.

After you’ve explored a problem and discussed ideas, you need to help a team discuss and choose the right solution. Consensus tools and methods such as those below help a group explore possible solutions before then voting for the best. They’re a great way to tap into the collective intelligence of the group for great results!

Remember that the process is often iterative. Great problem solvers often roadtest a viable solution in a measured way to see what works too. While you might not get the right solution on your first try, the methods below help teams land on the most likely to succeed solution while also holding space for improvement.

Every effective problem solving process begins with an agenda . A well-structured workshop is one of the best methods for successfully guiding a group from exploring a problem to implementing a solution.

In SessionLab, it’s easy to go from an idea to a complete agenda . Start by dragging and dropping your core problem solving activities into place . Add timings, breaks and necessary materials before sharing your agenda with your colleagues.

The resulting agenda will be your guide to an effective and productive problem solving session that will also help you stay organized on the day!

Tips for more effective problem solving

Problem-solving activities are only one part of the puzzle. While a great method can help unlock your team’s ability to solve problems, without a thoughtful approach and strong facilitation the solutions may not be fit for purpose.

Let’s take a look at some problem-solving tips you can apply to any process to help it be a success!

Clearly define the problem

Jumping straight to solutions can be tempting, though without first clearly articulating a problem, the solution might not be the right one. Many of the problem-solving activities below include sections where the problem is explored and clearly defined before moving on.

This is a vital part of the problem-solving process and taking the time to fully define an issue can save time and effort later. A clear definition helps identify irrelevant information and it also ensures that your team sets off on the right track.

Don’t jump to conclusions

It’s easy for groups to exhibit cognitive bias or have preconceived ideas about both problems and potential solutions. Be sure to back up any problem statements or potential solutions with facts, research, and adequate forethought.

The best techniques ask participants to be methodical and challenge preconceived notions. Make sure you give the group enough time and space to collect relevant information and consider the problem in a new way. By approaching the process with a clear, rational mindset, you’ll often find that better solutions are more forthcoming.  

Try different approaches  

Problems come in all shapes and sizes and so too should the methods you use to solve them. If you find that one approach isn’t yielding results and your team isn’t finding different solutions, try mixing it up. You’ll be surprised at how using a new creative activity can unblock your team and generate great solutions.

Don’t take it personally 

Depending on the nature of your team or organizational problems, it’s easy for conversations to get heated. While it’s good for participants to be engaged in the discussions, ensure that emotions don’t run too high and that blame isn’t thrown around while finding solutions.

You’re all in it together, and even if your team or area is seeing problems, that isn’t necessarily a disparagement of you personally. Using facilitation skills to manage group dynamics is one effective method of helping conversations be more constructive.

Get the right people in the room

Your problem-solving method is often only as effective as the group using it. Getting the right people on the job and managing the number of people present is important too!

If the group is too small, you may not get enough different perspectives to effectively solve a problem. If the group is too large, you can go round and round during the ideation stages.

Creating the right group makeup is also important in ensuring you have the necessary expertise and skillset to both identify and follow up on potential solutions. Carefully consider who to include at each stage to help ensure your problem-solving method is followed and positioned for success.

Document everything

The best solutions can take refinement, iteration, and reflection to come out. Get into a habit of documenting your process in order to keep all the learnings from the session and to allow ideas to mature and develop. Many of the methods below involve the creation of documents or shared resources. Be sure to keep and share these so everyone can benefit from the work done!

Bring a facilitator 

Facilitation is all about making group processes easier. With a subject as potentially emotive and important as problem-solving, having an impartial third party in the form of a facilitator can make all the difference in finding great solutions and keeping the process moving. Consider bringing a facilitator to your problem-solving session to get better results and generate meaningful solutions!

Develop your problem-solving skills

It takes time and practice to be an effective problem solver. While some roles or participants might more naturally gravitate towards problem-solving, it can take development and planning to help everyone create better solutions.

You might develop a training program, run a problem-solving workshop or simply ask your team to practice using the techniques below. Check out our post on problem-solving skills to see how you and your group can develop the right mental process and be more resilient to issues too!

Design a great agenda

Workshops are a great format for solving problems. With the right approach, you can focus a group and help them find the solutions to their own problems. But designing a process can be time-consuming and finding the right activities can be difficult.

Check out our workshop planning guide to level-up your agenda design and start running more effective workshops. Need inspiration? Check out templates designed by expert facilitators to help you kickstart your process!

In this section, we’ll look at in-depth problem-solving methods that provide a complete end-to-end process for developing effective solutions. These will help guide your team from the discovery and definition of a problem through to delivering the right solution.

If you’re looking for an all-encompassing method or problem-solving model, these processes are a great place to start. They’ll ask your team to challenge preconceived ideas and adopt a mindset for solving problems more effectively.

• Six Thinking Hats
• Lightning Decision Jam
• Problem Definition Process
• Discovery & Action Dialogue

Design Sprint 2.0

• Open Space Technology

1. Six Thinking Hats

Individual approaches to solving a problem can be very different based on what team or role an individual holds. It can be easy for existing biases or perspectives to find their way into the mix, or for internal politics to direct a conversation.

Six Thinking Hats is a classic method for identifying the problems that need to be solved and enables your team to consider them from different angles, whether that is by focusing on facts and data, creative solutions, or by considering why a particular solution might not work.

Like all problem-solving frameworks, Six Thinking Hats is effective at helping teams remove roadblocks from a conversation or discussion and come to terms with all the aspects necessary to solve complex problems.

2. Lightning Decision Jam

Featured courtesy of Jonathan Courtney of AJ&Smart Berlin, Lightning Decision Jam is one of those strategies that should be in every facilitation toolbox. Exploring problems and finding solutions is often creative in nature, though as with any creative process, there is the potential to lose focus and get lost.

Unstructured discussions might get you there in the end, but it’s much more effective to use a method that creates a clear process and team focus.

In Lightning Decision Jam, participants are invited to begin by writing challenges, concerns, or mistakes on post-its without discussing them before then being invited by the moderator to present them to the group.

From there, the team vote on which problems to solve and are guided through steps that will allow them to reframe those problems, create solutions and then decide what to execute on. 

By deciding the problems that need to be solved as a team before moving on, this group process is great for ensuring the whole team is aligned and can take ownership over the next stages. 

Lightning Decision Jam (LDJ)   #action   #decision making   #problem solving   #issue analysis   #innovation   #design   #remote-friendly   The problem with anything that requires creative thinking is that it’s easy to get lost—lose focus and fall into the trap of having useless, open-ended, unstructured discussions. Here’s the most effective solution I’ve found: Replace all open, unstructured discussion with a clear process. What to use this exercise for: Anything which requires a group of people to make decisions, solve problems or discuss challenges. It’s always good to frame an LDJ session with a broad topic, here are some examples: The conversion flow of our checkout Our internal design process How we organise events Keeping up with our competition Improving sales flow

3. Problem Definition Process

While problems can be complex, the problem-solving methods you use to identify and solve those problems can often be simple in design. 

By taking the time to truly identify and define a problem before asking the group to reframe the challenge as an opportunity, this method is a great way to enable change.

Begin by identifying a focus question and exploring the ways in which it manifests before splitting into five teams who will each consider the problem using a different method: escape, reversal, exaggeration, distortion or wishful. Teams develop a problem objective and create ideas in line with their method before then feeding them back to the group.

This method is great for enabling in-depth discussions while also creating space for finding creative solutions too!

Problem Definition   #problem solving   #idea generation   #creativity   #online   #remote-friendly   A problem solving technique to define a problem, challenge or opportunity and to generate ideas.

4. The 5 Whys 

Sometimes, a group needs to go further with their strategies and analyze the root cause at the heart of organizational issues. An RCA or root cause analysis is the process of identifying what is at the heart of business problems or recurring challenges. 

The 5 Whys is a simple and effective method of helping a group go find the root cause of any problem or challenge and conduct analysis that will deliver results. 

By beginning with the creation of a problem statement and going through five stages to refine it, The 5 Whys provides everything you need to truly discover the cause of an issue.

The 5 Whys   #hyperisland   #innovation   This simple and powerful method is useful for getting to the core of a problem or challenge. As the title suggests, the group defines a problems, then asks the question “why” five times, often using the resulting explanation as a starting point for creative problem solving.

5. World Cafe

World Cafe is a simple but powerful facilitation technique to help bigger groups to focus their energy and attention on solving complex problems.

World Cafe enables this approach by creating a relaxed atmosphere where participants are able to self-organize and explore topics relevant and important to them which are themed around a central problem-solving purpose. Create the right atmosphere by modeling your space after a cafe and after guiding the group through the method, let them take the lead!

Making problem-solving a part of your organization’s culture in the long term can be a difficult undertaking. More approachable formats like World Cafe can be especially effective in bringing people unfamiliar with workshops into the fold. 

World Cafe   #hyperisland   #innovation   #issue analysis   World Café is a simple yet powerful method, originated by Juanita Brown, for enabling meaningful conversations driven completely by participants and the topics that are relevant and important to them. Facilitators create a cafe-style space and provide simple guidelines. Participants then self-organize and explore a set of relevant topics or questions for conversation.

6. Discovery & Action Dialogue (DAD)

One of the best approaches is to create a safe space for a group to share and discover practices and behaviors that can help them find their own solutions.

With DAD, you can help a group choose which problems they wish to solve and which approaches they will take to do so. It’s great at helping remove resistance to change and can help get buy-in at every level too!

This process of enabling frontline ownership is great in ensuring follow-through and is one of the methods you will want in your toolbox as a facilitator.

Discovery & Action Dialogue (DAD)   #idea generation   #liberating structures   #action   #issue analysis   #remote-friendly   DADs make it easy for a group or community to discover practices and behaviors that enable some individuals (without access to special resources and facing the same constraints) to find better solutions than their peers to common problems. These are called positive deviant (PD) behaviors and practices. DADs make it possible for people in the group, unit, or community to discover by themselves these PD practices. DADs also create favorable conditions for stimulating participants’ creativity in spaces where they can feel safe to invent new and more effective practices. Resistance to change evaporates as participants are unleashed to choose freely which practices they will adopt or try and which problems they will tackle. DADs make it possible to achieve frontline ownership of solutions.

7. Design Sprint 2.0

Want to see how a team can solve big problems and move forward with prototyping and testing solutions in a few days? The Design Sprint 2.0 template from Jake Knapp, author of Sprint, is a complete agenda for a with proven results.

Developing the right agenda can involve difficult but necessary planning. Ensuring all the correct steps are followed can also be stressful or time-consuming depending on your level of experience.

Use this complete 4-day workshop template if you are finding there is no obvious solution to your challenge and want to focus your team around a specific problem that might require a shortcut to launching a minimum viable product or waiting for the organization-wide implementation of a solution.

8. Open space technology

Open space technology- developed by Harrison Owen – creates a space where large groups are invited to take ownership of their problem solving and lead individual sessions. Open space technology is a great format when you have a great deal of expertise and insight in the room and want to allow for different takes and approaches on a particular theme or problem you need to be solved.

Start by bringing your participants together to align around a central theme and focus their efforts. Explain the ground rules to help guide the problem-solving process and then invite members to identify any issue connecting to the central theme that they are interested in and are prepared to take responsibility for.

Once participants have decided on their approach to the core theme, they write their issue on a piece of paper, announce it to the group, pick a session time and place, and post the paper on the wall. As the wall fills up with sessions, the group is then invited to join the sessions that interest them the most and which they can contribute to, then you’re ready to begin!

Everyone joins the problem-solving group they’ve signed up to, record the discussion and if appropriate, findings can then be shared with the rest of the group afterward.

Open Space Technology   #action plan   #idea generation   #problem solving   #issue analysis   #large group   #online   #remote-friendly   Open Space is a methodology for large groups to create their agenda discerning important topics for discussion, suitable for conferences, community gatherings and whole system facilitation

Techniques to identify and analyze problems

Using a problem-solving method to help a team identify and analyze a problem can be a quick and effective addition to any workshop or meeting.

While further actions are always necessary, you can generate momentum and alignment easily, and these activities are a great place to get started.

We’ve put together this list of techniques to help you and your team with problem identification, analysis, and discussion that sets the foundation for developing effective solutions.

Let’s take a look!

• The Creativity Dice
• Fishbone Analysis
• Problem Tree
• SWOT Analysis
• Agreement-Certainty Matrix
• The Journalistic Six
• LEGO Challenge
• What, So What, Now What?
• Journalists

Individual and group perspectives are incredibly important, but what happens if people are set in their minds and need a change of perspective in order to approach a problem more effectively?

Flip It is a method we love because it is both simple to understand and run, and allows groups to understand how their perspectives and biases are formed. 

Participants in Flip It are first invited to consider concerns, issues, or problems from a perspective of fear and write them on a flip chart. Then, the group is asked to consider those same issues from a perspective of hope and flip their understanding.  

No problem and solution is free from existing bias and by changing perspectives with Flip It, you can then develop a problem solving model quickly and effectively.

Flip It!   #gamestorming   #problem solving   #action   Often, a change in a problem or situation comes simply from a change in our perspectives. Flip It! is a quick game designed to show players that perspectives are made, not born.

10. The Creativity Dice

One of the most useful problem solving skills you can teach your team is of approaching challenges with creativity, flexibility, and openness. Games like The Creativity Dice allow teams to overcome the potential hurdle of too much linear thinking and approach the process with a sense of fun and speed. 

In The Creativity Dice, participants are organized around a topic and roll a dice to determine what they will work on for a period of 3 minutes at a time. They might roll a 3 and work on investigating factual information on the chosen topic. They might roll a 1 and work on identifying the specific goals, standards, or criteria for the session.

Encouraging rapid work and iteration while asking participants to be flexible are great skills to cultivate. Having a stage for idea incubation in this game is also important. Moments of pause can help ensure the ideas that are put forward are the most suitable. 

The Creativity Dice   #creativity   #problem solving   #thiagi   #issue analysis   Too much linear thinking is hazardous to creative problem solving. To be creative, you should approach the problem (or the opportunity) from different points of view. You should leave a thought hanging in mid-air and move to another. This skipping around prevents premature closure and lets your brain incubate one line of thought while you consciously pursue another.

11. Fishbone Analysis

Organizational or team challenges are rarely simple, and it’s important to remember that one problem can be an indication of something that goes deeper and may require further consideration to be solved.

Fishbone Analysis helps groups to dig deeper and understand the origins of a problem. It’s a great example of a root cause analysis method that is simple for everyone on a team to get their head around. 

Participants in this activity are asked to annotate a diagram of a fish, first adding the problem or issue to be worked on at the head of a fish before then brainstorming the root causes of the problem and adding them as bones on the fish. 

Using abstractions such as a diagram of a fish can really help a team break out of their regular thinking and develop a creative approach.

Fishbone Analysis   #problem solving   ##root cause analysis   #decision making   #online facilitation   A process to help identify and understand the origins of problems, issues or observations.

12. Problem Tree 

Encouraging visual thinking can be an essential part of many strategies. By simply reframing and clarifying problems, a group can move towards developing a problem solving model that works for them. 

In Problem Tree, groups are asked to first brainstorm a list of problems – these can be design problems, team problems or larger business problems – and then organize them into a hierarchy. The hierarchy could be from most important to least important or abstract to practical, though the key thing with problem solving games that involve this aspect is that your group has some way of managing and sorting all the issues that are raised.

Once you have a list of problems that need to be solved and have organized them accordingly, you’re then well-positioned for the next problem solving steps.

Problem tree   #define intentions   #create   #design   #issue analysis   A problem tree is a tool to clarify the hierarchy of problems addressed by the team within a design project; it represents high level problems or related sublevel problems.

13. SWOT Analysis

Chances are you’ve heard of the SWOT Analysis before. This problem-solving method focuses on identifying strengths, weaknesses, opportunities, and threats is a tried and tested method for both individuals and teams.

Start by creating a desired end state or outcome and bare this in mind – any process solving model is made more effective by knowing what you are moving towards. Create a quadrant made up of the four categories of a SWOT analysis and ask participants to generate ideas based on each of those quadrants.

Once you have those ideas assembled in their quadrants, cluster them together based on their affinity with other ideas. These clusters are then used to facilitate group conversations and move things forward. 

SWOT analysis   #gamestorming   #problem solving   #action   #meeting facilitation   The SWOT Analysis is a long-standing technique of looking at what we have, with respect to the desired end state, as well as what we could improve on. It gives us an opportunity to gauge approaching opportunities and dangers, and assess the seriousness of the conditions that affect our future. When we understand those conditions, we can influence what comes next.

14. Agreement-Certainty Matrix

Not every problem-solving approach is right for every challenge, and deciding on the right method for the challenge at hand is a key part of being an effective team.

The Agreement Certainty matrix helps teams align on the nature of the challenges facing them. By sorting problems from simple to chaotic, your team can understand what methods are suitable for each problem and what they can do to ensure effective results. 

If you are already using Liberating Structures techniques as part of your problem-solving strategy, the Agreement-Certainty Matrix can be an invaluable addition to your process. We’ve found it particularly if you are having issues with recurring problems in your organization and want to go deeper in understanding the root cause. 

Agreement-Certainty Matrix   #issue analysis   #liberating structures   #problem solving   You can help individuals or groups avoid the frequent mistake of trying to solve a problem with methods that are not adapted to the nature of their challenge. The combination of two questions makes it possible to easily sort challenges into four categories: simple, complicated, complex , and chaotic .  A problem is simple when it can be solved reliably with practices that are easy to duplicate.  It is complicated when experts are required to devise a sophisticated solution that will yield the desired results predictably.  A problem is complex when there are several valid ways to proceed but outcomes are not predictable in detail.  Chaotic is when the context is too turbulent to identify a path forward.  A loose analogy may be used to describe these differences: simple is like following a recipe, complicated like sending a rocket to the moon, complex like raising a child, and chaotic is like the game “Pin the Tail on the Donkey.”  The Liberating Structures Matching Matrix in Chapter 5 can be used as the first step to clarify the nature of a challenge and avoid the mismatches between problems and solutions that are frequently at the root of chronic, recurring problems.

Organizing and charting a team’s progress can be important in ensuring its success. SQUID (Sequential Question and Insight Diagram) is a great model that allows a team to effectively switch between giving questions and answers and develop the skills they need to stay on track throughout the process. 

Begin with two different colored sticky notes – one for questions and one for answers – and with your central topic (the head of the squid) on the board. Ask the group to first come up with a series of questions connected to their best guess of how to approach the topic. Ask the group to come up with answers to those questions, fix them to the board and connect them with a line. After some discussion, go back to question mode by responding to the generated answers or other points on the board.

It’s rewarding to see a diagram grow throughout the exercise, and a completed SQUID can provide a visual resource for future effort and as an example for other teams.

SQUID   #gamestorming   #project planning   #issue analysis   #problem solving   When exploring an information space, it’s important for a group to know where they are at any given time. By using SQUID, a group charts out the territory as they go and can navigate accordingly. SQUID stands for Sequential Question and Insight Diagram.

16. Speed Boat

To continue with our nautical theme, Speed Boat is a short and sweet activity that can help a team quickly identify what employees, clients or service users might have a problem with and analyze what might be standing in the way of achieving a solution.

Methods that allow for a group to make observations, have insights and obtain those eureka moments quickly are invaluable when trying to solve complex problems.

In Speed Boat, the approach is to first consider what anchors and challenges might be holding an organization (or boat) back. Bonus points if you are able to identify any sharks in the water and develop ideas that can also deal with competitors!   

Speed Boat   #gamestorming   #problem solving   #action   Speedboat is a short and sweet way to identify what your employees or clients don’t like about your product/service or what’s standing in the way of a desired goal.

17. The Journalistic Six

Some of the most effective ways of solving problems is by encouraging teams to be more inclusive and diverse in their thinking.

Based on the six key questions journalism students are taught to answer in articles and news stories, The Journalistic Six helps create teams to see the whole picture. By using who, what, when, where, why, and how to facilitate the conversation and encourage creative thinking, your team can make sure that the problem identification and problem analysis stages of the are covered exhaustively and thoughtfully. Reporter’s notebook and dictaphone optional.

The Journalistic Six – Who What When Where Why How   #idea generation   #issue analysis   #problem solving   #online   #creative thinking   #remote-friendly   A questioning method for generating, explaining, investigating ideas.

18. LEGO Challenge

Now for an activity that is a little out of the (toy) box. LEGO Serious Play is a facilitation methodology that can be used to improve creative thinking and problem-solving skills. 

The LEGO Challenge includes giving each member of the team an assignment that is hidden from the rest of the group while they create a structure without speaking.

What the LEGO challenge brings to the table is a fun working example of working with stakeholders who might not be on the same page to solve problems. Also, it’s LEGO! Who doesn’t love LEGO! 

LEGO Challenge   #hyperisland   #team   A team-building activity in which groups must work together to build a structure out of LEGO, but each individual has a secret “assignment” which makes the collaborative process more challenging. It emphasizes group communication, leadership dynamics, conflict, cooperation, patience and problem solving strategy.

19. What, So What, Now What?

If not carefully managed, the problem identification and problem analysis stages of the problem-solving process can actually create more problems and misunderstandings.

The What, So What, Now What? problem-solving activity is designed to help collect insights and move forward while also eliminating the possibility of disagreement when it comes to identifying, clarifying, and analyzing organizational or work problems. 

Facilitation is all about bringing groups together so that might work on a shared goal and the best problem-solving strategies ensure that teams are aligned in purpose, if not initially in opinion or insight.

Throughout the three steps of this game, you give everyone on a team to reflect on a problem by asking what happened, why it is important, and what actions should then be taken. 

This can be a great activity for bringing our individual perceptions about a problem or challenge and contextualizing it in a larger group setting. This is one of the most important problem-solving skills you can bring to your organization.

W³ – What, So What, Now What?   #issue analysis   #innovation   #liberating structures   You can help groups reflect on a shared experience in a way that builds understanding and spurs coordinated action while avoiding unproductive conflict. It is possible for every voice to be heard while simultaneously sifting for insights and shaping new direction. Progressing in stages makes this practical—from collecting facts about What Happened to making sense of these facts with So What and finally to what actions logically follow with Now What . The shared progression eliminates most of the misunderstandings that otherwise fuel disagreements about what to do. Voila!

20. Journalists  

Problem analysis can be one of the most important and decisive stages of all problem-solving tools. Sometimes, a team can become bogged down in the details and are unable to move forward.

Journalists is an activity that can avoid a group from getting stuck in the problem identification or problem analysis stages of the process.

In Journalists, the group is invited to draft the front page of a fictional newspaper and figure out what stories deserve to be on the cover and what headlines those stories will have. By reframing how your problems and challenges are approached, you can help a team move productively through the process and be better prepared for the steps to follow.

Journalists   #vision   #big picture   #issue analysis   #remote-friendly   This is an exercise to use when the group gets stuck in details and struggles to see the big picture. Also good for defining a vision.

Problem-solving techniques for developing solutions 

The success of any problem-solving process can be measured by the solutions it produces. After you’ve defined the issue, explored existing ideas, and ideated, it’s time to narrow down to the correct solution.

Use these problem-solving techniques when you want to help your team find consensus, compare possible solutions, and move towards taking action on a particular problem.

• Improved Solutions
• Four-Step Sketch
• 15% Solutions
• How-Now-Wow matrix
• Impact Effort Matrix

21. Mindspin  

Brainstorming is part of the bread and butter of the problem-solving process and all problem-solving strategies benefit from getting ideas out and challenging a team to generate solutions quickly. 

With Mindspin, participants are encouraged not only to generate ideas but to do so under time constraints and by slamming down cards and passing them on. By doing multiple rounds, your team can begin with a free generation of possible solutions before moving on to developing those solutions and encouraging further ideation. 

This is one of our favorite problem-solving activities and can be great for keeping the energy up throughout the workshop. Remember the importance of helping people become engaged in the process – energizing problem-solving techniques like Mindspin can help ensure your team stays engaged and happy, even when the problems they’re coming together to solve are complex. 

MindSpin   #teampedia   #idea generation   #problem solving   #action   A fast and loud method to enhance brainstorming within a team. Since this activity has more than round ideas that are repetitive can be ruled out leaving more creative and innovative answers to the challenge.

22. Improved Solutions

After a team has successfully identified a problem and come up with a few solutions, it can be tempting to call the work of the problem-solving process complete. That said, the first solution is not necessarily the best, and by including a further review and reflection activity into your problem-solving model, you can ensure your group reaches the best possible result. 

One of a number of problem-solving games from Thiagi Group, Improved Solutions helps you go the extra mile and develop suggested solutions with close consideration and peer review. By supporting the discussion of several problems at once and by shifting team roles throughout, this problem-solving technique is a dynamic way of finding the best solution. 

Improved Solutions   #creativity   #thiagi   #problem solving   #action   #team   You can improve any solution by objectively reviewing its strengths and weaknesses and making suitable adjustments. In this creativity framegame, you improve the solutions to several problems. To maintain objective detachment, you deal with a different problem during each of six rounds and assume different roles (problem owner, consultant, basher, booster, enhancer, and evaluator) during each round. At the conclusion of the activity, each player ends up with two solutions to her problem.

23. Four Step Sketch

Creative thinking and visual ideation does not need to be confined to the opening stages of your problem-solving strategies. Exercises that include sketching and prototyping on paper can be effective at the solution finding and development stage of the process, and can be great for keeping a team engaged. 

By going from simple notes to a crazy 8s round that involves rapidly sketching 8 variations on their ideas before then producing a final solution sketch, the group is able to iterate quickly and visually. Problem-solving techniques like Four-Step Sketch are great if you have a group of different thinkers and want to change things up from a more textual or discussion-based approach.

Four-Step Sketch   #design sprint   #innovation   #idea generation   #remote-friendly   The four-step sketch is an exercise that helps people to create well-formed concepts through a structured process that includes: Review key information Start design work on paper,  Consider multiple variations , Create a detailed solution . This exercise is preceded by a set of other activities allowing the group to clarify the challenge they want to solve. See how the Four Step Sketch exercise fits into a Design Sprint

24. 15% Solutions

Some problems are simpler than others and with the right problem-solving activities, you can empower people to take immediate actions that can help create organizational change. 

Part of the liberating structures toolkit, 15% solutions is a problem-solving technique that focuses on finding and implementing solutions quickly. A process of iterating and making small changes quickly can help generate momentum and an appetite for solving complex problems.

Problem-solving strategies can live and die on whether people are onboard. Getting some quick wins is a great way of getting people behind the process.   

It can be extremely empowering for a team to realize that problem-solving techniques can be deployed quickly and easily and delineate between things they can positively impact and those things they cannot change. 

15% Solutions   #action   #liberating structures   #remote-friendly   You can reveal the actions, however small, that everyone can do immediately. At a minimum, these will create momentum, and that may make a BIG difference.  15% Solutions show that there is no reason to wait around, feel powerless, or fearful. They help people pick it up a level. They get individuals and the group to focus on what is within their discretion instead of what they cannot change.  With a very simple question, you can flip the conversation to what can be done and find solutions to big problems that are often distributed widely in places not known in advance. Shifting a few grains of sand may trigger a landslide and change the whole landscape.

25. How-Now-Wow Matrix

The problem-solving process is often creative, as complex problems usually require a change of thinking and creative response in order to find the best solutions. While it’s common for the first stages to encourage creative thinking, groups can often gravitate to familiar solutions when it comes to the end of the process. 

When selecting solutions, you don’t want to lose your creative energy! The How-Now-Wow Matrix from Gamestorming is a great problem-solving activity that enables a group to stay creative and think out of the box when it comes to selecting the right solution for a given problem.

Problem-solving techniques that encourage creative thinking and the ideation and selection of new solutions can be the most effective in organisational change. Give the How-Now-Wow Matrix a go, and not just for how pleasant it is to say out loud. 

How-Now-Wow Matrix   #gamestorming   #idea generation   #remote-friendly   When people want to develop new ideas, they most often think out of the box in the brainstorming or divergent phase. However, when it comes to convergence, people often end up picking ideas that are most familiar to them. This is called a ‘creative paradox’ or a ‘creadox’. The How-Now-Wow matrix is an idea selection tool that breaks the creadox by forcing people to weigh each idea on 2 parameters.

26. Impact and Effort Matrix

All problem-solving techniques hope to not only find solutions to a given problem or challenge but to find the best solution. When it comes to finding a solution, groups are invited to put on their decision-making hats and really think about how a proposed idea would work in practice. 

The Impact and Effort Matrix is one of the problem-solving techniques that fall into this camp, empowering participants to first generate ideas and then categorize them into a 2×2 matrix based on impact and effort.

Activities that invite critical thinking while remaining simple are invaluable. Use the Impact and Effort Matrix to move from ideation and towards evaluating potential solutions before then committing to them. 

Impact and Effort Matrix   #gamestorming   #decision making   #action   #remote-friendly   In this decision-making exercise, possible actions are mapped based on two factors: effort required to implement and potential impact. Categorizing ideas along these lines is a useful technique in decision making, as it obliges contributors to balance and evaluate suggested actions before committing to them.

27. Dotmocracy

If you’ve followed each of the problem-solving steps with your group successfully, you should move towards the end of your process with heaps of possible solutions developed with a specific problem in mind. But how do you help a group go from ideation to putting a solution into action? 

Dotmocracy – or Dot Voting -is a tried and tested method of helping a team in the problem-solving process make decisions and put actions in place with a degree of oversight and consensus. 

One of the problem-solving techniques that should be in every facilitator’s toolbox, Dot Voting is fast and effective and can help identify the most popular and best solutions and help bring a group to a decision effectively. 

Dotmocracy   #action   #decision making   #group prioritization   #hyperisland   #remote-friendly   Dotmocracy is a simple method for group prioritization or decision-making. It is not an activity on its own, but a method to use in processes where prioritization or decision-making is the aim. The method supports a group to quickly see which options are most popular or relevant. The options or ideas are written on post-its and stuck up on a wall for the whole group to see. Each person votes for the options they think are the strongest, and that information is used to inform a decision.

All facilitators know that warm-ups and icebreakers are useful for any workshop or group process. Problem-solving workshops are no different.

Use these problem-solving techniques to warm up a group and prepare them for the rest of the process. Activating your group by tapping into some of the top problem-solving skills can be one of the best ways to see great outcomes from your session.

• Check-in/Check-out
• Doodling Together
• Show and Tell
• Constellations
• Draw a Tree

28. Check-in / Check-out

Solid processes are planned from beginning to end, and the best facilitators know that setting the tone and establishing a safe, open environment can be integral to a successful problem-solving process.

Check-in / Check-out is a great way to begin and/or bookend a problem-solving workshop. Checking in to a session emphasizes that everyone will be seen, heard, and expected to contribute. 

If you are running a series of meetings, setting a consistent pattern of checking in and checking out can really help your team get into a groove. We recommend this opening-closing activity for small to medium-sized groups though it can work with large groups if they’re disciplined!

Check-in / Check-out   #team   #opening   #closing   #hyperisland   #remote-friendly   Either checking-in or checking-out is a simple way for a team to open or close a process, symbolically and in a collaborative way. Checking-in/out invites each member in a group to be present, seen and heard, and to express a reflection or a feeling. Checking-in emphasizes presence, focus and group commitment; checking-out emphasizes reflection and symbolic closure.

29. Doodling Together  

Thinking creatively and not being afraid to make suggestions are important problem-solving skills for any group or team, and warming up by encouraging these behaviors is a great way to start. 

Doodling Together is one of our favorite creative ice breaker games – it’s quick, effective, and fun and can make all following problem-solving steps easier by encouraging a group to collaborate visually. By passing cards and adding additional items as they go, the workshop group gets into a groove of co-creation and idea development that is crucial to finding solutions to problems. 

Doodling Together   #collaboration   #creativity   #teamwork   #fun   #team   #visual methods   #energiser   #icebreaker   #remote-friendly   Create wild, weird and often funny postcards together & establish a group’s creative confidence.

30. Show and Tell

You might remember some version of Show and Tell from being a kid in school and it’s a great problem-solving activity to kick off a session.

Asking participants to prepare a little something before a workshop by bringing an object for show and tell can help them warm up before the session has even begun! Games that include a physical object can also help encourage early engagement before moving onto more big-picture thinking.

By asking your participants to tell stories about why they chose to bring a particular item to the group, you can help teams see things from new perspectives and see both differences and similarities in the way they approach a topic. Great groundwork for approaching a problem-solving process as a team! 

Show and Tell   #gamestorming   #action   #opening   #meeting facilitation   Show and Tell taps into the power of metaphors to reveal players’ underlying assumptions and associations around a topic The aim of the game is to get a deeper understanding of stakeholders’ perspectives on anything—a new project, an organizational restructuring, a shift in the company’s vision or team dynamic.

31. Constellations

Who doesn’t love stars? Constellations is a great warm-up activity for any workshop as it gets people up off their feet, energized, and ready to engage in new ways with established topics. It’s also great for showing existing beliefs, biases, and patterns that can come into play as part of your session.

Using warm-up games that help build trust and connection while also allowing for non-verbal responses can be great for easing people into the problem-solving process and encouraging engagement from everyone in the group. Constellations is great in large spaces that allow for movement and is definitely a practical exercise to allow the group to see patterns that are otherwise invisible. 

Constellations   #trust   #connection   #opening   #coaching   #patterns   #system   Individuals express their response to a statement or idea by standing closer or further from a central object. Used with teams to reveal system, hidden patterns, perspectives.

32. Draw a Tree

Problem-solving games that help raise group awareness through a central, unifying metaphor can be effective ways to warm-up a group in any problem-solving model.

Draw a Tree is a simple warm-up activity you can use in any group and which can provide a quick jolt of energy. Start by asking your participants to draw a tree in just 45 seconds – they can choose whether it will be abstract or realistic. 

Once the timer is up, ask the group how many people included the roots of the tree and use this as a means to discuss how we can ignore important parts of any system simply because they are not visible.

All problem-solving strategies are made more effective by thinking of problems critically and by exposing things that may not normally come to light. Warm-up games like Draw a Tree are great in that they quickly demonstrate some key problem-solving skills in an accessible and effective way.

Draw a Tree   #thiagi   #opening   #perspectives   #remote-friendly   With this game you can raise awarness about being more mindful, and aware of the environment we live in.

Each step of the problem-solving workshop benefits from an intelligent deployment of activities, games, and techniques. Bringing your session to an effective close helps ensure that solutions are followed through on and that you also celebrate what has been achieved.

Here are some problem-solving activities you can use to effectively close a workshop or meeting and ensure the great work you’ve done can continue afterward.

• One Breath Feedback
• Who What When Matrix
• Response Cards

How do I conclude a problem-solving process?

All good things must come to an end. With the bulk of the work done, it can be tempting to conclude your workshop swiftly and without a moment to debrief and align. This can be problematic in that it doesn’t allow your team to fully process the results or reflect on the process.

At the end of an effective session, your team will have gone through a process that, while productive, can be exhausting. It’s important to give your group a moment to take a breath, ensure that they are clear on future actions, and provide short feedback before leaving the space. 

The primary purpose of any problem-solving method is to generate solutions and then implement them. Be sure to take the opportunity to ensure everyone is aligned and ready to effectively implement the solutions you produced in the workshop.

Remember that every process can be improved and by giving a short moment to collect feedback in the session, you can further refine your problem-solving methods and see further success in the future too.

33. One Breath Feedback

Maintaining attention and focus during the closing stages of a problem-solving workshop can be tricky and so being concise when giving feedback can be important. It’s easy to incur “death by feedback” should some team members go on for too long sharing their perspectives in a quick feedback round. 

One Breath Feedback is a great closing activity for workshops. You give everyone an opportunity to provide feedback on what they’ve done but only in the space of a single breath. This keeps feedback short and to the point and means that everyone is encouraged to provide the most important piece of feedback to them. 

One breath feedback   #closing   #feedback   #action   This is a feedback round in just one breath that excels in maintaining attention: each participants is able to speak during just one breath … for most people that’s around 20 to 25 seconds … unless of course you’ve been a deep sea diver in which case you’ll be able to do it for longer.

34. Who What When Matrix 

Matrices feature as part of many effective problem-solving strategies and with good reason. They are easily recognizable, simple to use, and generate results.

The Who What When Matrix is a great tool to use when closing your problem-solving session by attributing a who, what and when to the actions and solutions you have decided upon. The resulting matrix is a simple, easy-to-follow way of ensuring your team can move forward. 

Great solutions can’t be enacted without action and ownership. Your problem-solving process should include a stage for allocating tasks to individuals or teams and creating a realistic timeframe for those solutions to be implemented or checked out. Use this method to keep the solution implementation process clear and simple for all involved. 

Who/What/When Matrix   #gamestorming   #action   #project planning   With Who/What/When matrix, you can connect people with clear actions they have defined and have committed to.

35. Response cards

Group discussion can comprise the bulk of most problem-solving activities and by the end of the process, you might find that your team is talked out! 

Providing a means for your team to give feedback with short written notes can ensure everyone is head and can contribute without the need to stand up and talk. Depending on the needs of the group, giving an alternative can help ensure everyone can contribute to your problem-solving model in the way that makes the most sense for them.

Response Cards is a great way to close a workshop if you are looking for a gentle warm-down and want to get some swift discussion around some of the feedback that is raised. 

Response Cards   #debriefing   #closing   #structured sharing   #questions and answers   #thiagi   #action   It can be hard to involve everyone during a closing of a session. Some might stay in the background or get unheard because of louder participants. However, with the use of Response Cards, everyone will be involved in providing feedback or clarify questions at the end of a session.

Save time and effort discovering the right solutions

A structured problem solving process is a surefire way of solving tough problems, discovering creative solutions and driving organizational change. But how can you design for successful outcomes?

With SessionLab, it’s easy to design engaging workshops that deliver results. Drag, drop and reorder blocks  to build your agenda. When you make changes or update your agenda, your session  timing   adjusts automatically , saving you time on manual adjustments.

Collaborating with stakeholders or clients? Share your agenda with a single click and collaborate in real-time. No more sending documents back and forth over email.

Explore  how to use SessionLab  to design effective problem solving workshops or  watch this five minute video  to see the planner in action!

Over to you

The problem-solving process can often be as complicated and multifaceted as the problems they are set-up to solve. With the right problem-solving techniques and a mix of creative exercises designed to guide discussion and generate purposeful ideas, we hope we’ve given you the tools to find the best solutions as simply and easily as possible.

Is there a problem-solving technique that you are missing here? Do you have a favorite activity or method you use when facilitating? Let us know in the comments below, we’d love to hear from you! 

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

Leave a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Going from a mere idea to a workshop that delivers results for your clients can feel like a daunting task. In this piece, we will shine a light on all the work behind the scenes and help you learn how to plan a workshop from start to finish. On a good day, facilitation can feel like effortless magic, but that is mostly the result of backstage work, foresight, and a lot of careful planning. Read on to learn a step-by-step approach to breaking the process of planning a workshop into small, manageable chunks.  The flow starts with the first meeting with a client to define the purposes of a workshop.…

How does learning work? A clever 9-year-old once told me: “I know I am learning something new when I am surprised.” The science of adult learning tells us that, in order to learn new skills (which, unsurprisingly, is harder for adults to do than kids) grown-ups need to first get into a specific headspace.  In a business, this approach is often employed in a training session where employees learn new skills or work on professional development. But how do you ensure your training is effective? In this guide, we'll explore how to create an effective training session plan and run engaging training sessions. As team leader, project manager, or consultant,…

Effective online tools are a necessity for smooth and engaging virtual workshops and meetings. But how do you choose the right ones? Do you sometimes feel that the good old pen and paper or MS Office toolkit and email leaves you struggling to stay on top of managing and delivering your workshop? Fortunately, there are plenty of online tools to make your life easier when you need to facilitate a meeting and lead workshops. In this post, we’ll share our favorite online tools you can use to make your job as a facilitator easier. In fact, there are plenty of free online workshop tools and meeting facilitation software you can…

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

• Project Management

Home » Free Resources » »

What Is Problem Solving in Project Management? Here’s Everything You Need to Know

• Written by Contributing Writer
• Updated on August 4, 2023

In project management , problem-solving is a crucial and necessary skill. Whether you have failed to consider every possible factor impacting a project, a problem arises through no fault of your own, or conditions change that create issues, problems must be addressed promptly to keep projects on track.

In this article, we will define problem-solving and how it impacts projects, provide real-world examples of problem-solving, and give you a structured, step-by-step process to solve problems. We’ll also show you how earning a project management certification can help you gain practical experience in problem-solving methods.

What Is Problem-Solving?

Problem-solving is a process to identify roadblocks or defects that arise during a project. A structured system to define problems, identify root causes, brainstorm and test solutions, and monitor results can affect change to improve performance and overcome challenges.

Effective problem-solving enables teams to deal with uncertainties or gaps in planning to minimize the impact on outcomes.

The Importance of Problem-Solving in Project Management

During a project and operation, problems can arise at any time. You may find that your planning before launching a product, for example, did not consider all the factors that impact results. You may find that you were too optimistic about project timelines, performance, or workforce. Or, as many of us discovered over the past few years, supply chain disruption may make even the best project plans obsolete.

Regardless, your job is identifying, solving, and overcoming these problems. Project managers must be skilled in leading team members through a structured approach to resolving problems.

Proactive problem-solving requires careful consideration of all the variables in a project, including preparation to:

• Achieve project objectives
• Address obstacles before they arise
• Manage project risks and contingency plans
• Manage communication and collaboration
• Provide a framework for time and cost management
• Provide a pathway for continuous improvement

Also Read: 10 Tips on How to Increase Productivity in the Workplace

Problem-Solving Steps in Project Management

While the process you choose to solve problems may vary, here is a seven-step framework many project managers use. This problem-solving method combines primary and secondary problem-solving steps.

#1. Define the Problem

• Gather data and information from key stakeholders, team members, and project documentation. Include any relevant reporting or data analysis
• Itemized key details, such as a description of the problem, timelines, outcomes, and impact
• Frame the issue as a problem statement

A good example of a problem statement might be: An unexpected demand spike has exceeded our current production capacity. How can we still meet customer deadlines for delivery?

#2. Analyze Root Causes

• Break down issues into smaller components to diagnose bottlenecks or problems
• Identify the organizational, mechanical, environmental, or operational factors that contribute
• Distinguish between one-time issues vs. systematic, ongoing areas that need improvement

When analyzing root causes, it’s common to find multiple factors contributing to a problem. As such, it is essential to prioritize issues that have the most significant impact on outcomes.

#3. Brainstorm Potential Solutions

• Holding specific sessions focused on brainstorming ideas to resolve root causes
• Build on ideas or suggest combinations or iterations
• Categorize solutions by types, such as process or input changes, adding additional resources, outsourcing, etc.)

In brainstorming, you should refrain from immediately analyzing suggestions to keep ideas coming.

#4. Evaluate Potential Solutions

• Reframe the problem and concern for team members, providing a framework for evaluation such as cost, timing, and feasibility
• With ideas in hand, it is time to evaluate potential solutions. Project managers often employ strategies such as weighted scoring models to rank ideas.
• Consider the pros and cons in relation to project objectives

As you narrow the list, getting additional insight from subject matter experts to evaluate real-world viability is helpful. For example, if you are proposing a process change in operating a machine, get feedback from skilled operators before implementing changes.

#5. Decide on a Plan of Action

• Make a decision on which course of action you want to pursue and make sure the solution aligns with your organizational goals
• Create an action plan to implement the changes, including key milestones
• Assign project ownership, deadlines, resources, and budgets

Defining what outcomes you need to achieve to declare success is also essential. Are you looking for incremental change or significant improvements, and what timeline are you establishing for measurement?

#6. Implement the Action Plan

• Communicate the plan with key stakeholders
• Provide any training associated with the changes
• Allocate resources necessary for implementation

As part of the action plan, you will also want to detail the measures and monitoring you will put in place to assess process outcomes.

#7. Monitor and Track Results

• Track solution performance against the action plan and key milestones
• Solicit feedback from the project team on problem-solving effectiveness
• Ensure the solution resolves the root cause, creating the desired results without negatively impacting other areas of the operation

You should refine results or start the process over again to increase performance. For example, you may address the root cause but find a need for secondary problem-solving in project management, focusing on other factors.

These problem-solving steps are used repeatedly in lean management and Six Sigma strategies for continuous improvement.

Also Read: 5 Project Management Steps You Need to Know

How Project Management Tools Can Help You in Problem-Solving

Project management software can guide teams through problem-solving, acting as a central repository to provide visibility into the stages of a project.

The best project management software will include the following:

• Issue tracking to capture problems as they arise
• Chat and real-time collaboration for discussion and brainstorming
• Templates for analysis, such as fishbone diagrams
• Action plans, assigning tasks, ownership, and accountability
• Dashboards for updates to monitor solutions
• Reporting on open issues, mitigation, and resolution

Examples of Problem-Solving

Here are some examples of the problem-solving process demonstrating how team members can work through the process to achieve results.

Sign-ups for a New Software Solution Were Well Below First-Month Targets

After analyzing the data, a project team identifies the root cause as inefficient onboarding and account configurations. They then brainstorm solutions. Ideas include re-architecting the software, simplifying onboarding steps, improving the initial training and onboarding process, or applying additional resources to guide customers through the configuration process.

After weighing alternatives, the company invests in streamlining onboarding and developing software to automate configuration.

A Project Was at Risk of Missing a Hard Deadline Due to Supplier Delays

In this case, you already know the root cause: Your supplier cannot deliver the necessary components to complete the project on time. Brainstorming solutions include finding alternative sources for components, considering project redesigns to use different (available) components, negotiating price reductions with customers due to late delivery, or adjusting the scope to complete projects without this component.

After evaluating potential solutions, the project manager might negotiate rush delivery with the original vendor. While this might be more expensive, it enables the business to meet customer deadlines. At the same time, project schedules might be adjusted to account for later-than-expected part delivery.

A Construction Project Is Falling Behind Due to Inclement Weather

Despite months of planning, a major construction project has fallen behind schedule due to bad weather, preventing concrete and masonry work. The problem-solving team brainstorms the problem and evaluates solutions, such as constructing temporary protection from the elements, heating concrete to accelerate curing, and bringing on additional crews once the weather clears.

The project team might decide to focus on tasks not impacted by weather earlier in the process than expected to postpone exterior work until the weather clears.

Also Read: Understanding KPIs in Project Management

Improve Your Problem-Solving and Project Management Skills

This project management course delivered by Simpliearn, in collaboration wiht the University of Massachusetts, can boost your career journey as a project manager. This 24-week online bootcamp aligns with Project Management Institute (PMI) practices, the Project Management Professional (PMP®) certification, and IASSC-Lean Six Sigma.

This program teaches skills such as:

• Agile management
• Customer experience design
• Design thinking
• Digital transformation
• Lean Six Sigma Green Belt

You might also like to read:

5 Essential Project Management Steps You Need to Know

Project Management Frameworks and Methodologies Explained

13 Key Project Management Principles and How to Use Them

Project Management Phases: A Full Breakdown

How To Develop a Great Project Management Plan in 2023

Leave a Comment Cancel Reply

Your email address will not be published. Required fields are marked *

Recommended Articles

What is Project Resource Management? Everything You Need to Know

If you’re asking, “What is project resource management,” and want to learn the tools, techniques, and best practices involved, our comprehensive guide covers everything you need.

Best Apps for Project Management You Should Know in 2024

Every project needs a manager, especially in today’s fast-paced digital world. And every project manager needs tools to manage projects. Learn about some of the best project management apps you can choose from today in this blog.

20 Best Practices in Project Management [2024 Guide]

Explore our guide to the top best practices in project management. Strengthen your foundation and take your career to new heights.

How to Measure Project Success? A 2024 Guide

One person’s definition of success can vary wildly from another’s. That’s why project managers need definitive ways to measure project success. This article will share tips, best practices, and methods to determine whether you are hitting the mark.

Remote Project Management: How to Manage Remote Teams Effectively

Remote working became a harsh reality during the COVID-19 pandemic. Yet, many employers and their employees adapted to it quickly and still prefer it, making remote project management an essential skill for professionals.

What are Project Management Skills? Here are Top Skills You should Know in 2024

Here are the top project management skills you will need to master project management in 2024. This article will help you get started with both hard and soft skills.

Project Management Bootcamp

Learning Format

Online Bootcamp

Program benefits.

• 25 in-demand tools covered
• Aligned with PMI-PMP® and IASSC-Lean Six Sigma
• Masterclasses from top faculty of UMass Amherst
• UMass Amherst Alumni Association membership

Team Dynamics: Problem-Solving and Decision Making

• Teamwork and Team Leadership Table of Contents
• Fostering Communication & Promoting Cooperation
• Problem-Solving and Decision Making
• Handling Conflict
• Dealing with Power and Influence

1. Overview

• Different stages of team development call for different problem solving methods
• Problem solving requires the use of a systematic process
• The appropriate decision making method is determined by the amount of time available for the decision and the impact of the decision
• Effective decision making requires the use of smart techniques

2. Problem Solving in Team Development Stages

3. General Problem Solving Steps

• Defining the problem : phrase problem as probing questions to encourage explorative thinking; make explicit goal statement
• Establish criteria for evaluating the solution : identify characteristics of a satisfactory solution; distinguish requirements from desires
• Analyzing the problem : discover the root cause and extent of the problem
• Considering alternate solutions : brainstorm to generate many ideas before judging any of them
• Evaluate alternate solutions : use ranking-weighting matrix; check for issues/disagreement
• Deciding on a solution :  choose best answer to the problem from among all possible solutions
• Develop action plan : make team assignments with milestones(don’t underestimate time)
• Implementing the action plan : check for consistency with requirements identified in step 2
• Following up on the solution :  check up on the implementation and make necessary adjustments
• Evaluate outcomes and process :  review performance, process, and personal aspects of the solution

4. Decision Making Method Based on Time and Impact

5. Smart Decision Making is Enabled By. . .

• Modeling an open mind and asking for candid opinions
• What elements would you choose to change?
• What changes would you make to solve …?  
• Aligning rewards to team successes to ensure that individuals share what they know
• Ensuring that team members are aware of relevant roles and unique information required for team success
• Charging some team members to assume a position that opposes the team’s preference
• Creating an alternate team that attempts to find errors and weaknesses in the solution
• Using successive rounds of blind voting interspersed with discussions

6. Additional Readings

• Hartnett, T. (n.d). Consensus decision making. Retrieved from http://www.consensusdecisionmaking.org/
• UMass|Dartmouth (n.d.) 7 steps to effective decision making . Retrieved from https://www.umassd.edu/media/u massdartmouth/fycm/decision_ma king_process.pdf
• Sunstein, C.R. (2014).  Making dumb groups smarter.  Harvard Business Review, 92(12), 90-98. 
• << Previous: Fostering Communication & Promoting Cooperation
• Next: Handling Conflict >>

• Last Updated: Jan 12, 2023 10:00 AM
• URL: https://guides.himmelfarb.gwu.edu/teamdynamics

• Himmelfarb Intranet
• Privacy Notice
• Terms of Use
• GW is committed to digital accessibility. If you experience a barrier that affects your ability to access content on this page, let us know via the Accessibility Feedback Form .
• Himmelfarb Health Sciences Library
• 2300 Eye St., NW, Washington, DC 20037
• Phone: (202) 994-2850
• [email protected]
• https://himmelfarb.gwu.edu

Problem management is the discipline of proactively and reactively identifying IT issues and solutions to minimize any impact on an IT team’s ability to deliver services to end users.

Issues within IT services are called incidents and problems, which differ based on their frequency, impact, and solutions. In general, multiple recurring incidents are considered problems that are likely to continue if left unaddressed.

IT services include a complex system of interdependent applications, software, hardware, IT infrastructure and other technologies. Service disruptions can disrupt an organization’s goal of continual service improvement and create serious reputational and financial issues for an organization, so their IT teams need to prioritize solving problems efficiently and effectively.

Proactive problem management is an important component of an organization’s approach. It is necessary to identify incidents and known problems and solve errors before they cascade into even larger ones.

Thankfully, organizations can utilize automation to help better manage the impact of incidents and problems, delivering improved services and more resilient applications to maximize uptime. This can lead to reduced costs and improved decision-making. Problem management can also use templates, such as ones focused on escalation information and problem reviews, to minimize human resources previously dedicated to key problem management tasks.

Organizations that are starting or improving a robust problem management process must also manage organizational change 1  (link resides outside ibm.com).    Robust problem management not only addresses incidents in an organization’s tech stack, but it also compels that organization to explore better ways to address incidents across their operations. Effective problem management requires rigorous categorization and prioritization, which subsequently allow the business to address its most pertinent problems. Ideally, an organization will focus on solving major incidents and major problems first and then transition to other incidents and problems that have a less pronounced impact on the business.

Learn how both APM and ARM can enable faster decisions and resource application.

Register for the guide to operationalize FinOps

Problem management is intended to prevent the incident from reoccurring by addressing the root cause. It is related to incident management in that if the incident has occurred several times, it should be diagnosed and investigated as a problem or known error.

Incident management without problem management only addresses symptoms and not the underlying cause, leading to similar incidents occurring in the future. Effective problem management identifies a permanent solution to problems, decreasing the number of incidents an organization will have to manage in the future.

Ultimately, problem management seeks to understand the problem lifecycle, identify the root cause of the problem and fix the conditions 2 (link resides outside ibm.com) that led to its creation.

A problem management team can either engage in reactive or proactive problem management, depending on what incidents they observed and what historical data they have. Reactive problem management is concerned with identifying the problem when it occurs and solving it as quickly as possible. The problem first must occur before organizations can apply reactive problem management.

Proactive problem management involves more investigative work on why a problem is happening and building a solution to prevent it from happening again. This type of problem management is more concerned with identifying the root cause, so the team can deploy a lasting solution that helps to avoid future problems.

Effective problem management is an important component of IT service management (ITSM). ITSM is how an organization ensures its IT services work in the way that its users and business need them to work. The goal of any organization’s ITSM strategy is to enable and maintain optimal deployment, operation and management of every single IT resource. Problem management is a core component of ITSM.

Organizations often utilize several native and open-source strategies for accomplishing ITSM, especially using the Information Technology Infrastructure Library (ITIL).

ITIL is the most widely adopted best-practices guidance framework for implementing and documenting ITSM. ITIL problem management uses ITIL processes to minimize the foundational work that needs to go into addressing any one problem. Many problems that organizations face such as server outages and cyber security issues have happened before to other organizations and can often have standardized responses. Therefore, ITSM approaches often incorporate ITIL to minimize the required amount of custom work to solve IT problems.

Most problem management approaches follow a similar pattern of assessment, logging, analysis, and solution. Each component is necessary to ultimately solve the problem.

• Problem detection: Automated systems or IT professionals identify recurring incidents that could be classified as a problem.
• Problem assessment: This involves the identification and categorization of an incident as a problem record or as an unrelated issue that is unlikely to occur again.
• Problem logging:  This involves the IT team logging the identified problem and tracking each occurrence. Problem management teams that encounter a problem log it, often via a self-service platform, to create a problem record, which is the comprehensive accounting for the problem, any related incidents, where and how the problem occurred, the root cause analysis and the solution. That creates a known error record that is entered in the known error database (KEDB). Advanced organizations will often combine their problem-management and knowledge-management approaches.
• Root cause analysis: The organization studies the underlying issues behind these problems and develops a roadmap to create a long-term solution.
• Solve the problem: When an IT team understands the problem and its root cause, it can address the problem (also known as problem control). This can involve a quick or protracted response depending on the severity or complexity of the problem.
• Error control: Finally, an organization that successfully diagnoses 3 (link resides outside ibm.com) and solves the problem through a work-around or a permanent resolution conducts error control for that problem.

Problem management requires a well-thought-out approach to ensure a team is allocating resources as efficiently as possible. Fortunately, problem management teams can utilize several levers to successfully address problems effectively and efficiently, getting to the root cause and creating solutions that can stop the problem from happening again.

The Pareto principle, also known as the Pareto 80:20 rule, states that about 80% of problems arise from 20% of the causes. Put another way, an overwhelming majority of problems stem from a few major causes. Therefore, problem solving for those 20% of issues will efficiently solve many of the organization’s problems. 

Problem management teams ask why something happened five times to help get to the root cause of any problem. Addressing user experience is a good example of the five whys in action.

• Why #1: Users report substandard experience because of long load times.
• Why #2: The website takes too long to load because of slow or overloaded servers.
• Why #3: Inefficient code causes the server to run slowly.
• Why #4: Poorly written database queries fetch unnecessary data leading to inefficient code.
• Why #5: Overly complicated queries with multiple nested subqueries, which ultimately contribute to the long load time.

Therefore, DevOps can solve the user experience problem by simplifying the query structure.

Root cause analysis (RCA) is the quality management process by which an organization searches for the root of a problem, issue or incident after it occurs. Organizations need to find the root cause of any problem to effectively solve the problem.

This is a tool (link resides outside ibm.com) for identifying the potential causes of a specific problem. It places the problem or effect at the “head” of the fish while using the “bones” to list potential causes organized by categories. It is like the five whys approach, but it adds more structure to the potential causes part of the cause analysis.

The goal of problem management is to minimize downtime, increase efficiency and improve service delivery. Below are some of the more impactful benefits of problem management.

• Enhanced security: Identifying the underlying cause of incidents is an important part of cyber risk management . Organizations that merely patch or resolve individual incidents without exploring their root cause may never discover significant security issues. Problem management teams can work in coordination with security professionals to understand which incidents and problems result from malicious actors or security flaws; both of which can create catastrophic problems for the organization.
• Increased customer satisfaction: Customers have certain expectations about their services and are unhappy whenever they don’t receive the services that they expected or paid for. Organizations that cannot deliver service reliably risk losing customers and will struggle to recruit new ones. Customers can tolerate occasional disruptions to service, like the inability to access a website or application due to a traffic overload or a chatbot malfunctioning. However, they will have less tolerance for sustained downtime or potential risks to cyber-criminal activity. Incidents that cascade into larger problems are likely to create unhappy customers. By prioritizing problem identification and problem resolution, organizations can minimize downtime and create happier customers.
• Improved knowledge management: Long-standing organizations have likely encountered many types of tech incidents and problems throughout their history. Organizations that prioritize knowledge management , the process of identifying, organizing, storing and disseminating information in a knowledge base within an organization, as part of their problem management approach have a better chance of avoiding repeat incidents. By capturing this information in a problem record, organizations can create known error databases so they can avoid future incidents and create permanent solutions.
• Increased productivity and employee satisfaction: Organizations have two options when pursuing problem management: reactive problem management or proactive problem management. IT employees join organizations to work on large problems and make meaningful differences. They do not want to repeatedly fix the same recurring problems without having the chance to work on higher-level opportunities. Organizations need sophisticated problem management to improve their IT operations and to keep employees happy and engaged.

Get the context you need to resolve incidents faster with IBM’s observability solution.

Optimize software usage and cost.

Learn how Artificial Intelligence for IT Operations (AIOps) uses data and machine learning to improve and automate IT service management.

Predict and prevent performance issues before they impact your business with application performance management.

Incidents are errors or complications in IT service that need remedying. Those that point to underlying or more complicated issues that require more comprehensive addressing are called problems.

IT operations and AIOps oversee and automate the management, delivery and support of IT services throughout an organization.

ITSM is how an organization ensures its IT services work the way users and the business need them to work.

Automate IT operations tasks, accelerate software delivery, and minimize IT risk with site reliability engineering.

IBM Instana provides real-time observability that everyone and anyone can use. It delivers quick time-to-value while verifying that your observability strategy can keep up with the dynamic complexity of current and future environments. From mobile to mainframe, Instana supports over 250 technologies and growing. 

1  Problem Management: A Practical Guide  (link resides outside ibm.com), Jim Bolton III and Buff Scott III, 2016 

2  What is root cause analysis? A proactive approach to change management  (link resides outside ibm.com), CIO, 6, May 2022

3  Problem Management: Frequently Asked Questions  (link resides outside ibm.com), University of Minnesota

.css-s5s6ko{margin-right:42px;color:#F5F4F3;}@media (max-width: 1120px){.css-s5s6ko{margin-right:12px;}} Join us: Learn how to build a trusted AI strategy to support your company's intelligent transformation, featuring Forrester .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;} Register now .css-1k6cidy{width:11px;height:11px;margin-left:8px;}.css-1k6cidy path{fill:currentColor;}

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

Problem management: 8 steps to better problem solving

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. 

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

Solve your tech overload with an intelligent transformation

9 steps to craft a successful go-to-market (GTM) strategy

Unmanaged business goals don’t work. Here’s what does.

How Asana uses work management to effectively manage goals

Jira Software

Project and issue tracking

Content collaboration

Jira Service Management

High-velocity ITSM

Visual project management

• View all products

Marketplace

Connect thousands of apps and integrations for all your Atlassian products

Developer Experience Platform

Jira Product Discovery

Prioritization and roadmapping

You might find helpful

Cloud Product Roadmap

Atlassian Migration Program

Work Management

Manage projects and align goals across all teams to achieve deliverables

IT Service Management

Enable dev, IT ops, and business teams to deliver great service at high velocity

Agile & DevOps

Run a world-class agile software organization from discovery to delivery and operations

BY TEAM SIZE

Small Business

BY TEAM FUNCTION

Software Development

BY INDUSTRY

Telecommunications

Professional Services

What's new

Atlassian together.

Get Atlassian work management products in one convenient package for enterprise teams.

Atlassian Trust & Security

Customer Case Studies

Atlassian University

Atlassian Playbook

Product Documentation

Developer Resources

Atlassian Community

Atlassian Support

Enterprise Services

Partner Support

Purchasing & Licensing

Work Life Blog

Support for Server products ends February 15, 2024

With end of support for our Server products fast approaching, create a winning plan for your Cloud migration with the Atlassian Migration Program.

Assess my options

Atlassian Presents: Unleash

Product updates, hands-on training, and technical demos – catch all that and more at our biggest agile & DevOps event.

• Atlassian.com

ITSM for high-velocity teams

Problem management roles and responsibilities.

Problem management is about more than just finding and fixing incidents. Real problem management lies in identifying and understanding the underlying causes of an incident as well as identifying the best method to eliminate that root cause. 

That’s why effective problem management efforts consist of teams operating under clear roles and responsibilities. Team members understand what the roles are, what each person is responsible for, and who is in each role during a problem investigation.

Here are a few of the most common problem management roles. It’s important to understand that not every team will operate with every role on this list. And these aren’t necessarily permanent roles. Instead, think of them as designations for a team that comes together to work on a particular problem.

Problem manager

The problem owner manages the overall process for a specific problem. They coordinate and direct all facets of the problem management effort, including bringing the right teams, tools, and information together. The problem manager may also delegate subtasks to other team members as they see fit.

Also called : Problem owner, Major Incident Manager

Process owner

The process owner is responsible for the overall health and success of the team’s problem management process. They oversee evolution and development of the process, as well as team member training and onboarding.

Also called : Process manager, process coordinator

Service owner

The service owner is responsible for defining ongoing operations and health of the service. This can include measuring and reporting on the value of changes, enhancements, planned downtime, training, documentation, and more.

Also called : Service leader, product manager

Service desk agent

Front-line support for your service desk . The service desk agent is often the first to notice and report an incident or problem. The agent is often also the first person to notice that several unique incidents all relate to a greater problem.

Also called : Agent, Service agent, Support Agent, Help desk agent, Service desk analyst

An individual familiar with the impacted service experiencing a problem or incident. Often a developer or engineer, the tech lead can dive into recent code changes to see what root causes may be contributing to the problem.

Also called : Technical lead, subject matter expert, on-call engineer, developer, software developer, Site Reliability Engineer (SRE)

Stakeholders

Stakeholders can be whoever needs high-level info on the problem but isn’t directly involved in the problem management process. This can be anyone from adjacent teams, to customers, and organizational leaders.

Also called : Customers, executive teams, vendors, end users, business teams

Atlassian's guide to agile ways of working with ITIL 4

ITIL 4 is here—and it’s more agile than ever. Learn tips to bring agility and collaboration into ITSM with Atlassian.

What is IT change management? Definition, benefits and types

IT Change Management minimizes risk while making changes to systems and services. Learn about the change management process, its importance, best practices

• 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

7 Skills You Need to Effectively Manage Teams

• 07 Jan 2020

To effectively manage a team, you need several key characteristics and skills. Without them, it can be difficult to rally your employees to work toward common goals and perform at their best—which can be disastrous for both your organization and career.

Whether you're an aspiring manager, newly appointed leader without a lot of experience, or seasoned executive who's had difficulty overseeing your team, developing these critical skills will prove crucial to your success.

Access your free e-book today.

Team Management Skills All Professionals Need

1. clear, effective communication.

As a manager, your goal is to help the members of your team complete tasks in a manner that is efficient, consistent, and aligns with the company’s overarching strategic goals. To accomplish this, you must clearly articulate what those strategic goals are—while also detailing the specific work and processes that will be required of your team to reach them.

By becoming a more effective communicator , you'll remove confusion among your team and ensure everyone is aligned and working toward the same goals.

2. Emotional Intelligence

Emotional intelligence refers to an individual’s ability to manage their emotions, as well as those of others.

A highly developed level of emotional intelligence is a hallmark of strong managers and leaders. Someone with a keen sense of self-awareness, empathy, and other social skills is someone who can motivate and influence others —an important quality for managers to exhibit.

3. Organization

You may be responsible for overseeing budgets and project timelines in addition to the daily tasks that members of your team perform. Juggling so many moving pieces and making necessary adjustments along the way requires a high degree of organization.

4. Ability to Delegate

However tempting it might be for you to micromanage members of your team, doing so can be detrimental to progress.

A good manager knows how to delegate work to others. This involves understanding who's best suited to complete a particular task. It also requires ensuring an employee has the required resources to be successful and feels empowered to make their own decisions.

5. Openness

Openness goes hand in hand with both emotional intelligence and effective communication.

It’s important that the members of your team feel comfortable approaching you when they have questions or concerns, or when they need clarification on what's expected of them. If your employees don't believe they can reach out to you, there’s a risk that problems or concerns will go unaddressed before it's too late to correct them.

6. Problem-Solving

No matter how well prepared, organized, or established a project or process is, every manager runs into problems. This could be in the form of a missed deadline or milestone. It could be budgetary in nature. It could involve an unforeseen breakdown in the supply chain.

Whatever the case, managers must be skilled problem-solvers. The ability to evaluate a challenge, think critically about potential solutions, and formulate a response are essential to anyone who's tasked with leading a team.

7. Decision-Making

Over the course of a day, managers might be responsible for making a number of decisions that impact their team or the project they're overseeing. Prioritizing tasks, allocating resources, delegating duties—each of these is a decision that falls to the manager.

Sometimes, a manager will need to make an authoritative decision to resolve an issue. Other times, decision-making might involve consensus building, wherein members of the team are invited to participate in the discussion and help guide the process. Ultimately, the manager is responsible for the outcome of the decision and, as such, must be comfortable with ensuing results.

How You Can Develop Your Team Management Skills

If you want to take your team management skills to the next level, there are several steps you can take to improve them. These include:

• Taking stock of your current skills. To chart a path for your professional development, you first need to understand where your management skills currently stand . What are your strengths? What are your weaknesses? Where are your greatest opportunities to turn development into career success? These insights will help you create a plan that's right for you.
• Setting goals for improvement and development. Once you have a sense of your current skills, you need to set goals for your development efforts. Which skills do you need to improve? How will you measure success? What is your timeframe? By setting specific and attainable goals, you give yourself something to work toward and increase your chances of success.
• Inviting feedback from your team. If you're unsure about your current abilities or where you should prioritize growth, consider turning to co-workers for feedback. This can be invaluable in helping you identify your strengths and weaknesses.
• Practicing your skills. Practice your skills both in and out of the office. If you find that a project has suffered setbacks due to poor communication, for example, identify the point of confusion and make a mental note to avoid this in the future. Or, if a project has become bogged down due to micromanaging, find methods to help you manage from a perch instead of down in the trenches.
• Pursuing professional development. Professional development can be a valuable asset in helping you reach your managerial potential. Signing up for a management training course can help you quickly develop your management skills, while pursuing mentorship opportunities can aid you throughout the trajectory of your career.

In Management Essentials , students are given the tools and opportunities they will need to improve their management skills and become more effective managers within their organization. Is Management Essentials the right HBS Online leadership and management course for you? Download the free flowchart to find out.

About the Author

Introduction to Problem Solving in Project Management

Definition and importance of problem solving.

Problem solving is the process of identifying and resolving issues or obstacles that arise during a project. It is a critical skill for project managers as it allows them to overcome challenges and ensure the successful completion of a project. Effective problem solving enables project managers to make informed decisions, mitigate risks, and maintain project timelines and budgets.

Role of Problem Solving in Project Management

Problem solving plays a central role in project management. It helps project managers identify and address issues that may hinder project progress. By actively solving problems, project managers can minimize the impact of obstacles on project outcomes and ensure that the project stays on track.

Benefits of Effective Problem Solving

Effective problem solving in project management offers several benefits. It improves project efficiency by eliminating roadblocks and streamlining processes. It enhances team collaboration and communication as team members work together to find solutions. It also boosts stakeholder satisfaction by addressing their concerns and delivering successful project outcomes.

Understanding the Problem

Identifying and defining the problem.

In order to solve a problem, project managers must first identify and define it clearly. This involves gathering relevant information and data related to the problem. By understanding the problem statement, project managers can analyze its root causes and develop appropriate solutions.

1. Gathering Information and Data

Project managers should gather all available information and data related to the problem. This may include project documentation, stakeholder feedback, and historical data. By collecting comprehensive information, project managers can gain a holistic view of the problem and make informed decisions.

2. Analyzing the Problem Statement

Once the problem is identified, project managers need to analyze its statement. This involves breaking down the problem into its components and understanding its impact on the project. By analyzing the problem statement, project managers can prioritize their efforts and focus on the most critical aspects.

Determining the Root Cause of the Problem

Identifying the root cause of a problem is essential for effective problem solving. It allows project managers to address the underlying issues rather than just treating the symptoms. Various techniques can be used for root cause analysis, such as the fishbone diagram and the 5 Whys technique.

1. Techniques for Root Cause Analysis

The fishbone diagram, also known as the Ishikawa diagram, is a visual tool that helps identify the root causes of a problem. It categorizes potential causes into different branches, such as people, process, equipment, and environment. By analyzing these branches, project managers can pinpoint the root cause.

2. Importance of Identifying the Root Cause

Identifying the root cause is crucial because it allows project managers to implement targeted solutions. By addressing the underlying issue, project managers can prevent the problem from recurring in the future and ensure long-term project success.

Developing Problem Solving Strategies

Brainstorming techniques.

Brainstorming is a creative problem-solving technique that encourages the generation of ideas and solutions. There are various brainstorming techniques, including traditional brainstorming and mind mapping.

1. Traditional Brainstorming

Traditional brainstorming involves a group of individuals coming together to generate ideas. Participants freely share their thoughts and suggestions without any judgment or criticism. This technique encourages the exploration of diverse perspectives and fosters creativity.

2. Mind Mapping

Mind mapping is a visual brainstorming technique that helps organize ideas and connections. It involves creating a central idea or problem statement and branching out with related ideas. Mind mapping allows project managers to visualize the problem and its potential solutions.

Analytical Problem Solving Methods

Analytical problem-solving methods involve structured approaches to problem solving. Two commonly used methods are the fishbone diagram and the 5 Whys technique.

1. Fishbone Diagram

The fishbone diagram, as mentioned earlier, helps identify the root causes of a problem. By analyzing different branches, project managers can uncover the underlying factors contributing to the problem and develop appropriate solutions.

2. 5 Whys Technique

The 5 Whys technique involves asking “why” multiple times to uncover the root cause of a problem. By repeatedly asking why a problem occurred, project managers can dig deeper into the underlying causes and address them directly.

Decision-Making Approaches

Effective problem solving requires sound decision-making. Two decision-making approaches commonly used in project management are cost-benefit analysis and multi-criteria decision analysis.

1. Cost-Benefit Analysis

Cost-benefit analysis involves evaluating the costs and benefits associated with different solutions. Project managers weigh the potential advantages and disadvantages of each option to make an informed decision. This approach helps prioritize solutions based on their potential impact.

2. Multi-Criteria Decision Analysis

Multi-criteria decision analysis considers multiple factors or criteria when making a decision. Project managers assign weights to each criterion based on its importance and evaluate potential solutions accordingly. This approach ensures a comprehensive evaluation of available options.

Implementing the Solution

Creating an action plan.

Once a solution is determined, project managers need to create an action plan to implement it successfully. This involves setting clear objectives and goals and assigning tasks and responsibilities to team members.

1. Setting Clear Objectives and Goals

Clear objectives and goals provide a roadmap for implementing the solution. Project managers should define specific, measurable, achievable, relevant, and time-bound (SMART) objectives to ensure clarity and focus.

2. Assigning Tasks and Responsibilities

Assigning tasks and responsibilities ensures that each team member knows their role in implementing the solution. Project managers should clearly communicate expectations and deadlines to facilitate smooth execution.

Executing the Action Plan

During the implementation phase, project managers need to monitor progress and make necessary adjustments. Effective communication and collaboration among team members are crucial for successful execution.

1. Monitoring Progress and Making Adjustments

Project managers should regularly monitor the progress of the action plan and identify any deviations or roadblocks. By making timely adjustments, project managers can ensure that the solution stays on track and achieves the desired results.

2. Communication and Collaboration During Implementation

Open and transparent communication is essential during the implementation phase. Project managers should encourage team members to share updates, challenges, and suggestions. Collaboration fosters a supportive environment and enhances problem-solving capabilities.

Evaluating the Solution

Assessing the effectiveness of the solution.

After implementing the solution, project managers need to assess its effectiveness. This involves measuring outcomes and results and collecting feedback from stakeholders.

1. Measuring Outcomes and Results

Project managers should measure the outcomes and results achieved through the implemented solution. This may include evaluating key performance indicators (KPIs) and comparing them to the initial problem statement. Measuring outcomes provides insights into the solution’s effectiveness.

2. Collecting Feedback from Stakeholders

Feedback from stakeholders is invaluable for evaluating the solution. Project managers should actively seek feedback from team members, clients, and other relevant stakeholders. Their perspectives can highlight areas of improvement and inform future problem-solving strategies.

Identifying Lessons Learned

Documenting successes and failures is crucial for continuous improvement. Project managers should identify and document lessons learned from the problem-solving process.

1. Documenting Successes and Failures

Project managers should record both successful and unsuccessful problem-solving experiences. Documenting successes helps replicate effective strategies in future projects, while documenting failures allows project managers to learn from mistakes and avoid similar pitfalls.

2. Incorporating Lessons into Future Projects

Lessons learned should be incorporated into future projects to enhance problem-solving capabilities. Project managers can create knowledge repositories or conduct training sessions to share best practices and ensure continuous improvement.

Continuous Improvement

Encouraging a culture of continuous improvement.

To foster continuous improvement, project managers should encourage a culture that values learning and innovation. Team members should feel empowered to suggest improvements and experiment with new problem-solving techniques.

Implementing Feedback Loops and Learning Mechanisms

Feedback loops and learning mechanisms facilitate continuous improvement. Project managers should establish regular feedback sessions, retrospectives, or post-project reviews to gather insights and identify areas for growth.

Leveraging Problem-Solving Skills for Future Projects

Problem-solving skills developed during a project can be leveraged for future projects. Project managers should encourage team members to apply their problem-solving expertise and share their insights with colleagues.

Recap of Key Points Discussed

In this article, we explored the importance of problem solving in project management. We discussed the definition and benefits of effective problem solving, as well as the role it plays in project success. We also delved into understanding the problem, developing problem-solving strategies, implementing the solution, evaluating its effectiveness, and embracing continuous improvement.

Importance of Ongoing Problem-Solving Skills in Project Management

Ongoing problem-solving skills are essential for project managers to navigate challenges and ensure project success. By continuously improving their problem-solving capabilities, project managers can adapt to changing circumstances, mitigate risks, and deliver exceptional results.

Final Thoughts and Recommendations

To excel in problem solving, project managers should stay updated with industry best practices and leverage available tools and techniques. They should foster a collaborative and innovative environment that encourages creativity and critical thinking. By prioritizing problem solving, project managers can overcome obstacles and drive project success.

Related Terms

What is a Team? Definition, Features, Types, Strategies, and Examples

Table of Contents

What is a Team?

A team is a cohesive group of individuals with diverse skill sets and shared objectives, working collaboratively within an organizational culture. Unlike a mere group, a team focuses on a common goal , leveraging mutual support and compatible interactions.

Teams vary in types – ranging from self-managed and cross-functional teams to virtual and process improvement teams – each serving distinct purposes. Successful teams exhibit traits like open communication, strong leadership, and a collective understanding of goals, fostering synergy and outperforming individual efforts.

Teams offer advantages such as enhanced decision-making , comprehensive problem-solving, and increased morale. While teams harness varied expertise for greater innovation and problem-solving, individual efforts can sometimes be more focused and expedient.

In practice, a blend of both individual contributions and collaborative teamwork often optimizes organizational productivity.

Examples of Teams

Let’s look at some common team examples in the workplace settings:

• Work Groups or Natural Teams
• Project Teams
• Self-Managed Teams
• Functional Teams

Cross-Functional Teams

• Process Improvement Teams
• Matrix Teams
• Contract Teams

Virtual Teams

• Operational Teams
• Sales Teams
• Marketing Teams
• Research and Development Teams
• Customer Support Teams
• Creative Teams

Characteristics of Team

Here are five common characteristics of a team:

Common Goal

Teams share a unified objective or purpose. This goal guides their efforts, aligning individual actions toward achieving collective success.

Interdependence

Team members rely on each other’s contributions and skills. Their success is intertwined, emphasizing collaboration and mutual support.

Open Communication

Effective teams maintain transparent and frequent communication. Open dialogue fosters trust, enables idea-sharing, and resolves conflicts efficiently.

Leadership and Support

Successful teams benefit from capable leadership that guides, motivates, and supports members. Good leadership encourages growth and maintains team cohesion.

Synergy and Collective Performance

Teams produce results that exceed individual capabilities through synergy. Collective efforts create a combined performance greater than what each member could achieve alone.

Read More: 5 Stages of Group Formation

Types of Teams

Let’s look at 4 most common team types in management:

Problem-Solving Team

Comprised of individuals with diverse skills, a problem-solving team is formed to address specific issues within an organization. They collaboratively work to find solutions, improve quality, enhance productivity, or address workplace challenges.

Self-Managed Team

Empowered with autonomy, a self-managed team oversees its day-to-day operations, making decisions on tasks like quality, safety, scheduling, and personnel matters. It manages and executes responsibilities without direct supervision, fostering a sense of ownership and accountability.

Involves members from different functional areas or departments, combining diverse expertise to tackle tasks that require varied inputs. Promotes collaboration, leveraging a range of skills to achieve specific objectives efficiently.

Geographically dispersed members collaborate through digital tools like video conferencing and email, enabling remote work. It facilitates collaboration and flexibility, allowing team members to work together despite physical distances.

Read More: The 10 Reasons for Group Formation

Importance of Teams in the Workplace

Let’s look at the five key importance of teams in the workplace:

Enhanced Problem Solving

Teams with diverse skill sets and perspectives offer a broader range of solutions. Collaborative brainstorming and collective expertise help tackle complex problems more effectively than individual efforts.

Increased Innovation and Creativity

A team environment fosters an open exchange of ideas, encouraging innovative thinking. Diverse viewpoints and collaborative dynamics often lead to fresh concepts and inventive solutions.

Improved Efficiency and Productivity

Teams distribute workloads, leveraging each member’s strengths. With tasks divided based on skills, teams often achieve objectives faster and more efficiently than individuals working alone.

Enhanced Employee Engagement and Satisfaction

Working in teams promotes a sense of belonging and shared purpose. Collaborative environments where contributions are valued lead to higher job satisfaction and increased engagement.

Read More: 7 Pros and 5 Cons of Working in a Group

Better Decision-Making

Teams facilitate collective decision-making by pooling diverse perspectives. With varied inputs and viewpoints, teams are often more equipped to make informed and comprehensive decisions compared to individual choices.

Strategies To Manage Teams

So far we understand what a team is and its importance – now, let’s look at some strategies you can employ to manage it effectively:

Clear Goal Setting and Communication

Establish clear, achievable goals and communicate them effectively to the team. Clarity ensures everyone understands the objectives, fostering alignment and focus among members.

Role Clarity and Delegation

Clearly define roles and responsibilities within the team. Delegation based on individual strengths ensures tasks are distributed effectively, optimizing productivity and minimizing confusion.

Read More: The 10 Importance of Group Work in the Organization

Regular Feedback and Recognition

Provide constructive feedback to team members regularly, acknowledging their contributions. Recognition of achievements fosters motivation, encouraging continued high performance.

Promote Collaboration and Team Building

Encourage an environment where team members collaborate and support one another. Team-building activities foster stronger relationships, trust, and camaraderie among members, enhancing teamwork.

Adaptability and Flexibility

Foster an adaptable environment that embraces change. Encourage flexibility in approaches, allowing teams to adjust strategies based on evolving circumstances, promoting resilience and agility.

Teams Vs. Groups

Teams and groups both entail gatherings of individuals, yet their essence and purpose diverge notably. Teams unite around shared goals, interdependence, and a collective commitment to achieve specific objectives. Contrastingly, groups might lack a unified aim, often comprising individuals with distinct interests or goals.

Teams exhibit higher cohesion, mutual accountability, and a collaborative spirit, while groups might function more independently with less interconnectedness. Teams prioritize collective performance, sharing responsibilities and accomplishments, whereas groups may focus more on individual achievements.

Ultimately, teams harness collective synergy toward a unified goal, while groups might operate with less cohesion and a focus on individual outcomes or interests.

Read Next: The 10 Characteristics of a Group

Leave a Comment Cancel reply

Save my name, email, and website in this browser for the next time I comment.

• 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

Share Podcast

Do You Understand the Problem You’re Trying to Solve?

To solve tough problems at work, first ask these questions.

• Apple Podcasts
• Google Podcasts

Problem solving skills are invaluable in any job. But all too often, we jump to find solutions to a problem without taking time to really understand the dilemma we face, according to Thomas Wedell-Wedellsborg , an expert in innovation and the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

In this episode, you’ll learn how to reframe tough problems by asking questions that reveal all the factors and assumptions that contribute to the situation. You’ll also learn why searching for just one root cause can be misleading.

Key episode topics include: leadership, decision making and problem solving, power and influence, business management.

HBR On Leadership curates the best case studies and conversations with the world’s top business and management experts, to help you unlock the best in those around you. New episodes every week.

• Listen to the original HBR IdeaCast episode: The Secret to Better Problem Solving (2016)
• Find more episodes of HBR IdeaCast
• Discover 100 years of Harvard Business Review articles, case studies, podcasts, and more at HBR.org .

HANNAH BATES: Welcome to HBR on Leadership , case studies and conversations with the world’s top business and management experts, hand-selected to help you unlock the best in those around you.

Problem solving skills are invaluable in any job. But even the most experienced among us can fall into the trap of solving the wrong problem.

Thomas Wedell-Wedellsborg says that all too often, we jump to find solutions to a problem – without taking time to really understand what we’re facing.

He’s an expert in innovation, and he’s the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

  In this episode, you’ll learn how to reframe tough problems, by asking questions that reveal all the factors and assumptions that contribute to the situation. You’ll also learn why searching for one root cause can be misleading. And you’ll learn how to use experimentation and rapid prototyping as problem-solving tools.

This episode originally aired on HBR IdeaCast in December 2016. Here it is.

SARAH GREEN CARMICHAEL: Welcome to the HBR IdeaCast from Harvard Business Review. I’m Sarah Green Carmichael.

Problem solving is popular. People put it on their resumes. Managers believe they excel at it. Companies count it as a key proficiency. We solve customers’ problems.

The problem is we often solve the wrong problems. Albert Einstein and Peter Drucker alike have discussed the difficulty of effective diagnosis. There are great frameworks for getting teams to attack true problems, but they’re often hard to do daily and on the fly. That’s where our guest comes in.

Thomas Wedell-Wedellsborg is a consultant who helps companies and managers reframe their problems so they can come up with an effective solution faster. He asks the question “Are You Solving The Right Problems?” in the January-February 2017 issue of Harvard Business Review. Thomas, thank you so much for coming on the HBR IdeaCast .

THOMAS WEDELL-WEDELLSBORG: Thanks for inviting me.

SARAH GREEN CARMICHAEL: So, I thought maybe we could start by talking about the problem of talking about problem reframing. What is that exactly?

THOMAS WEDELL-WEDELLSBORG: Basically, when people face a problem, they tend to jump into solution mode to rapidly, and very often that means that they don’t really understand, necessarily, the problem they’re trying to solve. And so, reframing is really a– at heart, it’s a method that helps you avoid that by taking a second to go in and ask two questions, basically saying, first of all, wait. What is the problem we’re trying to solve? And then crucially asking, is there a different way to think about what the problem actually is?

SARAH GREEN CARMICHAEL: So, I feel like so often when this comes up in meetings, you know, someone says that, and maybe they throw out the Einstein quote about you spend an hour of problem solving, you spend 55 minutes to find the problem. And then everyone else in the room kind of gets irritated. So, maybe just give us an example of maybe how this would work in practice in a way that would not, sort of, set people’s teeth on edge, like oh, here Sarah goes again, reframing the whole problem instead of just solving it.

THOMAS WEDELL-WEDELLSBORG: I mean, you’re bringing up something that’s, I think is crucial, which is to create legitimacy for the method. So, one of the reasons why I put out the article is to give people a tool to say actually, this thing is still important, and we need to do it. But I think the really critical thing in order to make this work in a meeting is actually to learn how to do it fast, because if you have the idea that you need to spend 30 minutes in a meeting delving deeply into the problem, I mean, that’s going to be uphill for most problems. So, the critical thing here is really to try to make it a practice you can implement very, very rapidly.

There’s an example that I would suggest memorizing. This is the example that I use to explain very rapidly what it is. And it’s basically, I call it the slow elevator problem. You imagine that you are the owner of an office building, and that your tenants are complaining that the elevator’s slow.

Now, if you take that problem framing for granted, you’re going to start thinking creatively around how do we make the elevator faster. Do we install a new motor? Do we have to buy a new lift somewhere?

The thing is, though, if you ask people who actually work with facilities management, well, they’re going to have a different solution for you, which is put up a mirror next to the elevator. That’s what happens is, of course, that people go oh, I’m busy. I’m busy. I’m– oh, a mirror. Oh, that’s beautiful.

And then they forget time. What’s interesting about that example is that the idea with a mirror is actually a solution to a different problem than the one you first proposed. And so, the whole idea here is once you get good at using reframing, you can quickly identify other aspects of the problem that might be much better to try to solve than the original one you found. It’s not necessarily that the first one is wrong. It’s just that there might be better problems out there to attack that we can, means we can do things much faster, cheaper, or better.

SARAH GREEN CARMICHAEL: So, in that example, I can understand how A, it’s probably expensive to make the elevator faster, so it’s much cheaper just to put up a mirror. And B, maybe the real problem people are actually feeling, even though they’re not articulating it right, is like, I hate waiting for the elevator. But if you let them sort of fix their hair or check their teeth, they’re suddenly distracted and don’t notice.

But if you have, this is sort of a pedestrian example, but say you have a roommate or a spouse who doesn’t clean up the kitchen. Facing that problem and not having your elegant solution already there to highlight the contrast between the perceived problem and the real problem, how would you take a problem like that and attack it using this method so that you can see what some of the other options might be?

THOMAS WEDELL-WEDELLSBORG: Right. So, I mean, let’s say it’s you who have that problem. I would go in and say, first of all, what would you say the problem is? Like, if you were to describe your view of the problem, what would that be?

SARAH GREEN CARMICHAEL: I hate cleaning the kitchen, and I want someone else to clean it up.

THOMAS WEDELL-WEDELLSBORG: OK. So, my first observation, you know, that somebody else might not necessarily be your spouse. So, already there, there’s an inbuilt assumption in your question around oh, it has to be my husband who does the cleaning. So, it might actually be worth, already there to say, is that really the only problem you have? That you hate cleaning the kitchen, and you want to avoid it? Or might there be something around, as well, getting a better relationship in terms of how you solve problems in general or establishing a better way to handle small problems when dealing with your spouse?

SARAH GREEN CARMICHAEL: Or maybe, now that I’m thinking that, maybe the problem is that you just can’t find the stuff in the kitchen when you need to find it.

THOMAS WEDELL-WEDELLSBORG: Right, and so that’s an example of a reframing, that actually why is it a problem that the kitchen is not clean? Is it only because you hate the act of cleaning, or does it actually mean that it just takes you a lot longer and gets a lot messier to actually use the kitchen, which is a different problem. The way you describe this problem now, is there anything that’s missing from that description?

SARAH GREEN CARMICHAEL: That is a really good question.

THOMAS WEDELL-WEDELLSBORG: Other, basically asking other factors that we are not talking about right now, and I say those because people tend to, when given a problem, they tend to delve deeper into the detail. What often is missing is actually an element outside of the initial description of the problem that might be really relevant to what’s going on. Like, why does the kitchen get messy in the first place? Is it something about the way you use it or your cooking habits? Is it because the neighbor’s kids, kind of, use it all the time?

There might, very often, there might be issues that you’re not really thinking about when you first describe the problem that actually has a big effect on it.

SARAH GREEN CARMICHAEL: I think at this point it would be helpful to maybe get another business example, and I’m wondering if you could tell us the story of the dog adoption problem.

THOMAS WEDELL-WEDELLSBORG: Yeah. This is a big problem in the US. If you work in the shelter industry, basically because dogs are so popular, more than 3 million dogs every year enter a shelter, and currently only about half of those actually find a new home and get adopted. And so, this is a problem that has persisted. It’s been, like, a structural problem for decades in this space. In the last three years, where people found new ways to address it.

So a woman called Lori Weise who runs a rescue organization in South LA, and she actually went in and challenged the very idea of what we were trying to do. She said, no, no. The problem we’re trying to solve is not about how to get more people to adopt dogs. It is about keeping the dogs with their first family so they never enter the shelter system in the first place.

In 2013, she started what’s called a Shelter Intervention Program that basically works like this. If a family comes and wants to hand over their dog, these are called owner surrenders. It’s about 30% of all dogs that come into a shelter. All they would do is go up and ask, if you could, would you like to keep your animal? And if they said yes, they would try to fix whatever helped them fix the problem, but that made them turn over this.

And sometimes that might be that they moved into a new building. The landlord required a deposit, and they simply didn’t have the money to put down a deposit. Or the dog might need a $10 rabies shot, but they didn’t know how to get access to a vet.

And so, by instigating that program, just in the first year, she took her, basically the amount of dollars they spent per animal they helped went from something like $85 down to around $60. Just an immediate impact, and her program now is being rolled out, is being supported by the ASPCA, which is one of the big animal welfare stations, and it’s being rolled out to various other places.

And I think what really struck me with that example was this was not dependent on having the internet. This was not, oh, we needed to have everybody mobile before we could come up with this. This, conceivably, we could have done 20 years ago. Only, it only happened when somebody, like in this case Lori, went in and actually rethought what the problem they were trying to solve was in the first place.

SARAH GREEN CARMICHAEL: So, what I also think is so interesting about that example is that when you talk about it, it doesn’t sound like the kind of thing that would have been thought of through other kinds of problem solving methods. There wasn’t necessarily an After Action Review or a 5 Whys exercise or a Six Sigma type intervention. I don’t want to throw those other methods under the bus, but how can you get such powerful results with such a very simple way of thinking about something?

THOMAS WEDELL-WEDELLSBORG: That was something that struck me as well. This, in a way, reframing and the idea of the problem diagnosis is important is something we’ve known for a long, long time. And we’ve actually have built some tools to help out. If you worked with us professionally, you are familiar with, like, Six Sigma, TRIZ, and so on. You mentioned 5 Whys. A root cause analysis is another one that a lot of people are familiar with.

Those are our good tools, and they’re definitely better than nothing. But what I notice when I work with the companies applying those was those tools tend to make you dig deeper into the first understanding of the problem we have. If it’s the elevator example, people start asking, well, is that the cable strength, or is the capacity of the elevator? That they kind of get caught by the details.

That, in a way, is a bad way to work on problems because it really assumes that there’s like a, you can almost hear it, a root cause. That you have to dig down and find the one true problem, and everything else was just symptoms. That’s a bad way to think about problems because problems tend to be multicausal.

There tend to be lots of causes or levers you can potentially press to address a problem. And if you think there’s only one, if that’s the right problem, that’s actually a dangerous way. And so I think that’s why, that this is a method I’ve worked with over the last five years, trying to basically refine how to make people better at this, and the key tends to be this thing about shifting out and saying, is there a totally different way of thinking about the problem versus getting too caught up in the mechanistic details of what happens.

SARAH GREEN CARMICHAEL: What about experimentation? Because that’s another method that’s become really popular with the rise of Lean Startup and lots of other innovation methodologies. Why wouldn’t it have worked to, say, experiment with many different types of fixing the dog adoption problem, and then just pick the one that works the best?

THOMAS WEDELL-WEDELLSBORG: You could say in the dog space, that’s what’s been going on. I mean, there is, in this industry and a lot of, it’s largely volunteer driven. People have experimented, and they found different ways of trying to cope. And that has definitely made the problem better. So, I wouldn’t say that experimentation is bad, quite the contrary. Rapid prototyping, quickly putting something out into the world and learning from it, that’s a fantastic way to learn more and to move forward.

My point is, though, that I feel we’ve come to rely too much on that. There’s like, if you look at the start up space, the wisdom is now just to put something quickly into the market, and then if it doesn’t work, pivot and just do more stuff. What reframing really is, I think of it as the cognitive counterpoint to prototyping. So, this is really a way of seeing very quickly, like not just working on the solution, but also working on our understanding of the problem and trying to see is there a different way to think about that.

If you only stick with experimentation, again, you tend to sometimes stay too much in the same space trying minute variations of something instead of taking a step back and saying, wait a minute. What is this telling us about what the real issue is?

SARAH GREEN CARMICHAEL: So, to go back to something that we touched on earlier, when we were talking about the completely hypothetical example of a spouse who does not clean the kitchen–

THOMAS WEDELL-WEDELLSBORG: Completely, completely hypothetical.

SARAH GREEN CARMICHAEL: Yes. For the record, my husband is a great kitchen cleaner.

You started asking me some questions that I could see immediately were helping me rethink that problem. Is that kind of the key, just having a checklist of questions to ask yourself? How do you really start to put this into practice?

THOMAS WEDELL-WEDELLSBORG: I think there are two steps in that. The first one is just to make yourself better at the method. Yes, you should kind of work with a checklist. In the article, I kind of outlined seven practices that you can use to do this.

But importantly, I would say you have to consider that as, basically, a set of training wheels. I think there’s a big, big danger in getting caught in a checklist. This is something I work with.

My co-author Paddy Miller, it’s one of his insights. That if you start giving people a checklist for things like this, they start following it. And that’s actually a problem, because what you really want them to do is start challenging their thinking.

So the way to handle this is to get some practice using it. Do use the checklist initially, but then try to step away from it and try to see if you can organically make– it’s almost a habit of mind. When you run into a colleague in the hallway and she has a problem and you have five minutes, like, delving in and just starting asking some of those questions and using your intuition to say, wait, how is she talking about this problem? And is there a question or two I can ask her about the problem that can help her rethink it?

SARAH GREEN CARMICHAEL: Well, that is also just a very different approach, because I think in that situation, most of us can’t go 30 seconds without jumping in and offering solutions.

THOMAS WEDELL-WEDELLSBORG: Very true. The drive toward solutions is very strong. And to be clear, I mean, there’s nothing wrong with that if the solutions work. So, many problems are just solved by oh, you know, oh, here’s the way to do that. Great.

But this is really a powerful method for those problems where either it’s something we’ve been banging our heads against tons of times without making progress, or when you need to come up with a really creative solution. When you’re facing a competitor with a much bigger budget, and you know, if you solve the same problem later, you’re not going to win. So, that basic idea of taking that approach to problems can often help you move forward in a different way than just like, oh, I have a solution.

I would say there’s also, there’s some interesting psychological stuff going on, right? Where you may have tried this, but if somebody tries to serve up a solution to a problem I have, I’m often resistant towards them. Kind if like, no, no, no, no, no, no. That solution is not going to work in my world. Whereas if you get them to discuss and analyze what the problem really is, you might actually dig something up.

Let’s go back to the kitchen example. One powerful question is just to say, what’s your own part in creating this problem? It’s very often, like, people, they describe problems as if it’s something that’s inflicted upon them from the external world, and they are innocent bystanders in that.

SARAH GREEN CARMICHAEL: Right, or crazy customers with unreasonable demands.

THOMAS WEDELL-WEDELLSBORG: Exactly, right. I don’t think I’ve ever met an agency or consultancy that didn’t, like, gossip about their customers. Oh, my god, they’re horrible. That, you know, classic thing, why don’t they want to take more risk? Well, risk is bad.

It’s their business that’s on the line, not the consultancy’s, right? So, absolutely, that’s one of the things when you step into a different mindset and kind of, wait. Oh yeah, maybe I actually am part of creating this problem in a sense, as well. That tends to open some new doors for you to move forward, in a way, with stuff that you may have been struggling with for years.

SARAH GREEN CARMICHAEL: So, we’ve surfaced a couple of questions that are useful. I’m curious to know, what are some of the other questions that you find yourself asking in these situations, given that you have made this sort of mental habit that you do? What are the questions that people seem to find really useful?

THOMAS WEDELL-WEDELLSBORG: One easy one is just to ask if there are any positive exceptions to the problem. So, was there day where your kitchen was actually spotlessly clean? And then asking, what was different about that day? Like, what happened there that didn’t happen the other days? That can very often point people towards a factor that they hadn’t considered previously.

SARAH GREEN CARMICHAEL: We got take-out.

THOMAS WEDELL-WEDELLSBORG: S,o that is your solution. Take-out from [INAUDIBLE]. That might have other problems.

Another good question, and this is a little bit more high level. It’s actually more making an observation about labeling how that person thinks about the problem. And what I mean with that is, we have problem categories in our head. So, if I say, let’s say that you describe a problem to me and say, well, we have a really great product and are, it’s much better than our previous product, but people aren’t buying it. I think we need to put more marketing dollars into this.

Now you can go in and say, that’s interesting. This sounds like you’re thinking of this as a communications problem. Is there a different way of thinking about that? Because you can almost tell how, when the second you say communications, there are some ideas about how do you solve a communications problem. Typically with more communication.

And what you might do is go in and suggest, well, have you considered that it might be, say, an incentive problem? Are there incentives on behalf of the purchasing manager at your clients that are obstructing you? Might there be incentive issues with your own sales force that makes them want to sell the old product instead of the new one?

So literally, just identifying what type of problem does this person think about, and is there different potential way of thinking about it? Might it be an emotional problem, a timing problem, an expectations management problem? Thinking about what label of what type of problem that person is kind of thinking as it of.

SARAH GREEN CARMICHAEL: That’s really interesting, too, because I think so many of us get requests for advice that we’re really not qualified to give. So, maybe the next time that happens, instead of muddying my way through, I will just ask some of those questions that we talked about instead.

THOMAS WEDELL-WEDELLSBORG: That sounds like a good idea.

SARAH GREEN CARMICHAEL: So, Thomas, this has really helped me reframe the way I think about a couple of problems in my own life, and I’m just wondering. I know you do this professionally, but is there a problem in your life that thinking this way has helped you solve?

THOMAS WEDELL-WEDELLSBORG: I’ve, of course, I’ve been swallowing my own medicine on this, too, and I think I have, well, maybe two different examples, and in one case somebody else did the reframing for me. But in one case, when I was younger, I often kind of struggled a little bit. I mean, this is my teenage years, kind of hanging out with my parents. I thought they were pretty annoying people. That’s not really fair, because they’re quite wonderful, but that’s what life is when you’re a teenager.

And one of the things that struck me, suddenly, and this was kind of the positive exception was, there was actually an evening where we really had a good time, and there wasn’t a conflict. And the core thing was, I wasn’t just seeing them in their old house where I grew up. It was, actually, we were at a restaurant. And it suddenly struck me that so much of the sometimes, kind of, a little bit, you love them but they’re annoying kind of dynamic, is tied to the place, is tied to the setting you are in.

And of course, if– you know, I live abroad now, if I visit my parents and I stay in my old bedroom, you know, my mother comes in and wants to wake me up in the morning. Stuff like that, right? And it just struck me so, so clearly that it’s– when I change this setting, if I go out and have dinner with them at a different place, that the dynamic, just that dynamic disappears.

SARAH GREEN CARMICHAEL: Well, Thomas, this has been really, really helpful. Thank you for talking with me today.

THOMAS WEDELL-WEDELLSBORG: Thank you, Sarah.  

HANNAH BATES: That was Thomas Wedell-Wedellsborg in conversation with Sarah Green Carmichael on the HBR IdeaCast. He’s an expert in problem solving and innovation, and he’s the author of the book, What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve .

We’ll be back next Wednesday with another hand-picked conversation about leadership from the Harvard Business Review. If you found this episode helpful, share it with your friends and colleagues, and follow our show on Apple Podcasts, Spotify, or wherever you get your podcasts. While you’re there, be sure to leave us a review.

We’re a production of Harvard Business Review. If you want more podcasts, articles, case studies, books, and videos like this, find it all at HBR dot org.

This episode was produced by Anne Saini, and me, Hannah Bates. Ian Fox is our editor. Music by Coma Media. Special thanks to Maureen Hoch, Adi Ignatius, Karen Player, Ramsey Khabbaz, Nicole Smith, Anne Bartholomew, and you – our listener.

See you next week.

• Subscribe On:

Latest in this series

This article is about leadership.

• Decision making and problem solving
• Power and influence
• Business management

Partner Center