# What is problem solving
Executive summary
Problem solving is the disciplined process of recognizing a consequential gap between a current and desired state, defining its boundaries, developing and testing explanations, choosing and implementing an intervention, and learning from observed results. A managerial problem is therefore not merely an inconvenience; it is a decision under uncertainty within a social and operational system. Problem solving is not the production of answers but a governed learning cycle that converts an undesirable gap into a well-framed decision, tests competing explanations, intervenes proportionately, and verifies both improvement and unintended effects. The managerial task is to turn the concept into an evidence system: clarify the decision, expose assumptions, observe outcomes, compare alternatives, and revise action when results disagree. This chapter treats the method as a disciplined operating capability rather than a workshop artifact. It integrates theory, implementation, measurement, failure analysis, ethics, and a field exercise so a reader can use the model while respecting its limits.[s1][s2][s3][s4][s5][s6]
Learning objectives
By the end of this lesson, you will be able to:
- Diagnose when problem solving can materially improve a business decision.
- Design a defensible evidence and implementation process rather than a presentation-only exercise.
- Select leading, lagging, economic, and quality measures that reveal whether the intervention works.
- Identify analytical, organizational, and ethical failure modes before they cause stakeholder harm.
- Translate an insight into a time-bounded test with ownership, thresholds, and a learning loop.
Foundations: what the concept means
Problem solving is the disciplined process of recognizing a consequential gap between a current and desired state, defining its boundaries, developing and testing explanations, choosing and implementing an intervention, and learning from observed results. A managerial problem is therefore not merely an inconvenience; it is a decision under uncertainty within a social and operational system.
Foundation 1
Herbert Simon described decision activity through intelligence, design, and choice, while later work emphasizes implementation and feedback. This lineage matters because “solve” cannot mean selecting an idea alone: the organization must notice the right signals, construct alternatives, make a choice under constraints, and discover whether reality responds as expected. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 2
Problems differ in structure. A well-structured problem has relatively agreed goals, rules, and success criteria; an ill-structured or wicked problem contains disputed values, changing boundaries, interacting causes, and no final proof of correctness. Methods must match that structure rather than applying a root-cause template to every human system. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 3
A problem statement is a provisional model. It selects a unit of analysis, time horizon, stakeholder, consequence, and comparison. Because that selection directs attention and resources, framing is not neutral; strong teams make alternative frames visible before treating the initial wording as fact. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
Foundation 4
Expert problem solving depends on representations, domain knowledge, search strategies, and feedback, not a general-purpose cleverness detached from context. Yet expertise can also produce fixation. Cross-functional knowledge and disciplined challenge help teams use experience without becoming captive to familiar patterns. The practical implication is to record the claim at the level the evidence supports. Managers should ask what would look different if this explanation were false, whose perspective is missing, and whether an apparently stable pattern may be produced by context, selection, or measurement.
The literature provides complementary rather than interchangeable lenses.[s1][s2][s3][s4][s5][s6] A rigorous practitioner uses those lenses to sharpen observation and decision quality, not to borrow academic authority for a conclusion already chosen. Definitions, samples, methods, and boundary conditions should travel with every important claim.
A decision-ready operating framework
A useful framework must specify inputs, transformation, outputs, ownership, and feedback. The following five-stage system creates that chain while leaving room for the method to be adapted to category, organization, and evidence quality.
1. Signal the consequential gap
Translate complaints into an observable difference between current and desired conditions. Establish materiality, urgency, affected stakeholders, and what happens if no action is taken. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Frame boundaries and success
Specify where, when, for whom, and at what level the issue occurs; define constraints and success criteria; and write at least one alternative frame that would direct attention elsewhere. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Explain with competing models
Use process evidence, variation, stakeholder knowledge, and relevant theory to form multiple explanations. State what each explanation predicts and what observation would weaken it. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Choose a proportional test
Generate options that address the suspected mechanism, compare value, feasibility, risk, reversibility, and information gained, then authorize the smallest safe intervention capable of teaching. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Verify, adapt, and retain learning
Measure mechanism and outcome against baseline and comparison, inspect side effects and recurrence, decide whether to scale or reframe, and preserve the reasoning for future teams. This stage should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
This animated problem-solving learning cycle shows five linked stages move from consequential signal through framing, explanation, proportional intervention, and verified learning, showing that evidence can return the team to an earlier stage. The sequence remains fully understandable when motion is disabled.
The stages are iterative. New evidence may change the original question, expose a missing stakeholder, or show that an apparently attractive option is infeasible. Governance should allow the team to return to an earlier stage without describing learning as failure.
Worked example: Nivara Kitchens, a composite multi-city meal-delivery operator
Situation
Late deliveries rose from 8 percent to 17 percent in six weeks. Leaders initially framed the problem as rider indiscipline and proposed penalties, although delays varied sharply by kitchen, hour, order mix, and dispatch queue. The case is hypothetical and composite; it illustrates a reasoning process rather than reporting facts about any real organization. Management agreed to separate observations, interpretations, choices, and measured outcomes so hindsight could not erase uncertainty.
Case movement 1
The team rewrote the issue as a measured gap: promised-to-door time exceeded forty minutes for 17 percent of evening orders, concentrated in three kitchens, causing refunds, rider overtime, and customer uncertainty. That wording removed an untested cause from the statement. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 2
Event timestamps and observation revealed two rival mechanisms. The operations group suspected rider acceptance; kitchen teams pointed to batch releases that created synchronized queues. Missing timestamps had previously collapsed cooking wait and transport time into one number. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 3
A one-week shadow measurement separated order ready time, dispatch offer, acceptance, pickup, and travel. Long delays appeared before riders received offers; acceptance time was stable. A second pattern linked menu complexity with release bunching during promotion windows. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 4
Nivara tested staggered promotion slots and a kitchen work-in-process limit in two comparable locations while retaining existing policy elsewhere. It protected earnings, published the test rules, and monitored cancellations, food quality, rider idle time, and staff workload. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Case movement 5
Late delivery fell to 10 percent in the test kitchens without worsening quality or earnings. The team scaled gradually, kept an exception channel, and documented why a punitive intervention had been rejected: it targeted a visible actor rather than the queue-producing mechanism. At this point the team recorded what it knew, what it inferred, and what it still needed to test. That discipline prevented a single persuasive voice from converting an assumption into institutional memory.
Interpretation
The case matters because action followed the diagnosed mechanism, not the fashionable label. It also preserved a comparison and a boundary statement. A result in one setting changed the next decision; it did not become a universal law.
90-Day Action Plan
Implementation needs an executive sponsor, a working owner, protected access to evidence, and explicit decision dates. The plan below can be compressed for a small reversible choice or expanded for a regulated, capital-intensive, or high-harm decision.
1. Days 1–15: establish the decision charter
Name the decision, sponsor, working owner, affected stakeholders, current state, desired outcome, constraints, evidence sources, and the date on which action is required. Record what is assumed rather than observed. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Days 16–30: build the evidence baseline
Triangulate process data, direct observation, documents, and stakeholder accounts. Define units and denominators, examine variation and exceptions, and document missing or unreliable evidence before proposing causes. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Days 31–50: create and challenge explanations
Develop multiple causal or systemic accounts, identify the prediction each makes, search for disconfirming cases, and involve people close to the work. Select tests by information value as well as cost and speed. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Days 51–70: run a bounded intervention
Choose a reversible option, specify owner, resources, safeguards, comparison, leading indicators, counter-metrics, stop rules, and escalation thresholds. Preserve the old process where rollback may be necessary. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Days 71–90: decide and institutionalize learning
Compare results with the baseline and rival explanation, review stakeholder effects, decide whether to scale, adapt, stop, or reframe, and archive a decision record that distinguishes evidence from interpretation. This implementation commitment should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The plan should connect with Organizing information and ideas into common themes, The problem definition process, Improving solutions by arguing for and against your options, 8D problem solving process, Root Cause Analysis and the Strategy learning hub. These links are complementary tools, not substitutes for the evidence required by this decision. At day ninety, write a one-page decision record covering the original premise, evidence obtained, decision taken, result, unresolved risk, and next review.
Measurement and review
Measurement should serve learning and accountability. Establish a baseline, define the unit and denominator, segment outcomes where averages can conceal harm, and choose a review interval that matches how quickly the underlying mechanism can change.
1. Problem-definition stability
Track how often the stated problem changes after evidence review and whether revisions clarify mechanism, boundary, stakeholder, and desired outcome rather than merely changing language. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Evidence quality
Rate coverage, provenance, recency, reliability, missingness, triangulation, and the number of serious rival explanations that have been tested rather than dismissed. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Decision-cycle performance
Measure elapsed time from signal to framed decision, time spent waiting for information or authority, experiment cost, rework, and the proportion of decisions revisited on schedule. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Outcome and mechanism
Measure the operational result and the nearer mechanism expected to produce it. Report baseline, denominator, variation, comparison, confidence, and whether the effect persisted beyond the test. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Stakeholder and resilience counter-metrics
Monitor safety, workload, fairness, privacy, accessibility, customer harm, supplier burden, reversibility, unintended consequences, and recurrence after apparent resolution. This measure should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
The evidence chain separates a measured gap, chosen boundary, causal explanation, intervention, and observed effect so a plausible story cannot quietly become proof.
Avoid a dashboard in which every number rises when activity rises. Include outcome, quality, economic, and counter-metrics. Predefine a threshold that triggers investigation or stopping, and retain qualitative evidence that explains why the number moved.
Failure modes and corrective action
The most dangerous errors are often organizational rather than technical: incentives reward certainty, a senior sponsor prefers one explanation, or presentation deadlines arrive before evidence. Treat the following patterns as control failures with observable warning signs.
1. Solving the presented symptom
Urgency makes the first description feel authoritative. The warning sign is a solution embedded in the problem statement; correct it by separating observation, consequence, suspected mechanism, and proposed response. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
2. Single-story certainty
A coherent explanation crowds out alternatives. Watch for evidence collected only to confirm one cause; require rival hypotheses, disconfirming evidence, and an explicit confidence level. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
3. Workshop without decision rights
Teams generate maps and ideas but no authorized owner can alter the system. Define authority, resources, decision dates, escalation routes, and the artifact that commits action before convening. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
4. Activity mistaken for outcome
Meetings, ideas, tickets, and training completions rise while the underlying failure persists. Pair activity indicators with mechanism, outcome, recurrence, and harm measures. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
5. Premature standardization
A promising local result is converted into a universal procedure. Test transfer conditions, preserve local feedback, stage the rollout, and specify circumstances that require adaptation or rollback. This failure mode should be documented as a falsifiable managerial proposition: name the evidence supporting it, the person accountable for acting, the constraint that could make it fail, and the observable result that would justify continuation. Teams should compare the proposition with at least one plausible alternative instead of treating a coherent story as proof.
Run a pre-mortem before launch and an after-action review after the first decision cycle. Record near misses, not only visible failures. A healthy team can say that an attractive hypothesis was not supported and redirect resources without reputational punishment.
Ethics, limits, and responsible use
Business usefulness does not excuse deception, avoidable harm, or unsupported inference. The method should be proportionate to the decision and reviewed more carefully when it affects employment, credit, health, safety, privacy, or access to essential services.
Responsibility 1
A problem-solving process must not turn uncertainty into a pretext for surveillance, retaliation, or blame. Protect confidential reporting, separate learning from discipline, and give people affected by a decision a safe route to challenge the evidence and proposed remedy. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 2
Analytical elegance does not justify shifting costs onto workers, customers, suppliers, or communities with less power. Map who receives the benefit, who bears risk, whose knowledge is excluded, and what accessible remedy exists when the intervention causes harm. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 3
Collect only data proportionate to the decision, document purpose and retention, restrict access, and test whether proxies reproduce structural disadvantage. When employment, health, safety, credit, or legal rights are involved, obtain qualified review and preserve due process. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Responsibility 4
Models simplify reality and therefore create blind spots. State assumptions, uncertainty, scope, and reversibility; distinguish a test from a settled conclusion; and stop when evidence of harm, invalid measurement, or an unrepresented stakeholder makes the original design unsafe. Document the affected stakeholder, foreseeable harm, mitigation, escalation owner, and evidence that the protection works. Legal compliance is a floor; an action can be lawful yet inconsistent with informed choice, dignity, or the organization’s stated values.
Limits should be written into the decision record: population, context, time, method, uncertainty, and the conditions under which the conclusion should be revisited. Do not imply individualized legal, medical, financial, or employment advice.
Practice Checklist and Laboratory
Implementation Checklist
- [ ] The audience, decision, accountable owner, and intended value are explicit.
- [ ] Material claims have traceable evidence, sources, limits, and correction ownership.
- [ ] The plan includes a baseline, comparison, primary outcome, cost, and stakeholder counter-metric.
- [ ] Consent, privacy, accessibility, safety, legal, and platform obligations have been reviewed.
- [ ] Stop, escalation, remedy, and after-action review rules are documented before launch.
Complete the exercises with a live but reversible decision. Preserve artifacts so another reviewer can inspect how you moved from evidence to recommendation.
Exercise 1
Take one current operational complaint and write four separate statements: observed condition, consequence, plausible mechanism, and proposed solution. Ask a colleague to mark every word that assumes a cause not yet demonstrated. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 2
Construct an evidence ledger for the decision with columns for claim, source, method, date, scope, reliability, disconfirming observation, and responsible reviewer. Remove any claim that cannot support the decision being asked of it. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 3
Design the smallest safe test that distinguishes the two most credible explanations. Specify comparison, duration, sample or cases, expected signal, counter-metric, stop rule, owner, and what each possible result would mean. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Exercise 4
Facilitate a thirty-minute red-team review with someone affected by the proposed change. Record the strongest objection, hidden cost, missing stakeholder, and condition under which the intervention should not proceed. Produce a one-page artifact, exchange it with a colleague, and ask the reviewer to identify an unsupported leap, missing stakeholder, and alternative explanation. Revise the artifact and record what changed.
Finish with a decision memo: “We believed… We observed… We now infer… We will test… We will stop or revise if…” This format makes uncertainty actionable and creates an organizational memory stronger than a polished retrospective.
Key takeaways
- A problem is a consequential gap requiring a decision under uncertainty, not a solution disguised as a complaint. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Problem framing selects boundaries, stakeholders, measures, and possible causes, so it must remain contestable. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Different problem structures require different methods and standards of evidence. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Competing explanations reduce fixation and make tests more informative. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Implementation is part of problem solving because an untested recommendation has not solved anything. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Verification must include recurrence and stakeholder counter-metrics, not only the intended operational result. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
Mastery means choosing the method for the decision it can improve, using evidence at the level it supports, and changing course when the world contradicts the model.
References and further reading
The sources below establish the conceptual and methodological foundation. Publication details and locators have been retained so editors can verify every material attribution before publication.
[s1] Herbert A. Simon. “The Sciences of the Artificial, Third Edition.” 1996. https://mitpress.mit.edu/9780262691918/the-sciences-of-the-artificial/
[s2] Allen Newell and Herbert A. Simon. “Human Problem Solving.” 1972. https://www.pearson.com/en-us/subject-catalog/p/human-problem-solving/P200000003385
[s3] Dietrich Dörner. “The Logic of Failure: Recognizing and Avoiding Error in Complex Situations.” 1996. https://books.google.com/books?id=4UwA4A5sDDoC
[s4] Horst W. J. Rittel and Melvin M. Webber. “Dilemmas in a General Theory of Planning.” 1973. https://doi.org/10.1007/BF01405730
[s5] Daniel Kahneman. “Thinking, Fast and Slow.” 2011. https://us.macmillan.com/books/9780374533557/thinkingfastandslow/
[s6] Ken Watanabe. “Problem Solving 101: A Simple Book for Smart People.” 2009. https://www.penguinrandomhouse.com/books/185450/problem-solving-101-by-ken-watanabe/
