Unit 3: Ideation and Creative Problem Solving

I. Foundations of Ideation

Ideation is the design-thinking stage in which insights about users and a clearly defined problem are transformed into possible solutions. It depends on separating imaginative exploration from critical evaluation: teams first expand the solution space, then narrow it using evidence and constraints.

• Governing principle: Generate widely before selecting carefully; premature judgment restricts novelty, while endless generation prevents action.
• Human-centred focus: Ideas should respond to user needs identified through empathy research, observations, interviews, personas, or journey maps.
• Problem framing: A focused statement such as “How might we reduce waiting anxiety for clinic patients?” provides direction without prescribing a solution.
• Quantity and variety: A productive ideation session seeks numerous ideas across different categories, not minor variations of one familiar answer.
• Deferred judgment: Feasibility criticism is temporarily suspended during generation and deliberately restored during evaluation.
• Iteration: Ideas are provisional hypotheses that may be combined, prototyped, tested, rejected, or refined.
• Collaboration: Diverse participants contribute different disciplinary knowledge, experiences, and interpretations of the problem.
• Traceability: Selection criteria should connect chosen ideas to user evidence, project goals, resources, and measurable outcomes.

II. Divergent Thinking and Idea Generation — Expanding the Solution Space

A. Divergent Thinking and Idea Generation

Divergent thinking is the deliberate production of many varied responses to an open-ended problem.

• Fluency: Produce a large number of possibilities; a team might generate 40 ways to improve a clinic visit before discussing quality.
• Flexibility: Shift between categories such as digital communication, physical layout, staffing, scheduling, and emotional support.
• Originality: Seek uncommon but relevant ideas, such as replacing an uncertain queue with a patient-controlled arrival window.
• Elaboration: Develop a rough suggestion into a clearer concept with users, actions, context, and expected value.
• Provocation: Use prompts such as “What if waiting rooms did not exist?” to challenge assumptions and expose alternatives.
• Deferred evaluation: Record impractical ideas because they may contain useful principles that can be adapted later.
• Output: Express each idea as a concise statement or sketch so that it remains visible, distinct, and discussable.

B. Applications and Limitations

Divergence is most useful when the problem is understood but the appropriate response remains uncertain.

• Applications: It supports product concepts, service improvements, communication strategies, process redesign, and contingency planning.
• Limitation: Unstructured divergence can produce repetition, irrelevant suggestions, or idea overload.
• Control: Time-boxing, focused prompts, and category changes preserve creativity while preventing aimless discussion.

III. Convergent and Divergent Thinking — Alternating Expansion and Reduction

A. Convergent and Divergent Thinking

Creative problem solving alternates between divergent exploration and convergent decision-making rather than treating them as competing approaches.

1. Divergent thinking: Expands possibilities by suspending judgment, encouraging unusual associations, and asking “What else could work?”
2. Convergent thinking: Reduces possibilities by comparing evidence, constraints, risks, benefits, and strategic fit.

• Explicit contrast: Divergence values quantity, variety, and novelty; convergence values relevance, coherence, and justified choice.
• Double-diamond pattern: Teams commonly diverge and converge while understanding the problem, then repeat the cycle while developing solutions.
• Transition rule: Evaluation begins only after sufficient variety exists; otherwise the first acceptable idea may be mistaken for the best.
• Iterative movement: Testing may reveal a weakness, causing the team to diverge again around a narrower issue.

B. Significance

The disciplined alternation of these modes balances imagination with practical decision-making.

• Team behaviour: Declaring the current mode prevents one participant from evaluating while another is still generating.
• Decision quality: Convergence converts creativity into action but remains evidence-based and open to revision.
• Risk: Excessive divergence causes delay, whereas excessive convergence produces safe, conventional solutions.

IV. Brainstorming and Idea Generation — Collaborative Production of Possibilities

A. Brainstorming and Idea Generation

Brainstorming is a time-limited group method for generating numerous ideas around a clearly stated challenge.

• Preparation: Define the user, need, scope, duration, facilitator, and recording method before the session.
• Core rules: Defer criticism, seek quantity, welcome unusual ideas, build on others’ contributions, and keep one conversation active.
• Prompting: Use a question such as “How might we make appointment delays transparent and useful?”
• Brainwriting: Participants first write ideas independently, reducing domination by confident or senior speakers.
• Building: “Yes, and…” extends an idea; a queue display might become personalised updates plus remote waiting.
• Visualisation: Sticky notes, rapid sketches, or digital boards make contributions equally visible.
• Closing: Remove exact duplicates and clarify wording without evaluating the underlying concepts.

