How to build problem-solving capability
Building problem-solving capability in organisations requires a fundamentally different approach from traditional training. The distinction between knowledge transfer and genuine capability development determines whether people solve problems differently after a session, or simply know more about problem solving.
Most organisations invest in problem-solving training and see limited lasting change. The training may be well designed and well delivered. The content may be accurate and relevant. The issue is structural: you cannot build capability through knowledge transfer alone. Research on learning and forgetting shows that people retain only a fraction of what they learn in a single session without deliberate reinforcement and application. Problem solving is not a subject to be taught; it is a capability to be practised.
This distinction shapes everything about how effective capability development is designed and delivered.
Why most problem-solving training doesn't stick
The challenge for L&D professionals building problem-solving capability is not a shortage of frameworks or content. It is the gap between understanding a method and being able to apply it under the conditions of real work. John Sweller's cognitive load theory, developed at the University of New South Wales, demonstrates that learning acquired in low-stakes, abstract conditions transfers poorly to high-stakes, complex ones, because the cognitive demands of the real context are fundamentally different from those of the learning environment.
The forgetting curve, first documented by Hermann Ebbinghaus in the late nineteenth century, established that memory decays rapidly without reinforcement. People forget the majority of new information within days of acquiring it in the absence of active recall and application. For organisations, this means a training session that is not followed by structured practice and application produces knowledge that quickly evaporates rather than capability that compounds.
This is not an argument against structured learning sessions. It is an argument for designing them differently, and for treating what happens after the session as at least as important as what happens during it.
Real problems, not hypothetical scenarios
The most consequential design choice in a problem-solving capability session is whether participants work on genuine workplace challenges or invented scenarios. Generic case studies reduce cognitive engagement because the stakes are artificial. People know that the outcome does not matter, and they learn accordingly.
When participants work through problems they are actually facing, the dynamics shift entirely. Motivation becomes intrinsic. Context is immediately applicable. The cognitive and emotional investment deepens. And the learning transfers directly, because no translation is needed between the scenario and the real situation. This principle is embedded in the Edaith workshop model, which consistently directs facilitators to use participants' genuine workplace challenges wherever possible, because authentic problems create more meaningful learning.
Practically, this means asking participants to bring a real challenge to the session in advance. Not a cleaned-up version of a past project, and not a hypothetical. A live problem they need to solve.
Frame it as capability development, not problem-solving training
How a session is positioned significantly affects how people engage with it. "Problem-solving training" implies a deficit, that current approaches are inadequate and need to be fixed. This framing can activate defensiveness before the session begins. Positioning the same content as professional capability development, or as building transferable skills for current and future roles, produces a qualitatively different reception.
This is not a question of marketing language. Psychological safety affects learning outcomes. People need to feel safe to experiment with unfamiliar approaches, make errors, and iterate for genuine capability development. A session framed as remedial training does not create those conditions. One framed as skills investment does.
Systematic and lightning problem solving: knowing which to apply
A critical and often overlooked element of problem-solving capability development is teaching people when to use systematic analysis and when to act quickly without it. Not every problem warrants the full seven-phase process. Applying structured diagnostic tools to a low-stakes, reversible situation wastes time and adds friction. Applying rapid action-oriented thinking to a high-stakes, complex challenge produces superficial and often recurring solutions.
The Problem Solver framework addresses this directly. The seven-phase systematic process — Define, Analyse, Devise, Decide, Implement, Improve, Document — is designed for complex challenges where getting to the root cause matters and where the consequences of a poor solution are significant. Lightning problem solving, a complementary framework for everyday obstacles and time-sensitive situations, applies an action-oriented mindset to problems that need resolution quickly rather than diagnosis deeply.
Teaching both, and more importantly teaching people to distinguish which a given situation calls for, builds something more valuable than tool proficiency. It builds judgement.
What happens after the session
The design of follow-up is where most capability-building efforts fall short. A session that ends without structured application commitments and reinforcement mechanisms treats capability development as a single event rather than a process. Given what is known about how skills actually develop, this is almost guaranteed to produce shallow and temporary change.
Effective capability development after a session does not require complex systems. It requires two things: opportunities to apply the frameworks to real work promptly after the session, and a mechanism for reflection and sharing that reinforces learning over time. This could be as simple as a commitment from each participant to apply one tool to a current problem within two weeks, combined with a brief follow-up conversation about what they tried and what they found.
K. Anders Ericsson's research on expert performance establishes that capability develops through deliberate practice with feedback, not through exposure and experience alone. A single workshop provides exposure. The structured application that follows it builds capability. Organisations that invest in the session and neglect the follow-through rarely see the returns they were expecting.
Measuring capability development, not satisfaction
The standard metric for L&D programmes, post-session satisfaction scores, measures how people felt about the training, not whether it changed how they work. For capability development, the meaningful measures are behavioural: did participants apply the frameworks to real problems within the following weeks? Did they solve problems they had previously been stuck on? Did they approach new challenges differently?
These outcomes can be tracked informally through follow-up conversations, or formally through reassessment. The Edaith Systematic Problem-Solving Capability Profile can be used as a pre and post measure, establishing a capability baseline before development begins and measuring change after a defined period of practice. This produces evidence of actual capability improvement rather than evidence that training was delivered.
Getting started
Problem-solving capability is not built in a session. It is built through repeated application of systematic approaches to real problems, with reflection and reinforcement over time. A well-designed workshop creates the conditions for that development to begin. What sustains it is deliberate practice embedded in actual work.
The Problem Solver: The Systematic Problem-Solving Toolkit provides the evidence-based framework and 30 tools that support both workshop delivery and ongoing independent development. The Systematic Problem-Solving Capability Profile enables baseline assessment and progress tracking. Both are available at edaith.com. For team and organisational implementation, contact Edaith.