Effective Problem Solving: Process and Techniques

Every day brings situations that do not solve themselves. A project stalls, a budget falls short, two priorities clash, or a familiar approach suddenly stops working. What separates people who move through these situations smoothly from those who get stuck is rarely raw intelligence. It is having a clear process. Problem solving is a learnable skill with recognisable phases, supported by specific mental and emotional resources, and improved through deliberate planning. This article breaks down how effective problem solving actually works, drawing on established research in cognitive psychology, and what you can do to get better at it.

What problem solving really means 🔗

A problem exists when there is a gap between where you are and where you want to be, and the path across that gap is not obvious. The psychologist Richard Mayer captured this precisely. He defined problem solving as cognitive processing directed at achieving a goal when no clear solution method is available to the person facing it. If the answer were obvious, it would not be a problem; it would just be a task.

Mayer identified several features that make this idea concrete. Problem solving is cognitive, meaning it happens in the mind and is observed only indirectly through behaviour. It is a process, involving the representation and manipulation of knowledge. It is goal-directed, aimed at reaching a specific outcome. And it is personal, because each person’s experience and skills shape how difficult a given problem feels. Two people can face the same situation and experience it very differently, which is why there is no single universal formula that fits every case.

Researchers also distinguish between simple and complex problems. Joachim Funke and his colleagues describe how complex problem solving means overcoming barriers between a current state and a desired goal state through multi-step cognitive and behavioural activity. Complex problems tend to be dynamic, involve many interconnected variables, and rarely have one clean solution. Most of the meaningful problems in work and life sit closer to this end of the scale.

The phases of problem solving 🔗

One of the clearest early descriptions of how problem solving unfolds comes from the psychologist Josef Linhart, whose framework outlines three broad phases that a person moves through when tackling a problem. Understanding these phases gives structure to what can otherwise feel like a confusing scramble.

Discovering and defining the problem 🔗

The first phase is recognising that a problem exists and understanding its nature. This sounds obvious, but it is the step people most often rush. A careful first phase involves detecting the problem, identifying what it actually is, and defining it clearly. Many failed solutions trace back to solving the wrong problem. Spending time here, asking what is really going on and whether there are several issues hiding under one symptom, pays off later.

For example, a small business owner who notices falling sales might define the problem as “I need to advertise more.” But the real problem could be slow delivery, a pricing mismatch, or a competitor’s new offering. Defining the problem accurately changes everything that follows.

The solution process 🔗

In the second phase, the person engages directly with the situation, examines its properties, and looks for the resources or methods that could change it to reach the desired goal. This is where you generate possible courses of action and then evaluate them. In a group, this often takes the form of brainstorming, where different people contribute ideas based on their expertise before any single option is chosen.

The work here splits into two connected tasks: representing the problem and then solving it. Representation means building an accurate internal picture of the problem, often by writing it down, drawing it, or breaking it into parts. Only once the problem is represented clearly can the search for solutions proceed effectively.

Verifying the outcome 🔗

The third phase is verification. After a method has been applied, you check whether it actually solved the problem and whether it could be useful for similar problems in the future. The success of the action has to be measured, both to confirm the problem is solved and to judge its usefulness for future problems of the same type. If the outcome falls short, further action is needed.

This phase is frequently neglected. Research on problem solving in learning settings notes that the reflection phase is one of the most overlooked, yet it is critical for building expertise. Once people reach an answer, they tend to move on immediately. Pausing to ask why a solution worked, and what principle made it work, is what turns a one-time fix into a transferable skill.

The role of cognitive and motivational factors 🔗

Knowing the phases is not enough. What powers movement through them is a combination of mental ability and the drive to keep going. Researchers separate these into a few distinct layers.

Cognitive and metacognitive skills 🔗

Cognitive skills are the basic mental operations: recalling relevant knowledge, recognising patterns, reasoning through options, and applying rules. But having these skills is not the same as using them well. Mayer’s work distinguishes between possessing cognitive components and being able to orchestrate and control them, an ability referred to as metacognition.

