technical problem solving meaning

What is Problem Solving? (Steps, Techniques, Examples)

By Status.net Editorial Team on May 7, 2023 — 5 minutes to read

What Is Problem Solving?

Definition and importance.

Problem solving is the process of finding solutions to obstacles or challenges you encounter in your life or work. It is a crucial skill that allows you to tackle complex situations, adapt to changes, and overcome difficulties with ease. Mastering this ability will contribute to both your personal and professional growth, leading to more successful outcomes and better decision-making.

Problem-Solving Steps

The problem-solving process typically includes the following steps:

• Identify the issue : Recognize the problem that needs to be solved.
• Analyze the situation : Examine the issue in depth, gather all relevant information, and consider any limitations or constraints that may be present.
• Generate potential solutions : Brainstorm a list of possible solutions to the issue, without immediately judging or evaluating them.
• Evaluate options : Weigh the pros and cons of each potential solution, considering factors such as feasibility, effectiveness, and potential risks.
• Select the best solution : Choose the option that best addresses the problem and aligns with your objectives.
• Implement the solution : Put the selected solution into action and monitor the results to ensure it resolves the issue.
• Review and learn : Reflect on the problem-solving process, identify any improvements or adjustments that can be made, and apply these learnings to future situations.

Defining the Problem

To start tackling a problem, first, identify and understand it. Analyzing the issue thoroughly helps to clarify its scope and nature. Ask questions to gather information and consider the problem from various angles. Some strategies to define the problem include:

• Brainstorming with others
• Asking the 5 Ws and 1 H (Who, What, When, Where, Why, and How)
• Analyzing cause and effect
• Creating a problem statement

Generating Solutions

Once the problem is clearly understood, brainstorm possible solutions. Think creatively and keep an open mind, as well as considering lessons from past experiences. Consider:

• Creating a list of potential ideas to solve the problem
• Grouping and categorizing similar solutions
• Prioritizing potential solutions based on feasibility, cost, and resources required
• Involving others to share diverse opinions and inputs

Evaluating and Selecting Solutions

Evaluate each potential solution, weighing its pros and cons. To facilitate decision-making, use techniques such as:

• SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
• Decision-making matrices
• Pros and cons lists
• Risk assessments

After evaluating, choose the most suitable solution based on effectiveness, cost, and time constraints.

Implementing and Monitoring the Solution

Implement the chosen solution and monitor its progress. Key actions include:

• Communicating the solution to relevant parties
• Setting timelines and milestones
• Assigning tasks and responsibilities
• Monitoring the solution and making adjustments as necessary
• Evaluating the effectiveness of the solution after implementation

Utilize feedback from stakeholders and consider potential improvements. Remember that problem-solving is an ongoing process that can always be refined and enhanced.

Problem-Solving Techniques

During each step, you may find it helpful to utilize various problem-solving techniques, such as:

• Brainstorming : A free-flowing, open-minded session where ideas are generated and listed without judgment, to encourage creativity and innovative thinking.
• Root cause analysis : A method that explores the underlying causes of a problem to find the most effective solution rather than addressing superficial symptoms.
• SWOT analysis : A tool used to evaluate the strengths, weaknesses, opportunities, and threats related to a problem or decision, providing a comprehensive view of the situation.
• Mind mapping : A visual technique that uses diagrams to organize and connect ideas, helping to identify patterns, relationships, and possible solutions.

Brainstorming

When facing a problem, start by conducting a brainstorming session. Gather your team and encourage an open discussion where everyone contributes ideas, no matter how outlandish they may seem. This helps you:

• Generate a diverse range of solutions
• Encourage all team members to participate
• Foster creative thinking

When brainstorming, remember to:

• Reserve judgment until the session is over
• Encourage wild ideas
• Combine and improve upon ideas

Root Cause Analysis

For effective problem-solving, identifying the root cause of the issue at hand is crucial. Try these methods:

• 5 Whys : Ask “why” five times to get to the underlying cause.
• Fishbone Diagram : Create a diagram representing the problem and break it down into categories of potential causes.
• Pareto Analysis : Determine the few most significant causes underlying the majority of problems.

SWOT Analysis

SWOT analysis helps you examine the Strengths, Weaknesses, Opportunities, and Threats related to your problem. To perform a SWOT analysis:

• List your problem’s strengths, such as relevant resources or strong partnerships.
• Identify its weaknesses, such as knowledge gaps or limited resources.
• Explore opportunities, like trends or new technologies, that could help solve the problem.
• Recognize potential threats, like competition or regulatory barriers.

SWOT analysis aids in understanding the internal and external factors affecting the problem, which can help guide your solution.

Mind Mapping

A mind map is a visual representation of your problem and potential solutions. It enables you to organize information in a structured and intuitive manner. To create a mind map:

• Write the problem in the center of a blank page.
• Draw branches from the central problem to related sub-problems or contributing factors.
• Add more branches to represent potential solutions or further ideas.

Mind mapping allows you to visually see connections between ideas and promotes creativity in problem-solving.

Examples of Problem Solving in Various Contexts

In the business world, you might encounter problems related to finances, operations, or communication. Applying problem-solving skills in these situations could look like:

• Identifying areas of improvement in your company’s financial performance and implementing cost-saving measures
• Resolving internal conflicts among team members by listening and understanding different perspectives, then proposing and negotiating solutions
• Streamlining a process for better productivity by removing redundancies, automating tasks, or re-allocating resources

In educational contexts, problem-solving can be seen in various aspects, such as:

• Addressing a gap in students’ understanding by employing diverse teaching methods to cater to different learning styles
• Developing a strategy for successful time management to balance academic responsibilities and extracurricular activities
• Seeking resources and support to provide equal opportunities for learners with special needs or disabilities

Everyday life is full of challenges that require problem-solving skills. Some examples include:

• Overcoming a personal obstacle, such as improving your fitness level, by establishing achievable goals, measuring progress, and adjusting your approach accordingly
• Navigating a new environment or city by researching your surroundings, asking for directions, or using technology like GPS to guide you
• Dealing with a sudden change, like a change in your work schedule, by assessing the situation, identifying potential impacts, and adapting your plans to accommodate the change.
• How to Resolve Employee Conflict at Work [Steps, Tips, Examples]
• How to Write Inspiring Core Values? 5 Steps with Examples
• 30 Employee Feedback Examples (Positive & Negative)

What Is Problem Solving? How Software Engineers Approach Complex Challenges

From debugging an existing system to designing an entirely new software application, a day in the life of a software engineer is filled with various challenges and complexities. The one skill that glues these disparate tasks together and makes them manageable? Problem solving . 

Throughout this blog post, we’ll explore why problem-solving skills are so critical for software engineers, delve into the techniques they use to address complex challenges, and discuss how hiring managers can identify these skills during the hiring process. 

What Is Problem Solving?

But what exactly is problem solving in the context of software engineering? How does it work, and why is it so important?

Problem solving, in the simplest terms, is the process of identifying a problem, analyzing it, and finding the most effective solution to overcome it. For software engineers, this process is deeply embedded in their daily workflow. It could be something as simple as figuring out why a piece of code isn’t working as expected, or something as complex as designing the architecture for a new software system. 

In a world where technology is evolving at a blistering pace, the complexity and volume of problems that software engineers face are also growing. As such, the ability to tackle these issues head-on and find innovative solutions is not only a handy skill — it’s a necessity. 

The Importance of Problem-Solving Skills for Software Engineers

Problem-solving isn’t just another ability that software engineers pull out of their toolkits when they encounter a bug or a system failure. It’s a constant, ongoing process that’s intrinsic to every aspect of their work. Let’s break down why this skill is so critical.

Driving Development Forward

Without problem solving, software development would hit a standstill. Every new feature, every optimization, and every bug fix is a problem that needs solving. Whether it’s a performance issue that needs diagnosing or a user interface that needs improving, the capacity to tackle and solve these problems is what keeps the wheels of development turning.

It’s estimated that 60% of software development lifecycle costs are related to maintenance tasks, including debugging and problem solving. This highlights how pivotal this skill is to the everyday functioning and advancement of software systems.

Innovation and Optimization

The importance of problem solving isn’t confined to reactive scenarios; it also plays a major role in proactive, innovative initiatives . Software engineers often need to think outside the box to come up with creative solutions, whether it’s optimizing an algorithm to run faster or designing a new feature to meet customer needs. These are all forms of problem solving.

Consider the development of the modern smartphone. It wasn’t born out of a pre-existing issue but was a solution to a problem people didn’t realize they had — a device that combined communication, entertainment, and productivity into one handheld tool.

Increasing Efficiency and Productivity

Good problem-solving skills can save a lot of time and resources. Effective problem-solvers are adept at dissecting an issue to understand its root cause, thus reducing the time spent on trial and error. This efficiency means projects move faster, releases happen sooner, and businesses stay ahead of their competition.

Improving Software Quality

Problem solving also plays a significant role in enhancing the quality of the end product. By tackling the root causes of bugs and system failures, software engineers can deliver reliable, high-performing software. This is critical because, according to the Consortium for Information and Software Quality, poor quality software in the U.S. in 2022 cost at least $2.41 trillion in operational issues, wasted developer time, and other related problems.

Problem-Solving Techniques in Software Engineering

So how do software engineers go about tackling these complex challenges? Let’s explore some of the key problem-solving techniques, theories, and processes they commonly use.

Decomposition

Breaking down a problem into smaller, manageable parts is one of the first steps in the problem-solving process. It’s like dealing with a complicated puzzle. You don’t try to solve it all at once. Instead, you separate the pieces, group them based on similarities, and then start working on the smaller sets. This method allows software engineers to handle complex issues without being overwhelmed and makes it easier to identify where things might be going wrong.

Abstraction

In the realm of software engineering, abstraction means focusing on the necessary information only and ignoring irrelevant details. It is a way of simplifying complex systems to make them easier to understand and manage. For instance, a software engineer might ignore the details of how a database works to focus on the information it holds and how to retrieve or modify that information.

Algorithmic Thinking

At its core, software engineering is about creating algorithms — step-by-step procedures to solve a problem or accomplish a goal. Algorithmic thinking involves conceiving and expressing these procedures clearly and accurately and viewing every problem through an algorithmic lens. A well-designed algorithm not only solves the problem at hand but also does so efficiently, saving computational resources.

Parallel Thinking

Parallel thinking is a structured process where team members think in the same direction at the same time, allowing for more organized discussion and collaboration. It’s an approach popularized by Edward de Bono with the “ Six Thinking Hats ” technique, where each “hat” represents a different style of thinking.

In the context of software engineering, parallel thinking can be highly effective for problem solving. For instance, when dealing with a complex issue, the team can use the “White Hat” to focus solely on the data and facts about the problem, then the “Black Hat” to consider potential problems with a proposed solution, and so on. This structured approach can lead to more comprehensive analysis and more effective solutions, and it ensures that everyone’s perspectives are considered.

This is the process of identifying and fixing errors in code . Debugging involves carefully reviewing the code, reproducing and analyzing the error, and then making necessary modifications to rectify the problem. It’s a key part of maintaining and improving software quality.

Testing and Validation

Testing is an essential part of problem solving in software engineering. Engineers use a variety of tests to verify that their code works as expected and to uncover any potential issues. These range from unit tests that check individual components of the code to integration tests that ensure the pieces work well together. Validation, on the other hand, ensures that the solution not only works but also fulfills the intended requirements and objectives.

Explore verified tech roles & skills.

The definitive directory of tech roles, backed by machine learning and skills intelligence.

Explore all roles

Evaluating Problem-Solving Skills

We’ve examined the importance of problem-solving in the work of a software engineer and explored various techniques software engineers employ to approach complex challenges. Now, let’s delve into how hiring teams can identify and evaluate problem-solving skills during the hiring process.

Recognizing Problem-Solving Skills in Candidates

How can you tell if a candidate is a good problem solver? Look for these indicators:

• Previous Experience: A history of dealing with complex, challenging projects is often a good sign. Ask the candidate to discuss a difficult problem they faced in a previous role and how they solved it.
• Problem-Solving Questions: During interviews, pose hypothetical scenarios or present real problems your company has faced. Ask candidates to explain how they would tackle these issues. You’re not just looking for a correct solution but the thought process that led them there.
• Technical Tests: Coding challenges and other technical tests can provide insight into a candidate’s problem-solving abilities. Consider leveraging a platform for assessing these skills in a realistic, job-related context.

Assessing Problem-Solving Skills

Once you’ve identified potential problem solvers, here are a few ways you can assess their skills:

• Solution Effectiveness: Did the candidate solve the problem? How efficient and effective is their solution?
• Approach and Process: Go beyond whether or not they solved the problem and examine how they arrived at their solution. Did they break the problem down into manageable parts? Did they consider different perspectives and possibilities?
• Communication: A good problem solver can explain their thought process clearly. Can the candidate effectively communicate how they arrived at their solution and why they chose it?
• Adaptability: Problem-solving often involves a degree of trial and error. How does the candidate handle roadblocks? Do they adapt their approach based on new information or feedback?

Hiring managers play a crucial role in identifying and fostering problem-solving skills within their teams. By focusing on these abilities during the hiring process, companies can build teams that are more capable, innovative, and resilient.

Key Takeaways

As you can see, problem solving plays a pivotal role in software engineering. Far from being an occasional requirement, it is the lifeblood that drives development forward, catalyzes innovation, and delivers of quality software. 

By leveraging problem-solving techniques, software engineers employ a powerful suite of strategies to overcome complex challenges. But mastering these techniques isn’t simple feat. It requires a learning mindset, regular practice, collaboration, reflective thinking, resilience, and a commitment to staying updated with industry trends. 

For hiring managers and team leads, recognizing these skills and fostering a culture that values and nurtures problem solving is key. It’s this emphasis on problem solving that can differentiate an average team from a high-performing one and an ordinary product from an industry-leading one.

At the end of the day, software engineering is fundamentally about solving problems — problems that matter to businesses, to users, and to the wider society. And it’s the proficient problem solvers who stand at the forefront of this dynamic field, turning challenges into opportunities, and ideas into reality.

This article was written with the help of AI. Can you tell which parts?

Get started with HackerRank

Over 2,500 companies and 40% of developers worldwide use HackerRank to hire tech talent and sharpen their skills.

Recommended topics

• Hire Developers
• Problem Solving

Does a College Degree Still Matter for Developers in 2024?

Advisory boards aren’t only for executives. Join the LogRocket Content Advisory Board today →

• Product Management
• Solve User-Reported Issues
• Find Issues Faster
• Optimize Conversion and Adoption

A guide to problem-solving techniques, steps, and skills

You might associate problem-solving with the math exercises that a seven-year-old would do at school. But problem-solving isn’t just about math — it’s a crucial skill that helps everyone make better decisions in everyday life or work.

Problem-solving involves finding effective solutions to address complex challenges, in any context they may arise.

Unfortunately, structured and systematic problem-solving methods aren’t commonly taught. Instead, when solving a problem, PMs tend to rely heavily on intuition. While for simple issues this might work well, solving a complex problem with a straightforward solution is often ineffective and can even create more problems.

In this article, you’ll learn a framework for approaching problem-solving, alongside how you can improve your problem-solving skills.

The 7 steps to problem-solving

When it comes to problem-solving there are seven key steps that you should follow: define the problem, disaggregate, prioritize problem branches, create an analysis plan, conduct analysis, synthesis, and communication.

1. Define the problem

Problem-solving begins with a clear understanding of the issue at hand. Without a well-defined problem statement, confusion and misunderstandings can hinder progress. It’s crucial to ensure that the problem statement is outcome-focused, specific, measurable whenever possible, and time-bound.

Additionally, aligning the problem definition with relevant stakeholders and decision-makers is essential to ensure efforts are directed towards addressing the actual problem rather than side issues.

2. Disaggregate

Complex issues often require deeper analysis. Instead of tackling the entire problem at once, the next step is to break it down into smaller, more manageable components.

Various types of logic trees (also known as issue trees or decision trees) can be used to break down the problem. At each stage where new branches are created, it’s important for them to be “MECE” – mutually exclusive and collectively exhaustive. This process of breaking down continues until manageable components are identified, allowing for individual examination.

The decomposition of the problem demands looking at the problem from various perspectives. That is why collaboration within a team often yields more valuable results, as diverse viewpoints lead to a richer pool of ideas and solutions.

3. Prioritize problem branches

The next step involves prioritization. Not all branches of the problem tree have the same impact, so it’s important to understand the significance of each and focus attention on the most impactful areas. Prioritizing helps streamline efforts and minimize the time required to solve the problem.

Over 200k developers and product managers use LogRocket to create better digital experiences

4. Create an analysis plan

For prioritized components, you may need to conduct in-depth analysis. Before proceeding, a work plan is created for data gathering and analysis. If work is conducted within a team, having a plan provides guidance on what needs to be achieved, who is responsible for which tasks, and the timelines involved.

5. Conduct analysis

Data gathering and analysis are central to the problem-solving process. It’s a good practice to set time limits for this phase to prevent excessive time spent on perfecting details. You can employ heuristics and rule-of-thumb reasoning to improve efficiency and direct efforts towards the most impactful work.

6. Synthesis

After each individual branch component has been researched, the problem isn’t solved yet. The next step is synthesizing the data logically to address the initial question. The synthesis process and the logical relationship between the individual branch results depend on the logic tree used.

7. Communication

The last step is communicating the story and the solution of the problem to the stakeholders and decision-makers. Clear effective communication is necessary to build trust in the solution and facilitates understanding among all parties involved. It ensures that stakeholders grasp the intricacies of the problem and the proposed solution, leading to informed decision-making.

Exploring problem-solving in various contexts

While problem-solving has traditionally been associated with fields like engineering and science, today it has become a fundamental skill for individuals across all professions. In fact, problem-solving consistently ranks as one of the top skills required by employers.

Problem-solving techniques can be applied in diverse contexts:

• Individuals — What career path should I choose? Where should I live? These are examples of simple and common personal challenges that require effective problem-solving skills
• Organizations — Businesses also face many decisions that are not trivial to answer. Should we expand into new markets this year? How can we enhance the quality of our product development? Will our office accommodate the upcoming year’s growth in terms of capacity?
• Societal issues — The biggest world challenges are also complex problems that can be addressed with the same technique. How can we minimize the impact of climate change? How do we fight cancer?

Despite the variation in domains and contexts, the fundamental approach to solving these questions remains the same. It starts with gaining a clear understanding of the problem, followed by decomposition, conducting analysis of the decomposed branches, and synthesizing it into a result that answers the initial problem.

Real-world examples of problem-solving

Let’s now explore some examples where we can apply the problem solving framework.

Problem: In the production of electronic devices, you observe an increasing number of defects. How can you reduce the error rate and improve the quality?

Before delving into analysis, you can deprioritize branches that you already have information for or ones you deem less important. For instance, while transportation delays may occur, the resulting material degradation is likely negligible. For other branches, additional research and data gathering may be necessary.

Once results are obtained, synthesis is crucial to address the core question: How can you decrease the defect rate?

While all factors listed may play a role, their significance varies. Your task is to prioritize effectively. Through data analysis, you may discover that altering the equipment would bring the most substantial positive outcome. However, executing a solution isn’t always straightforward. In prioritizing, you should consider both the potential impact and the level of effort needed for implementation.

By evaluating impact and effort, you can systematically prioritize areas for improvement, focusing on those with high impact and requiring minimal effort to address. This approach ensures efficient allocation of resources towards improvements that offer the greatest return on investment.

Problem : What should be my next job role?

When breaking down this problem, you need to consider various factors that are important for your future happiness in the role. This includes aspects like the company culture, our interest in the work itself, and the lifestyle that you can afford with the role.

However, not all factors carry the same weight for us. To make sense of the results, we can assign a weight factor to each branch. For instance, passion for the job role may have a weight factor of 1, while interest in the industry may have a weight factor of 0.5, because that is less important for you.

By applying these weights to a specific role and summing the values, you can have an estimate of how suitable that role is for you. Moreover, you can compare two roles and make an informed decision based on these weighted indicators.

Key problem-solving skills

This framework provides the foundation and guidance needed to effectively solve problems. However, successfully applying this framework requires the following:

• Creativity — During the decomposition phase, it’s essential to approach the problem from various perspectives and think outside the box to generate innovative ideas for breaking down the problem tree
• Decision-making — Throughout the process, decisions must be made, even when full confidence is lacking. Employing rules of thumb to simplify analysis or selecting one tree cut over another requires decisiveness and comfort with choices made
• Analytical skills — Analytical and research skills are necessary for the phase following decomposition, involving data gathering and analysis on selected tree branches
• Teamwork — Collaboration and teamwork are crucial when working within a team setting. Solving problems effectively often requires collective effort and shared responsibility
• Communication — Clear and structured communication is essential to convey the problem solution to stakeholders and decision-makers and build trust

How to enhance your problem-solving skills

Problem-solving requires practice and a certain mindset. The more you practice, the easier it becomes. Here are some strategies to enhance your skills:

• Practice structured thinking in your daily life — Break down problems or questions into manageable parts. You don’t need to go through the entire problem-solving process and conduct detailed analysis. When conveying a message, simplify the conversation by breaking the message into smaller, more understandable segments
• Regularly challenging yourself with games and puzzles — Solving puzzles, riddles, or strategy games can boost your problem-solving skills and cognitive agility.
• Engage with individuals from diverse backgrounds and viewpoints — Conversing with people who offer different perspectives provides fresh insights and alternative solutions to problems. This boosts creativity and helps in approaching challenges from new angles

Final thoughts

Problem-solving extends far beyond mathematics or scientific fields; it’s a critical skill for making informed decisions in every area of life and work. The seven-step framework presented here provides a systematic approach to problem-solving, relevant across various domains.

Now, consider this: What’s one question currently on your mind? Grab a piece of paper and try to apply the problem-solving framework. You might uncover fresh insights you hadn’t considered before.

Featured image source: IconScout

LogRocket generates product insights that lead to meaningful action

Get your teams on the same page — try LogRocket today.

Share this:

• Click to share on Twitter (Opens in new window)
• Click to share on Reddit (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• #career development
• #tools and resources

Stop guessing about your digital experience with LogRocket

Recent posts:.

Team alignment strategies: A guide to effective teamwork

Team alignment is a state where team members understand, agree upon, and are committed to achieving clearly defined goals.

Defining your target market: Strategies and examples

As a business, you want to find the specific set of consumers that will buy, use, and appreciate your products and services.

A guide to data science for product managers

Data science is the area responsible for building, training, and applying machine learning (ML) and AI algorithms to business problems.

An overview of the problem space

Spending enough time to understand the underlying problems of your users is the key to success in product management.

Leave a Reply Cancel reply

What Are Problem-Solving Skills? Definition and Examples

• Share on Twitter Share on Twitter
• Share on Facebook Share on Facebook
• Share on LinkedIn Share on LinkedIn

Forage puts students first. Our blog articles are written independently by our editorial team. They have not been paid for or sponsored by our partners. See our full  editorial guidelines .

Why do employers hire employees? To help them solve problems. Whether you’re a financial analyst deciding where to invest your firm’s money, or a marketer trying to figure out which channel to direct your efforts, companies hire people to help them find solutions. Problem-solving is an essential and marketable soft skill in the workplace. 

So, how can you improve your problem-solving and show employers you have this valuable skill? In this guide, we’ll cover:

Problem-Solving Skills Definition

Why are problem-solving skills important, problem-solving skills examples, how to include problem-solving skills in a job application, how to improve problem-solving skills, problem-solving: the bottom line.

Problem-solving skills are the ability to identify problems, brainstorm and analyze answers, and implement the best solutions. An employee with good problem-solving skills is both a self-starter and a collaborative teammate; they are proactive in understanding the root of a problem and work with others to consider a wide range of solutions before deciding how to move forward. 

Examples of using problem-solving skills in the workplace include:

• Researching patterns to understand why revenue decreased last quarter
• Experimenting with a new marketing channel to increase website sign-ups
• Brainstorming content types to share with potential customers
• Testing calls to action to see which ones drive the most product sales
• Implementing a new workflow to automate a team process and increase productivity

Problem-solving skills are the most sought-after soft skill of 2022. In fact, 86% of employers look for problem-solving skills on student resumes, according to the National Association of Colleges and Employers Job Outlook 2022 survey . 

It’s unsurprising why employers are looking for this skill: companies will always need people to help them find solutions to their problems. Someone proactive and successful at problem-solving is valuable to any team.

“Employers are looking for employees who can make decisions independently, especially with the prevalence of remote/hybrid work and the need to communicate asynchronously,” Eric Mochnacz, senior HR consultant at Red Clover, says. “Employers want to see individuals who can make well-informed decisions that mitigate risk, and they can do so without suffering from analysis paralysis.”

Showcase new skills

Build the confidence and practical skills that employers are looking for with Forage’s free job simulations.

Problem-solving includes three main parts: identifying the problem, analyzing possible solutions, and deciding on the best course of action.

>>MORE: Discover the right career for you based on your skills with a career aptitude test .

Research is the first step of problem-solving because it helps you understand the context of a problem. Researching a problem enables you to learn why the problem is happening. For example, is revenue down because of a new sales tactic? Or because of seasonality? Is there a problem with who the sales team is reaching out to? 

Research broadens your scope to all possible reasons why the problem could be happening. Then once you figure it out, it helps you narrow your scope to start solving it. 

Analysis is the next step of problem-solving. Now that you’ve identified the problem, analytical skills help you look at what potential solutions there might be.

“The goal of analysis isn’t to solve a problem, actually — it’s to better understand it because that’s where the real solution will be found,” Gretchen Skalka, owner of Career Insights Consulting, says. “Looking at a problem through the lens of impartiality is the only way to get a true understanding of it from all angles.”

Decision-Making

Once you’ve figured out where the problem is coming from and what solutions are, it’s time to decide on the best way to go forth. Decision-making skills help you determine what resources are available, what a feasible action plan entails, and what solution is likely to lead to success.

On a Resume

Employers looking for problem-solving skills might include the word “problem-solving” or other synonyms like “ critical thinking ” or “analytical skills” in the job description.

“I would add ‘buzzwords’ you can find from the job descriptions or LinkedIn endorsements section to filter into your resume to comply with the ATS,” Matthew Warzel, CPRW resume writer, advises. Warzel recommends including these skills on your resume but warns to “leave the soft skills as adjectives in the summary section. That is the only place soft skills should be mentioned.”

On the other hand, you can list hard skills separately in a skills section on your resume .

Forage Resume Writing Masterclass

Learn how to showcase your skills and craft an award-winning resume with this free masterclass from Forage.

Avg. Time: 5 to 6 hours

Skills you’ll build: Resume writing, professional brand, professional summary, narrative, transferable skills, industry keywords, illustrating your impact, standing out

In a Cover Letter or an Interview

Explaining your problem-solving skills in an interview can seem daunting. You’re required to expand on your process — how you identified a problem, analyzed potential solutions, and made a choice. As long as you can explain your approach, it’s okay if that solution didn’t come from a professional work experience.

“Young professionals shortchange themselves by thinking only paid-for solutions matter to employers,” Skalka says. “People at the genesis of their careers don’t have a wealth of professional experience to pull from, but they do have relevant experience to share.”

Aaron Case, career counselor and CPRW at Resume Genius, agrees and encourages early professionals to share this skill. “If you don’t have any relevant work experience yet, you can still highlight your problem-solving skills in your cover letter,” he says. “Just showcase examples of problems you solved while completing your degree, working at internships, or volunteering. You can even pull examples from completely unrelated part-time jobs, as long as you make it clear how your problem-solving ability transfers to your new line of work.”

Learn How to Identify Problems

Problem-solving doesn’t just require finding solutions to problems that are already there. It’s also about being proactive when something isn’t working as you hoped it would. Practice questioning and getting curious about processes and activities in your everyday life. What could you improve? What would you do if you had more resources for this process? If you had fewer? Challenge yourself to challenge the world around you.

Think Digitally

“Employers in the modern workplace value digital problem-solving skills, like being able to find a technology solution to a traditional issue,” Case says. “For example, when I first started working as a marketing writer, my department didn’t have the budget to hire a professional voice actor for marketing video voiceovers. But I found a perfect solution to the problem with an AI voiceover service that cost a fraction of the price of an actor.”

Being comfortable with new technology — even ones you haven’t used before — is a valuable skill in an increasingly hybrid and remote world. Don’t be afraid to research new and innovative technologies to help automate processes or find a more efficient technological solution.

Collaborate

Problem-solving isn’t done in a silo, and it shouldn’t be. Use your collaboration skills to gather multiple perspectives, help eliminate bias, and listen to alternative solutions. Ask others where they think the problem is coming from and what solutions would help them with your workflow. From there, try to compromise on a solution that can benefit everyone.

If we’ve learned anything from the past few years, it’s that the world of work is constantly changing — which means it’s crucial to know how to adapt . Be comfortable narrowing down a solution, then changing your direction when a colleague provides a new piece of information. Challenge yourself to get out of your comfort zone, whether with your personal routine or trying a new system at work.

Put Yourself in the Middle of Tough Moments

Just like adapting requires you to challenge your routine and tradition, good problem-solving requires you to put yourself in challenging situations — especially ones where you don’t have relevant experience or expertise to find a solution. Because you won’t know how to tackle the problem, you’ll learn new problem-solving skills and how to navigate new challenges. Ask your manager or a peer if you can help them work on a complicated problem, and be proactive about asking them questions along the way.

Career Aptitude Test

What careers are right for you based on your skills? Take this quiz to find out. It’s completely free — you’ll just need to sign up to get your results!

Step 1 of 3

Companies always need people to help them find solutions — especially proactive employees who have practical analytical skills and can collaborate to decide the best way to move forward. Whether or not you have experience solving problems in a professional workplace, illustrate your problem-solving skills by describing your research, analysis, and decision-making process — and make it clear that you’re the solution to the employer’s current problems. 

Looking to learn more workplace professional skills? Check out Two Sigma’s Professional Skills Development Virtual Experience Program .

Image Credit: Christina Morillo / Pexels 

Related Posts

6 negotiation skills to level up your work life, how to build conflict resolution skills: case studies and examples, what is github uses and getting started, upskill with forage.

Build career skills recruiters are looking for.

Advertisement

Technological problem solving: an investigation of differences associated with levels of task success

• Open access
• Published: 02 June 2021
• Volume 32 , pages 1725–1753, ( 2022 )

Cite this article

You have full access to this open access article

• David Morrison-Love   ORCID: orcid.org/0000-0002-9009-4738 1  

8702 Accesses

Explore all metrics

Research into technological problem solving has shown it to exist in a range of forms and draw upon different processes and knowledge types. This paper adds to this understanding by identifying procedural and epistemic differences in relation to task performance for pupils solving a well-defined technological problem. The study is theoretically grounded in a transformative epistemology of technology education. 50 pupils in small groups worked through a cantilever problem, the most and least successful solutions to which were identified using a Delphi technique. Time-interval photography, verbal interactions, observations and supplementary data formed a composite representation of activity which was analysed with successively less contrasting groups to isolate sustained differences. Analyses revealed key differences in three areas. First, more successful groups used better and more proactive process-management strategies including use of planning, role and task allocation with lower levels of group tension. Second, they made greater use of reflection in which knowledge associated with the technological solution was explicitly verblised. This was defined as ‘analytical reflection’ and reveals aspects of pupils’ qualitative technical knowledge. Third, higher-performing groups exhibited greater levels of tacit-procedural knowledge within their solutions. There was also evidence that less successful groups were less affected by competition and not as comprehensive in translating prior conceptual learning into their tangible technological solutions. Overall findings suggest that proactive management, and making contextual and technical connections, are important for pupils solving well-defined technological problems. This understanding can be used to support classroom pedagogies that help pupils learn to problem solve more effectively.

Similar content being viewed by others

Investigating Preservice Teachers’ Educational Technology Skills: A Problem-Solving Process

Problem-Based Learning in Technology Education

Avoid common mistakes on your manuscript.

Introduction

Problem solving is an activity, a context and a dominant pedagogical frame for Technology Education. It constitutes a central method and a critical skill through which school pupils learn about and become proficient in technology (Custer et al., 2001 ). Research has, among other things, been able to identify and investigate sets of intellectual and cognitive processes (Buckley et al., 2019 ; Haupt, 2018 ; Johnson, 1997 ; Sung & Kelly, 2019 ) and shown there to be conceptual, procedural, relational and harder-to-get-to forms of ‘technological knowledge’ involved when pupils develop technological solutions (de Vries, 2005 ; McCormick, 1997 , 2004 ; Rauscher, 2011 ). Some authors argue that technological problem solving (and design) is a situated activity (Jackson & Strimel, 2018 ; Murphy & McCormick, 1997 ; Liddament, 1996 ), but with social and context-independent processes also playing an important role (e.g. Jones, 1997 ; Winkelmann & Hacker, 2011 ). Within and across this vista, there has been strong interest in more open-ended, creative and design-based problem-solving (Lewis, 2005 , 2009 ), which Xu et al. ( 2019 ) notes became particularly prominent after 2006. These studies have helped to understand some of the challenges and pedagogies of design (Gómez Puente et al., 2013 ; Lavonen et al., 2002 ; Mioduser & Dagan, 2007 ; Mawson, 2003 ) including those that mitigate effects such as cognitive fixation (e.g. McLellan & Nicholl, 2011 ). Problem solving, it seems, is a pervasive idea in technology education research and policy. Middleton ( 2009 ) notes that problem solving is found in almost all international technology education curricula.

The pace, nature and complexity of contemporary societal challenges make it more critical than ever that technology classrooms prepare people who can think through and respond to technological problems effectively. It requires that we strengthen our understanding in ways that will ultimately be powerful for shaping classroom learning. One way of contributing to this is to learn more about the differences between learners who are more and less successful at technological problem solving. Studies that share a comparative perspective and/or a focus upon task success are relatively few. Doornekamp ( 2001 ) compared pupils (circa 13 years old) who solved technological problems using weakly structured instructional materials with those using strongly structured materials. It was shown that the latter led to statistically significant improvements in the quality of the technical solutions. More recently, Bartholomew & Strimel ( 2018 ) were able to show that, for open-ended problem solving, there was no significant relationship between prior experience and folio creation, but that more in-school school experience of open-ended problem solving corresponded to higher ranked solutions.

This paper contributes to this work by reporting on a study that compares groups of pupils during technological problem solving in order to identify areas of difference and the factors associated with more successful outcomes. Specifically, it addresses the question: ‘In terms of intellectual processes and knowledge, what are the differences in the modi operandi between groups of pupils that produced more and less successful technological solutions to a well-defined problem?’ Theoretically grounded in a transformative epistemology of technology education (Morrison-Love, 2017 ), the study identifies prominent procedural and epistemic differences in pupils’ thinking and technical solutions. Groups of pupils engaged with a structures problem requiring them to develop a cantilever bridge system which would facilitate safe travel across a body of water.

The paper begins by setting out the theoretical basis and conceptual framework for investigation before describing the comparative methodological and analytical approaches that were adopted. Following an analysis and presentation of key findings, conclusion and implications are discussed.

A theoretical basis for the study of technological problem solving

Despite there being no single comprehensive paradigm for technological problem solving, a theoretical grounding and conceptual framework necessary for this study are presented. At the theoretical level, this study is based upon a ‘transformative epistemology’ for technology education (Morrison-Love, 2017 ). From this, a ternary conceptual framework based upon mode, epistemology and process is developed to support study design and initiate data analysis.

A transformative epistemology for technology education (Morrison-Love, ibid) proposes that pupils’ technological knowledge and capability arises from the ontological transformation of their technical solution from ‘perdurant’ (more conceptual, mutable, less well-defined, partial) in the early stages, to ‘endurant’ (comprehensive, tangible, stable over time) upon completion. It proposes that technical outcomes exist in material and tangible forms and that to be technological (rather than, for example, social, cultural or aesthetic) these must somehow enhance human capabilities in their intended systems of use. For this study, the ideas of transformative epistemology support problem solving in which pupils build technological knowledge by iteratively moving from concept to tangible, material solution. Moreover, it means pupils are successful in this when their solutions or prototypes: (1) enhance existing human capabilities in some way, and (2) are sufficiently developed to be stable over time, beyond the problem-solving activity that created it.

A conceptual framework for technological problem solving

A ternary conceptual framework (Fig. 1 ) of mode, process and epistemology was developed from the literature in which the knowledge and cognitive/intellectual processes used by pupils are enacted in the ‘process application block’. This is like the ‘problem space’ described in a model proposed by Mioduser ( 1998 ). Collectively, the goal of creating a physical artefact, the solution itself, the epistemic and procedural dimensions reflect the four dimensions of technology identified by Custer ( 1995 ).

‘A conceptual framework for technological problem solving’

Mode and forms dimension

Although problem solving may be ‘technological’, several classifications of both problem type and problem solving are found in the literature. Ill-defined and well-defined problems build upon the earlier work of information processing and cognitive psychology (see Jonassen, 1997 ). Typically, these two forms reflect different extents to which the outcome is specified to the solver at the outset. Ill-defined problems are strongly associated with design and creativity, and Twyford and Järvinen ( 2000 ) suggest that these more open briefs promote greater social interaction and use by pupils of prior knowledge and experience. Additionally, two forms of troubleshooting were identified in the literature: emergent troubleshooting and discrete troubleshooting. MacPherson ( 1998 ) argues that ‘troubleshooting’ constitutes a particular subset of technological problem solving—something earlier recognised by McCade ( 1990 ), who views it as the identification and overcoming of problems encountered during the production or use of a technical solution. In this study, emergent troubleshooting occurs in the process of developing solutions in response to emergent problems (McCormick, 1994 ). Discrete troubleshooting is a process in which significant technical understanding is applied in a structured way (Schaafstal et al., 2000 ) to resolve something about an existing artefact.

Intellectual and cognitive process dimension

Studies often conceptualise cognitive processes discretely rather than hierarchically, and different studies employ different process sets. Williams ( 2000 ), identifies evaluation, communication, modelling, generating ideas, research and investigation, producing and documenting as important to technological problem solving, while DeLuca ( 1991 ) identifies troubleshooting, the scientific process, the design process, research and development, and project management. There are also studies that employ specific, or more established, coding schemes for sets of intellectual and cognitive processes. A detailed analysis of these is given Grubbs et al. ( 2018 ), although the extent to which a particular process remains discrete or could form a sub-process of another remains problematic. In DeLuca’s ( 1991 ) break down for example, to what extent are research and investigation part of design and does this depend on the scale at which we conceptualise different processes?

Regardless of the processes a study defines, it is typically understood that pupils apply them in iterative or cyclic fashion. This is reflected across several models from Argyle’s ( 1972 ) ‘Motor Skill Process Model’ (perception-translation-motor response) through to those of Miodusre and Kipperman ( 2002 ) and Scrivener et al. ( 2002 ) (evaluation-modification cycles) which pertain specifically to technology education. All these models bridge pupils’ conceptual-internal representations with their practical-external representations as they move towards an ontologically endurant solution and this is captured by the ‘Re-Application/Transformation Loop’ of the conceptual framework. Given that little is known about where differences might lie, the process set identified by Halfin ( 1973 ) was adopted due to its rigour and the breadth of thinking it encompasses. This set was validated for technology classrooms by Hill and Wicklein ( 1999 ) and used successfully by other studies of pupils technological thinking including Hill ( 1997 ), Kelley ( 2008 ) and Strimel ( 2014 ).

Epistemology dimension

The nature and sources of knowledge play a critical role for pupils when solving technological problems, but these remain far from straightforward to conceptualise. McCormick ( 1997 ) observes that the activity of technology education, and its body of content, can be thought of as ‘procedural knowledge’ and ‘conceptual knowledge’ respectively. Vincenti ( 1990 ), in the context of Engineering, makes the case for descriptive knowledge (things as they currently are) and prescriptive knowledge (of that with is required to meet a desired state) but also recognises knowledge can take on implicit, or tacit forms relating to an individual’s skill, judgement, and practice (Polanyi, 1967 ; Schön, 1992 ; Sternberg, 1999 ; Welch, 1998 ). Arguably, moving from concept to physical solution will demand from pupils a certain level of practical skill and judgement, and Morgan ( 2008 ) observes that procedural knowledge which is explicit in the early stages becomes increasingly implicit with mastery. Notably, in addition to conceptual, procedural and tacit forms of knowledge, there is also evidence that knowledge of principles plays a role. Distinct from impoverished notions of technology as ‘applied science’, Rophol ( 1997 ) shows that it is often technological principles, laws and maxims that are applied during problem solving rather than scientific ones. Frey ( 1989 ) makes similar observations and sees this form of knowledge arising largely from practice. In this study, knowledge of principles involves knowledge of a relationship between things. It is not constrained to those that are represented scientifically.

The conceptual framework finally accounts for pupils’ sources of knowledge during problem solving, building principally on a design knowledge framework of media, community and domain presented by Erkip et al. ( 1997 ). In this study, media includes task information, representations and materials; community includes teachers and peers, and domain relates to prior technological knowledge from within technology lessons and prior personal knowledge from out with technology lessons. Finally, the developing solution is itself recognised a source of knowledge that pupils iteratively engage with and reflect upon, even when it appears that limited progress in being made (Hamel & Elshout, 2000 ).

Methodology

The research question in this study is concerned with differences in the knowledge and intellectual processes used by pupils in moving from a perdurant to an endurant technical solution. From an exploratory stance, this elicits a dualistic activity system involving pupils’ subjective constructions of reality as well as the resultant tangible and more objective material solution. The study does not aim to investigate pupils’ own subjective constructions from an emic perspective, but rather seeks to determine the nature and occurrences of any differences during observable real-time problem-solving activity. As such, content rather than thematic analysis was used (Elo & Kyngäs, 2008 ; Vaismoradi et al., 2013 ) with concurrent data collection to build a composite representation of reality (Gall et al., 2003 , p.14). Complementary data provided insights into study effects, the classrooms and contexts within which problem-solving took place.

This study assumes that should differences exist, these will be discernible in the inferred cognitive processes, external material transformations, interactions and verbalisation (even though this tends to diminish as activity becomes more practical). Absolute and objective observation is not possible. This study also accepts that data gathering and analysis are influenced by theory, researcher fallibility and bias which will be explicitly accounted for as far as possible. Finally, while the conceptual framework provides an analytical starting point, it should not preclude the capture of differences that may lie elsewhere in the data including, for example, process that lie out with those identified by Halfin ( 1973 ).

Participants, selection and grouping

To support transferability, a representative spread of pupils from low, medium and high socio-economic backgrounds took part in this study. Purposeful, four-stage criterion sampling was used (Gall et al., 2003 , p.179). Stage one identified six schools at each socio-economic level from all Scottish secondary schools that presented pupils for one or more technology subjects with the Scottish Qualifications Authority. This was done using socio-economic data from the Scottish Area Deprivation Index, the Carstairs Index and pupil eligibility for subsidised meals. Secondary school catchment areas were used to account for pupil demographics as accurately as possible. All eighteen schools were subsequently ranked with one median drawn from low, medium and high bands of socio-economic deprivation (School 1: Low, School 2: Medium, School 3: High).

One class in each school was then selected from the second year of study prior to pupils making specific subject choices to minimise variations in curricular experience. In total, 3 class teachers and 50 pupils (20 female, 30 male) aged between 12 and 13 years old took part in the study. The group rather than the individual was defined as unit of study to centralise verbal interaction.

None of the pupils participating in this study had experience of group approaches such as co-operative learning and it was likely that groups might experience participation effects including inter-group conflict and interaction effects (Harkins, 1987 ; Sherif et al., 1961 ), social loafing (Salomon & Globerson, 1989 ), free-rider (Strong & Anderson, 1990 ) and status differential effects (Rowell, 2002 ). Relevant also to this study is evidence suggesting that gender effects can take place in untrained groups undertaking practical/material manipulation activities. To maximise interaction between group members and the material solution, thirteen single sex groups averaging four pupils were formed in order to: (1) minimise the marginalisation of girls with boys’ tendency to monopolise materials and apparatus in groups (Conwell et al., 1993 ; Whyte, 1984 ); (2) recognise boys’ tendency to respond more readily to other boys (Webb, 1984 ) and, (3) maximise girls’ opportunities to interact which is seen to erode in mixed groups (Parker & Rennie, 2002 ; Rennie & Parker, 1987 ). Hong et al. ( 2012 ) examines such gender differences in detail specifically within the context of technological problem solving. Teacher participation in group allocation minimised inter-group conflict and interaction effects although groups still experienced naturally fluctuating attrition from pupil absences (School 1 = 17.6%; School 2 = 2.5% and School 3 = 8.8%).

Identification of most and least successful solutions

The research question requires differences to be identified in terms of levels of success. The overall trustworthiness of any differences therefore depends upon the credible identification of the most and least successful solutions from the thirteen produced. Wholly objective assessment of the pupils’ solutions is not possible, and material imperfections in different solutions negated reliable physical testing across the three classes. Moreover, because the researcher earlier observed pupils while problem solving, neutrality of researcher judgement in establishing a rank order of group solutions was equally problematic. Everton and Green ( 1986 ) identify this biasing risk between and early and later stages of research as a form of contamination.

To address these limitations, a Delphi technique was design using the work of Gordon ( 1994 ), Rowe and Wright ( 1999 ) and Yousuf ( 2007 ). This was undertaken anonymously prior to any analysis and, in conjunction with the results of physical testing, enabled the four most successful and four least successful solutions to be confidently identified independently of the researcher. A panel of eight secondary school teachers was convened from schools out with the study. All panel members had expertise in teaching structures with no dependent relationships or conflicts of interest. Following Delphi training, and a threshold level of 75%, the four most and four least successful solutions on outcome alone were identified after two rounds. Qualitative content validity checks confirmed that panel judgements fell within the scope of the accessible information. 37/43 reasons given were ‘High’, with six considered ‘Medium’ because the reasoning was partially speculative. When triangulated with additional evidence from physical testing, two cohorts of four groups were identified and paired to form four dyads (Table 1 ).

Study design

As noted, ‘Structures’ was chosen as a topic area and was new to all participants. It was appropriate for setting well-defined problems and allowed pupils to draw upon a sufficiently wide range of processes and knowledge types in developing a tangible, endurant solution. In discussion with the researcher, teachers did not alter their teaching style and adopted pedagogy and formative interactions that would support independent thinking, reasoning and problem solving. This study involved a learning phase, followed by a problem-solving phase.

In the learning phase, groups engaged over three fifty-minute periods with a unit of work on structures which was developed collaboratively with, and delivered by, the three classroom teachers. This allowed pupils to interact with materials and develop a qualitative understanding of key structural concepts including strength, tension and compression, triangulation, and turning moments. During this time, pupils also acclimatised to the presence of the researcher and recording equipment which helped to reduce any potential Hawthorne effect (Gall et al., 2003 ). Structured observations, teacher de-briefs and questionnaires were used in this phase to capture study effects, unit content coverage and environmental consistency between the three classrooms. Content coverage and environmental consistency were shown to be extremely high. Scores from the unit activity sheets that pupils completed were used to gauge group understanding of key concepts.

The problem-solving phase took place over two circa 50-minute periods (range: 40–52 m) in which pupils responded to a well-defined problem brief. This required them to develop a cantilever bridge enabling travel across a body of water. This bridge would enhance people’s ability to traverse terrain (conditions for being ‘technological’) with maximal span rigidity and minimal deflection (conditions for an ontologically ‘endurant’ solution). All groups had access to the same range and number of materials and resources and were issued with a base board showing water and land on which to develop their solutions.

While video capture was explored in depth (Lomax & Casey, 1998 ), challenges in reliably capturing solution detail resulted in group verbalisation being recorded as audio. This was synchronised with time interval photography and supplemented with structured observer-participant observation that focused on a sub-set of observable processes from the conceptual framework (Halfin, 1973 ). The developing technical solutions were viewed as manifestations of the knowledge and intellectual processes used by pupils at different points in time through their cognitive and material interactions. Photographs captured the results of these interactions in group solutions every 3–4 min but did not capture interactions between pupils. The structured observational approach adopted continuous coding similar to that found in the Flanders System of Interaction analysis (Amatari, 2015 ) and was refined through two pilot studies. During each problem-solving session, groups were observed at least twice between photographs and, following each session, pupil questionnaires, teacher de-briefs and solution videos (360° panoramic pivot about the solution) were completed to support future analysis. Reflexive accounts by the researcher also captured critical events, observer and study effects.

Analytical approach

All data were prepared, time-synchronised and analysed in three stages. Core verbal data (apx. 12h) and photographic data (n = 206) were triangulated with observational and other data against time. The problem-solving phase for each class was broken into a series of 3–4 min samples labelled S = 1, S = 2, S = 3…with durations in each recorded in minutes and seconds. Verbal data were analysed using NVivo software using digital waveforms rather than transcribed files to preserve immediacy, accuracy and minimise levels of interpretation (Wainwright & Russell, 2010 ; Zamawe, 2015 ). Photographic data were coded for the physical developments of the solutions (e.g. adding/removing materials in particular places) allowing solution development to be mapped for different groups over time. Triangulation of data also allowed coding to capture whether individual developments enhanced or detracted from the overall function efficacy of the solution.

The first stage of analysis was immersive, beginning with an initial codebook derived from the conceptual framework. In response to the data this iteratively shifted to a more inductive mode. To sensitise the analysis to differences, the most successful and the least successful groups were compared first as is discussed by Strauss 1987 (Miles & Huberman, 1994 , p.58). Three frameworks of differences emerged from this: (1) epistemic differences, (2) process differences, and (3) social and extrinsic differences. These were then applied to dyads of decreasing contrast and successively  refined in response to how these differences were reflected in the wider data set. Seven complete passes allowed non-profitable codes to be omitted and frameworks to be finalised. A final stage summarised differences across all groups.

Analysis and findings

The analysis and findings are presented in two main parts: (1) findings from the learning phase, and (2) findings from the problem-solving phase. Verbal data forms a core data source throughout and coding includes both counts and durations (in minutes and seconds). Direct quotations are used from verbal data, although the pupils involved in the study were from regions of Scotland with differing and often very strong local dialects. Quotations are therefore presented with dialect effects removed:

Example data excerpt reflecting dialect: “See instead-e all-e-us watchin’, we could all be doin’ su-hum instead-o watchin’ Leanne..” Example data excerpt with dialect removed: “See instead of all of us watching, we could all be doing something instead of watching Leanne..”

Part 1: Findings from the Learning Phase

Both teacher and researcher observation confirmed that pupils in all three classes engaged well with the unit of work (50 pupils across 13 groups) with all 40 content indicators covered by each class. Teachers of classes 1 and 3 commented that the lesson pace was slightly faster than pupils were used to. As expected, different teaching styles and examples were between classes, but all pupils completed the same unit activity sheets. The teacher of class 2, for example, used man-made structures and insect wings to explore triangulation; and the teacher in class 3 talked about the improved stability pupils get by standing with their feet apart. The understanding reflected in activity sheets was very good overall and Table 2 illustrates the percentage of correct responses for each class in relation to each of the three core concept areas.

Though unit activity sheets are not standardised tests, the conditions of administration, scoring, standards for interpretation, fairness and concept validity discussed by Gall et al. ( 2003 , p.xx) were maintained as far as possible. Evidence did not show that representational/stylistic variations by teachers had any discernible effect on pupil understanding and was seen to maintain normality from the pupils’ perspective. Class 3 scored consistently highly across all conceptual areas, although the qualitative understanding of turning moments was least secure for all three classes. Non-completion of selected questions in the task sheets partially explains lower numerical attainment for this concept in class 1 and 2, however, it is unknown if omissions resulted from a lack of understanding. The figures in Table 2 are absence corrected to account for fluctuating pupil attendance at sessions: (17.6% pupil absence across sessions for class 1, compared with 8.8% and 2.5% for classes 3 and 3 respectively). Table 3 illustrates the percentage scores for activity sheets completed by groups in the more and less successful cohorts.

Observational and reflexive data highlighted evidence of some researcher and recorder effects. These were typically associated with pupils’ interest in understanding the roles of the researcher and class teacher, and discussion around what they could say while being recorded. These subsided over time for all but two groups in Class 1, but with no substantive effect on pupils’ technological thinking.

In summary, findings from the learning phase show that: (1) Pupils engagement was high, and all classes covered the core structural concepts in the unit; (2) pupil knowledge and understanding, as measured by activity sheet responses, was very good overall but scores for turning moments were comparatively lower, and (3) study effect subsided quite quickly for all but two groups and there was no evidence showing these to be detrimental to technological thinking. These differences are considered epistemic and are captured in the framework of difference in Fig. 5 .

Part 2: findings from the problem-solving phase

Part 2 begins by describing the differences from comparing the material solutions produced by the most and least successful groups (dyad 1). Subsequent sections report upon the three areas in which difference were found: epistemic differences, process differences and social and extrinsic differences. Each of these sections lead with the analysis from the most contrasting groups (dyad 1) before presenting the resultant framework of difference. They conclude by reporting on how the differences in these frameworks are reflected across the wider data set. As with findings across all sections, findings only account for areas of the conceptual framework in which differences were identified. For processes such as measuring and testing, no difference was found and other processes, such as computing, did not feature for any of the groups.

Differences in the solutions produced by the most & least successful groups (dyad 1)

Group 5′s solution was identified as the most successful and Group7′s solution was identified as the least successful. Overall, both of these groups engaged well with the task and produced cantilevers that are shown in Figs. 2 and 3 . The order in which different parts of the solutions were developed is indicated by colour with the lighter parts appearing earlier in problem solving than the darker parts. Figure 4 shows this cumulative physical development of each solution over time. Both groups shared a similar conceptual basis and employed triangulation above and below the road surface. Figure 4 shows that Group 5′s solution evolved through 36 developments, while Group 7 undertook 23 developments and chose to strip down and restart their solution at the beginning of the second problem solving session. Similarly, groups 6, 11 and 13 removed or rebuilt significant sections of their solution. Neither group 5 or 7 undertook any developments under the rear of the road surface, and the greatest percentage of developments applied to the road surface itself (Group 7: 30.6%; Group 5: 47.8%). For Group 5, it was only developments 5 and 6 (Fig. 2 ) which offered little to no functional structural advantage. All other developments contributed to either triangulation, rigidity or strength through configuration and material choice with no evidence of misconception, which was also noted by the Delphi panel. The orientation, configuration and choice of materials by Group 7 share similarities with Group 5 insofar as each reflected knowledge of a cognate concept or principle (e.g. triangulation). Delphi Panel Member 8 described Group 7′s solution as having a good conceptual basis. Key differences, however, lay in the overall structural integrity of the solution and the underdevelopment of the road surface (Fig. 3 , Dev.1 and Dev.5) which mean that Group 5 achieved a more ontologically endurant solution than Group 7 did. Evidence from Group 7′s discussion (S = 3, 3.34–3.37; S = 3, 3.38–3.39; S = 16, 3.26–3.30) suggests this is partly because of misconception and deficits in knowledge about materials and the task/cantilever requirements. This was also reflected in the group’s activity responses during structures unit in the learning phase. Alongside the photographic evidence and reflexive notes of the researcher, this suggest that there was  some difficultly in translating concepts and ideas into a practical form. This constitutes a difference in tacit-procedural knowledge between Group 5 and Group 7.

‘Group 5 solution schematic’

‘Group 7 solution schematic’

‘Cumulative development of tangible solutions’

Epistemic differences during problem solving

As well as the knowledge differences in the learning phase and the physical solutions, analysis of the most and least successful groups revealed epistemic differences in problem solving activity related to ‘task knowledge’ and ‘knowledge of concepts and principles’. The extent to which ‘knowledge’ can be reliably coded for in this context is limited because it rapidly becomes inseparable from process. Skills are processes which, in turn, are forms of enacted knowledge. Consequently, although Halfin ( 1973 ) defines idea generation as a knowledge generating process using all the senses, attempts to code for this were unsuccessful because it was not possible to ascertain with any confidence where one idea ended, and another began. Coding was possible, however, for ‘prior personal knowledge’, ‘task knowledge’ and ‘prior technological knowledge’. The analysis of these is present along with the resulting framework of epistemic difference with prior personal knowledge omitted on the basis that no differences between groups was found. The final section looks at how epistemic differences are reflected in the activity of the remaining groups.

Epistemic differences between the most & least successful groups (dyad 1)

Task knowledge is the knowledge pupils have of the problem statement and includes relatively objective parameters, conditions, and constraints. One key difference was the extent to which groups explicitly used this to support decision making. Group 5 spent considerably more time than Group 7 discussing what they knew and understood of the task prior to construction (1m10s vs. 8 s) but during construction, had more instances where their knowledge of the task appeared uncertain or was questioned (n = 6 for Group 5 vs. n = 2 for Group 7). Differences were also found in the prior technological knowledge used by groups. This knowledge includes core structural concepts and principles explored in the learning phase. As with task knowledge, Group 5 verbalised this category of knowledge to a far greater extent than Group 7, both apart from, and as part of, formative discussions with the class teacher (18:59 s vs. 14:43 s). In only one instance was the prior technological knowledge of Group 5 incorrect or uncertain compared with four instances for Group 7. These included misconceptions about triangulation and strength despite performing well with these in the learning phase. Furthermore, some instances of erroneous knowledge impacted directly upon solution development. In response to a discussion about rigidity and the physical performance of the road surface, one pupil stated: “Yes, but it is supposed to be able to bend in the middle..” (Group 7, S = 3, 3.34–3.37) meaning that the group did not sufficient attend to this point of structural weakness which resulted in a less endurant solution. No such occurrences took place with Group 5. More prominent and accurate use of this type of knowledge supports stronger application of learning into the problem-solving context and appeared to accompany greater solution integrity.

From these findings, and those from the learning phase, the framework of difference shown in Fig. 5 was developed:

‘Framework of epistemic differences from comparative analysis of Group 5 and 7’

Epistemic differences across all groups (dyads 1–4)

As with dyad 1, the more successful groups in dyads 3 and 4 scored higher (+ 14% and + 20.7%, respectively) in the learning phase compared with their less successful partner groups. This, however, was not seen with dyad 2. The less successful group achieved a higher average score of 86.3% compared with 71% and, despite greater fluctuations in pupil attendance, scored 100% for turning moments compared with 58% for the more successful group. Although comparatively minimal across all groups, more successful groups in each dyad tended to explicitly verbalise technological and task knowledge more than less successful groups. Furthermore, it was more often correct or certain for more successful groups. This was particularly true for dyad 2, although there was some uncertainty about the strongest shapes for given materials in, for example, Group 12 which was the more successful group of dyad 3. The greatest similarity in verbalised task knowledge was observed with the least contrasting dyad, although evidence from concept sketching (Figs. 6 , 7 ) illustrated a shared misunderstanding between both groups of the cantilever and task requirements.

‘Group 2 concept sketch’

‘Group 8 concept sketch’

The differences in tacit-procedural knowledge between Group 5 and 7 were reflected quite consistently across other dyads, with more successful groups showing greater accuracy, skill and judgement in solution construction. The more successful groups in dyads 2 and 3 undertook three material developments that offered little to no functional advantage, and each of the developments these groups undertook correctly embodied knowledge of cognate structural concepts and principles. Notably, Group 8 of dyad 4 was able to achieved this with no structural redundancy at all. Less successful groups, however, were not as secure in their grasp of the functional dependencies and interrelationships between different parts of their structural systems. The starkest example of this was with Group 4 of dyad 3, who explicitly used triangulation but their failure to physically connect it with other parts of the structure rendered the triangulation redundant. Group 2 of dyad 4 were the only group not to triangulate the underside of the road surface. Less successful groups tended to focus slightly more of their material developments in areas of the bridge other than the road surface, whereas the opposite tended to be true for the other groups. Significantly, while all groups in the study included developments that offered little to no functional advantage, it was only in the case of less successful groups that these impaired the overall functional performance of solutions in some way. Table 4 summarises the sustained epistemic difference across all four dyads.

Process differences

Analysis of the most contrasting dyad yielded process differences in: (1) managing (Halfin, 1973 ), (2) planning, and (3) reflection. Groups managed role and task allocation differently, as well as engaging in different approaches to planning aspects of solution development. Reflection, as a process of drawing meaning or conclusions from past events, is not explicitly identified by Halfin or the conceptual framework. Two new forms of reflection for well-defined technological problem solving (declarative reflection and analytical reflection) were therefor developed to account for the differences found. The analysis of the process differences is presented with the resulting framework for this dyad. The final section presents sustained process differences across all groups.

Difference in managing—role & task allocation & adoption (dyad 1)

The autonomous creation of roles and allocation of tasks featured heavily in the activity of Group 5. These typically clustered around agreed tasks such as sketching (S = 2, 1.46), and points where group members were not directly engaged in construction. In total, Group 5 allocated or adopted roles or task on 31 occasions during problem solving compared with only 7 for Group 7. Both groups did so to assist other members (Group 5, S = 16, 3.33–3.38; Group 7, S = 3, 0.37–0.41), to take advantage of certain skills that group members were perceived to possess (Group 5, S = 2, 1.47- 1.49; Group 7, S = 2, 2.03–2.06) and, for one instance in Group 7, to prevent one group member from executing something incorrectly (S = 16, 2.11–2.13). There was evidence, however, that Group 5 moved beyond these quite pragmatic drivers. Member often had more of a choice and, as shown in Excerpt 5, allocation and adoption is mediated by sense of ownership and fairness.

Excerpt 5: Idea Ownership (Sketching) Pupil ?: “You can’t draw on them..” Pupil 1: “You draw Chloe, I can’t draw..” Pupil 2: “I know I can’t draw on them, that’s why I doing them; no, because you, you had the ideas… because you had…” Pupil ?: “(unclear)” Pupil 3: “Just draw your own ideas, right, you can share with mine right…. Right, you draw the thread one, I’ll do the straw thing…” (Group 5, S  =  2, 1.46–1.59)

The effective use of role and task allocation appeared to play an important role in realising an effective technical solution, however, negative managerial traits were perhaps more significant.

Difference in managing—negative managerial traits (dyad 1)

Evidence of differences between Group 5 and 7 were found in relation to: (1) group involvement, and (2) fragmentation of group vision, which were found to be highly interrelated. Negative group involvement accounted for traits of dominance and dismissiveness. For Group 7, this was more prevalent earlier in the problem-solving activity where one group member tended to dominate the process. This pupil tabled 9 out of 11 proposals prior to working with physical materials and, at times, readily dismissed suggestions by other group members (See Excerpt 1). Moreover, ideas and proposals within the group were sometimes poorly communicated (Excerpt 2), which led to a growing level of disenfranchisement for some group members and a fragmented group vision for solution development.

Excerpt 1 Pupil 1:“We could do it that way…” (Pupils continue discussion without acknowledgement) Pupil 1:“You could do that..” Pupil 2:“Shut up, how are we going to do that?” Pupil 1:“Well you’re allowed glue, and you’re allowed scissors..” Several group members: “Shut-up!” (Group 7, S = 1, 2.07–2.28) Excerpt 2 “(Loud inhalation) Watch my brilliant idea… I need scissors.. Are you allowed scissors?” (Group 7, S = 1, 1.36–1.41)

The was some evidence of dismissiveness present with Group 5 also (e.g. S = 9, 1.32–1.46), however, group members were able to voice their ideas which appeared to support a better shared understanding among group members. Notably, Group 5 reached a degree of consensus about what they would do prior to constructing anything, whilst Group 7 did not. Even in these early stages, two of the four members of Group 7 made it very clear that they did not know what was happening (Excerpt 3).

Excerpt 3 Pupil 1: “What are you all up to?” Pupil 2: “Move you” Pupil 4: “No idea” Pupil 2: “You’re allowed to say hell are you not?” Pupil ?: “Helli-yeh” Pupil 2: “Hellilouya” (slight laughter) Pupil 3: “Right so were going to..(unclear) and do that..” Pupil 1: “What are you all up to?” Pupil 2: “Just… I know what he’s thinking of..” Pupil 4: “I don’t have a clue what you’re thinking of..” Pupil 3: “Neither do I..” (Group 7, S = 2, 0.15–0.33)

Occurrence like these contributed to a growing sense of fragmentation in the group. Verbal and observational data show this to have been picked up by the class teacher who tried to encourage and support the group to share and discussed ideas more fully. Despite this, the group lost their sense of shared vision about how to approach a solution and, part way through the first session, two group members attempted to begin developing a separate solution of their own (S-3, 2.52).

The final managerial difference between Group 5 and 7 was the way in which efforts were made to increase the efficiency of solution development. Seen as a positive managerial trait, both groups did this, but it was more frequent and more developed with Group 5. There were four examples of this with Group 7 in the form of simple prompts to speed the process up (E.g. S = 5:3.02–3.04; S = 6:2.22–2.23; S = 11: 1.34–1.35) and 25 examples with Group 5 involving prompts and orchestrating parallel rather than successive activity.

Differences in planning (dyad 1)

Differences emerged in how Group 5 and 7 thought about and prepared for future problem-solving activity. While the complexity of the pupils’ problem-solving prevented cause and effect from being attributed to planning decisions, four areas of difference were identified: (1) determining use of/amount of materials/resources, (2) sequencing, ordering or prioritising, (3) identification of global solution requirements, and (4) working through how an idea should be practically executed. Across both problem-solving sessions, Group 5 spent over three times as long as Group 7 did, engaging in these forms of planning (8m17s vs. 2.23 s), but Group 7 planned on almost twice as many occasions (n = 98 vs. n = 56). Both groups considered the availability of materials for, and matching of materials to, given ideas (e.g. Group 5, S = 5:3.38–3.48; Group 7, S = 4:2.20–2.34; S = 12:1.53–2.00) and both identified global solution requirements. At the start, Group 5 engaged in 12 min of planning in which they read task instructions (S = 1, 0.49–1.49), explored, tested, and compared the available materials (S = 1, 1.49–2.10), and agreed on a starting point. As shown in Excerpt 4, these discussions attempted to integrate thinking on materials, joining methods, placement. As the class teacher observed, Group 7 were eager to begin construction after 4m45s and did so without an agreed starting point. Pupils in this group explored materials in a more reactive way in response to construction.

Excerpt 4 “..a tiny bit of cardboard, right, this is the cardboard, right.. (picks up part) put glue on it so that’s on that, right.. (modelling part orientation) then put glue on it there so it sticks down.. something to stick it down, do you know what I mean?” (Group 5, S = 9, 2.10–2.20)

Despite similar types of planning processes, the planning discourse of Group 5 was more proactive, and this may have minimised inefficiencies and avoidable errors. For Group 7, two group members unintentionally drew the same idea (S = 2, 3.19–3.26), parts were taped in the wrong place (S = 17, 1.26–1.40) and others glued in the wrong order (S = 5, 1.28–1.30 and 1.48–1.56). Such occurrences, however, notably reduced after the group re-started their solution in the second session which also mirrored a 73% drop in poor group involvement. Communication played an important role in planning and there was no evidence of avoidable errors with Group 5.

Differences in reflection (dyad 1)

The most prevent differences in this study were found in how Group 5 and Group 7 reflected upon their developing solutions. Analysis revealed two main forms of reflection that were used differently by groups. ‘Declarative reflection’ lies close to observation and is defined by this study as reflection that does not explicitly reveal anything of a pupil’s knowledge of technical relationships within their solution, e.g.: “that’s not going to be strong…” (Group 7, S = 2, 0.49–0.51). This form of reflection was critical for both groups who used it heuristically to quality assure material developments, but it was used slightly more often by Group 7 (n = 164:4m30s vs. n = 145:4m07s). By contrast, ‘analytical reflection’ is defined as that which does reveal something of a pupil’s knowledge of technical relationships between two or more parts of a solution. Examples of this are shown in Excerpts 5 and 6 where pupils are reflecting upon an attempt made to support the underside of the road surface.

Excerpt 5: “It’s not going to work because it’s in compression and straws bend..” (Group 5, S = 9, 2.3–2.35) Excerpt 6: “no, that’ll be… oh, aye, because that would weight it down and it would go into the water.” (Group 5, S = 14, 3.35–3.38)

Looking across verbal and observational data, there was no consistent pattern to the use of declarative reflection but analytical reflection for both groups was almost exclusively anchored around, and promoted by, the practical enactment of an idea and could be associated with predictions about the future performance of their solution. Overall, both Group 5 and 7 reflected a similar number of times (n = 216 and n = 209, respectively) although the total amount of time spent reflecting was 17% longer for Group 5. This difference in time was accounted for by comparatively more analytical reflection in Group 5 (n = 75:3m47s vs. n = 45:2m10s for Group 7), particularly during the first half of problem solving. It was also interesting that Group 7 engaged with no analytical reflection at all prior to construction.

Findings from process management, planning and reflection led to the framework of difference in Fig. 8 . This also accounts for differences in the amount of time each group reflected upon the task detail, but this was extremely limited (Group 5: n = 7, 26 s; Group 7: n = 5, 10 s).

‘Framework of process differences from comparative analysis of Group 5 and 7’

Process differences across all groups (dyads 1–4)

Task reflection, attempts at increasing efficiency and differences of fragmented vision found with the most contrasting dyad were not sustained across remaining groups. The only sufficiently consistent difference in patterns of solution development was that more successful groups, on average, spent 18% longer in planning and discussion before beginning to construct anything.

Overall, the nature and patterns of good and poor group involvement from dyad 1 were reflected more widely, with some instances of deviation. The more successful group in dyad 4 had more significant and numerous examples of poor group involvement than did the less successful group (n = 16 vs. n = 10), although they made more effective use of roles and task allocation and spent longer engaged in planning processes. Dyad 2 deviated also insofar as the less successful group (13) actually had fewer avoidable errors than Group 6 who accidentally cut the incorrect parts (e.g. S = 15, 2.44–2.47), undertook developments that were not required (e.g. S = 6, 2.11–2.16) and integrated the wrong parts into their solution (e.g. S = 7, 1.10–1.13).

Differences in the nature and use of reflection was one of the most consistently sustained findings between the most and least successful cohorts. All four of the more successful groups engaged more heavily in reflective processes and more of this reflection was analytical in nature. This shows that reflection which explicitly integrates knowledge of technical relationships between different aspects of a solution plays an important role in more successful technical outcomes. Whilst declarative reflection remained important for all groups, it was also less prominent for groups in the less successful cohort. Table 5 summarises the sustained process difference across dyads 1, 2, 3 and 4.

Social & extrinsic differences (dyad 1)

Differences reported in this section lie out with the formal conceptual framework of the study but, nonetheless, were shown to play a role in the technological problem-solving activity of dyad 1. Differences between Group 5 and 7 emerged in three areas: (1) group tension, (2) effects of the classroom competitive dynamic, and (3) study effects. Group tension, which relates to aspects of interaction such as argumentative discourse, raised voices and exasperation, were negligible for Group 5 (n = 4, 0m24s) when compared with Group 7 (n = 38, 2m38s) and related exclusively to pupils having their voiced heard. For group 7, tension was evident during both sessions, but was more significant in the first session before re-starting the solution in session 2 and purposeful attempts to work more collaboratively with the support of the teacher (Group 7, S = 10, 0.36–1.29). Observations revealed that tension was typically caused by pupils failing to carry out practical processes to the standard of other group members, or breaking parts such as the thread supporting the road surface in the 36 th minute of Session 2.

Despite collaborative efforts within groups, there was a sense of competitive dynamic which appeared either to positively bias, negatively bias, or to not affect group activity. This competitive dynamic was present in groups comparing themselves to other groups in the class. Group 7 had 3.7 times as many instances of this as Group 5 with 73% of these negatively affecting the group. These included interference from and with other groups (S = 7, 0.07–0.12), attempting to copy other groups (S = 7, 1.14–1.22) and comparing the solutions of other groups to their own (S = 8, 2.55–2.59). In contrast, Group 5 appeared to be far less affected by perceptions of competition. Around a third of instances were coded as neutral, however, Group 7 experienced more instances of positive competitive effects than Group 5 did (n = 5 vs. n = 1).

Study effects were present for both groups often triggered by the arrival of the researcher at their table to observe or take photographs. The biggest difference in study effects was associated with the audio recorder. Recorder effects for Group 7 were three and half times that of Group 5 involving discussion about how it worked (Group 7, S = 10, 3.04–3.17), or about what was caught or not caught on tape (Group 7, S = 14, 1.01–1.45). Although questionnaire data showed that pupils in Group 5 felt that they talked less in the presence of the recorder, this was not supported by observations, verbal data, or the class teacher. From these findings, the framework of social and extrinsic difference in Fig. 9 was developed.

‘Framework of social & extrinsic differences from comparative analysis of Group 5 and 7’

Social & extrinsic differences across all groups (dyads 1–4)

Most of the social and extrinsic differences identified with Groups 5 and 7 were reflected to greater or lesser extents in other dyads. In addition to less successful groups being more susceptible to researcher and recorder effects, two specific points of interest emerged. Firstly, group tension was considerably more prominent for less successful groups than it was for more successful groups. Although no evidence of a direct relationship was established, tension appeared to accompany poor managerial traits and the changing of group composition (e.g. Group 8, Group 13). The most significant differences in tension were found with dyad 3. No occurrences were found for the most successful group and 29 were seen with the least successful group including aggressive and abrupt communication between pupils involving blame for substandard construction (S = 10, 2.28–2.38), through to name calling (S = 12, 0.20–0.22), arguing (S = 6, 1.46–2.10) and threats of physical violence (S = 11, 3.25–3.29).

Secondly, the more successful groups were influenced by the competitive class dynamic more than the less successful groups were. This is the only sustained finding that directly opposes what was found with dyad 1. These took the form of neutral or negative inter-group effects involving comparing and judging other groups (e.g. Group 6), espionage, copying or suspicion thereof (e.g. Group 6, 8 and 12). Table 6 summarises the sustained social and extrinsic differences across the more and less successful cohorts.

Discussion and Conclusions

This study established and applied three frameworks to capture the epistemic, procedural, and social and extrinsic differences between groups of pupils as they developed solutions to a well-defined technological problem. Social & extrinsic findings revealed higher levels of group tension for the less successful cohort, but that more successful groups elicited more negative responses to the competitive class dynamic created by different groups solving the same problem. Major findings about differences in knowledge and process are discussed. Thereafter, a three-part characterisation of thinking for well-defined technological problem solving is presented in support of pedagogy for Design & Technology classrooms.

The most important of those knowledge differences uncovered were found in: (1) the material development of the solution itself, and (2) the reflective processes used by groups during problem solving. The conceptual framework characterises ‘tacit-procedural knowledge’ as the implicit procedural knowledge embodied in technical skill, accuracy and judgement, and this was further refined in the solutions of more successful groups. Linked to this was the fact that several of the material developments for triangulation and strength were improperly realised by less successful groups which negatively impacted on the functional performance of their solutions. Often, this was despite evidence of a good conceptual understanding of triangulation, tension, and compression in the learning phase. An ontologically endurant solution requires stability over time and lesser developed aspects of tacit-procedural knowledge and knowledge application meant that this was not realised as fully as possible for some groups.

This can be partly explained by the challenge of learning transfer, or more accurately, learning application. Several notable studies have explored these difficulties in technology education (Brown, 2001 ; Dixon & Brown, 2012 ; Kelly & Kellam, 2009 ; Wicklein & Schell, 1995 ), but typically at a subject or interdisciplinary level. The findings of this study suggest that, even when the concepts in a learning unit are tightly aligned with a well-defined problem brief, some pupils find difficulty in applying them within a tangible, material context. It could be argued that more successful groups were better at connecting learning between different contexts associated with the problem-solving task and could apply this with more developed skill and judgement.

The second important knowledge difference arose in the various forms of reflection that groups engaged with. Reflection in this study supports pupils in cycling through the re-application/transformation loop in a similar way to the perception/translation/evaluation blocks of the iterative models of problem solving (Argyle, 1972 ; Miodusre & Kipperman, 2002 ; Scrivener et al., 2002 ). Surprisingly few studies explore ‘reflection’ as a process in technological thinking (Kavousi et al., 2020 ; Luppicini, 2003 ; Lousberg et al., 2020 ), and fewer still in the context of school-level technological problem solving. This study found that more successful groups reflected more frequently, and that more of this reflection was analytical insofar as it explicitly revealed knowledge of technical relationships between different variables or parts of their solution. Such instances are likely to have been powerful in shaping the shared understanding of the group. This type of reflection is significant because it takes place at a deeper level than declarative reflection and is amalgamated with pupils’ subject knowledge and qualitative understanding of their technical solution. This allowed pupils to look back and to predict by explicitly making connections between technical aspects of their solution.

The final area in which important differences were found was management of the problem-solving process which is accounted for by Halfin ( 1973 ) in his mental process set. When analysed, the more successful cohort exploited more positive managerial strategies, and fewer negative traits. They made more extensive and effective use of role and task allocation, spent more time planning ahead and longer in the earlier conceptual phase prior to construction. Other studies have also captured aspects of these for technology education. Hennessy and Murphy ( 1999 ) discuss peer interaction, planning, co-operation and conflict, and changing roles and responsibilities as features of collaboration with significant potential for problem solving in technology. Rowell ( 2002 ), in a study of a single pair of technology pupils, demonstrated the significance of roles and participative decisions as enablers and inhibiters of what pupils take away from learning situations. What was interesting about the groups involved in this study, was that the managerial approaches were collectively more proactive in nature for more successful groups. Less successful groups were generally more reactive to emergent successes or problems during solution development.

The problem-solving activity of pupils in this study was exceptionally complex and a fuller understanding of how these complexities interacted would have to be further explored. Yet, key differences in knowledge and process collectively suggest that effectively solving well-defined technological problems involves a combination of proactive rather than reactive process management, and an ability to make two different types of technology-specific connections: contextual connections and technical connections. Proactively managing is generic and involves planning, sequencing, and resourcing developments beyond those that are immediately in play to minimise avoidable errors with reference to problem parameters. It involves group members through agreed roles and task allocation that, where possible, capitalise on their strengths. Contextual connections involve effectively linking and applying technological knowledge, concepts, and principles to the material context that have been learnt form other contexts out with solution development. This is supported by skill and judgement in the material developments that embody this knowledge. Finally, technical connections appear to be important for better functioning solutions. These are links in understanding that pupils make between different parts of the developing solution that reveal and build knowledge of interrelationships, dependencies and how their solution works. In addition to helping pupils developing effective managerial approaches in group work, this suggests that pedagogical approaches should not assume pupils are simply able to make contextual and technical connections during technological problem solving.  Rather, pedagogy should actively seek to help pupils make both forms of connection explicit in their thinking.

This study has determined that proactive management, contextual and technical connections are important characteristics of the modus operandi of pupils who successfully solve well-defined technological problems. This study does not make any claim about the learning that pupils might have taken from the problem-solving experience. It does, however, provide key findings that teachers can use to support questioning, formative assessment and pedagogies that help pupils in solving well-structured technological problems more effectively.

Ethical approval

Ethical approval for this study was granted by the School of Education Ethics Committee at the University of Glasgow and guided by the British Educational Research Association Ethical Code of Conduct. All necessary permissions and informed consents were gained, and participants knew they could withdraw at any time without giving a reason. The author declares no conflicts of interest in carrying out this study.

Argyle, M. (1972). Anlaysis of the behaviour of an interactor. In A. Morrison & D. McIntyre (Eds.), The social psychology of teaching. Cox & Wyman Ltd.

Google Scholar  

Bartholomew, S. R., & Strimel, G. J. (2018). Factors influencing student success on open-ended design problems. International Journal of Technology and Design Education, 28 (3), 753–770. https://doi.org/10.1007/s10798-017-9415-2 .

Article   Google Scholar  

Brown, D. (2001). Cognitive science concepts and technology teacher education. The Journal of Technology Studies, 27 (1), 33–42. https://doi.org/10.21061/jots.v27i1.a.7 .

Buckley, J., Seery, N., & Canty, D. (2019). Investigating the use of spatial reasoning strategies in geometric problem solving. International Journal of Technology and Design Education, 29 (2), 341–362. https://doi.org/10.1007/s10798-018-9446-3 .

Conwell, C. R., Griffin, S., & Algozzine, B. (1993). Gender and racial differences in unstructured learning groups in science. International Journal of Science Education, 15 (1), 107–115. https://doi.org/10.1080/0950069930150109 .

Custer, R. L. (1995). Examining the dimensions of technology. International Journal of Technology and Design Education, 5 (3), 219–244. https://doi.org/10.1007/BF00769905 .

Custer, R. L., Valesey, B. G., & Burke, B. N. (2001). An Assessment model for a design approach to technological problem solving. Journal of Technology Education, 12 (2), 5–20. https://doi.org/10.21061/jte.v12i2.a.1 .

de Vries, M. J. (2005). The nature of technological knowledge: Philosophical reflections and educational consequences. International Journal of Technology and Design Education, 15 (2), 149–154. https://doi.org/10.1007/s10798-005-8276-2 .

DeLuca, V. W. (1991). Implementing technology education problem-solving activities. Journal of Technology Education, 2 (2), 1–10. https://doi.org/10.21061/jte.v2i2.a.2 .

Dixon, R. A., & Brown, R. A. (2012). Transfer of learning: Connecting concepts during problem solving. Journal of Technology Education, 24 (1), 2–17. https://doi.org/10.21061/jte.v24i1.a.1 .

Doornekamp, B. G. (2001). Designing teaching materials for learning problem solving in technology education. Research in Science & Technological Education, 19 (1), 25–38. https://doi.org/10.1080/02635140120046204 .

Elo, S., & Kyngäs, H. (2008). The qualitative content analysis process. Journal of Advanced Nursing, 62 (1), 107–115. https://doi.org/10.1111/j.1365-2648.2007.04569.x .

Erkip, F., Demirkan, H., & Pultar, M. (1997). Knowledge acquisition for design education. In IDATER 97 Conference, 1997 (pp. 126-132). Loughborough: Loughborough University.

Everton, C. M., & Green, J. L. (1986). Observation as inquiry and method. In M. C. Wittrock (Ed.), Handbook of research on teaching. (3rd ed., pp. 192–213). MacMillan.

Frey, R. E. (1989). A philosophical framework for understanding technology. Journal of Industrial Teacher Education, 27 (1), 23–35.

Gall, M. D., Gall, J. P., & Borg, W. R. (2003). Educational Research: an introduction . (7th ed.). Allyn and Bacon.

Gómez Puente, S. M., van Eijck, M., & Jochems, W. (2013). A sampled literature review of design-based learning approaches: A search for key characteristics. International Journal of Technology and Design Education, 23 (3), 717–732. https://doi.org/10.1007/s10798-012-9212-x .

Gordon, T. J. (1994). The delphi method. Futures research methodology, 2 (3), 1–30.

Grubbs, M. E., Strimel, G. J., & Kim, E. (2018). Examining design cognition coding schemes for P-12 engineering/technology education. International Journal of Technology and Design Education, 28 (4), 899–920. https://doi.org/10.1007/s10798-017-9427-y .

Halfin, H. H. (1973). Technology: A process approach. Doctoral Thesis, West Virginia University, West Virginia.

Hamel, R., & Elshout, J. J. (2000). On the development of knowledge during problem solving. European Journal of Cognitive Psychology, 12 (3), 289–322.

Harkins, S. G. (1987). Social loafing and social facilitation. Journal of Experimental Social Psychology, 23 (1), 1–18.

Haupt, G. (2018). Hierarchical thinking: A cognitive tool for guiding coherent decision making in design problem solving. International Journal of Technology and Design Education, 28 (1), 207–237. https://doi.org/10.1007/s10798-016-9381-0 .

Hennessy, S., & Murphy, P. (1999). The potential for collaborative problem solving in design and technology. International Journal of Technology and Design Education, 9 (1), 1–36. https://doi.org/10.1023/A:1008855526312 .

Hill, R. B. (1997). The design of an instrument to assess problem solving activities in technology education. Journal of Technology Education , 9 (1), 31–46.

Hill, R. B., & Wicklein, R. C. (1999). A factor analysis of primary mental processes for technological problem solving. Journal of Industrial Teacher Education, 36 (2), 83–100.

Hong, J.-C., Hwang, M.-Y., Wong, W.-T., Lin, H.-C., & Yau, C.-M. (2012). Gender differences in social cognitive learning at a technological project design. International Journal of Technology and Design Education, 22 (4), 451–472. https://doi.org/10.1007/s10798-011-9152-x .

Jackson, A., & Strimel, G. (2018). Toward a matrix of situated design cognition. CTETE Research Monograph Series, 1 (1), 49–65. https://doi.org/10.21061/ctete-rms.v1.c.3 .

Johnson, S. D. (1997). Learning technological concepts and developing intellectual skills. International Journal of Technology and Design Education, 7 (1–2), 161–180.

Jonassen, D. H. (1997). Instructional design models for well-structured and III-structured problem-solving learning outcomes. Educational Technology Research and Development, 45 (1), 65–94. https://doi.org/10.1007/BF02299613 .

Jones, A. (1997). Recent research in learning technological concepts and processes. International Journal of Technology and Design Education, 7 (1–2), 83–96. https://doi.org/10.1023/A:1008813120391 .

Kavousi, S., Miller, P. A., & Alexander, P. A. (2020). Modeling metacognition in design thinking and design making. International Journal of Technology and Design Education, 30 (4), 709–735. https://doi.org/10.1007/s10798-019-09521-9 .

Kelley, T., & Kellam, N. (2009). A theoretical framework to guide the re-engineering of technology education. Journal of Technology Education, 20 (2), 37–49. https://doi.org/10.21061/jte.v20i2.a.3 .

Kelley, T. R. (2008). Cognitive processes of students participating in engineering-focused design instruction. Journal of Technology Education, 19 (2), 15.

Lavonen, J., Meisalo, V., & Lattu, M. (2002). Collaborative problem solving in a control technology learning environment, a pilot study. International Journal of Technology and Design Education, 12 (2), 139–160. https://doi.org/10.1023/A:1015261004362 .

Lewis, T. (2005). Creativity a framework for the design/problem solving discourse in technology education. Journal of Technology Education . https://doi.org/10.21061/jte.v17i1.a.3 .

Lewis, T. (2009). Creativity in technology education: Providing children with glimpses of their inventive potential. International Journal of Technology and Design Education, 19 (3), 255–268. https://doi.org/10.1007/s10798-008-9051-y .

Liddament, T. (1996). Design and Problem-Solving. In IDATER 1996 Conference, 1996 (pp. 1-5). Loughborough: Loughborough University.

Lomax, H., & Casey, N. (1998). Recording social life: Reflexivity and video methodology. Sociological Research Online, 3 (2), 121–146.

Lousberg, L., Rooij, R., van Jansen, S., Dooren, E., & van der Zaag, E. (2020). Reflection in design education. International Journal of Technology and Design Education, 30 (5), 885–897. https://doi.org/10.1007/s10798-019-09532-6 .

Luppicini, R. (2003). Reflective action instructional design (raid): A designer’s aid. International Journal of Technology and Design Education, 13 (1), 75–82. https://doi.org/10.1023/B:ITDE.0000039569.05754.a8 .

MacPherson, R. T. (1998). Factors affecting technological trouble shooting skills. Journal of Industrial Teacher Education, 35 (4), 1–29.

Mawson, B. (2003). Beyond `the design process’: an alternative pedagogy for technology education. International Journal of Technology and Design Education, 13 (2), 117–128. https://doi.org/10.1023/A:1024186814591 .

McCade, J. (1990). Problem solving: Much more than just design. Journal of Technology Education, 2 (1), 1–13. https://doi.org/10.21061/jte.v2i1.a.5 .

McCormick, R. (1994). The problem solving in technology education (PSTE) project. International Journal of Technology and Design Education, 5 (2), 173–175. https://doi.org/10.1007/BF00766816 .

Mccormick, R. (1997). Conceptual and procedural knowledge. International Journal of Technology and Design Education, 7 (1–2), 161–180.

McCormick, R. (2004). Issues of learning and knowledge in technology education. International Journal of Technology and Design Education, 14 (1), 21–44. https://doi.org/10.1023/B:ITDE.0000007359.81781.7c .

McLellan, R., & Nicholl, B. (2011). “If I was going to design a chair, the last thing I would look at is a chair”: Product analysis and the causes of fixation in students’ design work 11–16 years. International Journal of Technology and Design Education, 21 (1), 71–92. https://doi.org/10.1007/s10798-009-9107-7 .

Middleton, H. (2009). Problem-solving in technology education as an approach to education for sustainable development. International Journal of Technology and Design Education, 19 (2), 187–197. https://doi.org/10.1007/s10798-008-9075-3 .

Miles, B. M., & Huberman, A. M. (1994). Qualitative data analysis: An expanded source book (2nd ed.). California: Sage Publications.

Mioduser, D. (1998). Framework for the study of cognitive and curricular issues of technological problem solving. International Journal of Technology and Design Education, 8 (2), 167–184. https://doi.org/10.1023/A:1008824125352 .

Mioduser, D. (2002). Evaluation/Modification cycles in junior high students’ technological problem solving. International Journal of Technology and Design Education, 12 (2), 123–138. https://doi.org/10.1023/A:1015256928387 .

Mioduser, D., & Dagan, O. (2007). The effect of alternative approaches to design instruction (structural or functional) on students’ mental models of technological design processes. International Journal of Technology and Design Education, 17 (2), 135–148. https://doi.org/10.1007/s10798-006-0004-z .

Morgan, K. (2008). Does Polanyi’s Tacit Knowledge Dimension Exist? In Polanyi Society Conference, 2008 . Chicago: Loyola University.

Morrison-Love, D. (2017). Towards a transformative epistemology of technology education: An epistemology of technology education. Journal of Philosophy of Education, 51 (1), 23–37. https://doi.org/10.1111/1467-9752.12226 .

Murphy, P., & McCormick, R. (1997). Problem solving in science and technology education. Research in Science Education, 27 (3), 461–481. https://doi.org/10.1007/BF02461765 .

Odiri Amatari, V. (2015). The instructional process: a review of flanders’ interaction analysis in a classroom setting. International Journal of Secondary Education, 3 (5), 43–49. https://doi.org/10.11648/j.ijsedu.20150305.11 .

Parker, L. H., & Rennie, L. J. (2002). Teachers’ implementation of gender-inclusive instructional strategies in single-sex and mixed-sex science classrooms. International Journal of Science Education, 24 (9), 881–897. https://doi.org/10.1080/09500690110078860 .

Polanyi, M. (1967). The tacit dimension . Routledge and Kegan Paul.

Rauscher, W. (2011). The technological knowledge used by technology education students in capability tasks. International Journal of Technology and Design Education, 21 (3), 291–305. https://doi.org/10.1007/s10798-010-9120-x .

Relations, U. o. O. I. o. G., & Sherif, M. (1961). Intergroup conflict and cooperation: The Robbers Cave experiment (Vol. 10): University Book Exchange Norman, OK.

Rennie, L. J., & Parker, L. H. (1987). Detecting and accounting for gender differences in mixed-sex and single-sex groupings in science lessons. Educational Review, 39 (1), 65–73. https://doi.org/10.1080/0013191870390107 .

Ropohl, N. (1997). Knowledge types in technology. International Journal of Technology and Design Education, 7 (1–2), 56–72.

Rowe, G., & Wright, G. (1999). The delphi technique as a forecasting tool: Issues and analysis. International Journal of Forecasting, 15 (4), 353–375. https://doi.org/10.1016/S0169-2070(99)00018-7 .

Rowell, P. M. (2002). Peer interactions in shared technological activity: A study of participation. International Journal of Technology and Design Education, 12 (1), 1–22. https://doi.org/10.1023/A:1013081115540 .

Salomon, G., & Globerson, T. (1989). When teams do not function the way they ought to. International journal of Educational research, 13 (1), 89–99.

Schaafstal, A., Schraagen, J. M., & van Berl, M. (2000). Cognitive task analysis and innovation of training: The case of structured troubleshooting. Human Factors: The Journal of the Human Factors and Ergonomics Society, 42 (1), 75–86. https://doi.org/10.1518/001872000779656570 .

Schön, D. A. (1992). The reflective practitioner: How professionals think in action . Routledge.

Scrivener, S. A. R., Liang, K. C., & Ball, L. J. (2002). Extending the design problem-solving process model: Requirements and outcomes. In: Common Ground: Proceedings of the 2002 International Conference of the Design Research Society. Staffordshire University Press, Stoke-On-Trent.

Sternberg, R. J. (1999). The theory of successful intelligence. Review of General Psychology, 4 (3), 292–316.

Strimel, G. J. (2014). Engineering design: A cognitive process approach. Doctoral Thesis, Old Dominion University, Norfolk, VA.

Strong, J. T., & Anderson, R. E. (1990). Free-riding in group projects: Control mechanisms and preliminary data. Journal of marketing education, 12 (2), 61–67.

Sung, E., & Kelley, T. R. (2019). Identifying design process patterns: a sequential analysis study of design thinking. International Journal of Technology and Design Education, 29 (2), 283–302. https://doi.org/10.1007/s10798-018-9448-1 .

Twyford, J., & Järvinen, E.-M. (2000). The formation of children’s technological concepts: A study of what it means to do technology from a child’s perspective. Journal of Technology Education, 12 (1), 17.

Vaismoradi, M., Turunen, H., & Bondas, T. (2013). Content analysis and thematic analysis: Implications for conducting a qualitative descriptive study—qualitative descriptive study. Nursing & Health Sciences, 15 (3), 398–405. https://doi.org/10.1111/nhs.12048 .

Vincenti, W. G. (1990). What engineers know and how they know it: Analytical studies from aeronautical history . The Johns Hopkins University Press.

Wainwright, M. (2010). Using NVivo audio-coding: Practical, sensorial and epistemological considerations . (pp. 1–4). Social Research Update.

Webb, N. M. (1984). Stability of small group interaction and achievement over time. Journal of Educational Psychology, 76 (2), 211.

Welch, M. (1998). Students’ use of three-dimensional modelling while designing and making a solution to a technological problem. International Journal of Technology and Design Education, 8 (3), 241–260. https://doi.org/10.1023/A:1008802927817 .

Whyte, J. (1984). Observing sex stereotypes and interactions in the school lab and workshop. Educational Review, 36 (1), 75–86. https://doi.org/10.1080/0013191840360107 .

Wicklein, R. C., & Schell, J. W. (1995). Case studies of multidisciplinary approaches to integrating mathematics, science and technologyeducation. Journal of Technology Education, 6 (2), 18.

Williams, P. J. (2000). Design: The only methodology of technology. Journal of Technology Education . https://doi.org/10.21061/jte.v11i2.a.4 .

Winkelmann, C., & Hacker, W. (2011). Generic non-technical procedures in design problem solving: Is there any benefit to the clarification of task requirements? International Journal of Technology and Design Education, 21 (4), 395–407. https://doi.org/10.1007/s10798-010-9131-7 .

Xu, M., Williams, P. J., Gu, J., & Zhang, H. (2019). Hotspots and trends of technology education in the international journal of technology and design education: 2000–2018. International Journal of Technology and Design Education . https://doi.org/10.1007/s10798-019-09508-6 .

Yousuf, M. I. (2007). Using experts` opinions through delphi technique. Practical Assessment, Research, and Evaluation, 12 (4), 1–8.

Zamawe, F. (2015). The Implication of Using NVivo software in qualitative data analysis: Evidence-based reflections. Malawi Medical Journal, 27 (1), 13. https://doi.org/10.4314/mmj.v27i1.4 .

Download references

Acknowledgements

I would like to thank Dr Jane V. Magill, Dr. Alastair D. McPhee and Professor Frank Banks for their support in this work as well as the participating teachers and pupils who made this possible.

Author information

Authors and affiliations.

School of Education, University of Glasgow, 11 Eldon Street, Glasgow, G3 6NH, Scotland

David Morrison-Love

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to David Morrison-Love .

Additional information

Publisher's note.

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Rights and permissions

Open Access This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons licence, and indicate if changes were made. The images or other third party material in this article are included in the article's Creative Commons licence, unless indicated otherwise in a credit line to the material. If material is not included in the article's Creative Commons licence and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this licence, visit http://creativecommons.org/licenses/by/4.0/ .

Reprints and permissions

About this article

Morrison-Love, D. Technological problem solving: an investigation of differences associated with levels of task success. Int J Technol Des Educ 32 , 1725–1753 (2022). https://doi.org/10.1007/s10798-021-09675-5

Download citation

Accepted : 25 April 2021

Published : 02 June 2021

Issue Date : July 2022

DOI : https://doi.org/10.1007/s10798-021-09675-5

Share this article

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

• Technology education
• Well-defined problem solving
• Secondary school
• Learning differences
• Find a journal
• Publish with us
• Track your research

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.

The Art of Effective Problem Solving: A Step-by-Step Guide

Author: Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

Whether we realise it or not, problem solving skills are an important part of our daily lives. From resolving a minor annoyance at home to tackling complex business challenges at work, our ability to solve problems has a significant impact on our success and happiness. However, not everyone is naturally gifted at problem-solving, and even those who are can always improve their skills. In this blog post, we will go over the art of effective problem-solving step by step.

You will learn how to define a problem, gather information, assess alternatives, and implement a solution, all while honing your critical thinking and creative problem-solving skills. Whether you’re a seasoned problem solver or just getting started, this guide will arm you with the knowledge and tools you need to face any challenge with confidence. So let’s get started!

Problem Solving Methodologies

Individuals and organisations can use a variety of problem-solving methodologies to address complex challenges. 8D and A3 problem solving techniques are two popular methodologies in the Lean Six Sigma framework.

Methodology of 8D (Eight Discipline) Problem Solving:

The 8D problem solving methodology is a systematic, team-based approach to problem solving. It is a method that guides a team through eight distinct steps to solve a problem in a systematic and comprehensive manner.

The 8D process consists of the following steps:

• Form a team: Assemble a group of people who have the necessary expertise to work on the problem.
• Define the issue: Clearly identify and define the problem, including the root cause and the customer impact.
• Create a temporary containment plan: Put in place a plan to lessen the impact of the problem until a permanent solution can be found.
• Identify the root cause: To identify the underlying causes of the problem, use root cause analysis techniques such as Fishbone diagrams and Pareto charts.
• Create and test long-term corrective actions: Create and test a long-term solution to eliminate the root cause of the problem.
• Implement and validate the permanent solution: Implement and validate the permanent solution’s effectiveness.
• Prevent recurrence: Put in place measures to keep the problem from recurring.
• Recognize and reward the team: Recognize and reward the team for its efforts.

Download the 8D Problem Solving Template

A3 Problem Solving Method:

The A3 problem solving technique is a visual, team-based problem-solving approach that is frequently used in Lean Six Sigma projects. The A3 report is a one-page document that clearly and concisely outlines the problem, root cause analysis, and proposed solution.

The A3 problem-solving procedure consists of the following steps:

• Determine the issue: Define the issue clearly, including its impact on the customer.
• Perform root cause analysis: Identify the underlying causes of the problem using root cause analysis techniques.
• Create and implement a solution: Create and implement a solution that addresses the problem’s root cause.
• Monitor and improve the solution: Keep an eye on the solution’s effectiveness and make any necessary changes.

Subsequently, in the Lean Six Sigma framework, the 8D and A3 problem solving methodologies are two popular approaches to problem solving. Both methodologies provide a structured, team-based problem-solving approach that guides individuals through a comprehensive and systematic process of identifying, analysing, and resolving problems in an effective and efficient manner.

Step 1 – Define the Problem

The definition of the problem is the first step in effective problem solving. This may appear to be a simple task, but it is actually quite difficult. This is because problems are frequently complex and multi-layered, making it easy to confuse symptoms with the underlying cause. To avoid this pitfall, it is critical to thoroughly understand the problem.

To begin, ask yourself some clarifying questions:

• What exactly is the issue?
• What are the problem’s symptoms or consequences?
• Who or what is impacted by the issue?
• When and where does the issue arise?

Answering these questions will assist you in determining the scope of the problem. However, simply describing the problem is not always sufficient; you must also identify the root cause. The root cause is the underlying cause of the problem and is usually the key to resolving it permanently.

Try asking “why” questions to find the root cause:

• What causes the problem?
• Why does it continue?
• Why does it have the effects that it does?

By repeatedly asking “ why ,” you’ll eventually get to the bottom of the problem. This is an important step in the problem-solving process because it ensures that you’re dealing with the root cause rather than just the symptoms.

Once you have a firm grasp on the issue, it is time to divide it into smaller, more manageable chunks. This makes tackling the problem easier and reduces the risk of becoming overwhelmed. For example, if you’re attempting to solve a complex business problem, you might divide it into smaller components like market research, product development, and sales strategies.

To summarise step 1, defining the problem is an important first step in effective problem-solving. You will be able to identify the root cause and break it down into manageable parts if you take the time to thoroughly understand the problem. This will prepare you for the next step in the problem-solving process, which is gathering information and brainstorming ideas.

Step 2 – Gather Information and Brainstorm Ideas

Gathering information and brainstorming ideas is the next step in effective problem solving. This entails researching the problem and relevant information, collaborating with others, and coming up with a variety of potential solutions. This increases your chances of finding the best solution to the problem.

Begin by researching the problem and relevant information. This could include reading articles, conducting surveys, or consulting with experts. The goal is to collect as much information as possible in order to better understand the problem and possible solutions.

Next, work with others to gather a variety of perspectives. Brainstorming with others can be an excellent way to come up with new and creative ideas. Encourage everyone to share their thoughts and ideas when working in a group, and make an effort to actively listen to what others have to say. Be open to new and unconventional ideas and resist the urge to dismiss them too quickly.

Finally, use brainstorming to generate a wide range of potential solutions. This is the place where you can let your imagination run wild. At this stage, don’t worry about the feasibility or practicality of the solutions; instead, focus on generating as many ideas as possible. Write down everything that comes to mind, no matter how ridiculous or unusual it may appear. This can be done individually or in groups.

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the next step in the problem-solving process, which we’ll go over in greater detail in the following section.

Step 3 – Evaluate Options and Choose the Best Solution

Once you’ve compiled a list of potential solutions, it’s time to assess them and select the best one. This is the third step in effective problem solving, and it entails weighing the advantages and disadvantages of each solution, considering their feasibility and practicability, and selecting the solution that is most likely to solve the problem effectively.

To begin, weigh the advantages and disadvantages of each solution. This will assist you in determining the potential outcomes of each solution and deciding which is the best option. For example, a quick and easy solution may not be the most effective in the long run, whereas a more complex and time-consuming solution may be more effective in solving the problem in the long run.

Consider each solution’s feasibility and practicability. Consider the following:

• Can the solution be implemented within the available resources, time, and budget?
• What are the possible barriers to implementing the solution?
• Is the solution feasible in today’s political, economic, and social environment?

You’ll be able to tell which solutions are likely to succeed and which aren’t by assessing their feasibility and practicability.

Finally, choose the solution that is most likely to effectively solve the problem. This solution should be based on the criteria you’ve established, such as the advantages and disadvantages of each solution, their feasibility and practicability, and your overall goals.

It is critical to remember that there is no one-size-fits-all solution to problems. What is effective for one person or situation may not be effective for another. This is why it is critical to consider a wide range of solutions and evaluate each one based on its ability to effectively solve the problem.

Step 4 – Implement and Monitor the Solution

When you’ve decided on the best solution, it’s time to put it into action. The fourth and final step in effective problem solving is to put the solution into action, monitor its progress, and make any necessary adjustments.

To begin, implement the solution. This may entail delegating tasks, developing a strategy, and allocating resources. Ascertain that everyone involved understands their role and responsibilities in the solution’s implementation.

Next, keep an eye on the solution’s progress. This may entail scheduling regular check-ins, tracking metrics, and soliciting feedback from others. You will be able to identify any potential roadblocks and make any necessary adjustments in a timely manner if you monitor the progress of the solution.

Finally, make any necessary modifications to the solution. This could entail changing the solution, altering the plan of action, or delegating different tasks. Be willing to make changes if they will improve the solution or help it solve the problem more effectively.

It’s important to remember that problem solving is an iterative process, and there may be times when you need to start from scratch. This is especially true if the initial solution does not effectively solve the problem. In these situations, it’s critical to be adaptable and flexible and to keep trying new solutions until you find the one that works best.

To summarise, effective problem solving is a critical skill that can assist individuals and organisations in overcoming challenges and achieving their objectives. Effective problem solving consists of four key steps: defining the problem, generating potential solutions, evaluating alternatives and selecting the best solution, and implementing the solution.

You can increase your chances of success in problem solving by following these steps and considering factors such as the pros and cons of each solution, their feasibility and practicability, and making any necessary adjustments. Furthermore, keep in mind that problem solving is an iterative process, and there may be times when you need to go back to the beginning and restart. Maintain your adaptability and try new solutions until you find the one that works best for you.

• Novick, L.R. and Bassok, M., 2005.  Problem Solving . Cambridge University Press.

Was this helpful?

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website www.learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

What Is Takt Time and How Can It Improve Your Production Efficiency?

The Power of 5 Whys to get Results

Free lean six sigma templates.

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

The Evolution of 8D Problem-Solving: From Basics to Excellence

In a world where efficiency and effectiveness are more than just buzzwords, the need for…

8D: Tools and Techniques

Are you grappling with recurring problems in your organization and searching for a structured way…

How to Select the Right Lean Six Sigma Projects: A Comprehensive Guide

Going on a Lean Six Sigma journey is an invigorating experience filled with opportunities for…

35 problem-solving techniques and methods for solving complex problems

Design your next session with SessionLab

Join the 150,000+ facilitators 
using SessionLab.

Recommended Articles

A step-by-step guide to planning a workshop, how to create an unforgettable training session in 8 simple steps, 18 free facilitation resources we think you’ll love.

• 47 useful online tools for workshop planning and meeting facilitation

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

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

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

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

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

Let’s get started! 

How do you identify problems?

How do you identify the right solution.

• Tips for more effective problem-solving

Complete problem-solving methods

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

Problem-solving warm-up activities

Closing activities for a problem-solving process.

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

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

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

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

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

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

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

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

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

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

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

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

Tips for more effective problem solving

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

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

Clearly define the problem

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

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

Don’t jump to conclusions

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

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

Try different approaches  

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

Don’t take it personally 

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

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

Get the right people in the room

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

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

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

Document everything

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

Bring a facilitator 

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

Develop your problem-solving skills

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

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

Design a great agenda

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

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

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

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

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

Design Sprint 2.0

• Open Space Technology

1. Six Thinking Hats

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

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

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

2. Lightning Decision Jam

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

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

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

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

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

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

3. Problem Definition Process

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

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

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

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

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

4. The 5 Whys 

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

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

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

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

5. World Cafe

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

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

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

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

6. Discovery & Action Dialogue (DAD)

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

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

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

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

7. Design Sprint 2.0

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

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

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

8. Open space technology

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

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

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

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

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

Techniques to identify and analyze problems

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

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

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

Let’s take a look!

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

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

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

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

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

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

10. The Creativity Dice

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

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

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

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

11. Fishbone Analysis

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

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

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

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

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

12. Problem Tree 

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

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

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

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

13. SWOT Analysis

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

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

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

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

14. Agreement-Certainty Matrix

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

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

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

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

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

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

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

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

16. Speed Boat

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

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

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

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

17. The Journalistic Six

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

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

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

18. LEGO Challenge

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

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

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

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

19. What, So What, Now What?

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

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

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

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

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

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

20. Journalists  

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

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

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

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

Problem-solving techniques for developing solutions 

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

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

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

21. Mindspin  

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

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

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

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

22. Improved Solutions

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

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

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

23. Four Step Sketch

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

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

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

24. 15% Solutions

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

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

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

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

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

25. How-Now-Wow Matrix

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

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

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

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

26. Impact and Effort Matrix

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

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

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

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

27. Dotmocracy

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

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

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

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

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

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

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

28. Check-in / Check-out

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

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

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

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

29. Doodling Together  

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

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

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

30. Show and Tell

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

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

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

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

31. Constellations

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

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

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

32. Draw a Tree

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

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

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

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

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

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

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

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

How do I conclude a problem-solving process?

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

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

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

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

33. One Breath Feedback

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

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

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

34. Who What When Matrix 

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

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

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

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

35. Response cards

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

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

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

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

Save time and effort discovering the right solutions

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

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

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

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

Over to you

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

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

thank you very much for these excellent techniques

Certainly wonderful article, very detailed. Shared!

Your list of techniques for problem solving can be helpfully extended by adding TRIZ to the list of techniques. TRIZ has 40 problem solving techniques derived from methods inventros and patent holders used to get new patents. About 10-12 are general approaches. many organization sponsor classes in TRIZ that are used to solve business problems or general organiztational problems. You can take a look at TRIZ and dwonload a free internet booklet to see if you feel it shound be included per your selection process.

Leave a Comment Cancel reply

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

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

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

Facilitation is more and more recognized as a key component of work, as employers and society are faced with bigger and more complex problems and ideas. From facilitating meetings to big, multi-stakeholder strategy development workshops, the facilitator's skillset is more and more in demand. In this article, we will go through a list of the best online facilitation resources, including newsletters, podcasts, communities, and 10 free toolkits you can bookmark and read to upskill and improve your facilitation practice. When designing activities and workshops, you'll probably start by using templates and methods you are familiar with. Soon enough, you'll need to expand your range and look for facilitation methods and…

Design your next workshop with SessionLab

Join the 150,000 facilitators using SessionLab

Sign up for free

• Oct 13, 2019

10 Steps to Problem Solving for Engineers

Updated: Dec 6, 2020

With the official launch of the engineering book 10+1 Steps to Problem Solving: An Engineer's Guide it may be interesting to know that formalization of the concept began in episode 2 of the Engineering IRL Podcast back in July 2018.

As noted in the book remnants of the steps had existed throughout my career and in this episode I actually recorded the episode off the top of my head.

My goal was to help engineers build a practical approach to problem solving.

Have a listen.

Who can advise on the best approach to problem solving other than the professional problem solvers - Yes. I'm talking about being an Engineer.

There are 2 main trains of thought with Engineering work for non-engineers and that's trying to change the world with leading edge tech and innovations, or plain old boring math nerd type things.

Whilst, somewhat the case what this means is most content I read around Tech and Engineering are either super technical and (excruciatingly) detailed. OR really riff raff at the high level reveling at the possibilities of changing the world as we know it. And so what we end up with is a base (engineer only details) and the topping (media innovation coverage) but what about the meat? The contents?

There's a lot of beauty and interesting things there too. And what's the centrepiece? The common ground between all engineers? Problem solving.

The number one thing an Engineer does is problem solving. Now you may say, "hey, that's the same as my profession" - well this would be true for virtually every single profession on earth. This is not saying there isn't problem solving required in other professions. Some problems require very basic problem solving techniques such is used in every day life, but sometimes problems get more complicated, maybe they involve other parties, maybe its a specific quirk of the system in a specific scenario. One thing you learn in engineering is that not all problems are equal. These are

 The stages of problem solving like a pro:

Is the problem identified (no, really, are you actually asking the right question?)

Have you applied related troubleshooting step to above problem?

Have you applied basic troubleshooting steps (i.e. check if its plugged in, turned it on and off again, checked your basics)

Tried step 2 again? (Desperation seeps in, but check your bases)

Asked a colleague or someone else that may have dealt with your problem? (50/50 at this point)

Asked DR. Google (This is still ok)

Deployed RTFM protocol (Read the F***ing Manual - Engineers are notorious for not doing this)

Repeated tests, changing slight things, checking relation to time, or number of people, or location or environment (we are getting DEEP now)

Go to the bottom level, in networking this is packet sniffers to inspect packets, in systems this is taking systems apart and testing in isolation, in software this is checking if 1 equals 1, you are trying to prove basic human facts that everyone knows. If 1 is not equal to 1, you're in deep trouble.At this point you are at rebuild from scratch, re install, start again as your answer (extremely expensive, very rare)

And there you have it! Those are your levels of problem solving. As you go through each step, the more expensive the problem is. -- BUT WAIT. I picked something up along the way and this is where I typically thrive. Somewhere between problem solving step 8 and 10. 

The secret step

My recommendation at this point is to try tests that are seemingly unrelated to anything to do with the problem at all.Pull a random cable, test with a random system off/on, try it at a specific time of the day, try it specifically after restarting or replugging something in. Now, not completely random but within some sort of scope. These test are the ones that when someone is having a problem when you suggest they say "that shouldn't fix the problem, that shouldn't be related" and they are absolutely correct.But here's the thing -- at this stage they have already tried everything that SHOULD fix the problem. Now it's time for the hail mary's, the long shots, the clutching at straws. This method works wonders for many reasons. 1. You really are trying to try "anything" at this point.

2. Most of the time we may think we have problem solving step number 1 covered, but we really don't.

3. Triggering correlations.

This is important.

Triggering correlations

In a later post I will cover correlation vs causation, but for now understand that sometimes all you want to do is throw in new inputs to the system or problem you are solving in order to get clues or re identify problems or give new ways to approach earlier problem solving steps. There you have it. Problem solve like a ninja. Approach that extremely experienced and smart person what their problem and as they describe all the things they've tried, throw in a random thing they haven't tried. And when they say, well that shouldn't fix it, you ask them, well if you've exhausted everything that should  have worked, this is the time to try things that shouldn't. Either they will think of more tests they haven't considered so as to avoid doing your preposterous idea OR they try it and get a new clue to their problem. Heck, at worst they confirm that they do know SOMETHING about the system.

Go out and problem solve ! As always, thanks for reading and good luck with all of your side hustles.

If you prefer to listen to learn we got you covered with the Engineering IRL show!

For Youtube please go to:

https://youtu.be/EHaRNZhqmHA

For Spotify please go to:

https://open.spotify.com/show/3UZPfOvNwQkaCA1jLIOxp4

And don't forget to subscribe if you get any value from the Engineering IRL Content

• Technical Tactics
• 10+1 Steps to Problem Solving

Recent Posts

How to Implement OSHA’s Requirement of Emergency Medical Services in Construction

Preventing Noise-Induced Issues in Construction

The Advantages of CAD for Modern Engineers

Get your free Engineering Toolkit for Engineering IRL listeners only

Get a copy of the Operational Technology Ultimate Guide for Engineers e-book for free.

Explore Jobs

• Jobs Near Me
• Remote Jobs
• Full Time Jobs
• Part Time Jobs
• Entry Level Jobs
• Work From Home Jobs

Find Specific Jobs

• $15 Per Hour Jobs
• $20 Per Hour Jobs
• Hiring Immediately Jobs
• High School Jobs
• H1b Visa Jobs

Explore Careers

• Business And Financial
• Architecture And Engineering
• Computer And Mathematical

Explore Professions

• What They Do
• Certifications
• Demographics

Best Companies

• Health Care
• Fortune 500

Explore Companies

• CEO And Executies
• Resume Builder
• Career Advice
• Explore Majors
• Questions And Answers
• Interview Questions

What Are Problem-Solving Skills? (Definition, Examples, And How To List On A Resume)

• What Are Skills Employers Look For?
• What Are Inductive Reasoning?
• What Are Problem Solving Skills?
• What Are Active Listening Skills?
• What Are Management Skills?
• What Are Attention To Detail?
• What Are Detail Oriented Skills?
• What Are Domain Knowledge?
• What Is Professionalism?
• What Are Rhetorical Skills?
• What Is Integrity?
• What Are Persuasion Skills?
• How To Start A Conversation
• How To Write A Conclusion For A Research Paper
• Team Player
• Visual Learner
• High Income Skills
• The Most Important Professional Skills

Find a Job You Really Want In

Summary. Problem-solving skills include analysis, creativity, prioritization, organization, and troubleshooting. To solve a problem, you need to use a variety of skills based on the needs of the situation.

Most jobs essentially boil down to identifying and solving problems consistently and effectively. That’s why employers value problem-solving skills in job candidates for just about every role.

We’ll cover problem-solving methods, ways to improve your problem-solving skills, and examples of showcasing your problem-solving skills during your job search .

Key Takeaways:

If you can show off your problem-solving skills on your resume , in your cover letter , and during a job interview, you’ll be one step closer to landing a job.

Companies rely on employees who can handle unexpected challenges, identify persistent issues, and offer workable solutions in a positive way.

It is important to improve problem solving skill because this is a skill that can be cultivated and nurtured so you can become better at dealing with problems over time.

Types of Problem-Solving Skills

How to improve your problem-solving skills, example answers to problem-solving interview questions, how to show off problem-solving skills on a resume, example resume and cover letter with problem-solving skills, more about problem-solving skills, problem solving skills faqs.

• Sign Up For More Advice and Jobs

Problem-solving skills are skills that help you identify and solve problems effectively and efficiently . Your ability to solve problems is one of the main ways that hiring managers and recruiters assess candidates, as those with excellent problem-solving skills are more likely to autonomously carry out their responsibilities.

A true problem solver can look at a situation, find the cause of the problem (or causes, because there are often many issues at play), and then come up with a reasonable solution that effectively fixes the problem or at least remedies most of it.

The ability to solve problems is considered a soft skill , meaning that it’s more of a personality trait than a skill you’ve learned at school, on the job, or through technical training.

That being said, your proficiency with various hard skills will have a direct bearing on your ability to solve problems. For example, it doesn’t matter if you’re a great problem-solver; if you have no experience with astrophysics, you probably won’t be hired as a space station technician .

Problem-solving is considered a skill on its own, but it’s supported by many other skills that can help you be a better problem solver. These skills fall into a few different categories of problem-solving skills.

Problem recognition and analysis. The first step is to recognize that there is a problem and discover what it is or what the root cause of it is.

You can’t begin to solve a problem unless you’re aware of it. Sometimes you’ll see the problem yourself and other times you’ll be told about the problem. Both methods of discovery are very important, but they can require some different skills. The following can be an important part of the process:

Active listening

Data analysis

Historical analysis

Communication

Create possible solutions. You know what the problem is, and you might even know the why of it, but then what? Your next step is the come up with some solutions.

Most of the time, the first solution you come up with won’t be the right one. Don’t fall victim to knee-jerk reactions; try some of the following methods to give you solution options.

Brainstorming

Forecasting

Decision-making

Topic knowledge/understanding

Process flow

Evaluation of solution options. Now that you have a lot of solution options, it’s time to weed through them and start casting some aside. There might be some ridiculous ones, bad ones, and ones you know could never be implemented. Throw them away and focus on the potentially winning ideas.

This step is probably the one where a true, natural problem solver will shine. They intuitively can put together mental scenarios and try out solutions to see their plusses and minuses. If you’re still working on your skill set — try listing the pros and cons on a sheet of paper.

Prioritizing

Evaluating and weighing

Solution implementation. This is your “take action” step. Once you’ve decided which way to go, it’s time to head down that path and see if you were right. This step takes a lot of people and management skills to make it work for you.

Dependability

Teambuilding

Troubleshooting

Follow-Through

Believability

Trustworthiness

Project management

Evaluation of the solution. Was it a good solution? Did your plan work or did it fail miserably? Sometimes the evaluation step takes a lot of work and review to accurately determine effectiveness. The following skills might be essential for a thorough evaluation.

Customer service

Feedback responses

Flexibility

You now have a ton of skills in front of you. Some of them you have naturally and some — not so much. If you want to solve a problem, and you want to be known for doing that well and consistently, then it’s time to sharpen those skills.

Develop industry knowledge. Whether it’s broad-based industry knowledge, on-the-job training , or very specific knowledge about a small sector — knowing all that you can and feeling very confident in your knowledge goes a long way to learning how to solve problems.

Be a part of a solution. Step up and become involved in the problem-solving process. Don’t lead — but follow. Watch an expert solve the problem and, if you pay attention, you’ll learn how to solve a problem, too. Pay attention to the steps and the skills that a person uses.

Practice solving problems. Do some role-playing with a mentor , a professor , co-workers, other students — just start throwing problems out there and coming up with solutions and then detail how those solutions may play out.

Go a step further, find some real-world problems and create your solutions, then find out what they did to solve the problem in actuality.

Identify your weaknesses. If you could easily point out a few of your weaknesses in the list of skills above, then those are the areas you need to focus on improving. How you do it is incredibly varied, so find a method that works for you.

Solve some problems — for real. If the opportunity arises, step in and use your problem-solving skills. You’ll never really know how good (or bad) you are at it until you fail.

That’s right, failing will teach you so much more than succeeding will. You’ll learn how to go back and readdress the problem, find out where you went wrong, learn more from listening even better. Failure will be your best teacher ; it might not make you feel good, but it’ll make you a better problem-solver in the long run.

Once you’ve impressed a hiring manager with top-notch problem-solving skills on your resume and cover letter , you’ll need to continue selling yourself as a problem-solver in the job interview.

There are three main ways that employers can assess your problem-solving skills during an interview:

By asking questions that relate to your past experiences solving problems

Posing hypothetical problems for you to solve

By administering problem-solving tests and exercises

The third method varies wildly depending on what job you’re applying for, so we won’t attempt to cover all the possible problem-solving tests and exercises that may be a part of your application process.

Luckily, interview questions focused on problem-solving are pretty well-known, and most can be answered using the STAR method . STAR stands for situation, task, action, result, and it’s a great way to organize your answers to behavioral interview questions .

Let’s take a look at how to answer some common interview questions built to assess your problem-solving capabilities:

At my current job as an operations analyst at XYZ Inc., my boss set a quarterly goal to cut contractor spending by 25% while maintaining the same level of production and moving more processes in-house. It turned out that achieving this goal required hiring an additional 6 full-time employees, which got stalled due to the pandemic. I suggested that we widen our net and hire remote employees after our initial applicant pool had no solid candidates. I ran the analysis on overhead costs and found that if even 4 of the 6 employees were remote, we’d save 16% annually compared to the contractors’ rates. In the end, all 6 employees we hired were fully remote, and we cut costs by 26% while production rose by a modest amount.

I try to step back and gather research as my first step. For instance, I had a client who needed a graphic designer to work with Crello, which I had never seen before, let alone used. After getting the project details straight, I began meticulously studying the program the YouTube tutorials, and the quick course Crello provides. I also reached out to coworkers who had worked on projects for this same client in the past. Once I felt comfortable with the software, I started work immediately. It was a slower process because I had to be more methodical in my approach, but by putting in some extra hours, I turned in the project ahead of schedule. The client was thrilled with my work and was shocked to hear me joke afterward that it was my first time using Crello.

As a digital marketer , website traffic and conversion rates are my ultimate metrics. However, I also track less visible metrics that can illuminate the story behind the results. For instance, using Google Analytics, I found that 78% of our referral traffic was coming from one affiliate, but that these referrals were only accounting for 5% of our conversions. Another affiliate, who only accounted for about 10% of our referral traffic, was responsible for upwards of 30% of our conversions. I investigated further and found that the second, more effective affiliate was essentially qualifying our leads for us before sending them our way, which made it easier for us to close. I figured out exactly how they were sending us better customers, and reached out to the first, more prolific but less effective affiliate with my understanding of the results. They were able to change their pages that were referring us traffic, and our conversions from that source tripled in just a month. It showed me the importance of digging below the “big picture” metrics to see the mechanics of how revenue was really being generated through digital marketing.

You can bring up your problem-solving skills in your resume summary statement , in your work experience , and under your education section , if you’re a recent graduate. The key is to include items on your resume that speak direclty to your ability to solve problems and generate results.

If you can, quantify your problem-solving accomplishments on your your resume . Hiring managers and recruiters are always more impressed with results that include numbers because they provide much-needed context.

This sample resume for a Customer Service Representative will give you an idea of how you can work problem solving into your resume.

Michelle Beattle 111 Millennial Parkway Chicago, IL 60007 (555) 987-6543 [email protected] Professional Summary Qualified Customer Services Representative with 3 years in a high-pressure customer service environment. Professional, personable, and a true problem solver. Work History ABC Store — Customer Service Representative 01/2015 — 12/2017 Managed in-person and phone relations with customers coming in to pick up purchases, return purchased products, helped find and order items not on store shelves, and explained details and care of merchandise. Became a key player in the customer service department and was promoted to team lead. XYZ Store — Customer Service Representative/Night Manager 01/2018 — 03/2020, released due to Covid-19 layoffs Worked as the night manager of the customer service department and filled in daytime hours when needed. Streamlined a process of moving customers to the right department through an app to ease the burden on the phone lines and reduce customer wait time by 50%. Was working on additional wait time problems when the Covid-19 pandemic caused our stores to close permanently. Education Chicago Tech 2014-2016 Earned an Associate’s Degree in Principles of Customer Care Skills Strong customer service skills Excellent customer complaint resolution Stock record management Order fulfillment New product information Cash register skills and proficiency Leader in problem solving initiatives

You can see how the resume gives you a chance to point out your problem-solving skills and to show where you used them a few times. Your cover letter is your chance to introduce yourself and list a few things that make you stand out from the crowd.

Michelle Beattle 111 Millennial Parkway Chicago, IL 60007 (555) 987-6543 [email protected] Dear Mary McDonald, I am writing in response to your ad on Zippia for a Customer Service Representative . Thank you for taking the time to consider me for this position. Many people believe that a job in customer service is simply listening to people complain all day. I see the job as much more than that. It’s an opportunity to help people solve problems, make their experience with your company more enjoyable, and turn them into life-long advocates of your brand. Through my years of experience and my educational background at Chicago Tech, where I earned an Associate’s Degree in the Principles of Customer Care, I have learned that the customers are the lifeline of the business and without good customer service representatives, a business will falter. I see it as my mission to make each and every customer I come in contact with a fan. I have more than five years of experience in the Customer Services industry and had advanced my role at my last job to Night Manager. I am eager to again prove myself as a hard worker, a dedicated people person, and a problem solver that can be relied upon. I have built a professional reputation as an employee that respects all other employees and customers, as a manager who gets the job done and finds solutions when necessary, and a worker who dives in to learn all she can about the business. Most of my customers have been very satisfied with my resolution ideas and have returned to do business with us again. I believe my expertise would make me a great match for LMNO Store. I have enclosed my resume for your review, and I would appreciate having the opportunity to meet with you to further discuss my qualifications. Thank you again for your time and consideration. Sincerely, Michelle Beattle

You’ve no doubt noticed that many of the skills listed in the problem-solving process are repeated. This is because having these abilities or talents is so important to the entire course of getting a problem solved.

In fact, they’re worthy of a little more attention. Many of them are similar, so we’ll pull them together and discuss how they’re important and how they work together.

Communication, active listening, and customer service skills. No matter where you are in the process of problem-solving, you need to be able to show that you’re listening and engaged and really hearing what the problem is or what a solution may be.

Obviously, the other part of this is being able to communicate effectively so people understand what you’re saying without confusion. Rolled into this are customer service skills , which really are all about listening and responding appropriately — it’s the ultimate in interpersonal communications.

Analysis (data and historical), research, and topic knowledge/understanding. This is how you intellectually grasp the issue and approach it. This can come from studying the topic and the process or it can come from knowledge you’ve gained after years in the business. But the best solutions come from people who thoroughly understand the problem.

Creativity, brainstorming, troubleshooting, and flexibility. All of you creative thinkers will like this area because it’s when your brain is at its best.

Coming up with ideas, collaborating with others, leaping over hurdles, and then being able to change courses immediately, if need be, are all essential. If you’re not creative by nature, then having a team of diverse thinkers can help you in this area.

Dependability, believability, trustworthiness, and follow-through. Think about it, these are all traits a person needs to have to make change happen and to make you comfortable taking that next step with them. Someone who is shifty and shady and never follows through, well, you’re simply not going to do what they ask, are you?

Leadership, teambuilding, decision-making, and project management. These are the skills that someone who is in charge is brimming with. These are the leaders you enjoy working for because you know they’re doing what they can to keep everything in working order. These skills can be learned but they’re often innate.

Prioritizing, prediction, forecasting, evaluating and weighing, and process flow. If you love flow charts, data analysis, prediction modeling, and all of that part of the equation, then you might have some great problem-solving abilities.

These are all great skills because they can help you weed out bad ideas, see flaws, and save massive amounts of time in trial and error.

What is a good example of problem-solving skills?

Good examples of porblem-solving skills include research, analysis, creativity, communciation, and decision-making. Each of these skills build off one another to contribute to the problem solving process. Research and analysis allow you to identify a problem.

Creativity and analysis help you consider different solutions. Meanwhile, communication and decision-making are key to working with others to solve a problem on a large scale.

What are 3 key attributes of a good problem solver?

3 key attributes of a good problem solver are persistence, intellegince, and empathy. Persistence is crucial to remain motivated to work through challenges. Inellegince is needed to make smart, informed choices. Empathy is crucial to maintain positive relationships with others as well as yourself.

What can I say instead of problem-solving skills?

Instead of saying problem-solving skills, you can say the following:

Critical thinker

Solutions-oriented

Engineering

Using different words is helpful, especially when writing your resume and cover letter.

What is problem-solving in the workplace?

Problem-solving in the workplace is the ability to work through any sort of challenge, conflict, or unexpected situation and still achieve business goals. Though it varies by profession, roblem-solving in the workplace is very important for almost any job, because probelms are inevitable. You need to have the appropriate level of problem-solving skills if you want to succeed in your career, whatever it may be.

Department of Labor – Problem Solving and Critical Thinking

How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.

Kristin Kizer is an award-winning writer, television and documentary producer, and content specialist who has worked on a wide variety of written, broadcast, and electronic publications. A former writer/producer for The Discovery Channel, she is now a freelance writer and delighted to be sharing her talents and time with the wonderful Zippia audience.

Recent Job Searches

• Registered Nurse Jobs Resume Location
• Truck Driver Jobs Resume Location
• Call Center Representative Jobs Resume Location
• Customer Service Representative Jobs Resume
• Delivery Driver Jobs Resume Location
• Warehouse Worker Jobs Resume Location
• Account Executive Jobs Resume Location
• Sales Associate Jobs Resume Location
• Licensed Practical Nurse Jobs Resume Location
• Company Driver Jobs Resume

Related posts

What Is Deductive Reasoning? (With Examples)

How To Showcase Leadership Skills On Your Resume (With Examples)

How To Start A Conversation: (55+ Examples For Every Situation + Tips)

Most Important Administrative Skills (With Examples)

• Career Advice >
• Desired Traits >
• Problem Solving Skills

Introduction to Problem Solving Skills

What is problem solving and why is it important.

The ability to solve problems is a basic life skill and is essential to our day-to-day lives, at home, at school, and at work. We solve problems every day without really thinking about how we solve them. For example: it’s raining and you need to go to the store. What do you do? There are lots of possible solutions. Take your umbrella and walk. If you don't want to get wet, you can drive, or take the bus. You might decide to call a friend for a ride, or you might decide to go to the store another day. There is no right way to solve this problem and different people will solve it differently.

Problem solving is the process of identifying a problem, developing possible solution paths, and taking the appropriate course of action.

Why is problem solving important? Good problem solving skills empower you not only in your personal life but are critical in your professional life. In the current fast-changing global economy, employers often identify everyday problem solving as crucial to the success of their organizations. For employees, problem solving can be used to develop practical and creative solutions, and to show independence and initiative to employers.

Throughout this case study you will be asked to jot down your thoughts in idea logs. These idea logs are used for reflection on concepts and for answering short questions. When you click on the "Next" button, your responses will be saved for that page. If you happen to close the webpage, you will lose your work on the page you were on, but previous pages will be saved. At the end of the case study, click on the "Finish and Export to PDF" button to acknowledge completion of the case study and receive a PDF document of your idea logs.

What Does Problem Solving Look Like?

The ability to solve problems is a skill, and just like any other skill, the more you practice, the better you get. So how exactly do you practice problem solving? Learning about different problem solving strategies and when to use them will give you a good start. Problem solving is a process. Most strategies provide steps that help you identify the problem and choose the best solution. There are two basic types of strategies: algorithmic and heuristic.

Algorithmic strategies are traditional step-by-step guides to solving problems. They are great for solving math problems (in algebra: multiply and divide, then add or subtract) or for helping us remember the correct order of things (a mnemonic such as “Spring Forward, Fall Back” to remember which way the clock changes for daylight saving time, or “Righty Tighty, Lefty Loosey” to remember what direction to turn bolts and screws). Algorithms are best when there is a single path to the correct solution.

But what do you do when there is no single solution for your problem? Heuristic methods are general guides used to identify possible solutions. A popular one that is easy to remember is IDEAL [ Bransford & Stein, 1993 ] :

• I dentify the problem
• D efine the context of the problem
• E xplore possible strategies
• A ct on best solution

IDEAL is just one problem solving strategy. Building a toolbox of problem solving strategies will improve your problem solving skills. With practice, you will be able to recognize and use multiple strategies to solve complex problems.

Watch the video

What is the best way to get a peanut out of a tube that cannot be moved? Watch a chimpanzee solve this problem in the video below [ Geert Stienissen, 2010 ].

[PDF transcript]

Describe the series of steps you think the chimpanzee used to solve this problem.

• [Page 2: What does Problem Solving Look Like?] Describe the series of steps you think the chimpanzee used to solve this problem.

Think of an everyday problem you've encountered recently and describe your steps for solving it.

• [Page 2: What does Problem Solving Look Like?] Think of an everyday problem you've encountered recently and describe your steps for solving it.

Developing Problem Solving Processes

Problem solving is a process that uses steps to solve problems. But what does that really mean? Let's break it down and start building our toolbox of problem solving strategies.

What is the first step of solving any problem? The first step is to recognize that there is a problem and identify the right cause of the problem. This may sound obvious, but similar problems can arise from different events, and the real issue may not always be apparent. To really solve the problem, it's important to find out what started it all. This is called identifying the root cause .

Example: You and your classmates have been working long hours on a project in the school's workshop. The next afternoon, you try to use your student ID card to access the workshop, but discover that your magnetic strip has been demagnetized. Since the card was a couple of years old, you chalk it up to wear and tear and get a new ID card. Later that same week you learn that several of your classmates had the same problem! After a little investigation, you discover that a strong magnet was stored underneath a workbench in the workshop. The magnet was the root cause of the demagnetized student ID cards.

The best way to identify the root cause of the problem is to ask questions and gather information. If you have a vague problem, investigating facts is more productive than guessing a solution. Ask yourself questions about the problem. What do you know about the problem? What do you not know? When was the last time it worked correctly? What has changed since then? Can you diagram the process into separate steps? Where in the process is the problem occurring? Be curious, ask questions, gather facts, and make logical deductions rather than assumptions.

Watch Adam Savage from Mythbusters, describe his problem solving process [ ForaTv, 2010 ]. As you watch this section of the video, try to identify the questions he asks and the different strategies he uses.

Adam Savage shared many of his problem solving processes. List the ones you think are the five most important. Your list may be different from other people in your class—that's ok!

• [Page 3: Developing Problem Solving Processes] Adam Savage shared many of his problem solving processes. List the ones you think are the five most important.

“The ability to ask the right question is more than half the battle of finding the answer.” — Thomas J. Watson , founder of IBM

Voices From the Field: Solving Problems

In manufacturing facilities and machine shops, everyone on the floor is expected to know how to identify problems and find solutions. Today's employers look for the following skills in new employees: to analyze a problem logically, formulate a solution, and effectively communicate with others.

In this video, industry professionals share their own problem solving processes, the problem solving expectations of their employees, and an example of how a problem was solved.

Meet the Partners:

• Taconic High School in Pittsfield, Massachusetts, is a comprehensive, fully accredited high school with special programs in Health Technology, Manufacturing Technology, and Work-Based Learning.
• Berkshire Community College in Pittsfield, Massachusetts, prepares its students with applied manufacturing technical skills, providing hands-on experience at industrial laboratories and manufacturing facilities, and instructing them in current technologies.
• H.C. Starck in Newton, Massachusetts, specializes in processing and manufacturing technology metals, such as tungsten, niobium, and tantalum. In almost 100 years of experience, they hold over 900 patents, and continue to innovate and develop new products.
• Nypro Healthcare in Devens, Massachusetts, specializes in precision injection-molded healthcare products. They are committed to good manufacturing processes including lean manufacturing and process validation.

Making Decisions

Now that you have a couple problem solving strategies in your toolbox, let's practice. In this exercise, you are given a scenario and you will be asked to decide what steps you would take to identify and solve the problem.

Scenario: You are a new employee and have just finished your training. As your first project, you have been assigned the milling of several additional components for a regular customer. Together, you and your trainer, Bill, set up for the first run. Checking your paperwork, you gather the tools and materials on the list. As you are mounting the materials on the table, you notice that you didn't grab everything and hurriedly grab a few more items from one of the bins. Once the material is secured on the CNC table, you load tools into the tool carousel in the order listed on the tool list and set the fixture offsets.

Bill tells you that since this is a rerun of a job several weeks ago, the CAD/CAM model has already been converted to CNC G-code. Bill helps you download the code to the CNC machine. He gives you the go-ahead and leaves to check on another employee. You decide to start your first run.

What problems did you observe in the video?

• [Page 5: Making Decisions] What problems did you observe in the video?
• What do you do next?
• Try to fix it yourself.
• Ask your trainer for help.

As you are cleaning up, you think about what happened and wonder why it happened. You try to create a mental picture of what happened. You are not exactly sure what the end mill hit, but it looked like it might have hit the dowel pin. You wonder if you grabbed the correct dowel pins from the bins earlier.

You can think of two possible next steps. You can recheck the dowel pin length to make sure it is the correct length, or do a dry run using the CNC single step or single block function with the spindle empty to determine what actually happened.

• Check the dowel pins.
• Use the single step/single block function to determine what happened.

You notice that your trainer, Bill, is still on the floor and decide to ask him for help. You describe the problem to him. Bill asks if you know what the end mill ran into. You explain that you are not sure but you think it was the dowel pin. Bill reminds you that it is important to understand what happened so you can fix the correct problem. He suggests that you start all over again and begin with a dry run using the single step/single block function, with the spindle empty, to determine what it hit. Or, since it happened at the end, he mentions that you can also check the G-code to make sure the Z-axis is raised before returning to the home position.

• Run the single step/single block function.
• Edit the G-code to raise the Z-axis.

You finish cleaning up and check the CNC for any damage. Luckily, everything looks good. You check your paperwork and gather the components and materials again. You look at the dowel pins you used earlier, and discover that they are not the right length. As you go to grab the correct dowel pins, you have to search though several bins. For the first time, you are aware of the mess - it looks like the dowel pins and other items have not been put into the correctly labeled bins. You spend 30 minutes straightening up the bins and looking for the correct dowel pins.

Finally finding them, you finish setting up. You load tools into the tool carousel in the order listed on the tool list and set the fixture offsets. Just to make sure, you use the CNC single step/single block function, to do a dry run of the part. Everything looks good! You are ready to create your first part. The first component is done, and, as you admire your success, you notice that the part feels hotter than it should.

You wonder why? You go over the steps of the process to mentally figure out what could be causing the residual heat. You wonder if there is a problem with the CNC's coolant system or if the problem is in the G-code.

• Look at the G-code.

After thinking about the problem, you decide that maybe there's something wrong with the setup. First, you clean up the damaged materials and remove the broken tool. You check the CNC machine carefully for any damage. Luckily, everything looks good. It is time to start over again from the beginning.

You again check your paperwork and gather the tools and materials on the setup sheet. After securing the new materials, you use the CNC single step/single block function with the spindle empty, to do a dry run of the part. You watch carefully to see if you can figure out what happened. It looks to you like the spindle barely misses hitting the dowel pin. You determine that the end mill was broken when it hit the dowel pin while returning to the start position.

After conducting a dry run using the single step/single block function, you determine that the end mill was damaged when it hit the dowel pin on its return to the home position. You discuss your options with Bill. Together, you decide the best thing to do would be to edit the G-code and raise the Z-axis before returning to home. You open the CNC control program and edit the G-code. Just to make sure, you use the CNC single step/single block function, to do another dry run of the part. You are ready to create your first part. It works. You first part is completed. Only four more to go.

As you are cleaning up, you notice that the components are hotter than you expect and the end mill looks more worn than it should be. It dawns on you that while you were milling the component, the coolant didn't turn on. You wonder if it is a software problem in the G-code or hardware problem with the CNC machine.

It's the end of the day and you decide to finish the rest of the components in the morning.

• You decide to look at the G-code in the morning.
• You leave a note on the machine, just in case.

You decide that the best thing to do would be to edit the G-code and raise the Z-axis of the spindle before it returns to home. You open the CNC control program and edit the G-code.

While editing the G-code to raise the Z-axis, you notice that the coolant is turned off at the beginning of the code and at the end of the code. The coolant command error caught your attention because your coworker, Mark, mentioned having a similar issue during lunch. You change the coolant command to turn the mist on.

• You decide to talk with your supervisor.
• You discuss what happened with a coworker over lunch.

As you reflect on the residual heat problem, you think about the machining process and the factors that could have caused the issue. You try to think of anything and everything that could be causing the issue. Are you using the correct tool for the specified material? Are you using the specified material? Is it running at the correct speed? Is there enough coolant? Are there chips getting in the way?

Wait, was the coolant turned on? As you replay what happened in your mind, you wonder why the coolant wasn't turned on. You decide to look at the G-code to find out what is going on.

From the milling machine computer, you open the CNC G-code. You notice that there are no coolant commands. You add them in and on the next run, the coolant mist turns on and the residual heat issues is gone. Now, its on to creating the rest of the parts.

Have you ever used brainstorming to solve a problem? Chances are, you've probably have, even if you didn't realize it.

You notice that your trainer, Bill, is on the floor and decide to ask him for help. You describe the problem with the end mill breaking, and how you discovered that items are not being returned to the correctly labeled bins. You think this caused you to grab the incorrect length dowel pins on your first run. You have sorted the bins and hope that the mess problem is fixed. You then go on to tell Bill about the residual heat issue with the completed part.

Together, you go to the milling machine. Bill shows you how to check the oil and coolant levels. Everything looks good at the machine level. Next, on the CNC computer, you open the CNC G-code. While looking at the code, Bill points out that there are no coolant commands. Bill adds them in and when you rerun the program, it works.

Bill is glad you mentioned the problem to him. You are the third worker to mention G-code issues over the last week. You noticed the coolant problems in your G-code, John noticed a Z-axis issue in his G-code, and Sam had issues with both the Z-axis and the coolant. Chances are, there is a bigger problem and Bill will need to investigate the root cause .

Talking with Bill, you discuss the best way to fix the problem. Bill suggests editing the G-code to raise the Z-axis of the spindle before it returns to its home position. You open the CNC control program and edit the G-code. Following the setup sheet, you re-setup the job and use the CNC single step/single block function, to do another dry run of the part. Everything looks good, so you run the job again and create the first part. It works. Since you need four of each component, you move on to creating the rest of them before cleaning up and leaving for the day.

It's a new day and you have new components to create. As you are setting up, you go in search of some short dowel pins. You discover that the bins are a mess and components have not been put away in the correctly labeled bins. You wonder if this was the cause of yesterday's problem. As you reorganize the bins and straighten up the mess, you decide to mention the mess issue to Bill in your afternoon meeting.

You describe the bin mess and using the incorrect length dowels to Bill. He is glad you mentioned the problem to him. You are not the first person to mention similar issues with tools and parts not being put away correctly. Chances are there is a bigger safety issue here that needs to be addressed in the next staff meeting.

In any workplace, following proper safety and cleanup procedures is always important. This is especially crucial in manufacturing where people are constantly working with heavy, costly and sometimes dangerous equipment. When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost, and save money.

You now know that the end mill was damaged when it hit the dowel pin. It seems to you that the easiest thing to do would be to edit the G-code and raise the Z-axis position of the spindle before it returns to the home position. You open the CNC control program and edit the G-code, raising the Z-axis. Starting over, you follow the setup sheet and re-setup the job. This time, you use the CNC single step/single block function, to do another dry run of the part. Everything looks good, so you run the job again and create the first part.

At the end of the day, you are reviewing your progress with your trainer, Bill. After you describe the day's events, he reminds you to always think about safety and the importance of following work procedures. He decides to bring the issue up in the next morning meeting as a reminder to everyone.

In any workplace, following proper procedures (especially those that involve safety) is always important. This is especially crucial in manufacturing where people are constantly working with heavy, costly, and sometimes dangerous equipment. When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost, and save money. One tool to improve communication is the morning meeting or huddle.

The next morning, you check the G-code to determine what is wrong with the coolant. You notice that the coolant is turned off at the beginning of the code and also at the end of the code. This is strange. You change the G-code to turn the coolant on at the beginning of the run and off at the end. This works and you create the rest of the parts.

Throughout the day, you keep wondering what caused the G-code error. At lunch, you mention the G-code error to your coworker, John. John is not surprised. He said that he encountered a similar problem earlier this week. You decide to talk with your supervisor the next time you see him.

You are in luck. You see your supervisor by the door getting ready to leave. You hurry over to talk with him. You start off by telling him about how you asked Bill for help. Then you tell him there was a problem and the end mill was damaged. You describe the coolant problem in the G-code. Oh, and by the way, John has seen a similar problem before.

Your supervisor doesn't seem overly concerned, errors happen. He tells you "Good job, I am glad you were able to fix the issue." You are not sure whether your supervisor understood your explanation of what happened or that it had happened before.

The challenge of communicating in the workplace is learning how to share your ideas and concerns. If you need to tell your supervisor that something is not going well, it is important to remember that timing, preparation, and attitude are extremely important.

It is the end of your shift, but you want to let the next shift know that the coolant didn't turn on. You do not see your trainer or supervisor around. You decide to leave a note for the next shift so they are aware of the possible coolant problem. You write a sticky note and leave it on the monitor of the CNC control system.

How effective do you think this solution was? Did it address the problem?

In this scenario, you discovered several problems with the G-code that need to be addressed. When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring and avoid injury to personnel. The challenge of communicating in the workplace is learning how and when to share your ideas and concerns. If you need to tell your co-workers or supervisor that there is a problem, it is important to remember that timing and the method of communication are extremely important.

You are able to fix the coolant problem in the G-code. While you are glad that the problem is fixed, you are worried about why it happened in the first place. It is important to remember that if a problem keeps reappearing, you may not be fixing the right problem. You may only be addressing the symptoms.

You decide to talk to your trainer. Bill is glad you mentioned the problem to him. You are the third worker to mention G-code issues over the last week. You noticed the coolant problems in your G-code, John noticed a Z-axis issue in his G-code, and Sam had issues with both the Z-axis and the coolant. Chances are, there is a bigger problem and Bill will need to investigate the root cause .

Over lunch, you ask your coworkers about the G-code problem and what may be causing the error. Several people mention having similar problems but do not know the cause.

You have now talked to three coworkers who have all experienced similar coolant G-code problems. You make a list of who had the problem, when they had the problem, and what each person told you.

When you see your supervisor later that afternoon, you are ready to talk with him. You describe the problem you had with your component and the damaged bit. You then go on to tell him about talking with Bill and discovering the G-code issue. You show him your notes on your coworkers' coolant issues, and explain that you think there might be a bigger problem.

You supervisor thanks you for your initiative in identifying this problem. It sounds like there is a bigger problem and he will need to investigate the root cause. He decides to call a team huddle to discuss the issue, gather more information, and talk with the team about the importance of communication.

Root Cause Analysis

Root cause analysis ( RCA ) is a method of problem solving that identifies the underlying causes of an issue. Root cause analysis helps people answer the question of why the problem occurred in the first place. RCA uses clear cut steps in its associated tools, like the "5 Whys Analysis" and the "Cause and Effect Diagram," to identify the origin of the problem, so that you can:

• Determine what happened.
• Determine why it happened.
• Fix the problem so it won’t happen again.

RCA works under the idea that systems and events are connected. An action in one area triggers an action in another, and another, and so on. By tracing back these actions, you can discover where the problem started and how it developed into the problem you're now facing. Root cause analysis can prevent problems from recurring, reduce injury to personnel, reduce rework and scrap, and ultimately, reduce cost and save money. There are many different RCA techniques available to determine the root cause of a problem. These are just a few:

• Root Cause Analysis Tools
• 5 Whys Analysis
• Fishbone or Cause and Effect Diagram
• Pareto Analysis

How Huddles Work

Communication is a vital part of any setting where people work together. Effective communication helps employees and managers form efficient teams. It builds trusts between employees and management, and reduces unnecessary competition because each employee knows how their part fits in the larger goal.

One tool that management can use to promote communication in the workplace is the huddle . Just like football players on the field, a huddle is a short meeting where everyone is standing in a circle. A daily team huddle ensures that team members are aware of changes to the schedule, reiterated problems and safety issues, and how their work impacts one another. When done right, huddles create collaboration, communication, and accountability to results. Impromptu huddles can be used to gather information on a specific issue and get each team member's input.

The most important thing to remember about huddles is that they are short, lasting no more than 10 minutes, and their purpose is to communicate and identify. In essence, a huddle’s purpose is to identify priorities, communicate essential information, and discover roadblocks to productivity.

Who uses huddles? Many industries and companies use daily huddles. At first thought, most people probably think of hospitals and their daily patient update meetings, but lots of managers use daily meetings to engage their employees. Here are a few examples:

• Brian Scudamore, CEO of 1-800-Got-Junk? , uses the daily huddle as an operational tool to take the pulse of his employees and as a motivational tool. Watch a morning huddle meeting .
• Fusion OEM, an outsourced manufacturing and production company. What do employees take away from the daily huddle meeting .
• Biz-Group, a performance consulting group. Tips for a successful huddle .

Brainstorming

One tool that can be useful in problem solving is brainstorming . Brainstorming is a creativity technique designed to generate a large number of ideas for the solution to a problem. The method was first popularized in 1953 by Alex Faickney Osborn in the book Applied Imagination . The goal is to come up with as many ideas as you can in a fixed amount of time. Although brainstorming is best done in a group, it can be done individually. Like most problem solving techniques, brainstorming is a process.

• Define a clear objective.
• Have an agreed a time limit.
• During the brainstorming session, write down everything that comes to mind, even if the idea sounds crazy.
• If one idea leads to another, write down that idea too.
• Combine and refine ideas into categories of solutions.
• Assess and analyze each idea as a potential solution.

When used during problem solving, brainstorming can offer companies new ways of encouraging staff to think creatively and improve production. Brainstorming relies on team members' diverse experiences, adding to the richness of ideas explored. This means that you often find better solutions to the problems. Team members often welcome the opportunity to contribute ideas and can provide buy-in for the solution chosen—after all, they are more likely to be committed to an approach if they were involved in its development. What's more, because brainstorming is fun, it helps team members bond.

• Watch Peggy Morgan Collins, a marketing executive at Power Curve Communications discuss How to Stimulate Effective Brainstorming .
• Watch Kim Obbink, CEO of Filter Digital, a digital content company, and her team share their top five rules for How to Effectively Generate Ideas .

Importance of Good Communication and Problem Description

Communication is one of the most frequent activities we engage in on a day-to-day basis. At some point, we have all felt that we did not effectively communicate an idea as we would have liked. The key to effective communication is preparation. Rather than attempting to haphazardly improvise something, take a few minutes and think about what you want say and how you will say it. If necessary, write yourself a note with the key points or ideas in the order you want to discuss them. The notes can act as a reminder or guide when you talk to your supervisor.

Tips for clear communication of an issue:

• Provide a clear summary of your problem. Start at the beginning, give relevant facts, timelines, and examples.
• Avoid including your opinion or personal attacks in your explanation.
• Avoid using words like "always" or "never," which can give the impression that you are exaggerating the problem.
• If this is an ongoing problem and you have collected documentation, give it to your supervisor once you have finished describing the problem.
• Remember to listen to what's said in return; communication is a two-way process.

Not all communication is spoken. Body language is nonverbal communication that includes your posture, your hands and whether you make eye contact. These gestures can be subtle or overt, but most importantly they communicate meaning beyond what is said. When having a conversation, pay attention to how you stand. A stiff position with arms crossed over your chest may imply that you are being defensive even if your words state otherwise. Shoving your hands in your pockets when speaking could imply that you have something to hide. Be wary of using too many hand gestures because this could distract listeners from your message.

The challenge of communicating in the workplace is learning how and when to share your ideas or concerns. If you need to tell your supervisor or co-worker about something that is not going well, keep in mind that good timing and good attitude will go a long way toward helping your case.

Like all skills, effective communication needs to be practiced. Toastmasters International is perhaps the best known public speaking organization in the world. Toastmasters is open to anyone who wish to improve their speaking skills and is willing to put in the time and effort to do so. To learn more, visit Toastmasters International .

Methods of Communication

Communication of problems and issues in any workplace is important, particularly when safety is involved. It is therefore crucial in manufacturing where people are constantly working with heavy, costly, and sometimes dangerous equipment. As issues and problems arise, they need to be addressed in an efficient and timely manner. Effective communication is an important skill because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost and save money.

There are many different ways to communicate: in person, by phone, via email, or written. There is no single method that fits all communication needs, each one has its time and place.

In person: In the workplace, face-to-face meetings should be utilized whenever possible. Being able to see the person you need to speak to face-to-face gives you instant feedback and helps you gauge their response through their body language. Be careful of getting sidetracked in conversation when you need to communicate a problem.

Email: Email has become the communication standard for most businesses. It can be accessed from almost anywhere and is great for things that don’t require an immediate response. Email is a great way to communicate non-urgent items to large amounts of people or just your team members. One thing to remember is that most people's inboxes are flooded with emails every day and unless they are hyper vigilant about checking everything, important items could be missed. For issues that are urgent, especially those around safety, email is not always be the best solution.

Phone: Phone calls are more personal and direct than email. They allow us to communicate in real time with another person, no matter where they are. Not only can talking prevent miscommunication, it promotes a two-way dialogue. You don’t have to worry about your words being altered or the message arriving on time. However, mobile phone use and the workplace don't always mix. In particular, using mobile phones in a manufacturing setting can lead to a variety of problems, cause distractions, and lead to serious injury.

Written: Written communication is appropriate when detailed instructions are required, when something needs to be documented, or when the person is too far away to easily speak with over the phone or in person.

There is no "right" way to communicate, but you should be aware of how and when to use the appropriate form of communication for your situation. When deciding the best way to communicate with a co-worker or manager, put yourself in their shoes, and think about how you would want to learn about the issue. Also, consider what information you would need to know to better understand the issue. Use your good judgment of the situation and be considerate of your listener's viewpoint.

Did you notice any other potential problems in the previous exercise?

• [Page 6:] Did you notice any other potential problems in the previous exercise?

Summary of Strategies

In this exercise, you were given a scenario in which there was a problem with a component you were creating on a CNC machine. You were then asked how you wanted to proceed. Depending on your path through this exercise, you might have found an easy solution and fixed it yourself, asked for help and worked with your trainer, or discovered an ongoing G-code problem that was bigger than you initially thought.

When issues and problems arise, it is important that they are addressed in an efficient and timely manner. Communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost, and save money. Although, each path in this exercise ended with a description of a problem solving tool for your toolbox, the first step is always to identify the problem and define the context in which it happened.

There are several strategies that can be used to identify the root cause of a problem. Root cause analysis (RCA) is a method of problem solving that helps people answer the question of why the problem occurred. RCA uses a specific set of steps, with associated tools like the “5 Why Analysis" or the “Cause and Effect Diagram,” to identify the origin of the problem, so that you can:

Once the underlying cause is identified and the scope of the issue defined, the next step is to explore possible strategies to fix the problem.

If you are not sure how to fix the problem, it is okay to ask for help. Problem solving is a process and a skill that is learned with practice. It is important to remember that everyone makes mistakes and that no one knows everything. Life is about learning. It is okay to ask for help when you don’t have the answer. When you collaborate to solve problems you improve workplace communication and accelerates finding solutions as similar problems arise.

One tool that can be useful for generating possible solutions is brainstorming . Brainstorming is a technique designed to generate a large number of ideas for the solution to a problem. The method was first popularized in 1953 by Alex Faickney Osborn in the book Applied Imagination. The goal is to come up with as many ideas as you can, in a fixed amount of time. Although brainstorming is best done in a group, it can be done individually.

Depending on your path through the exercise, you may have discovered that a couple of your coworkers had experienced similar problems. This should have been an indicator that there was a larger problem that needed to be addressed.

In any workplace, communication of problems and issues (especially those that involve safety) is always important. This is especially crucial in manufacturing where people are constantly working with heavy, costly, and sometimes dangerous equipment. When issues and problems arise, it is important that they be addressed in an efficient and timely manner. Effective communication is an important tool because it can prevent problems from recurring, avoid injury to personnel, reduce rework and scrap, and ultimately, reduce cost and save money.

One strategy for improving communication is the huddle . Just like football players on the field, a huddle is a short meeting with everyone standing in a circle. A daily team huddle is a great way to ensure that team members are aware of changes to the schedule, any problems or safety issues are identified and that team members are aware of how their work impacts one another. When done right, huddles create collaboration, communication, and accountability to results. Impromptu huddles can be used to gather information on a specific issue and get each team member's input.

To learn more about different problem solving strategies, choose an option below. These strategies accompany the outcomes of different decision paths in the problem solving exercise.

• View Problem Solving Strategies Select a strategy below... Root Cause Analysis How Huddles Work Brainstorming Importance of Good Problem Description Methods of Communication

Communication is one of the most frequent activities we engage in on a day-to-day basis. At some point, we have all felt that we did not effectively communicate an idea as we would have liked. The key to effective communication is preparation. Rather than attempting to haphazardly improvise something, take a few minutes and think about what you want say and how you will say it. If necessary, write yourself a note with the key points or ideas in the order you want to discuss them. The notes can act as a reminder or guide during your meeting.

• Provide a clear summary of the problem. Start at the beginning, give relevant facts, timelines, and examples.

In person: In the workplace, face-to-face meetings should be utilized whenever possible. Being able to see the person you need to speak to face-to-face gives you instant feedback and helps you gauge their response in their body language. Be careful of getting sidetracked in conversation when you need to communicate a problem.

There is no "right" way to communicate, but you should be aware of how and when to use the appropriate form of communication for the situation. When deciding the best way to communicate with a co-worker or manager, put yourself in their shoes, and think about how you would want to learn about the issue. Also, consider what information you would need to know to better understand the issue. Use your good judgment of the situation and be considerate of your listener's viewpoint.

"Never try to solve all the problems at once — make them line up for you one-by-one.” — Richard Sloma

Problem Solving: An Important Job Skill

Problem solving improves efficiency and communication on the shop floor. It increases a company's efficiency and profitability, so it's one of the top skills employers look for when hiring new employees. Recent industry surveys show that employers consider soft skills, such as problem solving, as critical to their business’s success.

The 2011 survey, "Boiling Point? The skills gap in U.S. manufacturing ," polled over a thousand manufacturing executives who reported that the number one skill deficiency among their current employees is problem solving, which makes it difficult for their companies to adapt to the changing needs of the industry.

In this video, industry professionals discuss their expectations and present tips for new employees joining the manufacturing workforce.

Quick Summary

• [Quick Summary: Question1] What are two things you learned in this case study?
• What question(s) do you still have about the case study?
• [Quick Summary: Question2] What question(s) do you still have about the case study?
• Is there anything you would like to learn more about with respect to this case study?
• [Quick Summary: Question3] Is there anything you would like to learn more about with respect to this case study?

• Soft skills
• What is a credential?
• Why do a credential?
• How do credentials work?
• Selecting your level
• How will I be assessed?
• Benefits for professionals
• Benefits for organisations
• Benefits for postgraduates

Problem solving techniques: Steps and methods

Posted on May 29, 2019

Constant disruption has become a hallmark of the modern workforce and organisations want problem solving skills to combat this. Employers need people who can respond to change – be that evolving technology, new competitors, different models for doing business, or any of the other transformations that have taken place in recent years.

In addition, problem solving techniques encompass many of the other top skills employers seek . For example, LinkedIn’s list of the most in-demand soft skills of 2019 includes creativity, collaboration and adaptability, all of which fall under the problem-solving umbrella.

Despite its importance, many employees misunderstand what the problem solving method really involves.

What constitutes effective problem solving?

Effective problem solving doesn’t mean going away and coming up with an answer immediately. In fact, this isn’t good problem solving at all, because you’ll be running with the first solution that comes into your mind, which often isn’t the best.

Instead, you should look at problem solving more as a process with several steps involved that will help you reach the best outcome. Those steps are:

• Define the problem
• List all the possible solutions
• Evaluate the options
• Select the best solution
• Create an implementation plan
• Communicate your solution

Let’s look at each step in a little more detail.

1. Define the problem

The first step to solving a problem is defining what the problem actually is – sounds simple, right? Well no. An effective problem solver will take the thoughts of everyone involved into account, but different people might have different ideas on what the root cause of the issue really is. It’s up to you to actively listen to everyone without bringing any of your own preconceived notions to the conversation. Learning to differentiate facts from opinion is an essential part of this process.

An effective problem solver will take the opinions of everyone involved into account

The same can be said of data. Depending on what the problem is, there will be varying amounts of information available that will help you work out what’s gone wrong. There should be at least some data involved in any problem, and it’s up to you to gather as much as possible and analyse it objectively.

2. List all the possible solutions

Once you’ve identified what the real issue is, it’s time to think of solutions. Brainstorming as many solutions as possible will help you arrive at the best answer because you’ll be considering all potential options and scenarios. You should take everyone’s thoughts into account when you’re brainstorming these ideas, as well as all the insights you’ve gleaned from your data analysis. It also helps to seek input from others at this stage, as they may come up with solutions you haven’t thought of.

Depending on the type of problem, it can be useful to think of both short-term and long-term solutions, as some of your options may take a while to implement.

3. Evaluate the options

Each option will have pros and cons, and it’s important you list all of these, as well as how each solution could impact key stakeholders. Once you’ve narrowed down your options to three or four, it’s often a good idea to go to other employees for feedback just in case you’ve missed something. You should also work out how each option ties in with the broader goals of the business.

There may be a way to merge two options together in order to satisfy more people.

4. Select an option

Only now should you choose which solution you’re going to go with. What you decide should be whatever solves the problem most effectively while also taking the interests of everyone involved into account. There may be a way to merge two options together in order to satisfy more people.

5. Create an implementation plan

At this point you might be thinking it’s time to sit back and relax – problem solved, right? There are actually two more steps involved if you want your problem solving method to be truly effective. The first is to create an implementation plan. After all, if you don’t carry out your solution effectively, you’re not really solving the problem at all. 

Create an implementation plan on how you will put your solution into practice. One problem solving technique that many use here is to introduce a testing and feedback phase just to make sure the option you’ve selected really is the most viable. You’ll also want to include any changes to your solution that may occur in your implementation plan, as well as how you’ll monitor compliance and success.

6. Communicate your solution

There’s one last step to consider as part of the problem solving methodology, and that’s communicating your solution . Without this crucial part of the process, how is anyone going to know what you’ve decided? Make sure you communicate your decision to all the people who might be impacted by it. Not everyone is going to be 100 per cent happy with it, so when you communicate you must give them context. Explain exactly why you’ve made that decision and how the pros mean it’s better than any of the other options you came up with.

Prove your problem solving skills with Deakin

Employers are increasingly seeking soft skills, but unfortunately, while you can show that you’ve got a degree in a subject, it’s much harder to prove you’ve got proficiency in things like problem solving skills. But this is changing thanks to Deakin’s micro-credentials. These are university-level micro-credentials that provide an authoritative and third-party assessment of your capabilities in a range of areas, including problem solving. Reach out today for more information .

• INTERPERSONAL SKILLS
• Problem Solving and Decision Making

Problem Solving

Search SkillsYouNeed:

Interpersonal Skills:

• A - Z List of Interpersonal Skills
• Interpersonal Skills Self-Assessment
• Communication Skills
• Emotional Intelligence
• Conflict Resolution and Mediation Skills
• Customer Service Skills
• Team-Working, Groups and Meetings
• Decision-Making and Problem-Solving
• Effective Decision Making
• Decision-Making Framework
• Introduction to Problem Solving
• Identifying and Structuring Problems
• Investigating Ideas and Solutions
• Implementing a Solution and Feedback
• Creative Problem-Solving
• Social Problem-Solving
• Negotiation and Persuasion Skills
• Personal and Romantic Relationship Skills

Subscribe to our FREE newsletter and start improving your life in just 5 minutes a day.

You'll get our 5 free 'One Minute Life Skills' and our weekly newsletter.

We'll never share your email address and you can unsubscribe at any time.

Everybody can benefit from having good problem solving skills as we all encounter problems on a daily basis. Some of these problems are obviously more severe or complex than others.

It would be wonderful to have the ability to solve all problems efficiently and in a timely fashion without difficulty, unfortunately though there is no one way in which all problems can be solved.

You will discover, as you read through our pages on problem solving, that the subject is complex.

However well prepared we are for problem solving, there is always an element of the unknown. Although planning and structuring will help make the problem solving process more likely to be successful, good judgement and an element of good luck will ultimately determine whether problem solving was a success.

Interpersonal relationships fail and businesses fail because of poor problem solving.

This is often due to either problems not being recognised or being recognised but not being dealt with appropriately.

Problem solving skills are highly sought after by employers as many companies rely on their employees to identify and solve problems.

A lot of the work in problem solving involves understanding what the underlying issues of the problem really are - not the symptoms. Dealing with a customer complaint may be seen as a problem that needs to be solved, and it's almost certainly a good idea to do so. The employee dealing with the complaint should be asking what has caused the customer to complain in the first place, if the cause of the complaint can be eliminated then the problem is solved.

In order to be effective at problem solving you are likely to need some other key skills, which include:

Creativity. Problems are usually solved either intuitively or systematically. Intuition is used when no new knowledge is needed - you know enough to be able to make a quick decision and solve the problem, or you use common sense or experience to solve the problem. More complex problems or problems that you have not experienced before will likely require a more systematic and logical approach to solve, and for these you will need to use creative thinking. See our page on Creative Thinking for more information.

Researching Skills. Defining and solving problems often requires you to do some research: this may be a simple Google search or a more rigorous research project. See our Research Methods section for ideas on how to conduct effective research.

Team Working. Many problems are best defined and solved with the input of other people. Team working may sound like a 'work thing' but it is just as important at home and school as well as in the workplace. See our Team-Working page for more.

Emotional Intelligence. It is worth considering the impact that a problem and/or its solution has on you and other people. Emotional intelligence, the ability to recognise the emotions of yourself and others, will help guide you to an appropriate solution. See our Emotional Intelligence pages for more.

Risk Management. Solving a problem involves a certain amount of risk - this risk needs to be weighed up against not solving the problem. You may find our Risk Management page useful.

Decision Making . Problem solving and decision making are closely related skills, and making a decision is an important part of the problem solving process as you will often be faced with various options and alternatives. See Decision Making for more.

The measure of success is not whether you have a tough problem to deal with, but whether it is the same problem you had last year.

John Foster Dulles, Former US Secretary of State.

What is a Problem?

The Concise Oxford Dictionary (1995) defines a problem as:

“ A doubtful or difficult matter requiring a solution ”

“ Something hard to understand or accomplish or deal with.”

It is worth also considering our own view of what a problem is.

We are constantly exposed to opportunities in life, at work, at school and at home. However many opportunities are missed or not taken full advantage of. Often we are unsure how to take advantage of an opportunity and create barriers - reasons why we can't take advantage. These barriers can turn a potentially positive situation into a negative one, a problem.

Are we missing the 'big problem'? It is human nature to notice and focus on small, easy to solve problems but much harder to work on the big problems that may be causing some of the smaller ones.

It's useful to consider the following questions when faced with a problem.

Is the problem real or perceived?

Is this problem really an opportunity?

Does the problem need solving?

All problems have two features in common: goals and barriers.

Problems involve setting out to achieve some objective or desired state of affairs and can include avoiding a situation or event.

Goals can be anything that you wish to achieve, or where you want to be. If you are hungry then your goal is probably to eat something. If you are the head of an organisation (CEO), then your main goal may be to maximise profits and this main goal may need to be split into numerous sub-goals in order to fulfil the ultimate aim of increasing profits.

If there were no barriers in the way of achieving a goal, then there would be no problem. Problem solving involves overcoming the barriers or obstacles that prevent the immediate achievement of goals.

Following our examples above, if you feel hungry then your goal is to eat. A barrier to this may be that you have no food available - so you take a trip to the supermarket and buy some food, removing the barrier and thus solving the problem. Of course for the CEO wanting to increase profits there may be many more barriers preventing the goal from being reached. The CEO needs to attempt to recognise these barriers and remove them or find other ways to achieve the goals of the organisation.

Our problem solving pages provide a simple and structured approach to problem solving.

The approach referred to is generally designed for problem solving in an organisation or group context, but can also be easily adapted to work at an individual level at home or in education.

Trying to solve a complex problem alone however can be a mistake. The old adage " A problem shared is a problem halved " is sound advice.

Talking to others about problems is not only therapeutic but can help you see things from a different point of view, opening up more potential solutions.

Stages of Problem Solving

Effective problem solving usually involves working through a number of steps or stages, such as those outlined below.

Problem Identification:

This stage involves: detecting and recognising that there is a problem; identifying the nature of the problem; defining the problem.

The first phase of problem solving may sound obvious but often requires more thought and analysis. Identifying a problem can be a difficult task in itself. Is there a problem at all? What is the nature of the problem, are there in fact numerous problems? How can the problem be best defined? By spending some time defining the problem you will not only understand it more clearly yourself but be able to communicate its nature to others, which leads to the second phase.

Structuring the Problem:

This stage involves: a period of observation, careful inspection, fact-finding and developing a clear picture of the problem.

Following on from problem identification, structuring the problem is all about gaining more information about the problem and increasing understanding. This phase is all about fact finding and analysis, building a more comprehensive picture of both the goal(s) and the barrier(s). This stage may not be necessary for very simple problems but is essential for problems of a more complex nature.

Looking for Possible Solutions:

During this stage you will generate a range of possible courses of action, but with little attempt to evaluate them at this stage.

From the information gathered in the first two phases of the problem solving framework it is now time to start thinking about possible solutions to the identified problem. In a group situation this stage is often carried out as a brain-storming session, letting each person in the group express their views on possible solutions (or part solutions). In organisations different people will have different expertise in different areas and it is useful, therefore, to hear the views of each concerned party.

Making a Decision:

This stage involves careful analysis of the different possible courses of action and then selecting the best solution for implementation.

This is perhaps the most complex part of the problem solving process. Following on from the previous step it is now time to look at each potential solution and carefully analyse it. Some solutions may not be possible, due to other problems like time constraints or budgets. It is important at this stage to also consider what might happen if nothing was done to solve the problem - sometimes trying to solve a problem that leads to many more problems requires some very creative thinking and innovative ideas.

Finally, make a decision on which course of action to take - decision making is an important skill in itself and we recommend that you see our pages on decision making .

Implementation:

This stage involves accepting and carrying out the chosen course of action.

Implementation means acting on the chosen solution. During implementation more problems may arise especially if identification or structuring of the original problem was not carried out fully.

Monitoring/Seeking Feedback:

The last stage is about reviewing the outcomes of problem solving over a period of time, including seeking feedback as to the success of the outcomes of the chosen solution.

The final stage of problem solving is concerned with checking that the process was successful. This can be achieved by monitoring and gaining feedback from people affected by any changes that occurred. It is good practice to keep a record of outcomes and any additional problems that occurred.

Continue to: Identifying and Structuring Problems Social Problem Solving

See also: Project Management Risk Management Effective Decision Making

All industries

Goals & services

All goals & All services

Types of innovation

Innovation consulting

Innovation workshop

Innovation coaching

Technical Problem Solving: Technology innovation means cracking tough nuts

Or: how to solve any technical problem with ease.

Lars Lindner* is an engineer and technician. With body and soul. Since finishing his studies, he has been busy with technical products and groundbreaking new processes, always driven by the will to actively promote progress. To identify challenges and eliminate them through technical problem solving. Simply because it can be done. He has already seen everything from cooling systems to power plants, paper machines, ventilation systems and supplier parts for the automotive industry and has worked on them all. “Satisfied people never move the world forward” is his motto. Lars Lindner knows that things can always go one step further. And that’s what he’s passionate about.

Lars Lindner wants to drive technological progress and innovation

Today, Lars Lindner is a team leader in the research and pre-development department of an industrial supplier . Mainly filters, pumps, separators and everything where gases and liquids are conveyed, cleaned or separated from each other. As a team leader, he now faces new challenges. He can no longer solve every problem and work out all the details by himself. Team members and colleagues from other departments need to be empowered to create technical progress. Lars Lindner knows that it is possible. Getting the others on board and convincing them to get involved is his challenge.

Innovation in a technical environment usually means technical problem solving

Innovation , or more specifically, technology innovation , is a big word for Lars Lindner. Sure, it’s about inspiring the customer in new ways. In his company, the focus is clearly on a single aspect of innovation. Customer relationships have existed for a long time and are not in any danger – as long as you keep up with the market in terms of technology and price. The customer’s problems are also clear. No malfunctions, no downtimes, and best of all: The customer is not even aware of the pumps, filters, etc., in their systems at all. But you can’t be complacent. Maintenance, repair and parts replacement are still the reality. For Lars Lindner, innovation in day-to-day business therefore consists of overcoming technical hurdles, making the impossible possible and driving technological or technical problem solving. To invent, to question established technologies and to think beyond existing horizons… to innovate!

Your technology innovations

Are technical and technological problem solving your daily business? Get better solutions faster!

Engineers usually lack the courage to think big.

A very special project serves as an example of what Lars Lindner struggles with. It’s about a complex filtering solution. Expensive and complicated to manufacture. Difficult to handle and maintain. So, it’s also expensive to procure and to operate. Certainly, this solution was justified at the time it was developed. But by today’s standards, it is no longer up-to-date. Far too expensive. Far too complex! “But there’s no other way!” – “You just have to accept things as they are!” – “We’ve already had so many ideas” – “We’ve already tried everything!” Developers lack courage and self-confidence , and management lacks the confidence to free up resources. Lars Lindner feels powerless.

Everyone should broaden their perspectives to realize that the seemingly impossible is possible.

Lars Lindner is tempted to go to the drawing board himself and create realities on his own. He discusses his inner conflict with TOM SPIKE’S innovation consultancy team. TOM SPIKE understands that more is possible than everyone thinks – and that Lars Lindner has to create successes in order to get his team going – despite the fact that he feels powerless and not understood. Or precisely because of that! The experience of hundreds of technology innovations shows that innovation is always possible.

The more complex the technology, the more important interdisciplinary teams are.

A concrete technical challenge has arisen. Something that many lone warriors have already had a go at solving. Teams have even gotten involved. But there is more at stake than this single problem. Development personnel must also dare to think outside the box and gain new knowledge until that kind of thinking comes naturally. Actually, it is quite clear what needs to be done:

• Bring together a handful of experts and get the problem off the table within two days. A clearly structured approach and led by experienced innovators.
• Communicate success. To other teams, to management, and of course, to the customer.
• It is clear to the team and to company management that targeted technology innovation works, and that Lars Lindner is the man to make it happen. Use this energy and establish a proven approach for future issues.

To convince others of innovation, you have to be convinced yourself.

Basically, Lars Lindner is clear that the procedure works. He has already gone through it many times in the past. In many companies. But now he is the prophet in a new wilderness. Lars Lindner has his doubts. Ultimately, he is a technician. He is familiar with technical issues. But he is not a missionary. He didn’t learn how to be one. His colleagues are hesitant. They think there is no solution because no one has come up with one yet. Will the team give a multi-day workshop a chance? Or will skepticism capsize the whole ship and leave just wreckage floating on the surface? The specific concerns are:

• The team will not have any new ideas. They’re just not open to them.
• The boss will not be thrilled because the result will be “just ideas again”. And anyway, no one really knows how the boss ticks.
• If there are results, then the ideas will be too abstract and have no relation to the actual problem at hand. This was typical of previous brain storming sessions.

Innovation is a team sport, not an individual event

Your own comfort zone is a major obstacle to successful innovation. Trying things you’ve never done before. Getting people on board who have never been there before. Walking paths that no one has ever trodden. TOM SPIKE helps you overcome this feeling of insecurity. The clear advice of the experienced innovation consultants to Lars Lindner is this: “Get all the stakeholders together, both the benevolent and the critical, the experts and the decision-makers. Together, we’ll do the persuasion work and answer questions.” His concerns are, of course, real. And they need solutions.

• Could it be that the team will not have any new ideas? TOM SPIKE has never experienced this – ever. With the right approaches, new ideas always come. And the team is not alone. In technology innovation , the knowledge of hundreds of thousands of innovators and inventors is available to you. Knowledge about the principles of invention , solution patterns, and the spiritual power of experts. This power is always there. Setting it free is what TOM SPIKE is expert at doing.
• Will the boss be disappointed? Your superior is an important participant. Understanding what he wants is crucial. Only if he is convinced that the problem is worth solving will he support later implementation of a solution with arguments and resources. The team cannot do without this support. Once you understand what the boss wants, it will get done.
• Is there a real risk that, in the end, all you’ll get is a huge bunch of abstract, useless ideas? If the only answer to the question “How do we create ideas” is “brainstorming”, then that is a real possibility. But with proven tools and methods, there is no risk. The scope is clearly defined. The available potential of intellectual energy is concentrated on a clearly defined challenge. And in case of doubt, a clear guarantee of success is formulated at the start.

For Lars Lindner, a lot is at stake

If he doesn’t tackle the topic of technology innovation , it will take some time before anyone else does. More and more projects will likely fall victim to the company’s daily grind of optimization and efficiency issues. And even more projects will fail because no one is willing to take on the “impossible” and thus achieve what is actually possible. In addition, times are turbulent for industrial companies. Competition from Asian countries is growing and has to be taken seriously. The weakening domestic market in Asia is bringing new competitors to Europe and North America. And changes in the automotive industry are compelling an increasing number of automotive suppliers to enter the industrial market. For Lars Lindner, the danger is that his company will slip further into the commodity business where customers can only be secured by offering the lowest price. A price war that cannot be won in the long run. And a price war that Lars Lindner doesn’t enjoy anyway. No one in his company does.

Technology innovation for long-term success and increased self-confidence

Enough doom and gloom! Where could successful technology innovation take Lars Lindner and his company? Examples from all industries show what is possible. Together with his team, Lars Lindner will develop an outstanding technical solution that will put his company years ahead of its competitors. Be it through patents and property rights, or simply through the time gained. It takes at least one to two years for competitors to copy good solutions. In addition, the team will gain new confidence with the knowledge that it can achieve a technological advantage. And for Lars Lindner, the confirmation of what he has always known beckons: That great things are possible if you just believe it is so and the entire company pulls together.

He will have initiated a movement that can transform the company from an efficiency optimizer to an innovator. Lars will be the one who the company management turns to when it needs someone to lead technical products into the future. The culture of self-doubt and lethargy will give way to confidence and energy. The company will be better than ever. Its products will achieve a high market profile. With solutions that no one had thought of before.

In two days, the team cracks the toughest nuts: Technical problem solving par excellence

Crack the toughest nuts. This is exactly what the two-day workshop for developers, production staff and other functional areas is all about. Precisely those tough nuts that the experts have already tried to crack for more than half a year – in vain. The workshop goes beyond wishy-washy “brainstorming sessions” and leads the team toward actually addressing the technical challenges – step by step.

What has already been tried? Why didn’t it work? What has already been discussed, but never really tried? The total knowledge the team possesses is like a puzzle. Everyone knows something different and there is initially no agreement on which nut has to be cracked at all. In the end, however, the one-day kick-off succeeded in clearly structuring the challenge at hand. Nevertheless, the direct exchange of experiences is the decisive step. Technically fundamental considerations, analyses and collections of ideas followed. Technical problem solving and in-depth analyses quickly create blinders. Therefore, it was necessary to open and expand minds and horizons. A real challenge for the moderators.

But they succeed: After two days, an incredible variety of promising solutions were identified. In the last phase of the two-day workshop, the results were merged, bundled, evaluated and prioritized. What remained were three promising solution concepts. A small portfolio of different levels of innovation and implementation schedules was selected. Short-, medium- and long-term concepts. All of them are now being implemented in prototype in order to confirm their technical feasibility, customer acceptance and cost-effectiveness. In a year, the product should be on the market. Experts, managers and Lars Lindner are equally relieved, convinced and euphoric.

From timid lone warrior to respected trailblazer

Solutions that can be implemented directly and commitment from experts and executives. Lars Lindner’s doubts have evaporated. The proof that technology innovation can be fueled with targeted leadership and methodology is now clearly evident. With strengthened self-confidence, he and the team get to work on implementing the developed solution. And the next topics are already waiting. Technical problem solving is no longer regarded as a myth; it is a craft. More tough nuts are waiting to be cracked. And as of today, it is clear who the company can rely on to crack them: Lars Lindner.

Immediate Innovation Assistance

A recipe for success for technology innovation! Learn from the mistakes of companies like yours.

*Name changed

Leave a Reply Cancel reply

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

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

Similar articles

Ideation Workshop – How professionals develop outstanding ideas

That is Innovation – 6 Phases to successful Market Launch

Innovation Capability – How ADKAR can help

Implementation: WordPress agency MEWIGO

You are currently viewing a placeholder content from Google Maps . To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

Table of Contents

The problem-solving process, how to solve problems: 5 steps, train to solve problems with lean today, mastering problem solving: boost business performance & achieve success.

Problem solving is the art of identifying problems and implementing the best possible solutions. Revisiting your problem-solving skills may be the missing piece to leveraging the performance of your business, achieving Lean success, or unlocking your professional potential. 

Ask any colleague if they’re an effective problem-solver and their likely answer will be, “Of course! I solve problems every day.” 

Problem solving is part of most job descriptions, sure. But not everyone can do it consistently. 

Problem solving is the process of defining a problem, identifying its root cause, prioritizing and selecting potential solutions, and implementing the chosen solution.

There’s no one-size-fits-all problem-solving process. Often, it’s a unique methodology that aligns your short- and long-term objectives with the resources at your disposal. Nonetheless, many paradigms center problem solving as a pathway for achieving one’s goals faster and smarter. 

One example is the Six Sigma framework , which emphasizes eliminating errors and refining the customer experience, thereby improving business outcomes. Developed originally by Motorola, the Six Sigma process identifies problems from the perspective of customer satisfaction and improving product delivery. 

Lean management, a similar method, is about streamlining company processes over time so they become “leaner” while producing better outcomes. 

Trendy business management lingo aside, both of these frameworks teach us that investing in your problem solving process for personal and professional arenas will bring better productivity.

1. Precisely Identify Problems

As obvious as it seems, identifying the problem is the first step in the problem-solving process. Pinpointing a problem at the beginning of the process will guide your research, collaboration, and solutions in the right direction. 

At this stage, your task is to identify the scope and substance of the problem. Ask yourself a series of questions: 

• What’s the problem? 
• How many subsets of issues are underneath this problem? 
• What subject areas, departments of work, or functions of business can best define this problem? 

Although some problems are naturally large in scope, precision is key. Write out the problems as statements in planning sheets . Should information or feedback during a later step alter the scope of your problem, revise the statements. 

Framing the problem at this stage will help you stay focused if distractions come up in later stages. Furthermore, how you frame a problem will aid your search for a solution. A strategy of building Lean success, for instance, will emphasize identifying and improving upon inefficient systems. 

2. Collect Information and Plan 

The second step is to collect information and plan the brainstorming process. This is another foundational step to road mapping your problem-solving process. Data, after all, is useful in identifying the scope and substance of your problems. 

Collecting information on the exact details of the problem, however, is done to narrow the brainstorming portion to help you evaluate the outcomes later. Don’t overwhelm yourself with unnecessary information — use the problem statements that you identified in step one as a north star in your research process. 

This stage should also include some planning. Ask yourself:

• What parties will ultimately decide a solution? 
• Whose voices and ideas should be heard in the brainstorming process? 
• What resources are at your disposal for implementing a solution? 

Establish a plan and timeline for steps 3-5. 

3. Brainstorm Solutions

Brainstorming solutions is the bread and butter of the problem-solving process. At this stage, focus on generating creative ideas. As long as the solution directly addresses the problem statements and achieves your goals, don’t immediately rule it out. 

Moreover, solutions are rarely a one-step answer and are more like a roadmap with a set of actions. As you brainstorm ideas, map out these solutions visually and include any relevant factors such as costs involved, action steps, and involved parties. 

With Lean success in mind, stay focused on solutions that minimize waste and improve the flow of business ecosystems. 

Become a Quality Management Professional

• 10% Growth In Jobs Of Quality Managers Profiles By 2025
• 11% Revenue Growth For Organisations Improving Quality

Certified Lean Six Sigma Green Belt

• 4 hands-on projects to perfect the skills learnt
• 4 simulation test papers for self-assessment

Lean Six Sigma Expert

• IASSC® Lean Six Sigma Green Belt and Black Belt certification
• 13 Projects, 12 Simulation exams, 18 Case Studies & 114 PDUs

Here's what learners are saying regarding our programs:

Xueting Liu

Mechanical engineer student at sargents pty. ltd. ,.

A great training and proper exercise with step-by-step guide! I'll give a rating of 10 out of 10 for this training.

Abdus Salam

Completing Simplilearn's Lean Six Sigma Expert Master’s Program empowered me to excel in new projects, enhancing my performance significantly. Consequently, my research position's average pay rate surged by 21%.

4. Decide and Implement

The most critical stage is selecting a solution. Easier said than done. Consider the criteria that has arisen in previous steps as you decide on a solution that meets your needs. 

Once you select a course of action, implement it. 

Practicing due diligence in earlier stages of the process will ensure that your chosen course of action has been evaluated from all angles. Often, efficient implementation requires us to act correctly and successfully the first time, rather than being hurried and sloppy. Further compilations will create more problems, bringing you back to step 1. 

5. Evaluate

Exercise humility and evaluate your solution honestly. Did you achieve the results you hoped for? What would you do differently next time? 

As some experts note, formulating feedback channels into your evaluation helps solidify future success. A framework like Lean success, for example, will use certain key performance indicators (KPIs) like quality, delivery success, reducing errors, and more. Establish metrics aligned with company goals to assess your solutions.

Master skills like measurement system analysis, lean principles, hypothesis testing, process analysis and DFSS tools with our Lean Six Sigma Green Belt Training Course . Sign-up today!

Become a quality expert with Simplilearn’s Lean Six Sigma Green Belt . This Lean Six Sigma certification program will help you gain key skills to excel in digital transformation projects while improving quality and ultimate business results.

In this course, you will learn about two critical operations management methodologies – Lean practices and Six Sigma to accelerate business improvement.

Our Quality Management Courses Duration And Fees

Explore our top Quality Management Courses and take the first step towards career success

Get Free Certifications with free video courses

Quality Management

Lean Management

Project Management

Learn from industry experts with free masterclasses, digital marketing.

The Top 10 AI Tools You Need to Master Marketing in 2024

SEO vs. PPC: Which Digital Marketing Career Path Fits You Best in 2024?

Unlock Digital Marketing Career Success Secrets for 2024 with Purdue University

Recommended Reads

Introduction to Machine Learning: A Beginner's Guide

Webinar Wrap-up: Mastering Problem Solving: Career Tips for Digital Transformation Jobs

An Ultimate Guide That Helps You to Develop and Improve Problem Solving in Programming

Free eBook: 21 Resources to Find the Data You Need

ITIL Problem Workaround: A Leader’s Guide to Manage Problems

Your One-Stop Solution to Understand Coin Change Problem

Get Affiliated Certifications with Live Class programs

• PMP, PMI, PMBOK, CAPM, PgMP, PfMP, ACP, PBA, RMP, SP, and OPM3 are registered marks of the Project Management Institute, Inc.

Deep learning is a subset of machine learning that uses multi-layered neural networks , called deep neural networks, to simulate the complex decision-making power of the human brain. Some form of deep learning powers most of the artificial intelligence (AI) in our lives today.

By strict definition, a deep neural network, or DNN, is a neural network with three or more layers. In practice, most DNNs have many more layers. DNNs are trained on large amounts of data to identify and classify phenomena, recognize patterns and relationships, evaluate posssibilities, and make predictions and decisions. While a single-layer neural network can make useful, approximate predictions and decisions, the additional layers in a deep neural network help refine and optimize those outcomes for greater accuracy.

Deep learning drives many applications and services that improve  automation , performing analytical and physical tasks without human intervention. It lies behind everyday products and services—e.g., digital assistants, voice-enabled TV remotes,  credit card fraud detection—as well as still emerging technologies such as self-driving cars and generative AI. 

Learn the building blocks and best practices to help your teams accelerate responsible AI.

Register for the ebook on generative AI

If deep learning is a subset of machine learning, how do they differ? Deep learning distinguishes itself from classical machine learning by the type of data that it works with and the methods in which it learns.

Machine learning algorithms leverage structured, labeled data to make predictions—meaning that specific features are defined from the input data for the model and organized into tables. This doesn’t necessarily mean that it doesn’t use unstructured data; it just means that if it does, it generally goes through some pre-processing to organize it into a structured format.

Deep learning eliminates some of data pre-processing that is typically involved with machine learning. These algorithms can ingest and process unstructured data, like text and images, and it automates feature extraction, removing some of the dependency on human experts. For example, let’s say that we had a set of photos of different pets, and we wanted to categorize by “cat”, “dog”, “hamster”, et cetera. Deep learning algorithms can determine which features (e.g. ears) are most important to distinguish each animal from another. In machine learning, this hierarchy of features is established manually by a human expert.

Then, through the processes of gradient descent and backpropagation, the deep learning algorithm adjusts and fits itself for accuracy, allowing it to make predictions about a new photo of an animal with increased precision.  

Machine learning and deep learning models are capable of different types of learning as well, which are usually categorized as supervised learning, unsupervised learning, and reinforcement learning. Supervised learning utilizes labeled datasets to categorize or make predictions; this requires some kind of human intervention to label input data correctly. In contrast, unsupervised learning doesn’t require labeled datasets, and instead, it detects patterns in the data, clustering them by any distinguishing characteristics. Reinforcement learning is a process in which a model learns to become more accurate for performing an action in an environment based on feedback in order to maximize the reward.

For a deeper dive on the nuanced differences between the different technologies, see " AI vs. Machine Learning vs. Deep Learning vs. Neural Networks: What’s the Difference? "

For a closer look at the specific differences between supervised and unsupervised learning, see " Supervised vs. Unsupervised Learning: What's the Difference? "

Deep learning neural networks, or artificial neural networks, attempts to mimic the human brain through a combination of data inputs, weights, and bias. These elements work together to accurately recognize, classify, and describe objects within the data.

Deep neural networks consist of multiple layers of interconnected nodes, each building upon the previous layer to refine and optimize the prediction or categorization. This progression of computations through the network is called forward propagation. The input and output layers of a deep neural network are called  visible  layers. The input layer is where the deep learning model ingests the data for processing, and the output layer is where the final prediction or classification is made.

Another process called backpropagation   uses algorithms, like gradient descent, to calculate errors in predictions and then adjusts the weights and biases of the function by moving backwards through the layers in an effort to train the model. Together, forward propagation and backpropagation allow a neural network to make predictions and correct for any errors accordingly. Over time, the algorithm becomes gradually more accurate.

The above describes the simplest type of deep neural network in the simplest terms. However, deep learning algorithms are incredibly complex, and there are different types of neural networks to address specific problems or datasets. For example,

• Convolutional neural networks (CNNs),   used primarily in computer vision and image classification applications, can detect features and patterns within an image, enabling tasks, like object detection or recognition. In 2015, a CNN bested a human in an object recognition challenge for the first time.
• Recurrent neural network (RNNs)   are typically used in natural language and speech recognition applications as it leverages sequential or times series data.

Real-world deep learning applications are a part of our daily lives, but in most cases, they are so well-integrated into products and services that users are unaware of the complex data processing that is taking place in the background. Some of these examples include the following:

Law enforcement  

Deep learning algorithms can analyze and learn from transactional data to identify dangerous patterns that indicate possible fraudulent or criminal activity. Speech recognition, computer vision, and other deep learning applications can improve the efficiency and effectiveness of investigative analysis by extracting patterns and evidence from sound and video recordings, images, and documents, which helps law enforcement analyze large amounts of data more quickly and accurately.

Financial services  

Financial institutions regularly use predictive analytics to drive algorithmic trading of stocks, assess business risks for loan approvals, detect fraud, and help manage credit and investment portfolios for clients.

Customer service  

Many organizations incorporate deep learning technology into their customer service processes.  Chatbots —used in a variety of applications, services, and customer service portals—are a straightforward form of AI . Traditional chatbots use natural language and even visual recognition, commonly found in call center-like menus. However, more  sophisticated chatbot solutions  attempt to determine, through learning, if there are multiple responses to ambiguous questions. Based on the responses it receives, the chatbot then tries to answer these questions directly or route the conversation to a human user.

Virtual assistants like Apple's Siri, Amazon Alexa, or Google Assistant extends the idea of a chatbot by enabling speech recognition functionality. This creates a new method to engage users in a personalized way.

Healthcare  

The healthcare industry has benefited greatly from deep learning capabilities ever since the digitization of hospital records and images. Image recognition applications can support medical imaging specialists and radiologists, helping them analyze and assess more images in less time.

Deep learning requires a tremendous amount of computing power. High performance  graphical processing units (GPUs)  are ideal because they can handle a large volume of calculations in multiple cores with copious memory available. However, managing multiple GPUs on-premises can create a large demand on internal resources and be incredibly costly to scale.

IBM watsonx is a portfolio of business-ready tools, applications and solutions, designed to reduce the costs and hurdles of AI adoption while optimizing outcomes and responsible use of AI.

watsonx Assistant is the AI chatbot for business. This enterprise artificial intelligence technology enables users to build conversational AI solutions.

Build, run and manage AI models. Prepare data and build models on any cloud using open source code or visual modeling. Predict and optimize your outcomes.

Learn the fundamental concepts for AI and generative AI, including prompt engineering, large language models and the best open source projects.

Download our ebook for fresh insights into the opportunities, challenges and lessons learned from infusing AI into businesses.

Explore this branch of machine learning that's trained on large amounts of data and deals with computational units working in tandem to perform predictions.

Explore the fundamentals of machine learning and deep learning architecture and discover their associated applications and benefits.

Picking the right deep learning framework based on your individual workload is an essential first step in deep learning.

Train, validate, tune and deploy generative AI, foundation models and machine learning capabilities with IBM watsonx.ai, a next-generation enterprise studio for AI builders. Build AI applications in a fraction of the time with a fraction of the data.