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 framed problem are transformed into possible solutions. It alternates between expanding the solution space and narrowing it, ensuring that creativity is not separated from user relevance, technical reality, or organisational goals.

• Governing principle: Generate broadly before judging narrowly; premature criticism reduces variety, while unlimited generation without selection produces no actionable outcome.
• Starting point: Ideation normally begins with a human-centred problem statement or a “How might we...?” question, such as “How might we reduce waiting anxiety in a clinic?”
• Primary modes:
  • Divergence: Produces numerous, varied, and unconventional possibilities.
  • Convergence: Compares possibilities and selects promising directions.
• Core qualities of ideas:
  • Fluency: Number of ideas generated—for example, 40 ideas in 15 minutes.
  • Flexibility: Number of different categories represented, such as digital, spatial, procedural, and interpersonal solutions.
  • Originality: Degree to which an idea differs from familiar solutions.
  • Elaboration: Level of useful detail added to an initial concept.
• Expected output: A prioritised set of ideas ready for prototyping, not a single supposedly perfect answer.

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

A. Divergent Thinking and Idea Generation

Divergent thinking intentionally creates many different responses to one problem before feasibility or quality is judged.

• Purpose: It prevents fixation on the first obvious solution and exposes alternative ways to satisfy the same user need.
• Quantity-first rule: A team may target “30 ideas in 20 minutes”; the numerical target encourages movement beyond predictable early responses.
• Variety of directions: For a long cafeteria queue, ideas could alter payment, menu design, staffing, collection points, ordering time, or demand distribution.
• Useful prompts: “What else?”, “What would a child design?”, and “How could this work without a screen?” deliberately change perspective.
• Postponed judgement: Cost, risk, and practicality are temporarily deferred because criticism during generation can suppress unusual contributions.
• Limitation: Divergence can produce duplicates, irrelevant concepts, or cognitive overload; timeboxing and later clustering keep the output manageable.

III. Convergent and Divergent Thinking — Managing Creative Movement

A. Convergent and Divergent Thinking

Effective ideation cycles between opening up possibilities and narrowing them according to explicit evidence and constraints.

1. Divergent thinking:

   • Question asked: “What could we do?”
   • Operating logic: Seek difference, tolerate ambiguity, defer judgement, and combine incomplete suggestions.
   • Typical output: A large collection of sketches, notes, or concept statements.

2. Convergent thinking:

   • Question asked: “What should we pursue?”
   • Operating logic: Apply user needs, project goals, resources, ethics, and technical constraints.
   • Typical output: A shortlist, ranked portfolio, or selected concept.

• Explicit contrast: Divergence values breadth and novelty, whereas convergence values fit and defensible choice; treating convergence as mere criticism can eliminate bold but improvable ideas.
• Double-diamond rhythm: Teams first diverge and converge around the problem, then diverge and converge around solutions.
• Iteration: If testing invalidates a selected concept, the team can return to the idea pool rather than restarting from zero.

IV. Brainstorming and Idea Generation — Collaborative Production

A. Brainstorming and Idea Generation

Brainstorming is a structured group method for rapidly generating ideas through free contribution and association.

• Core rules: Defer judgement, seek quantity, welcome unusual ideas, and build on others’ suggestions.
• Procedure:
  • State one focused prompt and a fixed duration, such as 15 minutes.
  • Let participants contribute short, visible ideas—often one idea per sticky note.
  • Record every contribution without debate.
  • Clarify, cluster, and evaluate only after generation ends.
• Building mechanism: “Yes, and...” extends an idea; a proposal for mobile ordering might lead to scheduled pickup and then shared family orders.
• Facilitator’s role: Protect equal participation, maintain pace, restate the prompt, and prevent dominant speakers from controlling the session.
• Alternative format: Brainwriting allows participants to write silently before sharing, reducing production blocking and fear of public judgement.
• Limitation: Unstructured sessions may encourage conformity; individual generation followed by group sharing often preserves greater independence.

V. SCAMPER Technique — Transforming Existing Ideas

A. SCAMPER Technique

SCAMPER is a prompt-based technique that creates alternatives by systematically modifying an existing product, service, or process.

• S—Substitute: Replace a material, actor, step, or rule; substitute paper tickets with QR codes.
• C—Combine: Join functions or resources; combine appointment reminders with navigation instructions.
• A—Adapt: Borrow a feature from another context; adapt airport queue displays for hospital waiting rooms.
• M—Modify: Change size, shape, emphasis, speed, or frequency; enlarge high-priority controls on a dashboard.
• P—Put to another use: Apply an existing resource to a new purpose; use delivery lockers for equipment returns.
• E—Eliminate: Remove unnecessary steps or components; eliminate repeated entry of customer details.
• R—Reverse or rearrange: Invert order, roles, or layout; collect payment before service rather than afterward.
• Strength: The mnemonic supplies concrete prompts when a team feels stuck.
• Limitation: Because it begins with something existing, SCAMPER may produce incremental improvements rather than completely new systems.

VI. Mind Mapping and Reverse Thinking — Reframing Associations

A. Mind Mapping and Reverse Thinking

Mind mapping develops connected possibilities visually, while reverse thinking exposes assumptions by exploring how the opposite outcome could be created.

