problem solving and project management

• 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

• Become a Project Manager
• Certification

Problem Solving Techniques for Project Managers

Learn which problem solving techniques and strategies can help you effectively handle the challenges you face in your projects.

Problem Solving Techniques: A 5-Step Approach

Some problems are small and can be resolved quickly. Other problems are large and may require significant time and effort to solve. These larger problems are often tackled by turning them into formal projects.

"A project is a problem scheduled for solution."

- Joseph M. Juran

Problem Solving is one of the Tools & Techniques used for Managing Quality and Controlling Resources.

Modules 8 and 9 of the PM PrepCast cover Project Quality Management and Project Resource Management.

Consider this study program if you're preparing to take your CAPM or PMP Certification exam.

Disclosure:   I may receive a commission if you purchase the PM PrepCast with this link.

Whether the problem you are focusing on is small or large, using a systematic approach for solving it will help you be a more effective project manager.

This approach defines five problem solving steps you can use for most problems...

Define the Problem

Determine the causes, generate ideas, select the best solution, take action.

The most important of the problem solving steps is to define the problem correctly. The way you define the problem will determine how you attempt to solve it.

For example, if you receive a complaint about one of your project team members from a client, the solutions you come up with will be different based on the way you define the problem.

If you define the problem as poor performance by the team member you will develop different solutions than if you define the problem as poor expectation setting with the client.

Once you have defined the problem, you are ready to dig deeper and start to determine what is causing it.  You can use a fishbone diagram to help you perform a cause and effect analysis.

If you consider the problem as a gap between where you are now and where you want to be, the causes of the problem are the obstacles that are preventing you from closing that gap immediately.

This level of analysis is important to make sure your solutions address the actual causes of the problem instead of the symptoms of the problem. If your solution fixes a symptom instead of an actual cause, the problem is likely to reoccur since it was never truly solved.

Once the hard work of defining the problem and determining its causes has been completed, it's time to get creative and develop possible solutions to the problem.

Two great problem solving methods you can use for coming up with solutions are brainstorming and mind mapping .

After you come up with several ideas that can solve the problem, one problem solving technique you can use to decide which one is the best solution to your problem is a simple trade-off analysis .

To perform the trade-off analysis, define the critical criteria for the problem that you can use to evaluate how each solution compares to each other. The evaluation can be done using a simple matrix. The highest ranking solution will be your best solution for this problem.

Pass your PMP Exam!

The PM Exam Simulator is an online exam simulator.

Realistic exam sample questions so you can pass your CAPM or PMP Certification exam.

Disclosure:   I may receive a commission if you purchase the PM Exam Simulator with this link.

Once you've determined which solution you will implement, it's time to take action. If the solution involves several actions or requires action from others, it is a good idea to create an action plan and treat it as a mini-project.

Using this simple five-step approach can increase the effectiveness of your problem solving skills .

For more problem solving strategies and techniques, subscribe to my newsletter below.

Related Articles About Problem Solving Techniques

Fishbone Diagram: Cause and Effect Analysis Using Ishikawa Diagrams

A fishbone diagram can help you perform a cause and effect analysis for a problem. Step-by-step instructions on how to create this type of diagram. Also known as Ishikara or Cause and Effect diagrams.

Do You Want More Project Management Tips?

Subscribe to Project Success Tips , my FREE Project Management Newsletter where I share tips and techniques that you can use to get your Project Management Career off to a great start .

As a BONUS for signing up, you'll receive access to my Subscribers Only Download Page !  This is where you can download my " Become A Project Manager Checklist " and other project management templates.

Don't wait...

• Become a PM
• Problem Solving Techniques

New! Comments

Home      Privacy Policy      About      Contact

Copyright © 2010-2021 | ALL RIGHTS RESERVED

Project-Management-Skills.com

.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;}

• Project management |
• The 25 project management skills you ne ...

The 25 project management skills you need to succeed

Anyone who oversees projects is a project manager, but to become a more thoughtful manager (with a higher impact), you need to develop the right project management skills. Learn what skills are necessary to become a successful project manager and how to build them.

If you’re interested in honing and developing your project management skills, you’re in the right place. In this guide, we’ll cover 25 key skills you need to succeed as a project manager or project administrator , and how you can develop those skills over time.

What are project management skills (and why do they matter?)

Project management skills are the attributes you develop to become a more experienced project manager. Building a project management skill set includes learning technical and hard skills, such as portfolio management and project scoping, and soft skills (for example, adaptability).In honing these skills, you’re preparing yourself to more effectively perform in your role. 

Project management is the practice of organizing and executing work efficiently—and helping your team do the same. For a while, project managers had to be trained and certified in complicated project management technology. Traditional project management tools were hard to set up and required constant maintenance, which is where the position “project manager” comes from.

Modern project management tools

Modern project management evolved from traditional project management in two distinct ways. As companies and teams democratized their project management processes, they needed more team members and team leads who were able to manage a process from conception to completion. In order to support those team leads, project management software has also evolved, from complex mechanisms to flexible and easy-to-use tools.

Today, any team member may be called upon to run a project and become the de-facto project manager—which is why modern project management tools are built to be flexible enough for anyone to use on any project, so you’re able to jump in and hit the ground running. 

These tools, like Asana , make it easy to track, manage, and organize work—without the learning curve associated with traditional tools. With today's project management tools , you can easily implement project management best practices and bring a new level of clarity and visibility to your project team. 

How to use your project management skills

Project management tools do the heavy lifting when it comes to reducing silos, increasing visibility, and facilitating cross-functional collaboration. As the project manager, you can use these tools to give your team the insight they need to get their best work done. While you don’t need to learn complicated skills or tools in order to become a successful project manager , there are hard, soft, and technical skills you can develop in order to improve your management and collaboration skills.

Some of these skills might not apply to you—while others might be things you’re already seasoned in. Like everything in the five phases of project management , approach this list with flexibility and work on the skills that are most relevant to you.

10 soft skills for project managers

Soft skills are what we call “non-technical skills,” or skills that can help you improve your quality of work—without a specific tool or technical requirement. These are also called “people skills” or “interpersonal skills” because they often help you work with and relate to others in your workspace. These 10 skills are the most important soft skills for project management:

1. Collaboration

Collaboration is the cornerstone of all project management skills. In project management, collaboration helps you get work done quickly and more efficiently. When you can coordinate across teams, you gain valuable insights into your project that you might not find within your team. If more minds are involved in the work, projects are inherently more creative and well developed.

To improve your collaboration skills, practice having conversations. Use techniques like active listening , where you stay engaged and focused when others are speaking to you. It sounds simple, but learning how to have open communication, reduce boundaries, and co-create are critical for a collaborative team.

2. Teamwork

Everyone on your team has something to bring to the table, and your team is more effective working together than they would be alone. Teamwork ensures that everyone feels welcome, valued, and they are supported to contribute.

If you’re working to boost your teamwork skills, dig deeper into team brainstorms , 1:1 conversations, and ask for feedback from your team—how can you be a better team member? Notice if there’s someone who hasn’t spoken up in a while, and be supportive when another team member has a new idea.

3. Communication

Miscommunications are common when you’re working with a group of people. Learning how to communicate well and avoid these will make projects run more smoothly and be more enjoyable. 

To develop your communication skills, practice being open and honest with your coworkers. This requires a lot of trust between you and your team members. To build this trust, encourage your team members to bring any thoughts into a discussion—even if you disagree with them.

4. Time management

Time management and organization skills go hand in hand. As you become better at organizing your tasks, you’ll also have a clearer sense of everything that’s on your plate and how long your upcoming tasks are going to take.

Still, it can be hard to buckle down and prioritize your work. To improve your time management skills and reduce procrastination, try prioritizing tasks. When you’re clear on which tasks are higher priority, you can tackle them first, to make sure nothing gets left behind or falls through the cracks.

5. Leadership

Even if you don’t think of yourself as a leader or have a role in team management, when you’re managing a project, your project team is looking to you for leadership, guidance, and support. 

To develop your leadership skills, practice approaching situations with empathy and understanding. Good leaders bring everyone together and make them feel supported to foster teamwork and collaboration.

6. Organization

For a lot of project managers, organization is the most intimidating soft skill. You might think organization is either something you “have” or “don’t have.” But, like every other project management skill in this article, you can develop your organizational skills and become a Marie Kondo in your own right.

The best way to become a better organizer is to create (and maintain) a central source of truth for your work and your team’s work. We’re often disorganized because work is disconnected—in fact, the average employee switches between 10 tools per day . Instead of splitting your time between 10 tools, try using a digital organization tool to act as that one central source of truth for your team.

7. Problem solving

Problem solving skills are collaborative, iterative skills that help you approach a problem and, ultimately, solve it. Developing problem solving skills isn’t about always having the “right” answer to every problem—rather, people with great problem solving skills practice approaching problems from new perspectives and methodically working towards a solution.

To become a better problem solver, use data-driven decision-making frameworks or routine analyses. For example, if you need to solve for how to boost sales by 10% over your competition, you can run a competitive analysis to determine where you currently stand in the market. Then, use that information to solve the problem of lower sales. In this case, you could develop a new marketing strategy coordinated with the sales team.

8. Critical thinking

Critical thinking, like problem solving, doesn’t have a “solution.” You can’t “win” at critical thinking, but you can practice approaching problems logically instead of making decisions based on your emotions. Good critical thinkers practice analyzing information in front of them and forming their own conclusions based on the facts—the way Sherlock Holmes solves a mystery.

To practice critical thinking, always take a step back and ask yourself: how did I come to this conclusion? Could there be another answer? Am I being swayed by something other than factual information? Emotional decisions aren’t necessarily bad—in fact, some of the best decisions are those we’re passionate about. But critical thinking is a helpful way to make sure you’re approaching a situation from the right perspective.

9. Adaptability

At some point, whether it’s this project or the next one, aspects of your project plan will change. Maybe your deadline or priorities shifts, and you need to adapt your workflow accordingly. Great project managers are able to pivot and adapt to new situations to continue steering their project team in the right direction.

Becoming more adaptable is all about understanding when and how to shift gears. To do this, you need to understand yourself. Developing other soft skills, such as self-awareness and mindfulness, can help you be more in touch with and manage your emotions, which are often in flux during times of change.

10. Conflict resolution

Inevitably, conflict will arise during the projects you manage. It could be that a stakeholder wants to change the project scope. Or maybe you missed your budget or deadline. Conflict resolution is about addressing both sides of the conflict so everyone feels heard and supported. If there are harmed parties, take the time to listen to them and try to find a solution that works for everyone. Even when that can’t happen, approaching the conversation with patience and empathy can help defuse a potentially frustrating situation and lead to a better result.

7 hard skills for project managers

Unlike soft skills, hard skills are quantifiable abilities. While the soft skills mentioned above are applicable for many work skills, these seven hard skills are relevant specifically to project management. Developing these will help you become a more well rounded and efficient project manager.

1. Project planning

At its core, a  project plan  (sometimes called a project charter) is a blueprint of the key elements your project needs to succeed. Typically a project plan will include seven things:

Goals and  project objectives

Success metrics

Stakeholders  and  roles

Scope  and  budget

Milestones ,  deliverables , and  project dependencies

Timeline  and  schedule

Communication plan

Some of these things, like your goals or your milestones, might already be defined in your project roadmap or brief. But your project plan is where all of these project elements come together to create a cohesive picture of your upcoming work.

A lot of planning goes into the beginning of the year for what our vision is and where we will be by the end of that particular year. Once that is done, we summarize it in a project so it's visible to everyone... Having that visual representation in Asana makes it easier to move things around.”

2. Project scoping

Project scope is the size, goals, and limitations (i.e., deadlines and resources) for your project. Your project scope will define what you can achieve within a certain timeframe and budget. Setting and defining your project scope is important in order to prevent scope creep , which is when your project deliverables outgrow your original project scope.

