How to assess problem-solving skills

Most organisations cannot reliably assess problem-solving capability or identify where development investment will have the greatest impact. Here's why conventional approaches fall short and what a research-backed alternative measures.

Problem-solving capability is one of the most consequential skills a professional can develop and one of the least reliably measured. Organisations invest significantly in training and development, yet most lack the diagnostic tools to understand where capability actually stands or where development effort will create the greatest impact.

The gap is not one of intent. It's one of method.

 

Why most soft skills assessments fall short

Most approaches to assessing problem-solving fall into one of three categories, each with a fundamental limitation.

Personality-based tools categorise rather than diagnose. Knowing you have a tendency toward analytical thinking or a preference for structured approaches tells you something about who you are, but it doesn't inform what you can do, or where specific capability is lacking. These tools answer the wrong question for development purposes.

Generic skill ratings lack the granularity to be useful. A self-rating of three out of five on "problem-solving ability" provides no actionable direction. The issue could lie in how a problem is defined, how root causes are investigated, how solutions are designed, or how implementation is managed. Without specificity, development remains unfocused.

Most frameworks also treat problem solving as a single skill rather than a system. Rather than being a single capability, effective problem solving is a sequence of distinct competencies applied across multiple phases. Assessing creative thinking or analytical reasoning in isolation misses how these interact across a complete problem-solving cycle.

Development that is genuinely useful requires assessment that measures learnable capabilities, provides granular diagnosis, and reflects how expert problem solvers actually work.

 

The seven-phase problem-solving framework

Research on expert problem solvers across diverse professional contexts reveals a consistent pattern. A study of 52 expert scientists and engineers by Dillon and colleagues, published in CBE Life Sciences Education, found a remarkably consistent decision structure underlying professional problem solving across disciplines. One that maps to seven categories of decisions. Effective problem solving progresses through seven distinct phases, each requiring specific competencies that can be assessed and developed.

Define is the starting point. Establishing what problem is actually being solved, who is affected and holds influence, and what measurable success looks like. Research on expert-novice differences consistently shows that experts invest significantly more time defining a problem before acting; a pattern documented across disciplines. Common failures at this phase include solving symptoms rather than root causes and proceeding without clear success criteria.

Analyse follows. Understanding underlying causes, mapping system dynamics and interdependencies, and gathering information systematically from diverse sources. Superficial analysis produces superficial solutions. The most significant failures here involve accepting surface explanations and missing how changes in one area affect others.

Devise involves generating solution possibilities, drawing on approaches from other contexts, exploring options beyond the familiar, and designing solutions that address identified root causes rather than managing their symptoms.

Decide requires explicit evaluation criteria, systematic comparison of options, and the willingness to commit despite incomplete information. Both premature commitment and prolonged indecision are failure modes.

Implement is where many capable analysts falter. Effective implementation requires breaking solutions into executable steps, allocating resources strategically and managing resistance to change. A well-designed solution that is poorly implemented creates no value.

Improve closes the loop. Measuring whether the solution worked, extracting lessons, and refining the approach based on evidence rather than assumption.

Document ensures that individual learning becomes organisational knowledge. Insights that are not captured and shared are lost.

 

A granular capability profile produces specific, actionable diagnosis. Knowing your stakeholder analysis scores 3.4 out of 10 is more useful than knowing your problem-solving is average.

 

What effective problem-solving assessment measures

A robust problem-solving capability profile evaluates 17 distinct competencies across these seven phases. The specificity matters. Consider the difference between two possible assessment outcomes.

A generic result might indicate that problem-solving capability is average and recommend a general course. A granular capability profile identifies that root cause analysis is strong, creative ideation is above proficient, but stakeholder analysis and change management are priority development areas, and that the pattern reflects a common combination of analytical strength and implementation difficulty when multiple stakeholders are involved.

The second result enables targeted development. It points to specific capability building, not general training.

At team level, aggregated capability profiles reveal something that individual results cannot: collective patterns. A team where everyone is strong at analysis but weak at implementation will fail differently from a team with the opposite profile. Understanding these dynamics enables more effective work allocation, more targeted development programmes, and a common language for problem-solving practice across the group.

 

Assessing your own problem-solving capability

Before seeking a formal profile, recent projects offer a useful diagnostic. The questions worth asking follow the seven phases: Did you clearly articulate the problem before acting, or did you move to solutions before the problem was properly defined? Did you investigate root causes, or address what was most visible? Did you generate multiple options, or default to the first plausible approach?

At the implementation end: Did you create a detailed action plan with clear ownership, or was execution left loosely defined? Did you measure whether the solution actually worked? Did you capture what you learned in a form others could use?

Patterns across these questions tend to reveal more than any single answer. Consistently skipping certain phases, or finding that specific competencies feel effortful or unfamiliar, identifies where focused development will create the greatest improvement. A professional capability profile makes that diagnosis precise.

 

Introducing the Systematic Problem-Solving Capability Profile

The Systematic Problem-Solving Capability Profile evaluates all 17 competencies across the complete seven-phase cycle. It takes approximately 15 minutes to complete. The resulting report includes an overall capability summary, a phase-by-phase profile showing strengths and development priorities, identification of problem-solving style from seven distinct patterns, and personalised development guidance calibrated to current proficiency level.

Unlike personality assessments, this measures capabilities that are learnable and developable. Unlike generic skill surveys, it provides the granularity required for targeted development. Unlike theoretical frameworks, it translates research into specific actions.

The gap between assessment and action should be minimal. Development recommendations are specific enough to implement without additional interpretation.

 

Using your profile results for professional development

A profile without action creates awareness without improvement. A few principles apply consistently across proficiency levels and development contexts.

Focus on three to five competencies, not 17 simultaneously. Distributed attention distributes results. The profile identifies priority areas; these are the starting point.

Match development activities to current proficiency level. Foundation-level capability requires structured practice in lower-stakes situations. Proficient-level capability develops through more complex problems and, increasingly, through the act of making tacit knowledge explicit for others.

Systematically practise, rather than hoping that experience alone produces improvement. Capability develops through repeated application with reflection.

Reassess after three to six months of focused effort. This validates progress, maintains direction, and determines whether development priorities should shift.

 

Team problem-solving capability development

For teams, profiling enables a more deliberate approach to capability development than generic training permits. Mapping collective capability across the seven phases identifies where the whole team is strong, where development is needed, and where complementary strengths can be leveraged. When team members share a common framework, collaboration on complex problems becomes more effective. Roles in a problem-solving process can be allocated deliberately rather than by default.

Baseline profiling followed by reassessment after a development initiative also provides something organisations rarely have: evidence that capability actually changed, rather than that training was delivered.

 

Getting started

Problem-solving capability is not innate. Capability develops through structured, deliberate practice. The question is whether development happens deliberately, with accurate diagnosis and targeted effort, or by exposure alone, which is slower, less reliable, and harder to scale.

The Systematic Problem-Solving Capability Profile is available for individuals via edaith.com. For teams, volume pricing applies to purchases of five or more profiles; aggregated team reports are available for purchases of ten or more. Contact Edaith to discuss team or organisational implementation.