# A Robust and Creative Problem-Solving Tool
Executive summary
The Simplex process is an iterative creative problem-solving method associated with Min Basadur. Its eight stages are problem finding, fact finding, problem definition, idea finding, evaluation and selection, action planning, gaining acceptance, and taking action. Each stage separates divergence—expanding observations, frames, or options—from convergence—selecting promising material with explicit criteria. Action generates new facts, so the sequence is a cycle rather than a one-pass funnel. Basadur’s Simplex process is robust because it treats problem finding, fact finding, definition, ideation, evaluation, implementation, acceptance, and action as an iterative system; it is creative because it deliberately alternates divergence and convergence, not because a workshop produces a large number of ideas. 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 Simplex problem solving process 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
The Simplex process is an iterative creative problem-solving method associated with Min Basadur. Its eight stages are problem finding, fact finding, problem definition, idea finding, evaluation and selection, action planning, gaining acceptance, and taking action. Each stage separates divergence—expanding observations, frames, or options—from convergence—selecting promising material with explicit criteria. Action generates new facts, so the sequence is a cycle rather than a one-pass funnel.
Foundation 1
Problem finding precedes solution making. Organizations often react to visible failures while missing emerging opportunities or recurring frictions normalized as “how work is.” Deliberate sensing turns vague dissatisfaction into an investigable challenge. 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
Divergence and convergence are different cognitive and social operations. Generating while judging favors familiar, politically safe ideas; judging without criteria favors status. Separation protects range, while convergence restores discipline and commitment. 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
Fact finding includes qualitative experience, process evidence, operational data, history, constraints, and stakeholder differences. Facts are not neutral inventory: teams must mark provenance, uncertainty, absence, and interpretation. 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
Acceptance is part of solution quality. An option that is technically elegant but misunderstood, unfair, impossible to operate, or outside authority is not implementation-ready. Involvement can improve knowledge and legitimacy, but it must not manufacture consent. 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. Find problems and opportunities
Scan customer friction, defects, delays, workarounds, near misses, strategic change, and weak signals. Diverge on possible challenges, then converge on a consequential area with sponsorship and a real decision path. 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. Find facts and define the challenge
Gather contrasting evidence, stakeholders, history, boundaries, and prior attempts. Draft multiple “How might we?” formulations at different levels; choose one broad enough for alternatives and specific enough for action. 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. Find ideas
Generate individually before group sharing, use stimulus and combination techniques, suspend evaluation temporarily, and seek mechanisms—not just slogans. Cluster without deleting minority ideas or attaching status to authorship. 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. Evaluate and plan
Create criteria from stakeholder value, strategy, evidence, safety, feasibility, reversibility, cost, time, and learning. Strengthen options, test assumptions, combine complementary elements, and turn the choice into owners, dependencies, milestones, and experiments. 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. Gain acceptance, act, and recycle
Map affected people and veto points, invite genuine challenge, adapt communication and support, pilot, measure outcomes and side effects, and feed what happens back into fact and problem finding. 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 simplex creative problem-solving cycle shows an animated five-part cycle compresses problem finding, facts and framing, idea finding, evaluation and planning, and acceptance with action. 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: A composite municipal permit-service redesign
Situation
A city team began with the solution “build a faster application portal,” although small contractors reported abandonment, repeat visits, contradictory guidance, and fear of penalties. 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
Problem finding broadened the field from page speed to avoidable rework and unequal access. Fact finding combined journey observation, call logs, processing timestamps, forms, language access, and interviews with applicants and reviewers. 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
Multiple formulations revealed different levers: reduce uncertainty before submission, make reviewer interpretation consistent, and preserve assisted routes. The team chose a portfolio question rather than a portal-only brief. 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
Separate ideation produced document previews, rule examples, pre-submission checks, reviewer calibration, case continuity, multilingual assistance, and a plain-language exception route. Options were clustered by prevention, detection, and recovery. 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
Evaluation included processing time, first-pass completeness, legal accuracy, accessibility, staff load, privacy, cost, and exclusion risk. A digital-only option scored poorly despite apparent speed. 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
A district pilot combined simpler evidence prompts, assisted submission, reviewer calibration, and status explanations. Action data exposed a new fact—one policy ambiguity drove much rework—so the team escalated policy clarification rather than endlessly optimizing interface copy. 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–12: charter the problem
Name the affected stakeholder, operational gap, decision owner, baseline, boundary, risk class, and evidence that would disconfirm the preferred Simplex problem solving process explanation. Separate symptom containment from causal correction. 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 13–28: build the evidence record
Observe the work where it occurs, map the process and timeline, interview contrasting participants, preserve artifacts, quantify frequency and impact, and log assumptions. Protect people from blame while refusing to sanitize inconvenient evidence. 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 29–45: diverge and challenge
Generate alternatives before selecting, include process and system changes rather than retraining alone, surface trade-offs, run a pre-mortem, and invite an independent reviewer to test the frame, evidence, and neglected stakeholders. 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 46–70: test safely
Pilot the strongest option at the smallest scale that can expose its mechanism. Predefine primary outcome, quality, cost, safety, equity, adoption, recurrence, and stop thresholds; preserve a comparison where feasible. 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: verify and standardize
Confirm that the effect persists under ordinary conditions, audit transfer to adjacent risks, update standards and training, assign control ownership, close the loop with affected people, and schedule a recurrence review. 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 What is problem solving, The problem definition process, The Four-Step Innovation Process, Creative Problem Solving, Cause and Effect Analysis, Interrelationship Diagrams 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 portfolio value
Magnitude, frequency, strategic importance, stakeholder harm, controllability, and evidence confidence of selected challenges. 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. Divergence quality
Distinct frames or mechanisms, source diversity, independent contributions, and presence of non-obvious or minority options—not raw idea count alone. 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. Convergence integrity
Criteria defined before scoring, conflicts disclosed, assumptions tested, and reasons for selection traceable. 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. Acceptance readiness
Affected groups heard, unresolved objections, decision authority, implementation capability, accessibility, and support commitments. 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. Outcome and learning
Primary result, quality, cost, adoption, equity, unintended effects, new facts, and changes to the next problem definition. 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 second infographic shows divergence and convergence as a repeated pulse across the whole Simplex cycle, preventing creativity from being confined to a single brainstorm.
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. Solution-led brief
The desired answer is embedded in the challenge. Generate frames at multiple causal levels. 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. Brainstorming theater
Idea volume substitutes for evidence and action. Track mechanisms, tests, and implementation. 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. Voting by status
Senior preference becomes convergence. Use prior criteria and independent scoring. 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. Acceptance as selling
Stakeholders are persuaded after decisions. Involve them where their knowledge and rights matter. 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. Linear ritual
Stages become gates immune to new facts. Loop backward explicitly when evidence changes. 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
Problem finding can expose vulnerable individuals and informal workarounds; protect identity and understand why adaptation exists before removing it. 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
Facilitation must prevent hierarchy, language, disability, remote participation, and schedule from determining whose ideas become visible. 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
Gaining acceptance is not permission to manipulate or suppress legitimate dissent. 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
Implementation must distribute benefits, risks, workload, and remedies transparently across affected groups. 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
Audit one recent Simplex problem solving process effort. Separate the triggering event, verified observations, assumptions, causal claims, decision criteria, chosen action, and evidence of sustained effect. 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
Rewrite the problem from the viewpoint of a frontline worker, customer, operator, regulator, and downstream team. Identify which boundary or success criterion changes under each view. 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
Generate three structurally different options, including prevention, detection, and recovery. Run a pre-mortem and specify a reversible test that could eliminate each option. 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
Complete the implementation checklist, assign owners and dates, and draft the one-page verification record that will be reviewed thirty and ninety days after launch. 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
- Start with problem finding, not a favored solution. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Separate divergence from convergence at every stage. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Treat evidence and framing as creative work. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Evaluate with criteria and testable assumptions. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Design acceptance through involvement and fairness. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Use action results to reopen the cycle. 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] Min Basadur. “The Economic Power of Creativity.” 1995. https://search.worldcat.org/title/32350191
[s2] Min Basadur. “Simplex: A Flight to Creativity.” 1994. https://search.worldcat.org/title/29389395
[s3] Min Basadur, George Graen, and Stephen Green. “A New Methodology for Formulating Ill-Structured Problems.” 1982. https://doi.org/10.1016/0024-6301(82)90053-6
[s4] Scott G. Isaksen and K. Brian Dorval. “Creative Problem Solving: The Basic Course.” 1993. https://search.worldcat.org/title/29877326
[s5] Sam Kaner et al.. “Facilitator’s Guide to Participatory Decision-Making, Third Edition.” 2014. https://www.wiley.com/en-us/Facilitator%27s+Guide+to+Participatory+Decision-Making%2C+3rd+Edition-p-9781118404959
[s6] Jennifer S. Mueller, Shimul Melwani, and Jack A. Goncalo. “The Bias Against Creativity.” 2012. https://doi.org/10.1177/0956797611421018