In order to improve your project scoping skills, practice setting project scope early and often. Once you’ve set your project scope, share it with stakeholders and surface it frequently, so everyone is on the same page about the project’s aims and limitations. Use it as a point of reference, so you know when to say no to new asks.

We have been able to reduce the number of products that we’ve oversold and the number of times we have to contact the customer to push a ship date out.”

3. Writing a project brief

Your project brief outlines your general project objectives and how you plan to get there. This can serve as a helpful North Star to guide planning sessions.

The most important thing to remember about your project brief is that it’s a living document. As you develop your project plan and get input from stakeholders, you can adapt and update your project brief. In general, your project brief should contain a link to your project roadmap if you created one, a list of your project stakeholders and their responsibilities  (sometimes called a RACI chart), other relevant documentation or files, and any other high-level information your team might need.

Having executive oversight and insight into projects is key so we can quickly get up to speed on what is happening at any point.”

4. Hosting a project kickoff meeting

A kickoff meeting is an opportunity to align with your project stakeholders. This is your chance to clarify your project goals and scope, and share any documents you’ve already put together like your project roadmap, project brief, or supplemental documentation like a bill of materials for a marketing campaign or a creative brief for a design team.

To host a successful kickoff meeting, plan to share the documentation you have put together with project stakeholders. Then, host a brainstorming or Q&A session to align on any additional variables, like budget,  resources , or final deliverables.

5. Project roadmapping

A project roadmap is a high-level overview of your project’s key deliverables and timeline. Project roadmaps are helpful for complex initiatives with a lot of stakeholders because they help the entire project team get on the same page before the project even starts.

Traditionally, project roadmaps are created in Gantt chart-like software , in order to display a general schedule of your project as a horizontal bar chart. To create a project roadmap, use a tool like Timeline in Asana to create a rough timeline of your project, adding key milestones or important dependencies.

6. Mapping your project timeline

Your project timeline is the order and duration of events during your project lifecycle. Knowing your project timeline helps your team track project success and deliver the right assets on time.

In order to build a great project timeline, make sure you clarify the start and end dates of your project, as well as any key milestones. As you continue building out individual tasks and deliverables, set dependencies between tasks, and clarify the start and end date of each piece of work.

7. Task management

Once your project is officially underway, task management refers to how well you manage your and your team’s time. The best project managers have visibility into what their team is working on in real-time, so they can help their team effectively prioritize and execute work.

But you don’t have to magically know everything that’s happening in your project—instead, use task management software.  Task management software  is more than a to-do list—it’s a way to get a holistic view of all of the work happening in your project. With effective task management, you can empower your team to work more productively, efficiently, and effectively.

With Asana, we can see project progress and blockers, plus feedback and action items, all in one place. We're now able to complete work more efficiently and effectively, which has become even more critical while working from home. We’d be lost without it!”

8 technical skills all project managers need

Soft skills: check. Hard skills: got it. The only thing you have left to master are technical skills!

Technical skills refer to your knowledge of specific tools and softwares within project management. These tools aren’t hard to learn—as we mentioned before, modern project management is built to be flexible and easy to use. These eight skills are aspects of project management roles you should become familiar with, so you know when and how to leverage them.

1. Project management software skills

Project management software  has come a long way from legacy tools that were difficult to use and required a project management professional to implement. But like any tool, even easy-to-use ones, the software you choose takes time to learn and truly master. Make sure the tool you select has a written  guide  and  helpful videos  to teach you the ins and outs of how to use it.

2. Gantt charts

Gantt charts are a way to visualize your project as a horizontal bar chart, where each bar represents a piece of work and the length of each bar represents the amount of time that work will take.

Project milestones

Dependencies

Real-time project progress

Start and end dates

Traditional Gantt chart technology can be tricky to use and limited in scope, which is why, at Asana, we took the best of Gantt chart technology and created  Timeline , a Gantt-chart like tool that helps you see how all of the pieces fit together.

Launching an album has so many moving parts, and Asana helps us track every detail, who’s responsible for it, and when it needs to be completed.”

3. Kanban boards

Another popular type of visual project management is the  Kanban board . Each column in a Kanban board represents a stage of work, like  New ,  In progress , or  Done . Individual work is represented by cards, which move through the columns until they’re completed.

Kanban boards tools  are a popular visual project management tool for lean project management teams, particularly product, engineering, and software development teams. They’re an Agile methodology , designed to be adaptable and flexible to adjust to development needs in real-time.

4. Agile management

Agile management is a lean project management methodology that’s particularly popular with product, engineering, and software development teams. Agile operates on a system of continuous improvement and incremental evolution, and it encompasses several lean methodologies, like lean portfolio management ,  Scrum , and  Kanban .

In order to manage an Agile team, it's the project manager’s job to coordinate between team members and stay flexible. This can mean changing the project schedule, aligning with teams working on a different project, or just staying in touch with effective communication.

5. Workload management

If you’ve managed projects before, you know how hard it is to gain clarity on who is working on what—but it doesn’t have to be.  Workload management  helps you measure your team’s bandwidth and make sure they aren’t over- or under-worked. It’s an interactive process that doesn’t have a beginning or end state—rather, an effective project manager will continuously monitor their team’s workload to ensure no one is burning out.

There are two steps to using workload management software . First, start by figuring out your team’s capacity, competencies, and current workload. From there, allocate resources based on individual workload, or rebalance workloads as needed.

6. Cost management

In project management, cost management is considering how each task impacts your budget at every stage of the project. Cost management is a key part of project leadership, and an important element of whether or not your project is a success. Staying within budget is as important as hitting your project due date, and cost management can help you get there.

To manage cost effectively, good project managers define their costs and budget at the beginning of a project. Make sure project stakeholders and team members all understand the budget. Then, during the project, keep cost and budget in mind. Check in on your spending several times during the project to make sure you aren’t overshooting your budget. Once the project is completed, tally predicted cost vs. actual cost to determine how effective your cost management strategies were. This can also help you benchmark for future projects.

7. Project portfolio management

With project portfolio management (PMM), you can get a bird’s-eye view of your team’s work across multiple projects. Unlike traditional project management, PMM involves working on multiple projects or large-scale initiatives simultaneously. Project portfolio management tools help you get a holistic view of all of your team’s work in real-time, so you can connect strategy to execution.

Portfolios are also a key Asana feature for our team. It is a great tool for our executive team so they can see our big pieces of work all in a single place with the status, progress and ownership. Our CEO visits our portfolio daily and adds comments. He loves to be able to see what's going on in a snapshot.”

8. Change management

If you’ve ever rolled out a big organizational change, you’ve likely practiced change management, even if you didn’t know it. Change management is the process of introducing organizational change—like new processes or tools—over a set period of time to make them easier to adapt to.

At Asana, we use the Asana Way of Change, a six step process developed by our Customer Success team that incorporates proven change management strategies. To learn more,  read our guide to change management .

The standard of our creative team, for a while, was just to react to work. But we’ll never do the best work we possibly can without a clear process.”

How to build your project management skills

Twenty five skills might feel like a lot, but remember that you don’t need to master every skill in this list. Some, like Agile, are only relevant for specific teams. Others, like organization, become virtually effortless with a little focus and great tools .

Keep in mind that developing your project management skills takes practice. Challenge yourself to focus on one or two new skills for each project—whether that’s trying out a new  visual form of project management  like Kanban, drafting your first ever project plan, or leaning into time-management.

There are also classes you can take to develop hard and soft project management skills. Though you no longer need certifications in order to be considered a project manager, the  Project Management Institute  (PMI) offers courses, learning events, and their famous  Guide to the Project Management Body of Knowledge (PMBOK® Guide) , which was the first project management guide ever published.

Finally, once you’ve  selected a project management tool , you can also take their classes to learn technical project management skills. At Asana, we’ve developed the  Asana Academy  and  How to Asana  series to help new project managers learn new soft, hard, and technical skills.

Build your project management toolkit

If you manage a project, you’re a project manager—and you likely already have some key project management skills. The most important thing is to be intentional, listen to your team, and collaborate with your team members. The rest will follow.

Project management doesn’t need to be complex. Asana was designed specifically to keep project manager’s organized, with tools, automations, and customizations built for collaborating and coordinating everything from a simple brainstorming session to a full-fledged product launch. 

Related resources

15 project management interview questions, answers, and tips

Critical path method: How to use CPM for project management

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

How Asana uses work management to drive product development

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

15 Problem-Solving Strategies for Projects and Teams

In project management and team collaboration, problem-solving is the process of identifying and resolving issues that arise during a project. It is a crucial skill that helps fix broken processes, improve performance, and identify opportunities. Problem-solving enables project managers and team leaders to overcome challenges and achieve success.

In this blog article, we will explore 15 problem-solving strategies that can revolutionize your approach and help you achieve success. From effective communication techniques to fostering collaboration, these strategies are designed to tackle the most common obstacles encountered in project management. Get ready to unlock the potential of your projects and teams with these tried-and-tested problem-solving strategies!

The 5 Whys Analysis

This problem-solving technique aims to uncover a problem's underlying cause by repeatedly asking the question, "Why?". The goal is to dig deep and identify the root cause rather than addressing surface-level symptoms. By asking "Why?" five times or more, depending on the complexity of the problem, you and your team members can gain valuable insights into the chain of events or processes that led to the issue. This method helps expose weaknesses, improve processes, and achieve project goals.

SWOT Analysis in Project Management

A SWOT analysis is a valuable tool in project management that helps identify and evaluate the internal pros and cons, weaknesses and strengths, and the external impacts that can threaten your project. By examining these factors, project managers can better understand the project's current state and potential risks.

SWOT analysis provides insights that help decision-making, resource allocation, and risk mitigation strategies. It allows project teams to counter threats, address weaknesses, and capitalize on strengths, ultimately enhancing project success.

Bring in a Facilitator

A skilled facilitator can provide objective guidance, ensure everyone's participation, and create a safe space for open discussions. They can help the project team effectively identify and evaluate strengths, weaknesses, opportunities, and threats.

Additionally, a facilitator can assist in summarizing and documenting the analysis, ensuring clarity and alignment among team members. Bringing in a facilitator enhances quality and efficiency, leading to better project outcomes.

Root Cause Analysis

Root Cause Analysis is a systematic approach used to identify the underlying causes of problems or incidents. It involves investigating the factors contributing to an issue rather than just addressing the symptoms.

By understanding the root causes, organizations can develop effective solutions to prevent similar problems from recurring in the future. This analysis helps improve processes, enhance quality, and reduce risks, ultimately leading to better outcomes and customer satisfaction.

Kipling Method

Also known as the 6 W's, this technique is used to gather information and comprehensively understand a situation. It involves asking and answering six key questions: Who, What, Where, When, Why, and How. Addressing these questions helps team members and leaders analyze and evaluate a problem or decision from various angles, ensuring a thorough examination of the topic at hand. This method is widely used in journalism, problem-solving, and decision-making processes.

Work Backward

Working backward is a problem-solving approach where you start with the desired outcome and then identify the steps needed to achieve it. This method allows you to break down complex problems into smaller, manageable tasks.

By starting with the end goal in mind, you can create a clear roadmap and prioritize actions accordingly. Working backward helps ensure that your efforts are focused and aligned with the desired outcome, leading to more efficient and effective problem-solving.

Trial and Error

Trial and Error is a problem-solving approach that involves trying different solutions and learning from the outcomes. It is a standard method used to discover what works and what doesn't in various situations. By systematically testing different options, you can identify the most effective solution through a process of elimination.

Trial and Error allow team members flexibility and adaptability, as it encourages learning from mistakes and refining strategies based on feedback. This approach can be beneficial when dealing with complex or ambiguous problems that require experimentation.

Risk Analysis and Mitigation within Teams

Risk analysis and mitigation play a crucial role in project management. By identifying and planning for potential risks, teams can prevent problems. One effective way to facilitate this process is by utilizing project management software.

