How to be a better problem solver: a systematic framework

Systematic problem solving is not intuition applied more carefully. It is a distinct set of competencies organised across seven phases, each addressing a specific point where unstructured approaches typically fail.

The ability to solve problems consistently and well is one of the most consequential professional skills. The U.S. Department of Labor, European Commission, Jobs and Skills Australia, the World Economic Forum and the OECD all identify problem solving as a core capability required across roles, industries and career stages. Yet most professionals have never been given a systematic framework for it. They rely on intuition, pattern recognition and experience, approaches that work well for familiar problems and fail quietly on complex ones.

The difference between adequate problem solvers and genuinely capable ones is not intelligence or effort. It is method. Systematic problem solving builds on generations of research and practice, from John Dewey's conceptualisation of reflective thought in 1910 to mathematician George Polya's four-step framework in How to Solve It in 1945. Both emphasised structured, iterative approaches over instinct. The seven-phase framework used by Edaith builds on this lineage, adding a critical final step that traditional approaches overlook.

The seven-phase problem-solving framework

Effective problem solving progresses through seven distinct phases. Each addresses a specific point of failure in unstructured approaches. Used in sequence — or selectively, depending on the problem — they provide a complete system for navigating challenges of any scale or complexity.

The seven-phase framework organises problem solving into distinct, developable competencies. Each phase addresses a specific point where unstructured approaches typically fail. Source: Problem Solver: The Problem Solving Toolkit by Edaith.

Define: establishing what problem you are actually solving

What is initially perceived as a problem may not be upon further examination. Effective problem solvers invest time at this phase before acting — establishing what the actual problem is, who is affected and has influence, and what measurable success looks like. Problems that are poorly defined at the outset consume significant resources solving the wrong thing.

Defining the problem clearly requires examining whether there are constraints, such as resources, timing, legality or feasibility, that shape what solutions are possible. It also requires distinguishing between the problem as it presents and the underlying issue it may be masking. A recurring operational failure, for instance, is often a symptom of a process or incentive problem that the surface issue does not reveal.

Tools to define a problem.

Analyse: understanding causes before devising solutions

The analysis phase moves beyond surface-level assumptions and symptoms to understand underlying causes. It is the diagnostic stage: what is actually driving the problem, and how do the contributing factors interact? Skipping or abbreviating this phase is among the most common and costly mistakes in professional problem solving. It produces solutions that address what is visible rather than what is real, and problems that recur.

Thorough analysis enables solutions that are tailored to the actual context, rather than generic interventions that fit the category of problem rather than the specific instance. In complex or multifaceted situations, this distinction determines whether an intervention holds.

Tools to analyse a problem.

Devise: generating possibilities rather than defaulting to the familiar

To devise is to work out or create. This phase requires divergent thinking — generating a range of possible approaches rather than committing to the first plausible one. Experienced problem solvers resist the impulse to act on an early idea. They generate multiple options, including approaches drawn from other contexts or domains, before evaluating any of them.

In group settings, the quality of idea generation improves when collaborators have time to develop ideas independently before collective discussion begins. Scrutiny and cooperative debate, while uncomfortable, spur the kind of conceptual reframing that produces genuinely novel solutions rather than variations on the familiar.

Tools to generate solution ideas.

Decide: making sound choices despite uncertainty

Outside mathematical or technical problems, there is rarely one correct answer. The Decide phase requires identifying the best available option against explicit criteria — not the most obvious, the most comfortable, or the one argued for most forcefully.

Nobel Prize-winning psychologist Daniel Kahneman, in Thinking, Fast and Slow, explains how people switch between intuitive and analytical modes of thinking when evaluating options. Experienced decision-makers rely more heavily on fast, intuitive processes, but this is a function of practised pattern recognition, not the abandonment of systematic evaluation. For complex problems with significant consequences, systematic comparison of options using explicit criteria is consistently more reliable than gut feel alone.

Tools to make decisions.

Implement: making solutions reality

Implementation is consistently identified as the most difficult phase of achieving any goal. The challenge is not only complexity or scale. Solutions involving behavioural or organisational change must also contend with a well-documented human tendency to prefer existing states. Loss aversion, status quo bias and the effort required to sustain new behaviours mean that even well-designed solutions fail at the implementation stage when this resistance is underestimated.

Effective implementation begins with breaking the goal into specific, actionable steps with clear ownership, and then managing resources and stakeholder dynamics as the solution moves from plan to reality. The smallest executable actions are often more powerful than ambitious plans that never translate into behaviour change.

Tools to get things done.

Improve: learning from outcomes systematically

Continuous improvement is central to long-term effectiveness. The concept of Kaizen, influential since the 1980s and widely credited as a factor in Japanese organisational competitiveness, advocates for ongoing incremental improvement at every level, from leadership to frontline practice. Its cornerstones are process improvement, elimination of waste, adaptability and a culture of learning.

At an individual level, the Improve phase requires measuring whether the solution actually worked, extracting lessons from the experience, and refining approaches based on evidence. Without this step, mistakes repeat, assumptions go unchallenged, and problem solving stays at the same level of effectiveness regardless of experience accumulated.

Tools for continuous improvement.

Document: turning individual learning into lasting knowledge

Most problem-solving frameworks stop at implementation or review. The Document phase is what distinguishes a system that compounds over time from one that resets after each problem. Problem solving relies on cognitive processes that connect memories of past experiences and relevant knowledge to the current challenge. Without systematic documentation, those insights are not reliably retrievable — by the individual, by colleagues, or by the AI tools increasingly used for information retrieval.

Advances in AI, including natural language processing and knowledge retrieval systems, can substantially extend an individual's and an organisation's problem-solving capability, but only when the knowledge they draw on has been captured and structured. Documentation is not an administrative task. It is the mechanism by which problem-solving capability accumulates rather than evaporates.

Tools to document information and insights.

Lightning problem solving: when systematic analysis is not the right tool

The seven-phase framework is designed for complex problems where getting to root causes matters and where the consequences of a poor solution are significant. Not every problem warrants this level of investment. Everyday obstacles, urgent low-stakes decisions and situations where rapid action is more valuable than thorough analysis call for a different approach.

Lightning problem solving is a complementary framework for exactly these situations: problems that need a resolution quickly, or challenges that have become unnecessarily complicated. The distinction between when to apply systematic analysis and when to move fast with action-oriented thinking is itself a critical professional capability. The full lightning problem solving framework is available to Edaith product update subscribers.

Getting started

Problem-solving capability develops with practice, not just exposure. With a systematic framework, diverse tools and the discipline to apply them to real challenges, capability compounds over time. The problem solver who works through a problem using structured approaches builds more durable capability than one who relies on intuition alone.

Problem Solver: The Problem Solving Toolkit contains 30 evidence-based tools across all seven phases, including lightning problem solving, and is available at edaith.com. To understand your current proficiency across the 17 competencies within this framework, the Systematic Problem-Solving Capability Profile delivers a personalised report with targeted development actions for each competency. For team and organisational implementation, contact Edaith.