B. Applications and Limitations

Brainstorming works best when participation is psychologically safe and facilitation limits social bias.

• Strength: Interaction can trigger associations that isolated thinking might not produce.
• Weakness: Production blocking, conformity, hierarchy, and evaluation anxiety can suppress contributions.
• Mitigation: Begin silently, use round-robin sharing, permit anonymous input, and separate facilitation from decision authority.

V. SCAMPER Technique — Systematic Transformation of Existing Ideas

A. SCAMPER Technique

SCAMPER is a prompt-based method that generates alternatives by modifying an existing product, service, or process.

• Substitute: Replace a component, person, material, or step; substitute paper clinic forms with pre-visit digital entry.
• Combine: Join functions or resources; combine appointment reminders with preparation instructions.
• Adapt: Borrow a principle from another context; adapt restaurant wait-time notifications to outpatient care.
• Modify: Change size, shape, emphasis, frequency, or meaning; shorten registration by requesting only essential data initially.
• Put to another use: Reassign an existing resource; use waiting-area screens for personalised queue information.
• Eliminate: Remove unnecessary features or steps; eliminate repeated identity checks where policy permits.
• Reverse or rearrange: Change sequence, roles, or direction; collect routine information before arrival instead of after check-in.

B. Applications and Limitations

SCAMPER is especially effective when a recognisable solution already exists but needs improvement.

• Application: Each prompt forces a different transformation, reducing reliance on unguided inspiration.
• Limitation: It may encourage incremental modification rather than fundamental reframing.
• Control: Apply the prompts to user journeys and service relationships, not only physical product components.

VI. Mind Mapping and Reverse Thinking — Associative and Assumption-Challenging Methods

A. Mind Mapping and Reverse Thinking

Mind mapping expands ideas through visible associations, while reverse thinking exposes solutions by deliberately considering the opposite condition.

1. Mind mapping: Place the central challenge in the middle and branch into users, causes, contexts, technologies, emotions, and solution families.
2. Reverse thinking: Ask how to worsen, prevent, or invert the desired outcome, then reverse the resulting actions.

• Concrete map: “Reduce clinic waiting stress” might branch into information, comfort, control, privacy, and productive time.
• Reverse prompt: “How could we maximise waiting stress?” may produce uncertainty, silence, crowding, and repeated forms.
• Reversal: These negatives suggest live updates, clear explanations, quieter spaces, and unified data collection.
• Combination: Reversed insights can become new branches on the mind map, linking causes directly to interventions.

B. Applications and Limitations

These methods help when ideas are repetitive or hidden assumptions constrain discussion.

• Strength: Mind maps reveal relationships; reversal makes familiar problems cognitively unfamiliar.
• Limitation: Maps can become cluttered, while reversed suggestions may remain superficial.
• Control: Use distinct branch labels and translate every useful reversal into a specific positive concept.

VII. Idea Evaluation and Selection — Moving from Options to Decisions

A. Idea Evaluation and Selection

Idea evaluation is the systematic comparison of alternatives, while selection identifies concepts worth prototyping or implementing.

• Criteria: Common measures include desirability, feasibility, viability, accessibility, sustainability, risk, and strategic alignment.
• Evidence: User interviews support desirability; technical reviews support feasibility; cost and demand estimates support viability.
• Thresholds: Legal compliance, safety, and ethical acceptability should operate as mandatory gates rather than optional advantages.
• Comparison: Judge all ideas against the same defined criteria to reduce preference-based decisions.
• Combination: Selection need not produce one untouched winner; complementary features may form a stronger concept.
• Validation: A selected idea remains a hypothesis until prototypes and user tests provide behavioural evidence.

B. Limitations

Evaluation can create false confidence when uncertain judgments are converted into precise-looking scores.

• Biases: Familiarity, authority, sunk cost, and attachment to one’s own idea can distort ratings.
• Mitigation: Score independently, record assumptions, involve users and specialists, and review disagreement before averaging results.

VIII. Idea Organisation and Clustering — Structuring a Large Idea Set

A. Idea Organisation and Clustering

Idea organisation and clustering group related concepts so patterns, duplicates, gaps, and broader opportunities become visible.