Project management software such as ActiveCollab provides a centralized platform where teams can document and track risks throughout the project lifecycle. This software often includes features such as risk registers , where risks can be identified, categorized, and assigned to team members for mitigation. Additionally, the software may offer risk assessment tools that help teams evaluate the impact and likelihood of each risk.

With ActiveCollab, teams can collaborate in real time, ensuring all members can access the latest risk information. This promotes transparency and allows immediate communication and decision-making regarding risk mitigation strategies.

Using project management software for risk analysis and mitigation, your team members can proactively address potential challenges, minimize project disruptions, and improve project success rates.

Implementing Conflict Resolution Techniques

Conflict resolution techniques are essential for maintaining healthy relationships and fostering a positive work environment. Some effective methods include active listening, communication skills training, mediation, negotiation, and compromise. Conflicts can be understood and resolved more effectively by actively listening to all parties involved and encouraging open and honest communication.

Mediation allows a neutral third party to facilitate discussions, while negotiation and compromise help find mutually agreeable solutions. These techniques promote understanding, empathy, and collaboration, improving relationships and increasing productivity.

Scenario Planning and Forecasting

Scenario planning and forecasting are essential tools used by organizations to anticipate and prepare for future uncertainties. Scenario planning involves creating multiple plausible narratives or scenarios to explore possible futures, allowing decision-makers to identify risks and opportunities. Forecasting, on the other hand, uses historical data and statistical models to project future outcomes.

Combining these approaches allows businesses to develop robust strategies and make informed decisions in an ever-changing and unpredictable environment. This proactive approach helps organizations adapt, minimize risks, and seize opportunities, ensuring long-term success and resilience in an uncertain world.

Brainstorming and Ideation Sessions

Brainstorming and ideation sessions are great for generating creative ideas and solutions. You can bring together a diverse group of individuals while these sessions help them with collaboration and free thinking. Participants in brainstorming sessions are encouraged to share their thoughts and ideas without judgment, allowing for a wide range of possibilities to be explored.

The goal is to generate as many ideas as possible, with the understanding that quantity leads to quality. Through active listening and open-mindedness, participants can build upon each other's ideas and spark new insights. This collaborative process fosters innovation and can lead to breakthrough solutions to complex problems.

Design Thinking

Design Thinking is a problem-solving approach that emphasizes empathy, creativity, and collaboration. It involves understanding the needs and experiences of users, generating a wide range of ideas, prototyping, testing solutions, and iterating based on feedback.

It encourages a human-centered and iterative mindset, which leads to exploring multiple possibilities before arriving at a final solution. Design Thinking enables teams to approach challenges with an open mind, fostering innovation and driving meaningful change. By putting people at the heart of the process, Design Thinking helps create solutions that meet their needs and aspirations.

Creating a Feedback Loop with Team Members

Creating a feedback loop with team members leads to a culture of continuous improvement. Regularly soliciting positive and constructive feedback allows open communication, builds trust, and enhances teamwork. Encourage team members to share their thoughts, ideas, and concerns in a safe and non-judgmental environment.

Actively listen to their feedback, acknowledge their contributions, and provide actionable insights to help them grow professionally. Remember, a well-functioning feedback loop promotes collaboration, boosts morale, and ultimately leads to better outcomes for the entire team.

Agile Principles for Efficient Problem-Solving (Enhance Flexibility and Responsiveness)

Agile principles are values and practices that enhance flexibility and responsiveness in problem-solving. These principles prioritize individuals and interactions, working solutions, customer collaboration, and responding to change.

Agile principles promote a more efficient problem-solving process by encouraging frequent communication and collaboration. Iterative development, continuous feedback, and adaptive planning are key components of agile problem-solving, allowing teams to adapt and respond to changing requirements quickly. Focusing on delivering value to the customer and embracing change enables organizations to address problems efficiently and effectively.

Importance of Effective Problem-Solving

Effective problem-solving is crucial in project management as it ensures that issues are identified, analyzed, and resolved promptly and efficiently. By integrating problem-solving strategies with project management software like ActiveCollab, teams can enhance collaboration and streamline workflow.

Integrating problem-solving strategies with project management software allows for better communication and coordination among team members. It enables teams to track the progress of problem-solving activities, assign tasks, and monitor deadlines, ensuring everyone is on the same page. This integration also facilitates the sharing of information and knowledge, enabling teams to leverage their collective expertise and experience.

Moreover, project management software such as ActiveCollab provides a centralized platform where team members can document and access relevant information, making it easier to analyze problems and make informed decisions. It also allows the implementation of feedback loops, enabling continuous improvement and learning from past experiences.

In conclusion, integrating problem-solving strategies with ActiveCollab enhances teamwork, improves communication, and facilitates the efficient resolution of issues. This integration ultimately contributes to the successful execution of projects and achieving desired outcomes.

Chat Etiquette Cheat Sheet

All Newsletter subscribers can download this (and other) ActiveCollab Project Management Guides.

*Enter your email address and subscribe to our newsletter to get your hands on this, as well as many other free project management guides.

Sorry, we could not subscribe you at this moment. please double check your email address. If issue still persist, please let us know by sending an email to [email protected]

Make Real Work Happen!

Start your trial today, free for 14 days! Onboard your team, plan, collaborate, organize your work, and get paid.

By signing up you are agreeing to the ActiveCollab Terms of Service & Privacy Policy .

Great, just a few seconds and you're in.

We detected that you already have an ActiveCollab account

You can log in to existing account or you may start a new one

Great, your account has been created!

You will be redirected to your new account in a couple of seconds.

Sorry, we could not create an account for you at this moment.

Please double check your email address. If the issue still persists, please let us know by sending an email to [email protected]

Sign up for ActiveCollab newsletter!

Choose your favorite topics and we'll send our stories from the tech front lines straight to your inbox.

Unsubscribe at any time * Privacy Policy

Just a second

Thank you for subscribing to our newsletter.

Oops, something went wrong! Please try again later.

Related Articles

Team Conflicts - Dealing And Solving Them

Project Planning - A Practical Guide

Start your free trial.

Enter your email to get 14 days of ActiveCollab absolutely free, without any limitations.

Mark as disposable account.

ActiveCollab Is Using Cookies

By accepting all cookies you are giving us permission to use our tracking technologies to personalize your content and provide you the best possible experience on our website. Essential cookies are always on as we need them to make sure our website is working properly.

Read more about our cookie policy.

Learn Creative Problem Solving Techniques to Stimulate Innovation in Your Organization

By Kate Eby | October 20, 2017 (updated August 27, 2021)

• Share on Facebook
• Share on LinkedIn

Link copied

In today’s competitive business landscape, organizations need processes in place to make strong, well-informed, and innovative decisions. Problem solving - in particular creative problem solving (CPS) - is a key skill in learning how to accurately identify problems and their causes, generate potential solutions, and evaluate all the possibilities to arrive at a strong corrective course of action. Every team in any organization, regardless of department or industry, needs to be effective, creative, and quick when solving problems. 

In this article, we’ll discuss traditional and creative problem solving, and define the steps, best practices, and common barriers associated. After that, we’ll provide helpful methods and tools to identify the cause(s) of problematic situations, so you can get to the root of the issue and start to generate solutions. Then, we offer nearly 20 creative problem solving techniques to implement at your organization, or even in your personal life. Along the way, experts weigh in on the importance of problem solving, and offer tips and tricks. 

What Is Problem Solving and Decision Making?

Problem solving is the process of working through every aspect of an issue or challenge to reach a solution. Decision making is choosing one of multiple proposed solutions  — therefore, this process also includes defining and evaluating all potential options. Decision making is often one step of the problem solving process, but the two concepts are distinct. 

Collective problem solving is problem solving that includes many different parties and bridges the knowledge of different groups. Collective problem solving is common in business problem solving because workplace decisions typically affect more than one person. 

Problem solving, especially in business, is a complicated science. Not only are business conflicts multifaceted, but they often involve different personalities, levels of authority, and group dynamics. In recent years, however, there has been a rise in psychology-driven problem solving techniques, especially for the workplace. In fact, the psychology of how people solve problems is now studied formally in academic disciplines such as psychology and cognitive science.

Joe Carella is the Assistant Dean for Executive Education at the University of Arizona . Joe has over 20 years of experience in helping executives and corporations in managing change and developing successful business strategies. His doctoral research and executive education engagements have seen him focus on corporate strategy, decision making and business performance with a variety of corporate clients including Hershey’s, Chevron, Fender Musical Instruments Corporation, Intel, DP World, Essilor, BBVA Compass Bank.

He explains some of the basic psychology behind problem solving: “When our brain is engaged in the process of solving problems, it is engaged in a series of steps where it processes and organizes the information it receives while developing new knowledge it uses in future steps. Creativity is embedded in this process by incorporating diverse inputs and/or new ways of organizing the information received.”

Laura MacLeod is a Professor of Social Group Work at City University of New York, and the creator of From The Inside Out Project® , a program that coaches managers in team leadership for a variety of workplaces. She has a background in social work and over two decades of experience as a union worker, and currently leads talks on conflict resolution, problem solving, and listening skills at conferences across the country. 

MacLeod thinks of problem solving as an integral practice of successful organizations. “Problem solving is a collaborative process — all voices are heard and connected, and resolution is reached by the group,” she says. “Problems and conflicts occur in all groups and teams in the workplace, but if leaders involve everyone in working through, they will foster cohesion, engagement, and buy in. Everybody wins.”

10 tips that will make you more productive.

Uncover the top three factors that are killing your productivity and 10 tips to help you overcome them.

Download the free e-book to overcome my productivity killers

Project Management Guide

Your one-stop shop for everything project management

Ready to get more out of your project management efforts? Visit our comprehensive project management guide for tips, best practices, and free resources to manage your work more effectively.

View the guide

What Is the First Step in Solving a Problem?

Although problem solving techniques vary procedurally, experts agree that the first step in solving a problem is defining the problem. Without a clear articulation of the problem at stake, it is impossible to analyze all the key factors and actors, generate possible solutions, and then evaluate them to pick the best option. 

Dr. Elliott Jaffa is a behavioral and management psychologist with over 25 years of problem solving training and management experience. “Start with defining the problem you want to solve,” he says, “And then define where you want to be, what you want to come away with.” He emphasizes these are the first steps in creating an actionable, clear solution. 

Bryan Mattimore is Co-Founder of Growth Engine, an 18-year old innovation agency based in Norwalk, CT. Bryan has facilitated over 1,000 ideation sessions and managed over 200 successful innovation projects leading to over $3 billion in new sales. His newest book is 21 Days to a Big Idea . When asked about the first critical component to successful problem solving, Mattimore says, “Defining the challenge correctly, or ‘solving the right problem’ … The three creative techniques we use to help our clients ‘identify the right problem to be solved’ are questioning assumptions, 20 questions, and problem redefinition. A good example of this was a new product challenge from a client to help them ‘invent a new iron. We got them to redefine the challenge as first: a) inventing new anti-wrinkle devices, and then b) inventing new garment care devices.”

What Are Problem Solving Skills?

To understand the necessary skills in problem solving, you should first understand the types of thinking often associated with strong decision making. Most problem solving techniques look for a balance between the following binaries:

• Convergent vs. Divergent Thinking: Convergent thinking is bringing together disparate information or ideas to determine a single best answer or solution. This thinking style values logic, speed, and accuracy, and leaves no chance for ambiguity. Divergent thinking is focused on generating new ideas to identify and evaluate multiple possible solutions, often uniting ideas in unexpected combinations. Divergent thinking is characterized by creativity, complexity, curiosity, flexibility, originality, and risk-taking.
• Pragmatics vs. Semantics: Pragmatics refer to the logic of the problem at hand, and semantics is how you interpret the problem to solve it. Both are important to yield the best possible solution.
• Mathematical vs. Personal Problem Solving: Mathematical problem solving involves logic (usually leading to a single correct answer), and is useful for problems that involve numbers or require an objective, clear-cut solution. However, many workplace problems also require personal problem solving, which includes interpersonal, collaborative, and emotional intuition and skills. 