1. Mind mapping:

   • Structure: Place the central problem in the middle, add major branches, and extend each branch with keywords, sketches, or links.
   • Concrete example: A map for “better commuting” might branch into time, comfort, cost, safety, information, and sustainability.
   • Value: Visible relationships reveal missing categories and combinations, such as connecting “real-time information” with “accessibility.”

2. Reverse thinking:

   • Procedure: Reverse the goal, generate ways to cause the unwanted result, and invert those answers into solutions.
   • Concrete example: For “improve onboarding,” ask “How could we make onboarding confusing?” Answers such as “use unexplained jargon” become actions such as defining terms contextually.
   • Value: Negative prompts make hidden assumptions and failure conditions easier to identify.

• Limitation: Mind maps can become cluttered, while reversed ideas still require validation because a simple opposite may not be a workable solution.

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

A. Idea Evaluation and Selection

Idea evaluation compares alternatives against agreed criteria so that selection is transparent rather than based on enthusiasm or seniority.

• Evaluation criteria: Common measures include desirability, feasibility, viability, novelty, ethical acceptability, strategic alignment, and environmental effect.
• Criterion definition: “Desirability” should refer to evidence of a meaningful user benefit, not merely whether team members like the concept.
• Two-stage process:
  • Initial filter: Remove duplicates and ideas that violate mandatory requirements.
  • Comparative assessment: Score or discuss the remaining concepts against consistent criteria.
• Evidence base: User interviews, prototypes, cost estimates, technical advice, and operational data strengthen the decision.
• Selection strategy: A portfolio may include one safe improvement, one medium-risk concept, and one high-potential experiment rather than only one winner.
• Bias control: Anonymous voting and recorded reasons reduce authority bias, anchoring, and attachment to an idea’s creator.

VIII. Idea Organisation and Clustering — Creating Meaning from Volume

A. Idea Organisation and Clustering

Idea organisation converts a large, unstructured set of suggestions into meaningful groups that can be compared and developed.

• Preparation: Write each idea as one clear action on a separate note; “send alerts” is more sortable than a paragraph containing several features.
• Affinity clustering: Group ideas by natural similarity without imposing categories in advance.
• Possible cluster labels: For a library project, clusters might include navigation, borrowing, study environment, staff support, and digital access.
• Duplicate handling: Merge exact repetitions but preserve distinct variations; “SMS reminder” and “app notification” share a purpose but use different channels.
• Relationship mapping: Mark ideas as complementary, dependent, contradictory, or mutually exclusive.
• Cluster development: Combine strong elements into concept bundles—for example, digital booking, occupancy displays, and quiet-zone maps may form a “smart study-space” concept.
• Limitation: Labels can oversimplify cross-category ideas, so teams should allow notes to sit between clusters or appear in more than one group.

IX. Feasibility and Relevance Analysis — Testing Practical Fit

A. Feasibility and Relevance Analysis

Feasibility and relevance analysis checks whether an idea can be implemented and whether it meaningfully addresses the defined user problem.

1. Feasibility:

   • Technical: Required technology, skills, reliability, integration, and safety.
   • Operational: Staffing, training, workflow, maintenance, and delivery capacity.
   • Economic and legal: Budget, expected cost, regulations, privacy, and intellectual-property constraints.
   • Time-related: Ability to deliver within the project schedule.

2. Relevance:

   • User fit: Connection to a documented need or pain point.
   • Problem fit: Direct contribution to the “How might we...?” statement.
   • Context fit: Suitability for users’ culture, accessibility requirements, and environment.
   • Strategic fit: Alignment with organisational purpose and desired outcomes.

• Decision principle: A feasible idea with low relevance wastes resources, while a highly relevant but infeasible idea may need simplification, partnership, or staged development.

X. Idea Screening Matrices — Structured Comparison

A. Idea Screening Matrices

An idea screening matrix scores alternatives against common criteria, making trade-offs visible and decisions easier to justify.

• Matrix design: Place ideas in rows, criteria in columns, and use a consistent scale such as 1–5.
• Weighted score:

T_i = Σ(w_j × s_ij)

• T_i = total score for idea i.
• w_j = importance weight of criterion j.
• s_ij = score of idea i on criterion j.
• Σ = addition across all criteria.

• Worked example: If desirability has weight 0.5 and score 4, feasibility weight 0.3 and score 3, and viability weight 0.2 and score 5, the total is (0.5×4) + (0.3×3) + (0.2×5) = 3.9.
• Good practice: Define what each score means before rating and record evidence beside the numbers.
• Limitation: A precise total can conceal subjective assumptions; sensitivity checks should test whether changing a weight alters the ranking.

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 and allocation of resources.

• Priority dimensions: User impact, urgency, effort, cost, risk, learning value, and dependency.
• Impact–effort grid:
  • High impact, low effort: Quick wins to implement early.
  • High impact, high effort: Major projects requiring planning or experiments.
  • Low impact, low effort: Optional improvements.
  • Low impact, high effort: Usually postpone or reject.
• Voting methods: Dot voting identifies group preference, while weighted voting allows participants to assign more points to stronger choices.
• Decision record: Document selected, deferred, and rejected ideas with reasons, assumptions, and supporting evidence.
• Sequencing: Prioritise enabling concepts before dependent ones; a secure data system may be required before launching personalised recommendations.
• Final output: Translate priorities into concept owners, prototype goals, success measures, deadlines, and the next decision point.