• Preparation: Write one clearly expressed idea per note and preserve enough detail to distinguish similar proposals.
• Affinity clustering: Group ideas by natural similarity without imposing categories in advance.
• Labelling: Name clusters by the shared principle, such as “predictability,” “remote waiting,” or “faster registration.”
• Hierarchy: Separate broad themes, concepts, and individual features to avoid comparing items at different levels.
• Duplication: Merge exact repetitions while retaining meaningful variations and contributor reasoning.
• Outliers: Keep unusual ideas visible because they may represent original directions rather than classification errors.
• Outcome: Convert clusters into a manageable shortlist of concept families for evaluation.

B. Applications and Limitations

Clustering turns an unstructured idea collection into a shared representation of the opportunity space.

• Application: It supports team sense-making, voting, portfolio balance, and identification of underexplored areas.
• Limitation: Grouping is interpretive; labels can oversimplify ideas or hide cross-category connections.
• Control: Allow ideas to appear in more than one cluster when they serve multiple functions.

IX. Feasibility and Relevance Analysis — Testing Practicality and Problem Fit

A. Feasibility and Relevance Analysis

Feasibility asks whether an idea can be delivered, while relevance asks whether it meaningfully addresses the defined user problem.

1. Feasibility analysis: Examines technology, skills, time, budget, infrastructure, regulation, operations, and dependencies.
2. Relevance analysis: Examines user need, problem-statement alignment, expected benefit, context, and inclusiveness.

• Technical test: Determine whether required systems, integrations, data, and performance levels are available.
• Operational test: Identify who performs each action and whether the solution fits existing workflows.
• Economic test: Compare development and operating costs with expected financial or social value.
• User test: Connect each proposed feature to a documented pain point or desired outcome.
• Balanced judgment: A feasible but irrelevant idea wastes resources; a relevant but infeasible idea requires adaptation or staging.

B. Applications and Limitations

The analysis is strongest when estimates are supported by small experiments and specialist input.

• Assumptions: Record uncertain claims such as expected adoption or integration effort.
• Response: Use prototypes, technical spikes, pilots, or cost estimates to replace assumptions with evidence.

X. Idea Screening Matrices — Transparent Multi-Criteria Comparison

A. Idea Screening Matrices

An idea screening matrix compares alternatives by assigning scores against consistently defined and, when necessary, weighted criteria.

• Structure: Ideas form rows, criteria form columns, and each cell contains a rating, commonly from 1 to 5.
• Weighting: Give more important criteria larger weights; weights should be agreed before ideas are scored.
• Calculation: Compute a weighted score as:

Total score = Σ(w_i × r_i)

• Symbols: w_i is the weight of criterion i, r_i is the idea’s rating on that criterion, and Σ means sum across all criteria.
• Example: With relevance weight 5 and rating 4, that criterion contributes 5 × 4 = 20.
• Documentation: Define what ratings 1, 3, and 5 mean so different evaluators use a comparable scale.
• Interpretation: Review category scores and assumptions, not only the final total.

B. Limitations

A matrix supports judgment but cannot substitute for user research, expertise, or experimentation.

• Sensitivity: Small changes in weights may alter rankings, especially when totals are close.
• Control: Test alternative weights and flag mandatory constraints separately from compensatory scores.

XI. Idea Selection and Prioritisation — Building an Actionable Portfolio

A. Idea Selection and Prioritisation

Idea selection chooses concepts for further development, while prioritisation determines their sequence, urgency, and resource allocation.

• Shortlisting: Remove ideas that fail mandatory safety, ethical, legal, or strategic requirements.
• Prioritisation dimensions: Compare user impact, effort, confidence, urgency, risk, dependencies, and learning value.
• Impact-effort grid: Classify ideas as quick wins, major projects, fill-ins, or low-value tasks.
• Portfolio balance: Combine low-risk improvements with a limited number of higher-risk, potentially transformative concepts.
• Dependency order: Prioritise enabling work before concepts that rely on it; data integration may precede personalised notifications.
• Confidence: Prefer evidence-backed estimates, but prioritise small tests when uncertainty itself is the main risk.
• Ownership: Assign responsibility, resources, decision dates, and a next action to each selected concept.
• Iteration: Reprioritise after prototypes, user feedback, cost changes, or new constraints alter the evidence.

B. Significance

Prioritisation converts a ranked list into a defensible programme of learning and implementation.

• Decision record: Document criteria, scores, assumptions, exclusions, and reasons for final choices.
• Strategic discipline: A high-scoring idea may still be delayed because of dependencies, limited capacity, or portfolio imbalance.
• Final outcome: Selected ideas enter prototyping with explicit hypotheses, success measures, and conditions for continuation or rejection.