The following basic methods are fundamental problem solving concepts. Implement them to help balance the above thinking models.

• Reproductive Thinking: Reproductive thinking uses past experience to solve a problem. However, be careful not to rely too heavily on past solutions, and to evaluate current problems individually, with their own factors and parameters. 
• Idea Generation: The process of generating many possible courses of action to identify a solution. This is most commonly a team exercise because putting everyone’s ideas on the table will yield the greatest number of potential solutions. 

However, many of the most critical problem solving skills are “soft” skills: personal and interpersonal understanding, intuitiveness, and strong listening. 

Mattimore expands on this idea: “The seven key skills to be an effective creative problem solver that I detail in my book Idea Stormers: How to Lead and Inspire Creative Breakthroughs are: 1) curiosity 2) openness 3) a willingness to embrace ambiguity 4) the ability to identify and transfer principles across categories and disciplines 5) the desire to search for integrity in ideas, 6) the ability to trust and exercise “knowingness” and 7) the ability to envision new worlds (think Dr. Seuss, Star Wars, Hunger Games, Harry Potter, etc.).”

“As an individual contributor to problem solving it is important to exercise our curiosity, questioning, and visioning abilities,” advises Carella. “As a facilitator it is essential to allow for diverse ideas to emerge, be able to synthesize and ‘translate’ other people’s thinking, and build an extensive network of available resources.”

MacLeod says the following interpersonal skills are necessary to effectively facilitate group problem solving: “The abilities to invite participation (hear all voices, encourage silent members), not take sides, manage dynamics between the monopolizer, the scapegoat, and the bully, and deal with conflict (not avoiding it or shutting down).” 

Furthermore, Jaffa explains that the skills of a strong problem solver aren’t measurable. The best way to become a creative problem solver, he says, is to do regular creative exercises that keep you sharp and force you to think outside the box. Carella echoes this sentiment: “Neuroscience tells us that creativity comes from creating novel neural paths. Allow a few minutes each day to exercise your brain with novel techniques and brain ‘tricks’ – read something new, drive to work via a different route, count backwards, smell a new fragrance, etc.”

What Is Creative Problem Solving? History, Evolution, and Core Principles

Creative problem solving (CPS) is a method of problem solving in which you approach a problem or challenge in an imaginative, innovative way. The goal of CPS is to come up with innovative solutions, make a decision, and take action quickly. Sidney Parnes and Alex Osborn are credited with developing the creative problem solving process in the 1950s. The concept was further studied and developed at SUNY Buffalo State and the Creative Education Foundation. 

The core principles of CPS include the following:

• Balance divergent and convergent thinking
• Ask problems as questions
• Defer or suspend judgement
• Focus on “Yes, and…” rather than “No, but…”

According to Carella, “Creative problem solving is the mental process used for generating innovative and imaginative ideas as a solution to a problem or a challenge. Creative problem solving techniques can be pursued by individuals or groups.”

When asked to define CPS, Jaffa explains that it is, by nature, difficult to create boundaries for. “Creative problem solving is not cut and dry,” he says, “If you ask 100 different people the definition of creative problem solving, you’ll get 100 different responses - it’s a non-entity.”

Business presents a unique need for creative problem solving. Especially in today’s competitive landscape, organizations need to iterate quickly, innovate with intention, and constantly be at the cutting-edge of creativity and new ideas to succeed. Developing CPS skills among your workforce not only enables you to make faster, stronger in-the-moment decisions, but also inspires a culture of collaborative work and knowledge sharing. When people work together to generate multiple novel ideas and evaluate solutions, they are also more likely to arrive at an effective decision, which will improve business processes and reduce waste over time. In fact, CPS is so important that some companies now list creative problem solving skills as a job criteria.

MacLeod reiterates the vitality of creative problem solving in the workplace. “Problem solving is crucial for all groups and teams,” she says. “Leaders need to know how to guide the process, hear all voices and involve all members - it’s not easy.”

“This mental process [of CPS] is especially helpful in work environments where individuals and teams continuously struggle with new problems and challenges posed by their continuously changing environment,” adds Carella. 

Problem Solving Best Practices

By nature, creative problem solving does not have a clear-cut set of do’s and don’ts. Rather, creating a culture of strong creative problem solvers requires flexibility, adaptation, and interpersonal skills. However, there are a several best practices that you should incorporate:

• Use a Systematic Approach: Regardless of the technique you use, choose a systematic method that satisfies your workplace conditions and constraints (time, resources, budget, etc.). Although you want to preserve creativity and openness to new ideas, maintaining a structured approach to the process will help you stay organized and focused. 
• View Problems as Opportunities: Rather than focusing on the negatives or giving up when you encounter barriers, treat problems as opportunities to enact positive change on the situation. In fact, some experts even recommend defining problems as opportunities, to remain proactive and positive.
• Change Perspective: Remember that there are multiple ways to solve any problem. If you feel stuck, changing perspective can help generate fresh ideas. A perspective change might entail seeking advice of a mentor or expert, understanding the context of a situation, or taking a break and returning to the problem later. “A sterile or familiar environment can stifle new thinking and new perspectives,” says Carella. “Make sure you get out to draw inspiration from spaces and people out of your usual reach.”
• Break Down Silos: To invite the greatest possible number of perspectives to any problem, encourage teams to work cross-departmentally. This not only combines diverse expertise, but also creates a more trusting and collaborative environment, which is essential to effective CPS. According to Carella, “Big challenges are always best tackled by a group of people rather than left to a single individual. Make sure you create a space where the team can concentrate and convene.”
• Employ Strong Leadership or a Facilitator: Some companies choose to hire an external facilitator that teaches problem solving techniques, best practices, and practicums to stimulate creative problem solving. But, internal managers and staff can also oversee these activities. Regardless of whether the facilitator is internal or external, choose a strong leader who will value others’ ideas and make space for creative solutions.  Mattimore has specific advice regarding the role of a facilitator: “When facilitating, get the group to name a promising idea (it will crystalize the idea and make it more memorable), and facilitate deeper rather than broader. Push for not only ideas, but how an idea might specifically work, some of its possible benefits, who and when would be interested in an idea, etc. This fleshing-out process with a group will generate fewer ideas, but at the end of the day will yield more useful concepts that might be profitably pursued.” Additionally, Carella says that “Executives and managers don’t necessarily have to be creative problem solvers, but need to make sure that their teams are equipped with the right tools and resources to make this happen. Also they need to be able to foster an environment where failing fast is accepted and celebrated.”
• Evaluate Your Current Processes: This practice can help you unlock bottlenecks, and also identify gaps in your data and information management, both of which are common roots of business problems.

MacLeod offers the following additional advice, “Always get the facts. Don’t jump too quickly to a solution – working through [problems] takes time and patience.”

Mattimore also stresses that how you introduce creative problem solving is important. “Do not start by introducing a new company-wide innovation process,” he says. “Instead, encourage smaller teams to pursue specific creative projects, and then build a process from the ground up by emulating these smaller teams’ successful approaches. We say: ‘You don’t innovate by changing the culture, you change the culture by innovating.’”

Barriers to Effective Problem Solving

Learning how to effectively solve problems is difficult and takes time and continual adaptation. There are several common barriers to successful CPS, including:

• Confirmation Bias: The tendency to only search for or interpret information that confirms a person’s existing ideas. People misinterpret or disregard data that doesn’t align with their beliefs.
• Mental Set: People’s inclination to solve problems using the same tactics they have used to solve problems in the past. While this can sometimes be a useful strategy (see Analogical Thinking in a later section), it often limits inventiveness and creativity.
• Functional Fixedness: This is another form of narrow thinking, where people become “stuck” thinking in a certain way and are unable to be flexible or change perspective.
• Unnecessary Constraints: When people are overwhelmed with a problem, they can invent and impose additional limits on solution avenues. To avoid doing this, maintain a structured, level-headed approach to evaluating causes, effects, and potential solutions.
• Groupthink: Be wary of the tendency for group members to agree with each other — this might be out of conflict avoidance, path of least resistance, or fear of speaking up. While this agreeableness might make meetings run smoothly, it can actually stunt creativity and idea generation, therefore limiting the success of your chosen solution.
• Irrelevant Information: The tendency to pile on multiple problems and factors that may not even be related to the challenge at hand. This can cloud the team’s ability to find direct, targeted solutions.
• Paradigm Blindness: This is found in people who are unwilling to adapt or change their worldview, outlook on a particular problem, or typical way of processing information. This can erode the effectiveness of problem solving techniques because they are not aware of the narrowness of their thinking, and therefore cannot think or act outside of their comfort zone.

According to Jaffa, the primary barrier of effective problem solving is rigidity. “The most common things people say are, ‘We’ve never done it before,’ or ‘We’ve always done it this way.’” While these feelings are natural, Jaffa explains that this rigid thinking actually precludes teams from identifying creative, inventive solutions that result in the greatest benefit.

“The biggest barrier to creative problem solving is a lack of awareness – and commitment to – training employees in state-of-the-art creative problem-solving techniques,” Mattimore explains. “We teach our clients how to use ideation techniques (as many as two-dozen different creative thinking techniques) to help them generate more and better ideas. Ideation techniques use specific and customized stimuli, or ‘thought triggers’ to inspire new thinking and new ideas.” 

MacLeod adds that ineffective or rushed leadership is another common culprit. “We're always in a rush to fix quickly,” she says. “Sometimes leaders just solve problems themselves, making unilateral decisions to save time. But the investment is well worth it — leaders will have less on their plates if they can teach and eventually trust the team to resolve. Teams feel empowered and engagement and investment increases.”

Strategies for Problem Cause Identification

As discussed, most experts agree that the first and most crucial step in problem solving is defining the problem. Once you’ve done this, however, it may not be appropriate to move straight to the solution phase. Rather, it is often helpful to identify the cause(s) of the problem: This will better inform your solution planning and execution, and help ensure that you don’t fall victim to the same challenges in the future. 

Below are some of the most common strategies for identifying the cause of a problem:

• Root Cause Analysis: This method helps identify the most critical cause of a problem. A factor is considered a root cause if removing it prevents the problem from recurring. Performing a root cause analysis is a 12 step process that includes: define the problem, gather data on the factors contributing to the problem, group the factors based on shared characteristics, and create a cause-and-effect timeline to determine the root cause. After that, you identify and evaluate corrective actions to eliminate the root cause.

‌ Download Fishbone Diagram Template - Excel

Download 5 Whys Template   Excel  |  Word  |  PDF   

Problem Solving Techniques and Strategies

In this section, we’ll explain several traditional and creative problem solving methods that you can use to identify challenges, create actionable goals, and resolve problems as they arise. Although there is often procedural and objective crossover among techniques, they are grouped by theme so you can identify which method works best for your organization.

Divergent Creative Problem Solving Techniques

Brainstorming: One of the most common methods of divergent thinking, brainstorming works best in an open group setting where everyone is encouraged to share their creative ideas. The goal is to generate as many ideas as possible – you analyze, critique, and evaluate the ideas only after the brainstorming session is complete. To learn more specific brainstorming techniques, read this article . 

Mind Mapping: This is a visual thinking tool where you graphically depict concepts and their relation to one another. You can use mind mapping to structure the information you have, analyze and synthesize it, and generate solutions and new ideas from there. The goal of a mind map is to simplify complicated problems so you can more clearly identify solutions.

Appreciative Inquiry (AI): The basic assumption of AI is that “an organization is a mystery to be embraced.” Using this principle, AI takes a positive, inquisitive approach to identifying the problem, analyzing the causes, and presenting possible solutions. The five principles of AI emphasize dialogue, deliberate language and outlook, and social bonding. 

