# Creative Problem Solving
Executive summary
Creative Problem Solving (CPS) is a deliberate process for constructing novel and useful responses to open-ended challenges. Contemporary CPS formulations commonly organize work into Clarify, Ideate, Develop, and Implement, with substeps that explore vision, gather data, formulate challenges, explore ideas, formulate solutions, and formulate plans. Divergence expands possibilities and convergence selects promising directions; both occur throughout the process. Creative problem solving is disciplined alternation between divergent and convergent thinking across clarification, ideation, development, and implementation; novelty becomes useful only when teams challenge fixation, protect cognitive and social range, apply evidence-based criteria, test assumptions, and build ownership for action. 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 creative 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
Creative Problem Solving (CPS) is a deliberate process for constructing novel and useful responses to open-ended challenges. Contemporary CPS formulations commonly organize work into Clarify, Ideate, Develop, and Implement, with substeps that explore vision, gather data, formulate challenges, explore ideas, formulate solutions, and formulate plans. Divergence expands possibilities and convergence selects promising directions; both occur throughout the process.
Foundation 1
Creativity requires novelty and usefulness relative to a context. An unusual idea that cannot serve the goal is not sufficient, while an efficient familiar answer may be improvement without meaningful creativity. Evaluation therefore depends on stakeholders, constraints, time, and evidence. 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
Problem representations shape the solution space. Reframing from “make people comply” to “reduce the effort and uncertainty required for safe completion,” for example, changes mechanisms, ethics, and measures before a single idea is generated. 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
Fixation can arise from examples, expertise, sunk costs, hierarchy, functional boundaries, and the first plausible option. Independent generation, analogies, counterfactuals, constraint changes, and delayed exposure to dominant examples can expand search. 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
Group creativity is social. Psychological safety helps people offer incomplete or dissenting ideas, but safety alone does not guarantee useful output. Diversity of relevant knowledge, equitable airtime, skilled facilitation, task conflict, and clear convergence rules matter. 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. Clarify
Explore the desired future, collect stakeholder and system data, formulate multiple challenge questions, and select a frame with a consequential owner. Keep facts, interpretations, constraints, and aspirations distinguishable. 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. Ideate
Create psychological permission and procedural separation from evaluation. Generate independently, then build collectively using combinations, analogies, reversals, attribute changes, and different stakeholder or time perspectives. Seek variety across mechanisms. 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. Develop
Construct criteria before attachment hardens, screen transparently, strengthen promising ideas, expose assumptions, model economics and operations, prototype risky elements, and combine options when their strengths are complementary. 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. Implement
Identify assistance and resistance, co-design with affected operators and users, assign owners and resources, sequence experiments, communicate evidence and uncertainty, establish safeguards, and turn the concept into observable behavior. 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. Learn and renew
Measure primary value and counter-effects, compare with baseline, invite disconfirming feedback, preserve abandoned concepts and reasons, and reopen clarification when implementation reveals that the original problem was incomplete. 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 creative problem-solving learning arc shows an animated five-stage arc connects clarify, ideate, develop, implement, and learn while divergence and convergence alternate. 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 university redesigning evening student support
Situation
Leaders believed low attendance at advising appointments reflected poor motivation and asked for creative marketing ideas. Working students described schedules, transport, caregiving, language, and fear of exposing academic difficulty. 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
Clarification reframed the challenge from increasing appointment bookings to enabling timely, dignified access to decisions students could act on. Journey evidence and no-show patterns were segmented rather than moralized. 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
Ideation used independent brainwriting, analogies to urgent-care triage, reversals, student-led prompts, and constraint removal. Options included asynchronous case preparation, rotating evening hours, peer navigation, one-stop triage, translated decision guides, and continuity across advisers. 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
Development criteria covered educational usefulness, privacy, accessibility, staffing, response time, adviser cognitive load, equity, cost, and failure recovery. Students and advisers tested low-fidelity service blueprints before software work. 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
A pilot combined asynchronous intake, a rapid triage promise, selectable channel, translated guides, and case ownership. The university compared response, resolution, repeat contact, student confidence, staff load, and persistence with similar programs. 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
The result improved access but exposed a policy bottleneck outside advising. The team reopened clarification and changed the escalation rule, illustrating that CPS is adaptive inquiry rather than a four-box performance. 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 creative problem solving 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, Improving solutions by arguing for and against your options, The problem definition process, A Robust and Creative Problem-Solving Tool, The Four-Step Innovation Process, 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. Frame quality
Stakeholder relevance, evidence, level of abstraction, decision ownership, opportunity breadth, and explicit boundary conditions. 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. Divergent range
Distinct mechanisms, perspectives, analogies, combinations, and assumptions challenged—not the count of minor variations. 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 quality
Prior criteria, independent judgment, evidence traceability, minority concerns, conflicts, and robustness under sensitivity checks. 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. Learning velocity
Time and cost to test the riskiest assumption, evidence gained, and degree to which the option or frame changed. 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. Responsible value
Outcome, usability, quality, safety, accessibility, equity, workload, economics, adoption, and unintended effects over time. 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 expansion and selection recurring at every CPS stage, countering the common mistake of treating creativity as one unstructured idea session.
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. Brainstorm-only CPS
Generation is mistaken for the whole process. Allocate equal rigor to clarification, development, 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.
2. Premature evaluation
Ideas are judged while fragile. Separate phases and capture concerns for later criteria. 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. Quantity fetish
Near-duplicate ideas inflate output. Measure mechanism range and testability. 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. Facilitator capture
Prompts and clustering steer the answer. Make influence visible and preserve raw contributions. 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. Novelty bias
Unusual concepts receive preference despite weak value or safety. Require usefulness and evidence. 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
Creative freedom does not authorize deceptive, discriminatory, unsafe, exploitative, or inaccessible solutions. 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
Participants need clear expectations about attribution, intellectual property, confidentiality, and how ideas will influence employment decisions. 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
Inclusive facilitation should provide accessible formats, asynchronous contribution, language support, and protection from status retaliation. 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
Teams should examine who gains novelty, who bears experimentation risk, whose work increases, and what remedy exists when a pilot harms. 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 creative problem solving 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
- Creativity joins novelty with contextual usefulness. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Clarification determines the space in which ideas can exist. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Separate divergence and convergence repeatedly. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Design group process against fixation and hierarchy. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Prototype assumptions before scaling commitment. For each proposition, preserve the evidence, boundary, accountable owner, and next review point.
- Judge success through responsible realized value. 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] Donald J. Treffinger, Scott G. Isaksen, and K. Brian Dorval. “Creative Problem Solving: An Introduction, Fourth Edition.” 2006. https://search.worldcat.org/title/62282370
[s2] Gerard J. Puccio, Marie Mance, and Mary C. Murdock. “Creative Leadership: Skills That Drive Change, Second Edition.” 2011. https://us.sagepub.com/en-us/nam/creative-leadership/book232607
[s3] Alex F. Osborn. “Applied Imagination, Third Revised Edition.” 1963. https://search.worldcat.org/title/181998
[s4] 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
[s5] Jennifer S. Mueller, Shimul Melwani, and Jack A. Goncalo. “The Bias Against Creativity.” 2012. https://doi.org/10.1177/0956797611421018
[s6] Michael Diehl and Wolfgang Stroebe. “Does Group Participation When Using Brainstorming Facilitate or Inhibit Creative Thinking?.” 1987. https://doi.org/10.1037/0022-3514.53.3.497