Metacognition is essentially thinking about your own thinking. It includes planning what to do, monitoring whether your approach is working, and adjusting when it is not. A person can know every relevant fact and still fail at a problem if they cannot manage their own process. This is why a strong student sometimes freezes on an unfamiliar question while another with less knowledge but better self-monitoring works it out.

Motivation and emotional engagement 🔗

The third layer is motivation. Difficult problems are demanding, and the willingness to stay engaged when progress is slow makes a real difference. Funke and colleagues emphasise that problem solving is not only a cognitive process but also an emotional one, and strongly dependent on motivation. The same problem feels different depending on whether you care about the outcome and believe you can affect it.

Emotions are not merely a distraction here. Frustration, curiosity, anxiety, and satisfaction all shape how long a person persists and how flexibly they think. Research in this area, including work by Funke with collaborators on the role of emotions, treats emotional engagement as part of the problem-solving system rather than noise to be filtered out. Practically, this means managing your emotional state, taking a break when frustration narrows your thinking, is a legitimate problem-solving move, not avoidance.

Strategies for planning and execution 🔗

If there is one phase where extra effort consistently raises the quality of outcomes, it is planning. Planning is where you map out the sequence of steps, anticipate what could go wrong, and decide what resources each step needs.

Mapping steps and contingencies 🔗

A good plan does more than list actions. It describes the order of those actions, the timescale, and the resources required at each stage. Crucially, it also builds in ways to minimise risk and sets out what to do if things go wrong. These are contingencies, your backup options for the points where reality is most likely to deviate from the plan.

Thinking through contingencies in advance is far easier than improvising under pressure. A student preparing for competitive exams, for instance, plans not just a study schedule but also what to do if a topic proves harder than expected or if illness costs a week. The plan with contingencies survives contact with reality; the rigid plan does not.

Staying flexible as information arrives 🔗

The most important quality of a good problem solver during execution is flexibility. No plan is complete at the start, because solving a problem reveals new information. The phases of problem solving are not a strict one-way sequence. As one analysis notes, at any stage it may be necessary to go back and adapt work done at an earlier stage. Discovering a fact during execution might send you back to redefine the problem.

This flexibility has a basis in how the mind handles changing situations. Studies of decision-making distinguish between a fast, habitual approach that repeats what worked before and a slower, goal-directed approach that plans using an internal model of the situation and can immediately adapt when the conditions change. The goal-directed approach is more effortful, but it is what allows you to respond correctly when the rules of the problem shift midway. Effective problem solvers lean on this adaptive mode, treating their plan as a living guide rather than a fixed script.

The same principle applies in organisations. Management research on the contingency approach argues that flexible decision-making, where responses are tailored to each situation rather than forced into a rigid framework, helps teams react faster when circumstances change. Whether for an individual or a team, the lesson is the same: plan thoroughly, then hold the plan loosely.

Bringing it together 🔗

Effective problem solving is a cycle, not a straight line. You discover and define the problem, work through possible solutions, and verify the outcome, looping back whenever new information demands it. Carrying you through that cycle are three resources working together: the cognitive skills to process the problem, the metacognitive control to manage your own approach, and the motivation and emotional steadiness to persist. Planning sharpens the whole process by mapping steps and contingencies in advance, while flexibility keeps that plan useful as the situation evolves.

The encouraging part is that none of this is fixed talent. The phases can be practised, metacognitive habits can be built, and planning improves with repetition. Each problem you work through deliberately, rather than reactively, strengthens the underlying skill.

What do you think? When you last faced a difficult problem, did you spend enough time defining it before jumping to solutions, or did you rush ahead? And how often do you pause to reflect on why a solution worked, rather than simply moving on to the next thing?

References

1. https://files.eric.ed.gov/fulltext/EJ1234950.pdf
2. https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2017.01153/full
3. https://www.researchgate.net/publication/277651623_Theory_of_Problem_Solving
4. https://www.linkedin.com/pulse/stages-problem-solving-gowthaman-senaratna
5. https://itseducation.asia/article/the-stages-of-problem-solving
6. https://arxiv.org/pdf/1602.06352
7. http://rhartshorne.com/fall-2012/eme6507-rh/cdisturco/eme6507-eportfolio/documents/Mayer%201998.pdf
8. https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005753