Lateral Thinking: This is an indirect problem solving approach centered on the momentum of idea generation. As opposed to critical thinking, where people value ideas based on their truth and the absence of errors, lateral thinking values the “movement value” of new ideas: This means that you reward team members for producing a large volume of new ideas rapidly. With this approach, you’ll generate many new ideas before approving or rejecting any.

Problem Solving Techniques to Change Perspective

Constructive Controversy: This is a structured approach to group decision making to preserve critical thinking and disagreement while maintaining order. After defining the problem and presenting multiple courses of action, the group divides into small advocacy teams who research, analyze, and refute a particular option. Once each advocacy team has presented its best-case scenario, the group has a discussion (advocacy teams still defend their presented idea). Arguing and playing devil’s advocate is encouraged to reach an understanding of the pros and cons of each option. Next, advocacy teams abandon their cause and evaluate the options openly until they reach a consensus. All team members formally commit to the decision, regardless of whether they advocated for it at the beginning. You can learn more about the goals and steps in constructive controversy here . 

Carella is a fan of this approach. “Create constructive controversy by having two teams argue the pros and cons of a certain idea,” he says. “It forces unconscious biases to surface and gives space for new ideas to formulate.”

Abstraction: In this method, you apply the problem to a fictional model of the current situation. Mapping an issue to an abstract situation can shed extraneous or irrelevant factors, and reveal places where you are overlooking obvious solutions or becoming bogged down by circumstances. 

Analogical Thinking: Also called analogical reasoning , this method relies on an analogy: using information from one problem to solve another problem (these separate problems are called domains). It can be difficult for teams to create analogies among unrelated problems, but it is a strong technique to help you identify repeated issues, zoom out and change perspective, and prevent the problems from occurring in the future. .

CATWOE: This framework ensures that you evaluate the perspectives of those whom your decision will impact. The factors and questions to consider include (which combine to make the acronym CATWOE):

• Customers: Who is on the receiving end of your decisions? What problem do they currently have, and how will they react to your proposed solution?
• Actors: Who is acting to bring your solution to fruition? How will they respond and be affected by your decision?
• Transformation Process: What processes will you employ to transform your current situation and meet your goals? What are the inputs and outputs?
• World View: What is the larger context of your proposed solution? What is the larger, big-picture problem you are addressing?
• Owner: Who actually owns the process? How might they influence your proposed solution (positively or negatively), and how can you influence them to help you?
• Environmental Constraints: What are the limits (environmental, resource- and budget-wise, ethical, legal, etc.) on your ideas? How will you revise or work around these constraints?

Complex Problem Solving

Soft Systems Methodology (SSM): For extremely complex problems, SSM can help you identify how factors interact, and determine the best course of action. SSM was borne out of organizational process modeling and general systems theory, which hold that everything is part of a greater, interconnected system: This idea works well for “hard” problems (where logic and a single correct answer are prioritized), and less so for “soft” problems (i.e., human problems where factors such as personality, emotions, and hierarchy come into play). Therefore, SSM defines a seven step process for problem solving: 

• Begin with the problem or problematic situation 
• Express the problem or situation and build a rich picture of the themes of the problem 
• Identify the root causes of the problem (most commonly with CATWOE)
• Build conceptual models of human activity surrounding the problem or situation
• Compare models with real-world happenings
• Identify changes to the situation that are both feasible and desirable
• Take action to implement changes and improve the problematic situation

SSM can be used for any complex soft problem, and is also a useful tool in change management . 

Failure Mode and Effects Analysis (FMEA): This method helps teams anticipate potential problems and take steps to mitigate them. Use FMEA when you are designing (redesigning) a complex function, process, product, or service. First, identify the failure modes, which are the possible ways that a project could fail. Then, perform an effects analysis to understand the consequences of each of the potential downfalls. This exercise is useful for internalizing the severity of each potential failure and its effects so you can make adjustments or safeties in your plan. 

‌ Download FMEA Template  

Problem Solving Based on Data or Logic (Heuristic Methods)

TRIZ: A Russian-developed problem solving technique that values logic, analysis, and forecasting over intuition or soft reasoning. TRIZ (translated to “theory of inventive problem solving” or TIPS in English) is a systematic approach to defining and identifying an inventive solution to difficult problems. The method offers several strategies for arriving at an inventive solution, including a contradictions matrix to assess trade-offs among solutions, a Su-Field analysis which uses formulas to describe a system by its structure, and ARIZ (algorithm of inventive problem solving) which uses algorithms to find inventive solutions. 

Inductive Reasoning: A logical method that uses evidence to conclude that a certain answer is probable (this is opposed to deductive reasoning, where the answer is assumed to be true). Inductive reasoning uses a limited number of observations to make useful, logical conclusions (for example, the Scientific Method is an extreme example of inductive reasoning). However, this method doesn’t always map well to human problems in the workplace — in these instances, managers should employ intuitive inductive reasoning , which allows for more automatic, implicit conclusions so that work can progress. This, of course, retains the principle that these intuitive conclusions are not necessarily the one and only correct answer. 

Process-Oriented Problem Solving Methods

Plan Do Check Act (PDCA): This is an iterative management technique used to ensure continual improvement of products or processes. First, teams plan (establish objectives to meet desired end results), then do (implement the plan, new processes, or produce the output), then check (compare expected with actual results), and finally act (define how the organization will act in the future, based on the performance and knowledge gained in the previous three steps). 

Means-End Analysis (MEA): The MEA strategy is to reduce the difference between the current (problematic) state and the goal state. To do so, teams compile information on the multiple factors that contribute to the disparity between the current and goal states. Then they try to change or eliminate the factors one by one, beginning with the factor responsible for the greatest difference in current and goal state. By systematically tackling the multiple factors that cause disparity between the problem and desired outcome, teams can better focus energy and control each step of the process. 

Hurson’s Productive Thinking Model: This technique was developed by Tim Hurson, and is detailed in his 2007 book Think Better: An Innovator’s Guide to Productive Thinking . The model outlines six steps that are meant to give structure while maintaining creativity and critical thinking: 1) Ask “What is going on?” 2) Ask “What is success?” 3) Ask “What is the question?” 4) Generate answers 5) Forge the solution 6) Align resources. 

Control Influence Accept (CIA): The basic premise of CIA is that how you respond to problems determines how successful you will be in overcoming them. Therefore, this model is both a problem solving technique and stress-management tool that ensures you aren’t responding to problems in a reactive and unproductive way. The steps in CIA include:

• Control: Identify the aspects of the problem that are within your control.
• Influence: Identify the aspects of the problem that you cannot control, but that you can influence.
• Accept: Identify the aspects of the problem that you can neither control nor influence, and react based on this composite information. 

GROW Model: This is a straightforward problem solving method for goal setting that clearly defines your goals and current situation, and then asks you to define the potential solutions and be realistic about your chosen course of action. The steps break down as follows:

• Goal: What do you want?
• Reality: Where are you now?
• Options: What could you do?
• Will: What will you do?

OODA Loop: This acronym stands for observe, orient, decide, and act. This approach is a decision-making cycle that values agility and flexibility over raw human force. It is framed as a loop because of the understanding that any team will continually encounter problems or opponents to success and have to overcome them.

There are also many un-named creative problem solving techniques that follow a sequenced series of steps. While the exact steps vary slightly, they all follow a similar trajectory and aim to accomplish similar goals of problem, cause, and goal identification, idea generation, and active solution implementation.

MacLeod offers her own problem solving procedure, which echoes the above steps:

“1. Recognize the Problem: State what you see. Sometimes the problem is covert. 2. Identify: Get the facts — What exactly happened? What is the issue? 3. and 4. Explore and Connect: Dig deeper and encourage group members to relate their similar experiences. Now you're getting more into the feelings and background [of the situation], not just the facts.  5. Possible Solutions: Consider and brainstorm ideas for resolution. 6. Implement: Choose a solution and try it out — this could be role play and/or a discussion of how the solution would be put in place.  7. Evaluate: Revisit to see if the solution was successful or not.”

Many of these problem solving techniques can be used in concert with one another, or multiple can be appropriate for any given problem. It’s less about facilitating a perfect CPS session, and more about encouraging team members to continually think outside the box and push beyond personal boundaries that inhibit their innovative thinking. So, try out several methods, find those that resonate best with your team, and continue adopting new techniques and adapting your processes along the way. 

Improve Problem Solving with Work Management in Smartsheet

Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change. 

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed. 

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time.  Try Smartsheet for free, today.

Discover why over 90% of Fortune 100 companies trust Smartsheet to get work done.

A Short Guide to Problem Solving in Project Management (Expert Tips)

One of the foremost skills that makes you a great project manager is problem-solving.

When you are managing your projects, problems are inevitable. As we all have to face the same sort of situations even in our daily life. What makes the difference is knowledge and how efficiently you put in that knowledge to solve a current or impending issue.

Problem-solving is the process of observing what is going on in your environment; identifying things that could be changed or improved. kepner-tregoe

Problem-solving in project management is a strategic process. Hence, you can't achieve that skill overnight. It needs step-by-step learning, adopting a framework to do that, and obviously, maintaining some crucial considerations.

Well, in this short guide, we will show you some of the proven problem-solving methods to follow in project management. After you finish reading, you will be able to understand what are the most essential things you must do, and initiate a roadmap to become an efficient problem solver.

Importance of Problem Solving in Project Management

There are many reasons that you must learn the skill of problem-solving in project management. Before you get on with the top techniques or best practices, let's go through some of the key points that make problem-solving in project management a serious business.

• Fixing Broken Things in the Process
• Sort Out the Risks
• Improving performance
• Looking for Opportunities

1. Fixing Broken Things in the Process

Problem-solving demands a unique mentality. When you have that in mind, you can easily look after your projects with more intensity. Doing business and managing projects is a simultaneous thing . A well-developed problem-solving structure helps you to point out things that are broken, need improvement, or an update.

2. Sort Out the Risks

Identifying risks is crucial to your projects. The problem-solving framework helps you to understand the current state of your business. With sufficient data, you can easily sort out the risks that can be handled with proper resources.

3. Improving performance

Your projects and the employees are integral, they complement each other to reach a single goal – success and development. So, when you are all up to looking for a reliable solution to your problems, it also makes a good impact on your employees. Eventually, that leads to improving your overall performance.

4. Looking for Opportunities

The more you keep solving problems, you see the newest crack, broken things, and things that need an update. With the same process, you can learn to see the big picture, understand the nature of the big picture, and become capable to convey it as a project manager . Hence, you can sort out the risks and opportunities and the same time.

If you want to manage all your project activities right from your WordPress dashboard check this article on The Beginner’s Guide To WordPress Project Management .

5 Steps to Problem Solving in Project Management You Should Follow

As you already know, problem-solving skills demand a framework. As a project manager, you must streamline the most fitting methods following your expertise and resources. Below, we have sorted a handful of the most proven techniques that can make you a smart professional for problem-solving in project management.

Take a look at them one by one –

• Defining the Problem is Your First Priority
• Find Out the Reasons Behind the Problem
• Generating Ideas for Solutions
• Select the Most Fitting Solution
• Taking Action to Solve Your Problems

1. Defining the Problem is Your First Priority

The way you look at a problem, your employees won't. Because, when they see a problem, they want you to solve it for them, as you are the project manager. So, it's important for you to define the problem in the first place. For example, your team is continuously missing deadlines, so it's an issue from their end. To get to a viable solution, you must understand why your team is doing the same mistakes.

Understanding the nature of a problem is possible when you know why something is happening to your project, and why things keep getting in trouble. To figure it out, you can follow the 5W1H approach.

It means asking these six questions to define a problem in project management –

• Who   does the problem affect?
• What are the symptoms of the problem?
• Where does/ wherein the project did it happen?
• When does it happen?
• Why   does the problem take place?
• How does it happen?

So, asking this question would definitely help you to define your problem when you want to solve it in a smart and impeccable way.

Read more: How to Improve Team Productivity Using WP Project Manager .

2. Find Out the Reasons Behind the Problem

After you understand the nature of a problem, the next necessary step is to find out the reasons behind it and analyze them to the core. It is similar to finding the gap in your workflow and filling them one after another to reach a suitable solution. Therefore, finding reasons won't be hard if you follow a strategic approach.

For example, you can use a Fishbone diagram. It is a famous and useful process to find out the reasons for a problem. Well, what is a Fishbone diagram? Japanese organizational theorist Kaoru Ishikawa created it that is used to categorize the core reasons for a problem in a visual form.

Look above the picture. Suppose, the problem is your website is down. A Fishbone diagram will help you to note down the possible reasons that can cause your website to fall. By maintaining such a visual demonstration , you can get better and more effective regarding your problem-solving in project management.

Here are some unavoidable things – the reasons you note down, they ought to be real. From a lot of possible reasons, your job is to understand the real reasons. It is possible if you go for deep analysis. Hence, to do this, Root Cause Analysis (RCA) would be helpful.

3. Generating Ideas for Solutions

Now that you know which problem you need to solve, and what are the causes, you can go for generating ideas for the right solutions. It is a gradual step of problem-solving in project management. So, in this step, you have more liberty to become creative. The goal of this step is to find out a set of solutions. You need a reserve of solutions or alternative solutions evidently. They help you to reduce your risks. If one solution fails, you may go for an alternative approach.

Hence, you need to do a lot of mind work, research and gather ways to possible solutions. The two best ways of generating ideas are – brainstorming and mind mapping.

Mindtools explains that creative problem-solving works in four steps. They are – clarify, ideate, develop, implement.

The clarification stage makes you explore again your vision of the project and the nature of the problems. Then it guides to gathering necessary data and formulating questions. The following steps are all about expanding the framework with all of your understanding, data, resources, and goal to explore ideas, formulate solutions, and create a plan for implementation.

4. Select the Most Fitting Solution

It's not easy to select the right color when your wardrobe is full of similar clothing. But when you are determined, and know the etiquette and dress code of that particular program, your fashion sense lets you choose the color that is most fitting. The same thing always occurs while you are managing any projects and up to solve something.

After you have generated a lot of ideas and formulated a bunch of different solutions, hesitation is inevitable. So as a project manager, your problem-solving skill demands that you select the most useful and easiest way to sort out your trouble.

Well, the best ways to do that is to measure all the solutions, compare them with each other, and consider the following facts –

• Your expectation and priorities
• Evaluate all the solutions and measure them
• Consider your resources
• Go for the simplest one in the first place

However, you should never stop asking questions. Ask yourself, inspire your pupils working on the project to ask questions. The more question arises, the solution would be more effective and flawless.

5. Taking Action to Solve Your Problems

When you know what is your problem, and which solution you must implement, start right over. It's time to take action. Implementing a solution is the final step. But you must come through all the earlier steps to reach that level. It's an established framework to increase your skill as a problem solver.

Read More: 6 Interesting Project Management Ideas To Follow in 2023 .

How a Project Management Tool Can Help You in Problem-solving

In an age of automation, project management becomes easier because of tools that help you create an online database of your employees, clients, accounts, overall projects, etc. PM automation software lets you keep track of every process live, and ease your effort to make better decisions.

For example, if you have a PM automation tool like WP Project Manager , you're problem-solving in project management would be more viable and simple. Here's how –

• It ensures the best use of your resources and planning
• Robustly organize and track your projects and tasks
• Advanced management tool to make your tracking more efficient
• The tool will intensify your collaborative effort
• Generate a report so that you can see how your projects going on and what are your lackings

Overall, WP Project Manager has all the features that can make your workflow streamlined. When you see live updates and activities of your projects dashboard (including Kanban board, Gantt Chart, Task list, Calendar, etc), you can easily follow all the problem-solving steps with more efficiency. The job would be easier, nonetheless.

Bonus: A Quick Glimpse of Project Management Best Practices

To excel in project management, it is essential to follow industry best practices.

Here are some key best practices to consider:

• Define clear project objectives and success criteria at the beginning.
• Develop a comprehensive project plan that includes a detailed schedule, resource allocation, and risk management strategy.
• Establish a robust management process that can easily adjust to new changes.
• Foster a culture of open communication and collaboration throughout the project team.
• Regularly monitor project progress and key performance indicators.
• Proactively identify and mitigate project risks.
• Provide ongoing support and feedback to team members.
• Continuously learn from past projects and incorporate lessons learned into future projects.

Though it's not mandatory one strategy will work the same way for all industries. But if you have prior ideas, it would be easier for you to make constructive decisions.

By adopting these best practices, project managers can set themselves up for success and increase the likelihood of delivering projects on time and within budget.

Read more: 7 Project Management Strategies To Get Ahead Of The Game (Tips+Tool).

Closing Up for Problem-Solving in Project Management

Most problems are small in the beginning. As a resourceful project manager, your job is to solve them as soon as possible. The more you delay, the bigger the problem would grow. A ship often has many little glitches in the engine or cracks when it is on a long voyage. The smart captain is always in the loop to fix them simultaneously. As a project manager, your job is nothing less than that.

A strategic problem-solving framework will help you to cope with that loop, and a perfect project management automation tool lets you solve your problems faster (don't forget to add up flexibility, affordability, time management, and smartness).

So, here are our final words – keep innovating the newest ways to solve problems in your projects, and don't let your problem grow bigger than you.

Subscribe to weDevs blog

We send weekly newsletter, no spam for sure

Kaji Enamul Islam

Enamul is an author of fiction, eCommerce, digital business, and WordPress. Addicted to stories, facts, movies, and books. Loves traveling to unusual places.

Have something to say? Cancel Reply

Your email address will not be published.

Table of Contents

An Introduction to Problem Solving in Project Management

5 Steps to Identify and Eliminate Project-Halting Problems

Problem solving is a process for analysing a problem, and then developing and executing a solution. It is a task at which project managers must excel. There are many techniques that can be used for problem solving. The nature of the problem determines which is selected.

In this article, I describe a five-step process for problem solving that provides a systematic approach and helps improve the effectiveness of project management.

Step #1: Define the Problem

If you don’t understand the nature of the problem, then you cannot develop a sustainable solution.

For example, let’s say that a project team continuously misses deadlines. You may believe that the problem is caused by poor performance. On the other hand, the deadlines set may be too restrictive. The nature of the problem will determine the approach you take to solving it.

Step #2: Discover the Causes

Once you understand the problem, you can analyse it more deeply to discover the cause. The cause of a problem acts as a barrier to achieving your goals. Only by analysing the problem and determining the cause can you move to the next step in developing a solution.

It is important not to confuse cause with symptoms. If you only treat the symptoms, the underlying cause remains and will create more problems in the future.

Step #3: Develop Ideas for Solutions

Now it’s time to develop ideas to solve the problem. The wider the range of ideas, the more likely you are to choose a solution that is achievable and actionable.

This step is often achieved through a brainstorming process.

Step #4: Solution Selection

Of course, the point of developing a range of ideas for solutions is to ensure that the best is selected. One way to do this would be to conduct a trade-off analysis.

To do this, you must define the criteria for deciding which solution is best, usually as a series of weighted pros and cons. For each potential solution, the pros and cons are listed and its ranking is scored. The solution with the best ranking is the one that is selected.

Step #5: Put the Solution into Action

Having determined which is the solution of choice, the project manager should develop an action plan. This should include resources needed, budget, timetables, and all those involved. The solution is often run as a mini-project.

Despite PRINCE2’s framework and planning process – which seeks to anticipate risks and problems so that mitigating action can be taken ahead of potential problems becoming issues – all projects may suffer from unforeseen events and circumstances.

This five-step process for problem solving will increase a project manager’s capability to handle problems should they arise during a project – and project managers who react swiftly and decisively to problems have greater success in delivering expected project outcomes.

In our next article, I discuss several techniques which might be used to run effective problem-solving meetings in project management. In the meantime, for project management and project management training that motivates your employees, contact Your Project Manager:

© Your Project Manager 2013 | Web Design Brisbane

• On-Site Project Management Training/Coaching
• PRINCE2® Training and Implementation in Brisbane
• PMBOK Training

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

HotPMO News -Find out what’s happening in our business, and in the world of PMO

• January 28, 2024

In the fast-paced world of Project Management Offices (PMOs), effective problem-solving is a key skill that PMO Analysts and PMO Managers must master. From aligning projects with strategic objectives to ensuring smooth operational workflows, problem-solving skills are used daily in the PMOs, in projects, and when managing portfolios. In this post, we’ll explore why it’s a critical skill for PMO managers and analysts and discuss some effective techniques and mindsets that can enhance your problem-solving capabilities.

Why Problem-Solving Matters in PMO

Problem-solving in PMO goes beyond fixing immediate issues; it’s about identifying and addressing the root causes of challenges to prevent recurrence and drive continuous improvement. In a strategic sense, it ensures that projects align with the organization’s broader goals, enabling better resource allocation and risk management. And when it comes to running and operating the PMO, problem-solving skills are used to refine methodologies, improve team dynamics, and swiftly adapt to changes – crucial in today’s dynamic project and agile environments.

Four Effective Techniques for PMO Problem-Solving

Here are four of our favourite, road-tested techniques for solving problems in the PMO. Too much reading? Scroll to the bottom of the page, and we have a handy video digest for you!

1: The STOP Method

Quick and efficient, the STOP method stands for:

• Stop : Don’t react impulsively. Pause and assess the situation.
• Think : Consider the problem and potential causes briefly.
• Options : Brainstorm possible solutions quickly.
• Proceed : Choose the most suitable option and act on it.

The STOP method is perfect for immediate response to unforeseen challenges in project management.

2: The A3 Process

Originating from Lean methodology, the A3 process is a structured approach to problem-solving. It involves:

• Defining the problem and the current situation.
• Setting realistic goals.
• Performing root cause analysis.
• Developing countermeasures.
• Implementing a plan and following up. A3 encourages a thorough examination of problems and fosters a systematic approach to solving them.

Learn more about A3 Analysis here: https://www.hotpmo.com/management-models/a3-analysis-a-powerful-problem-solving-tool-for-pmo-managers/ 

3: Fishbone Diagram (Ishikawa Diagram) :

• This technique, developed by Kaoru Ishikawa, helps identify a problem’s root causes. It visually maps out the various causes leading to an effect (the problem) and categorizes them, often into factors like People, Processes, Policies, and Environment.
• It’s particularly useful for complex problems where multiple contributing factors must be understood and addressed.

4: Empathy Mapping :

• Empathy Mapping is a tool for gaining insight into stakeholders or customers. It involves creating a visual map articulating what a specific group or individual thinks, feels, sees, and does. This understanding can lead to better problem-solving by aligning solutions more closely with stakeholder needs and experiences.
• It’s particularly useful in PMO for understanding the perspectives of project stakeholders, ensuring that solutions are not just technically sound but also empathically aligned with user needs and expectations.

5: Thinking Hats

Created by Edward de Bono, the Thinking Hat technique is great for helping everyone see a problem from the same perspective. It is also a great way of avoiding time lost in conflict. The thinking hat approach encourages everyone in the problem-solving team to wear different perspectives or hats one after the other. This method is particularly effective in group discussions and brainstorming sessions, allowing team members to shift their thinking and consider issues from multiple angles.

• White Hat : Focuses on data and facts. Used for objective analysis and neutral information gathering.
• Red Hat : This hat represents feelings, intuition, and emotions. It encourages the expression of emotions and gut reactions without justification.
• Black Hat : Concerned with caution and risk assessment. It helps identify potential barriers, weaknesses, or risks in a plan or decision.
• Yellow Hat : This hat symbolizes optimism and the exploration of positives. It is used to identify benefits and value in ideas and situations.
• Green Hat : This hat stands for creativity and new ideas. It encourages thinking outside the box and seeking alternative solutions.
• Blue Hat : Represents process control and organization. Used for managing the thinking process, summarizing insights, and outlining next steps.

Cultivating a Problem-Solving Mindset

Understanding the problem-solving mindset.

Solving problems is more than a skill; it’s a way of thinking that enables individuals to approach challenges with confidence, creativity, and efficiency. This mindset is characterized by a proactive approach, where problems are seen as opportunities to improve and innovate rather than mere obstacles to overcome. It involves thinking ahead, anticipating potential issues, and being prepared with strategies to mitigate them. In the dynamic environment of PMO, where projects are complex and ever-changing, such a mindset is invaluable.

The Importance of a Problem-Solving Mindset in PMO

The importance of a problem-solving mindset cannot be overstated in PMO roles. It’s essential for aligning projects with strategic goals, ensuring efficient execution, and adapting to new challenges. This mindset allows PMO professionals to break down complex problems into manageable components, assess them logically, and devise effective solutions. It’s not just about finding any solution but about finding the right one that aligns with the project’s objectives and the organization’s strategic direction.

Characteristics of a Problem-Solving Mindset

Those with a problem-solving mindset tend to be adaptable, resilient, and open-minded. They view challenges through a lens of curiosity, asking questions to understand the problem deeply before jumping to solutions. They are collaborative, recognizing that diverse perspectives can lead to more innovative solutions. Critical thinking is a cornerstone of this mindset; it involves evaluating situations objectively, questioning assumptions, and considering various solutions before deciding. Additionally, a problem-solving mindset is marked by a focus on continuous learning and development, understanding that skills and strategies must evolve to meet the changing demands of the project management landscape.

Nurturing Your Problem-Solving Mindset

Developing a problem-solving mindset is a journey of personal and professional growth. It starts with a willingness to embrace challenges and a commitment to continuous learning. This means staying updated with new PMO methodologies, learning from successes and setbacks and being open to feedback. It also involves cultivating resilience so that when faced with challenges, you can recover quickly and maintain a positive, solution-focused attitude. Mindfulness and stress management techniques can help maintain clarity of thought, especially in high-pressure situations. Finally, nurturing a problem-solving mindset involves embracing collaboration and empathy and understanding that effective solutions often come from understanding the needs and perspectives of all stakeholders involved.

Solving PMO problems at PMO HotHouse

PMO Hothouse is a monthly magazine show we deliver in partnership with the House of PMO team. In January 2024, we discussed problem-solving in the PMO – and we recorded it for you! Check it out below:

Problem-solving is a skill that can be developed and refined over time. It’s about more than just techniques; it’s about cultivating a mindset that embraces challenges as opportunities for growth. For PMO analysts and managers alike, mastering this skill means driving project success and contributing to their organization’s strategic achievements. For PMO Administrators, this is an essential skill you will need to hone if you are pursuing a promotion to Analyst in the future. Here are your homework tasks:

• The STOP method is quick to master and can be used in problem-solving, from negotiating with angry toddlers in the home environment to getting key projects back on track at work. Learn the STOP technique and practice it in everyday problem-solving challenges. Practice until it becomes second nature.
• Expand your problem-solving toolbox with other techniques from the list above.
• Nurture your problem-solving mindset, recognize when to shift mentally, and bring your problem-solving strengths to the foreground.

Remember, in the world of PMO, every problem is an opportunity to demonstrate your expertise, adaptability, and value. Enhancing your problem-solving skills and mindset makes you a key asset in any project management scenario.

Other news you might like

OKR – Objectives and Key Results

How Can Design Thinking Help You Achieve Better Results In Your Projects?

A3 Analysis: A Powerful Problem-Solving Tool for PMO Managers

Sign up for our newsletter.

Our newsletter is packed with tips and ideas that will put you on the fast-track to becoming that one person in your organization who always knows exactly what to do to deliver the right things, faster. Whether you’re agile or waterfall, project manager or PMO, we’ve got advice that will help you in your role

• 20-22 Wenlock Road
• London, N1 7GU
• Unit 1, Derwent Business Centre
• Clarke Street
• Derby, DE1 2BU

Tel: 02036272650

• TERMS OF SERVICE /
• PRIVACY POLICY /
• HotPMO.com is a trading name of HotPMO Ltd. Company number 12214149

• Unito home /
• The Project Manager’s Guide to Critical Thinking Skills

Remember playing the game Clue as a kid? You’d collect evidence, analyze the possibilities, and come to your own conclusions based on what you knew (and what you didn’t). As a project manager, the skills you developed playing games like Clue are extremely useful. The acting gatekeeper for your team, you’re used to evaluating information and making decisions to benefit your department and the business as a whole. Whether you’re a seasoned project manager or just learning the ropes, knowing how to fine-tune your critical thinking skills will come in handy every single day.

Continue reading to learn: 

• A definition of critical thinking
• The six critical skills project managers need
• Why critical thinking skills are crucial for project managers
• How to work your critical thinking muscles
• Effective critical thinking techniques

Let’s get critical. 

What is critical thinking?

Ask five different people what critical thinking means and you’ll probably get five different answers. But, generally speaking, critical thinking refers to intellectual tactics used to observe and analyze information to draw better conclusions. A key factor in critical thinking is looking beyond the surface of an idea, a concept, or a piece of information. It involves asking questions — to yourself or others — to go deeper and draw better conclusions.

Critical thinking can be used by anyone, in any role, to make their job easier. You can find new insights, optimize an inefficient process, and get projects done faster. Developing your critical thinking means building habits that follow you throughout your career.

Here’s a breakdown of crucial critical thinking skills for project managers — or any other role.

6 critical thinking skills for project managers

Skill #1: observation.

Critical thinking skills starts with being more aware of what’s going on. Working on an important project? Being observant might mean keeping a close eye on comments from collaborators, or just paying better attention during meetings with your data team. Becoming a more observant person means you can identify problems others miss or pick up on context clues that help you solve problems down the road.

Skill #2: Analysis

Spotting problems, clues, and that one important comment in a Slack thread is just the beginning. If observation is how you bring in more information, analysis is how you determine what you’re going to do with it. Having an analytical approach to your problems means knowing what information you have available, knowing how relevant each piece is to the problem at hand, and being able to ask better questions. 

Skill #3: Identifying bias

This critical thinking skill ties in closely with analysis but is important enough to be its own skill. Bias is inherent in everything we do, from collecting data to creating content and solving problems. For instance, because this blog post is being written by a marketer, it might use different examples than a writer from a more technical team. You can spot a bias by asking yourself questions, like “are there elements of this person’s experience or perspective that might be affecting what they’re saying?” Bias can affect every role in an organization.

Skill #4: Inference

This is a fancy term for drawing better conclusions. This crucial critical thinking skill helps you make better use of the information you collect, the questions you ask, and the potential problems you spot. Think of everything you might have done so far as putting ingredients in a stew. You can have the best ingredients in the world, but if you leave the pot on too long, you’ll end up with something closer to charcoal than stew.

One of the quickest ways to improve your inference skills is, ironically, by slowing down. Instead of blurting out the first conclusion that comes to mind, start with a few educated guesses, and compare them to each other. Which one makes the most sense? Which is weakest?

Skill #5: Problem-solving

If inference is how you come to better conclusions, problem-solving is how you put them into action. This critical thinking skill encompasses the tactics and strategies you use to take something that looks good on paper and make it great in practice. Problem-solving includes  planning  how you’ll solve a problem, but also reacting to hurdles along the way and staying flexible. A great way to improve your problem-solving skills is asking yourself “is this still the best way to solve the problem?” at every stage of your plan. Sometimes, people can get set in their ways, meaning they stick to an ineffective solution long after they should have pivoted to something else.

Skill #6: Curiosity

This is less a skill than it is a characteristic every critical thinker should work to develop. Every other critical thinking skill is helped by broadening having access to more information and more knowledge. For instance, you can be the most observant person in the world, but you’d still struggle to pick out all the problems in a presentation from the data team if you weren’t at least a little familiar with data analysis. Beyond expertise in specific fields, critical thinking — and thinking in general — is easier when you have a breadth of knowledge and experiences to draw from. You can find links that others would miss and learn to think in different ways. Read more books, listen to more podcasts, and approach the world at large with more curiosity.

Why do project managers need critical thinking skills? 

When people hear the phrase ‘critical thinking’, they often picture a negative person. Being a critical thinker doesn’t mean you have a bad attitude or that you aren’t a team player. It’s quite the opposite. 

Critical thinking means questioning processes, projects, and even core business practices that are widely accepted as given. Not to tear them down, but to improve them for the benefit of the entire team. 

The Project Management Institute (PMI) outlines how important this skill is: 

“Corporate leaders have put critical thinking at the top of the list of essential competencies needed by their workers to understand these challenges, explore opportunities, and make good decisions in this new competitive environment.” 

When used in the context of project management, effective critical thinking can: 

• Encourage deeper, more  productive discussions
• Facilitate open communication between team members 
• Resolve issues between team members and stakeholders more quickly
• Develop better solutions to problems 
• Reduce stress throughout a project 
• Prevent repetitive issues
• Achieve better results faster 

Now that you know why critical thinking skills are priority for project managers, it’s time to find out how you can improve yours.

How project managers can develop better critical thinking skills 

There’s one core principle that will guide your critical thinking: question everything. Project managers can’t just approve all requests that come in from stakeholders across the organization — unless they want a stressed-out, overworked team.

A good project manager knows how to prioritize projects according to the business’ overall needs and goals. With every request that comes in, you need to be prepared to evaluate the project’s impact on the business, the necessity of the project, and the why. Building this process — this instinct — into your daily work is how you build and strengthen your critical thinking skills.

For every potential project, consider: 

• Why is this important right now? While most stakeholders will say their project is urgent, you need to find out exactly how true this is. Perhaps the project could be scheduled for a later date that works better for your team’s schedule. 
• Why does my team need to be involved? For example, if you manage the creative team and a request for a sales presentation comes in, figure out exactly what your team will need to do.
• Why is my team’s time better spent on this project than other projects? Does this project contribute more to the business than other work your team could be doing? 

Those are three important questions to ask yourself, but what about the questions you ask others?

When a new project lands in your inbox, you need to know what to ask of the sender and how to delicately frame those questions. There are a few question formats that work especially well for this stage of the project. These include:

• ‘tell me more’ questions (eg. Tell me more about what will be required from each member of my team)
• ‘help me understand’ questions (eg. Help me understand why this project is urgent)
• ‘can you give me an example’ questions (eg. Can you give me an example of the types of results you’re looking for here?). 

These questions allow you to get a better understanding of the project and make sure it’s a good fit for your team. They’re also usually well-received by whoever initiated the project.

Prioritization means making tough calls, and project managers need to be ready and equipped to do so. You can’t be afraid to say no when the project doesn’t make sense from a timing or business standpoint. However, you will also need to be ready to explain the reasoning behind your “no”. The following techniques will help you feel confident in your decisions and authority as a project manager. 

Critical thinking techniques for project managers 

Critical thinking skills are one thing, but when evaluating the priority of a new project, there are critical thinking techniques you can put into practice to boost results and team morale. 

• Avoid making or accepting assumptions 
• Identify potential issues (and their consequences) from the start
• Use the Five Whys to find the root of problems 

Let’s dive into these a little bit more. 

1. Avoid assumptions 

You know what they say about assuming things. When you make assumptions as a project manager, you’re missing out on and ignoring key information that could make or break your project. You can have the best critical thinking skills in the office, but making the wrong assumption can undo all your hard work.

A big part of critical thinking is digging into reasoning and probing for evidence rather than drawing your own immediate conclusions. When you’re pitched a new project — and during the course of the entire project — question any preconceived notions (yours or theirs). Ensure you’re given concrete evidence for the viability of the project, and look for any holes in the process or strategy that could impact your team. 

When challenging assumptions, consider the following questions: 

• Am I assuming all members of this project have all the information they need to complete their tasks?
• What assumptions am I making about each team members’ skill sets? 
• Am I making assumptions about each team member’s time and availability? 
• What are some possible issues that may arise with this project? How can I work backwards and challenge any assumptions in order to avoid these issues? 
• What assumptions have I made about the stakeholder or project creator? What do they need to know? 

Never take anything for granted. When your job is to facilitate and manage expectations, it’s important that you’re questioning and challenging your own assumptions — and those of team members and stakeholders — at all stages of the process. 

2. Consider potential issues 

When you’re questioning assumptions, you’re also working towards another big part of your job: risk management. By proactively questioning what could go wrong, you can prepare for any issues that might arise during the course of the project. Not only that, but you can consider the implications and consequences of when things go awry. 

Consider a cause and effect approach with hypothetical — but realistic — issues. Give yourself an hour to write down any possible issues that could arise with the project, along with a list of consequences associated with each one. For example: 

• Problem : The video editor won’t have enough time to deliver the final file. 
• Consequence : The rest of the project will be held up. Costs will increase and we could miss the deadline.  

In a perfect world, project managers wouldn’t face any problems and all projects would be smooth sailing. Since that’s unfortunately not the case, here are some helpful tools you can use to avoid the escalation of issues — as well as repeating roadblocks with future projects.

3. Use the Five Whys

In addition to the “why” questions outlined above, a proven project management technique called “The Five Whys” can help you explore the true cause or causes of any problem. 

Here’s how ProjectManagement.com explains it: 

“5 Whys is an iterative elicitation method used to explore cause-and-effect relationships underlying a particular problem. The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question ‘Why?’. Each answer forms the basis of the next question.” 

To complete The Five Whys, you simply repeat the question “why?” five times until you come to the root of the problem. Each answer is understood to be a “contributing cause” that impacts the final result. 

For example: 

• Because multiple teams weren’t able to complete their tasks on time (contributing cause). 
• Because their time wasn’t prioritized properly (contributing cause). 
• Because multiple last-minute projects were assigned (contributing cause). 
• Because other stakeholders didn’t understand the prioritization and project assignment process (contributing cause). 
• Because they haven’t been properly trained or given the necessary information (root cause). 

Once you get to the root of the problem, you can take action to ensure these issues are minimized or avoided in the future. 

For project managers, sometimes taking a moment to just stop and consider all of the possibilities, consequences, and information can make all the difference between a well-thought-out decision and a future regret. Developing and exercising your critical thinking skills is a surefire way to drive positive business results.

How do project managers save time?

They use Unito to sync crucial data across tools like Trello, Jira, Asana, and more.

Find out how

How To Optimize Your Pre-Sales Support Workflow

Organizations need to keep growing to thrive. That growth depends on a team of sales representatives that take prospects from leads to closed deals. Often, that process relies on a sales rep identifying potential objections and squashing them. But when your sales team needs backup, how do you make sure that happens?

How to Use Basecamp Like a Pro

From the “campfire” chat, itemized to-do lists, and a space to organize shared files, Basecamp offers an elegant, simple solution for project management.

Related articles

Unlock the Power of Sync (Ebook)

Data integration isn’t a luxury, but most existing platforms haven’t stepped up to the plate in a meaningful way. In this ebook, you’ll learn how a 2-way sync can change the game for your organization.

Zapier vs. Unito: Which integration solution is for you?

Zapier is one of the most popular automation platforms out there. How does it stack up against Unito?

How to Export Jira Projects to Microsoft Excel (2 Methods)

Not everyone works in Jira, and sometimes you need to build reports for stakeholders. Here’s how you can export Jira issues to Excel and do just that.

• 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

Creativity and Problem-Solving Combine in Project Management Career

Marie Spark wanted to be a journalist. Then she discovered that what she loved doing—creative problem-solving and coordinating logistics—was project management.

Lecturer and Project Management program director Marie Spark loves preparing students for an industry experiencing surging growth. By 2020, it’s anticipated that 11 million project management jobs will be added by the United States and its 10 major trading partners. Marie’s classes emphasize hands-on, situational application of theory. The technical knowledge and advanced communication skills students gain makes all the difference on-the-job.

Marie’s own professional path started at UC Berkeley, where she majored in Rhetoric and minored in French. She couldn’t have predicted the career that followed. As Steve Jobs said, “You can’t connect the dots looking forward; you can only connect them looking backwards.”

From NPR to MBA

After discovering a passion for journalism, Marie landed an internship with NPR that, she later realized, was her first project management role. She loved tracking down information and coordinating studio interviews, but decided against a career in radio where job prospects were low.

She went back to school for her MBA and discovered the project management field—a mix of creative problem-solving and detail orientation that was an immediate fit. She took a consulting position with IBM and learned IT project management on-the-job before moving to Bank of America in IT project management.

“My strengths,” said Marie, “are that I dive into learning things and I’m not afraid to ask questions. I’m good at understanding complex concepts and explaining them. That’s a lot of what it takes to be a project manager.”

Six Sigma Certification

At Bank of America, Marie received Black Belt certification in Six Sigma, a set of tools for improving processes, products, and services. She also coached people pursuing Green Belt certification. When Marie was laid off from B of A, she seized the opportunity for growth and realized coaching others was what she loved most.

“I volunteered with the Project Management Institute’s San Francisco chapter in a leadership role—an amazing opportunity,” said Marie. “Through contacts I eventually was offered a teaching position at Golden Gate University. There’s tremendous value in volunteering with professional organizations and putting yourself out there because you never know where things will end up.”

Leadership and Problem-Solving Skills

Today, Marie equips students with crucial leadership and problem-solving skills like negotiation, motivation, and conflict resolution.

“There used to be the idea that project management is administrative overhead,” said Marie. “Today, companies are realizing that project management provides a structure that gives you the freedom to create change. Any business you can think of is going through massive transformation and in order to change effectively you need to understand how to manage projects. That’s why it’s exciting to be in project management.”

Leave a Reply Cancel reply

You must be logged in to post a comment.

From Biotech Expert to Entrepreneur: An MBA Alumni Story

Learn more about Golden Gate University’s MBA Program.

International Students — Golden Gate University Welcomes YOU!

Golden Gate University welcomes students of all nations to study in San Francisco, California — the business and innovation capital...

Golden Gate University 2019 Innovation in Practice Series

Yes! Hacking is legal … that is, when you hire a professional hacker to break into your company and test...

David Franklyn, Golden Gate University 2019 Innovation in Practice Series

Delve into fascinating ideas that are arising at the intersection of tech, law, and innovation with David Franklyn, Director of...

Keynote – Golden Gate University Undergraduate Commencement 2019

Dr. David J. Fike, Golden Gate University President, conferred an honorary doctorate degree to GGU Alumna and Salesforce.org EVP and...

Van Ton-Quinlivan, GGU 2019 Graduate Commencement Address

Dr. David J. Fike, Golden Gate University President, conferred an honorary doctorate degree to Van-Ton-Quilivan, who gave an inspirational talk...

Join L&T EduTech’s Faculty Immersion Program Exclusively for HODs & Senior Professors

10 - 15 June, 2024 Venue: L&T HQ, Manapakkam, Chennai

Unleashing Faculty Potential for Tangible Solutions

Shaping leaders through real world problem solving.

10-15 June 2024

L&T HQ, Chennai

Introduction

In today's fast-paced landscape, academia faces the ongoing challenges of evolving demands from diverse industries. Traditional problem-solving methods often fall short in addressing the dynamic needs of modern businesses, which have transitioned into what is now termed the project economy. Projects play a pivotal role in achieving organizational strategic objectives.

Effective leadership is essential for understanding stakeholder needs and translating creative ideas into successful outcomes. The essence of problem-solving lies in the ability to bridge the gap between creative ideation and successful execution. This entails transforming abstract concepts into actionable plans with clearly defined goals, timelines, and allocated resources. The iterative process of exploration, experimentation, and adaptation empowers academic leaders to deliver innovative solutions that not only tackle core challenges but also surpass expectations, driving sustainable long-term success.

The Faculty Immersion Program on Real World Problem Solving (FIP-RPS) aims to equip academicians with the skills and knowledge to prepare future-ready engineers and project managers. Rather than focusing solely on project management principles, this program adopts a problem-solving approach with an emphasis on effective leadership. Tailored for senior educators across various disciplines, this FIP-RPS stands as a beacon of empowerment in navigating the complexities of contemporary challenges.

About L&T IPM

The L&T Institute of Project Management (IPM) was established to offer long-term and short-term training programs on project management for the L&T group of companies and its eco-system partners (ONGC, HPCL, RIL, World Bank, Vedanta, TAFE, SAIL, Aditya Birla Group, Aramco IKTVA, and knowledge providers in the domain of civil and project management).

IPM has international and domestic academic collaborations with esteemed universities such as SDA Bocconi, Italy; University of Texas, Austin, USA; IIM Indore, India; and IIM Calcutta, India. L&T IPM also has collaborations with premier professional bodies, such as PMI (USA), AACE International (USA), RICS (UK), and the Construction Industry Institute (CII, University of Texas, USA).

The IPM has an excellent Knowledge Centre that provides a comprehensive collection of reference books, technical and professional periodicals. IPM has subscriptions to several prestigious journals and databases such as ProQuest, Emerald, SAGE, ASCE, and collections of DVDs on mega projects. These resources aid extensive research and teaching on project management.

IPM offers a wide range of learning paths tailor-made for the target audience, with a strong focus on the capability, competency, and maturity required to perform project management functions. We use modern pedagogies and teaching methods to provide exceptional project management education to the participants.

Faculty Immersion Program on Real World Problem Solving

L&T EduTech in collaboration with L&T Institute of Project Management (IPM) has customized this program exclusively for leading academicians across the Nation.

Program Outcomes

• To keep pace with the changing & current scenarios in technical education ensuring alignment with industry trends.
• To enhance skills and competencies to solve real world industry problems through project management techniques.
• To develop domain specific problem-solving competencies.
• To gain awareness of modern teaching tools and methodologies in academia.
• To engage in various research and academic skill development programs.
• To upgrade knowledge and skills of the Project Management across various aspects of theory & practice.

What to Expect

Interaction with practising experts to create experiential learning

Develop the skills to lead larger, more dispersed teams

Gain a comprehensive understanding of project management knowledge areas

Insights into shaping organizational culture and develop strategies for change management

Explore new pedagogical techniques and prepare students for problem-solving

Gain a competitive edge for professional advancement in academia

Immersive experience at L&T mega projects

Networking and collaboration with global industry leaders, practising experts and peers

Focus areas.

Effective Organizational Leadership

Problem Solving Expertise through Project Management

Industry Collaboration and Future Trends

Building Self-Awareness and Emotional Intelligence

Who can participate, this program is applicable to senior faculty members across various domains., l&t ipm certifications along with the pmi pdus (21 pdus), opportunities to associate with l&t ipm for project management advisory, paid training assignments for selected individuals*, probable research collaboration with the ipm faculty**, dissemination of industry trends and problem solving competency to students.

* as per the selection criteria of L&T IPM ** in the area of project management

Program Guidelines

The colleges shall nominate leading academicians across various domains for the Program.

Participants are obliged to carry both their government-issued ID proof and institutional ID card.

The participants will have to take care of their own travel and accommodation.

The participants are requested to report at the venue by 9:00 AM on the first day of the Program.

The Program fee includes lunch, refreshments and travel to sites.

A participation certificate will be awarded to all participants by Larsen & Toubro

Important Dates

09 April 2024

Registrations Open

15 May 2024

Registration Closes

4th Week of May 2024

Confirmation to Participation

Program Dates