Ideation and Concept Development

Introduction

Ideation is the deliberate generation, development and selection of possible responses to a user, market or organisational problem. In product management, it is not synonymous with producing a large number of clever features. Effective ideation connects evidence about people and context with technically feasible, commercially responsible and strategically coherent concepts.

Ideation follows problem framing and precedes concept validation. It therefore performs a bridging role: insights from research are transformed into alternatives that can later be prototyped and tested. Poor ideation either narrows the opportunity too early or produces attractive but irrelevant ideas. Strong ideation temporarily separates imagination from judgement, then reconnects them through explicit evaluation.

A useful distinction is between an idea, a brief possibility such as “help commuters share unused charging capacity,” and a concept, a more developed proposition describing the target user, need, experience, value mechanism and key assumptions. A concept is not yet a product specification. It is a testable hypothesis about how value might be created.

Learning Objectives

By the end of this chapter, learners should be able to:

1. Explain the purpose and stages of product ideation.
2. Select and facilitate brainstorming, brainwriting, SCAMPER, analogy, co-creation and morphological methods.
3. Manage divergent and convergent thinking without premature judgement.
4. Convert raw ideas into coherent product concepts.
5. Evaluate concepts using evidence, criteria and experiments rather than authority alone.
6. Recognise and mitigate fixation, groupthink, HiPPO decision-making and other cognitive or organisational risks.
7. Apply ideation methods to an integrated product-management case.

1. The Logic of Divergence and Convergence

Design thinking commonly alternates between widening and narrowing the opportunity space. During divergence, the team seeks variety: different users, mechanisms, channels, business models and experiences are considered. During convergence, the team interprets, clusters, evaluates and selects options.

These activities are complementary but should not be confused. Judging ideas while they are being generated can suppress unusual alternatives. Conversely, endless divergence can become avoidance of commitment. A disciplined workshop makes the transition explicit—for example, by announcing that the first thirty minutes are for generation and the next thirty minutes are for synthesis.

Divergence should be assessed by more than the number of ideas. Useful indicators include diversity of user groups, solution mechanisms, levels of ambition and assumptions. Ten variations of the same feature may represent less creative range than five fundamentally different approaches.

Convergence should also be more rigorous than voting. It involves clarifying the concept, identifying assumptions, comparing it with evidence and deciding what must be learned next. A concept can be selected for experimentation without being declared the final product.

2. Preparing an Ideation Session

Ideation quality depends heavily on preparation. The product manager should establish:

• A design challenge: a focused, opportunity-oriented question, such as “How might we help first-year students find trustworthy study partners within their preferred schedule?”
• Evidence: interview excerpts, behavioural observations, journey maps, market data and relevant constraints.
• Participants: a deliberately varied group including product, design, engineering, operations, sales, customer support and, where appropriate, users or domain experts.
• Boundaries: regulatory, technical, financial, ethical, accessibility and time constraints.
• Materials: visible problem evidence, a timer, an idea-capture system and clear evaluation criteria.
• Decision rights: the group should know whether it is generating options, recommending a shortlist or making a final prioritisation decision.

A challenge should be neither so broad that every answer is acceptable nor so narrow that only one feature is imaginable. “How might we improve the app?” is generally weak. “How might we reduce uncertainty for a customer choosing a plan?” creates a more productive design space without dictating the answer.

Participants should agree on behavioural norms: defer judgement during divergence, build on others’ ideas, make ideas visible, seek quantity and range, and invite quieter voices. Psychological safety is not simply friendliness; it is the practical condition that enables people to offer incomplete, unconventional or dissenting contributions without disproportionate social risk.

3. Core Ideation Methods

3.1 Brainstorming

Classical brainstorming is a facilitated group process based on suspending criticism, encouraging quantity, building on ideas and welcoming unusual suggestions. Its value lies in rapid association and shared momentum. It is most useful when the group has a clear challenge and sufficient shared context.

A product manager can run a 45-minute session as follows:

1. Present the challenge and relevant evidence.
2. Allow silent individual reflection.
3. Conduct a rapid idea-generation round.
4. Ask participants to extend or combine selected ideas.
5. Clarify and cluster ideas without evaluating them.
6. Move to a separate selection activity.

Unstructured brainstorming has limitations. Dominant speakers may control the conversation, production blocking may prevent people from contributing while waiting to speak, and social conformity may reduce originality. Brainstorming is therefore a facilitation discipline, not a guarantee of creativity.

3.2 Brainwriting

Brainwriting replaces spoken turn-taking with written or digital contribution. Each participant independently records ideas, after which ideas may be circulated for extension. The commonly used 6–3–5 format asks six participants to write three ideas in five-minute rounds, although the numbers can be adapted.

Brainwriting is valuable when the team is distributed, hierarchical, multilingual or contains introverted participants. It reduces evaluation apprehension and gives everyone an equal initial opportunity. Its risks include shallow entries, limited discussion and excessive dependence on the prompt. Combining a silent round with later conversation often produces a useful balance.

3.3 SCAMPER

SCAMPER is a prompt system for transforming an existing product, service or process:

SCAMPER is especially effective for incremental innovation and service redesign. It can produce radical outcomes when prompts are applied to assumptions rather than superficial interface elements. Its limitation is that it may keep the team anchored to the current product; it should therefore be paired with methods that question the underlying problem.

3.4 Analogies and Biomimicry

Analogy transfers a relationship, mechanism or organising principle from another domain. A team might ask how an airport manages flow, how a library supports discovery, how a marketplace builds trust or how an immune system detects threats. The strongest analogies are structural rather than merely visual.

An analogy process has four steps:

1. Define the product problem without proposing a solution.
2. Select distant domains with a comparable underlying relationship.
3. Study how the domain handles the relationship.
4. Translate the principle, adapting it to user, technical and ethical constraints.

Analogy is not proof that a solution will work. It is a generative device. A hospital triage model may inspire prioritisation, but a digital product must still examine fairness, privacy and error consequences.

3.5 Co-creation

Co-creation involves users, customers, partners or other stakeholders as active contributors to concept development rather than merely respondents to a finished proposal. Techniques include participatory design, customer workshops, role play, collaborative journey mapping, diary prompts and concept remixing.

Co-creation is particularly valuable for tacit knowledge: workarounds, emotional meanings and contextual constraints that users may not articulate in conventional interviews. However, participants are not always representative, and requested features may reflect current habits rather than deeper needs. Product teams should interpret co-created outputs as evidence and inspiration, not as automatic requirements.

Good practice includes compensating participants fairly, explaining how contributions will be used, protecting confidential information and avoiding the implication that participation guarantees implementation. Accessibility and power differences must also be considered: the most articulate participant should not define the group’s needs.

3.6 Morphological Analysis

Morphological analysis decomposes a design challenge into dimensions and generates alternatives for each dimension. The alternatives are then combined into complete concepts.

For example, a learning-support product might be decomposed into:

Selecting one alternative from each row produces a concept configuration. The method makes the design space visible and encourages combinations that would not arise from ordinary discussion. It can also generate an unmanageable number of combinations. Teams should therefore apply constraints, remove incompatible options and test combinations against user evidence and feasibility.

4. From Ideas to Concepts

Raw ideas should be transformed into concise concept cards. A useful concept card contains:

• target user and context;
• problem or desired outcome;
• proposed experience or mechanism;
• distinctive value proposition;
• evidence supporting the opportunity;
• key assumptions;
• operational, technical and ethical dependencies;
• an initial experiment;
• major risks and unanswered questions.

A concept statement might follow this pattern: “For [target user] who struggles with [contextual problem], [concept] provides [experience or mechanism], unlike [current alternative], because [reason to believe].” The statement is a thinking aid, not marketing copy. It should expose uncertainty rather than conceal it.

Assumptions and testability

Product concepts often contain assumptions about desirability, usability, feasibility, viability and responsibility. These should be made explicit. For example:

• Desirability: users experience the problem frequently enough to seek help.
• Usability: users can understand and complete the proposed interaction.
• Feasibility: the organisation can access required data and build the service reliably.
• Viability: benefits justify acquisition, delivery and support costs.
• Responsibility: the concept does not create unacceptable privacy, safety, exclusion or environmental harms.

The next experiment should target the assumption whose failure would most seriously invalidate the concept. A clickable prototype may test comprehension, while a concierge service may test willingness to use the underlying service before automation is built.

5. Evaluating Concepts

Evaluation should be transparent, multi-perspective and proportionate to the decision. Common criteria include user value, strategic fit, differentiation, feasibility, economic potential, speed to learning, scalability, accessibility and risk.

A simple decision matrix can support discussion. Each concept is considered against agreed criteria using a documented scale, such as 1 (weak) to 5 (strong). If criteria are weighted, the team must explain why one criterion matters more than another. Scores are not objective facts; they are structured judgements that expose disagreement and assumptions.

A practical evaluation sequence is:

1. Clarify: remove duplicate ideas and resolve ambiguous wording.
2. Screen: eliminate concepts that violate non-negotiable safety, legal or strategic constraints.
3. Compare: use agreed criteria and independent initial scoring.
4. Discuss variance: investigate why participants scored differently.
5. Select experiments: choose concepts whose uncertainty is important and learnable.
6. Review evidence: update the decision after testing.

A high score should not be treated as certainty. A concept with moderate current evidence but a cheap, informative experiment may deserve priority over a seemingly attractive concept based only on executive preference. Conversely, a concept may be rejected even if users like it when it creates unacceptable harm or cannot be delivered responsibly.

6. Cognitive and Organisational Barriers

Fixation

Fixation is attachment to an existing object, solution, representation or assumption. Examples include copying a competitor’s feature, interpreting every problem as an app feature, or treating the first plausible concept as the design target. Countermeasures include reframing the challenge, using distant analogies, imposing deliberate constraints, generating alternatives before discussing feasibility and asking what would be possible without the current technology or business model.

Groupthink

Groupthink occurs when the desire for harmony suppresses critical examination. Symptoms include self-censorship, an illusion of unanimity, stereotyping dissenters and rationalising warning signs. It is more likely when teams are cohesive, status differences are strong, deadlines are tight and a leader signals a preferred answer.

Countermeasures include independent pre-work, anonymous scoring, a rotating devil’s advocate, explicit dissent rounds, outside reviewers and separating idea generation from executive review. The devil’s advocate should challenge assumptions, not attack people.

HiPPO decision-making

HiPPO means “highest-paid person’s opinion.” Senior experience can be valuable, but hierarchy is a poor substitute for evidence. When a senior person speaks first or scores publicly, others may anchor on that view. Product leaders can reduce this effect by collecting independent views before discussion, asking leaders to speak last, recording the evidence behind each judgement and agreeing in advance what evidence could change the decision.

Other biases

Availability bias favours memorable examples; confirmation bias seeks supporting evidence; status quo bias favours existing arrangements; sunk-cost reasoning protects previous investment; and novelty bias overvalues newness. No process removes judgement, but structured comparison, diverse participation and explicit assumptions make judgement more inspectable.

7. Facilitation and Decision Governance

The facilitator manages the process rather than advocating a favourite concept. Useful interventions include asking for a second idea, inviting a missing perspective, separating observation from interpretation, and converting disagreement into a testable question.

A healthy workshop distinguishes three roles:

• Generator: contributes possibilities.
• Facilitator: protects the quality of participation and process.
• Decision owner: accepts accountability for the next decision.

The decision owner should document the decision, alternatives considered, evidence used, unresolved assumptions, experiment selected and review date. This creates an audit trail and prevents later revisionism. It also enables organisational learning when a concept fails for reasons that were visible but ignored.

For sensitive products, governance should include privacy, security, accessibility, legal, safety and responsible-innovation review at the appropriate stage. Governance should not be used as a late-stage veto after substantial emotional investment; constraints should inform ideation from the beginning.

8. Technology and AI in Ideation

Digital whiteboards, collaborative repositories and generative AI can increase the speed and breadth of ideation. AI can propose variations, classify ideas, identify missing stakeholders, simulate alternative contexts or help create first drafts of concept cards. It is most useful as a provocative assistant rather than an authority.

AI-generated ideas may reproduce training-data biases, reveal confidential information through inappropriate tools, or create superficially novel but strategically irrelevant suggestions. Teams should document prompts and sources where material, avoid entering personal or proprietary data into unapproved systems, verify factual claims and preserve human accountability for selection. A generated idea is not evidence of user demand, technical feasibility or ethical acceptability.

Technology should also support inclusion: asynchronous contribution, translation, accessible interfaces and transparent records can broaden participation. Yet digital access, language models’ uneven cultural representation and automated clustering errors require human review.

9. Illustrative Case: Reimagining a University Careers Service

Background

This fictional case concerns “Pathway,” a university team seeking to improve use of its careers service. Usage data showed that final-year students attended appointments, but many first-year students did not engage until shortly before graduation.

Problem

Research indicated that first-year students felt careers advice was premature, did not know what questions to ask and worried that appointments were intended for students already pursuing a specific profession. The initial internal proposal was to add more promotional messages to the student portal.

Analysis

The product manager reframed the challenge as: “How might we help students connect everyday university choices with possible future directions, without requiring them to have a career decision already made?” The team assembled interview excerpts, an enrolment journey, adviser constraints and accessibility requirements.

In a brainwriting session, participants generated ideas independently. SCAMPER then challenged the existing appointment model: substitute one-off appointments with recurring check-ins; combine career exploration with course activities; eliminate the requirement to formulate a question; reverse the process so students explore examples before requesting adviser support. An analogy exercise examined how music-streaming services support discovery without requiring a listener to know the exact song they want.

Morphological analysis produced combinations across user moment, interaction mode, guidance source and value proposition. One concept combined a short, optional “exploration path,” peer examples, adviser escalation and reflection prompts embedded in existing course activities.

Evaluation and approach

The team used criteria agreed before discussion: relevance to the identified barrier, accessibility, adviser capacity, learning potential, privacy and strategic fit. A senior administrator preferred a mass email campaign, but independent scoring showed that the campaign addressed awareness more directly than uncertainty. The group did not reject the administrator’s view; it treated it as a hypothesis about the cause of low usage.

The selected concept was not immediately built as a full platform. A concierge pilot used existing forms and human-curated prompts in two courses. Students could explore examples, record interests and request a conversation without naming a target occupation. The pilot measured completion, perceived relevance, requests for follow-up and adviser workload, while collecting qualitative feedback.

Outcome

The pilot showed that students valued low-commitment exploration, but some disliked occupational examples that appeared culturally narrow. The team expanded examples, added accessibility checks and clarified that participation would not be used for academic assessment. Adviser workload was higher than expected, so the next experiment focused on group sessions and reusable content rather than immediate automation.

Learning points

The case demonstrates that ideation improved when the team reframed the problem rather than decorating an existing solution. Multiple methods produced different kinds of value: brainwriting broadened participation, SCAMPER challenged the current service, analogy suggested a discovery mechanism, and morphological analysis exposed combinations. Evaluation did not identify a permanently “best” concept; it selected a responsible next experiment. Finally, governance issues—representation, privacy, accessibility and workload—were design considerations, not post-launch corrections.

10. Best Practices for Product Managers

1. Begin with evidence and a human-centred opportunity, not a predetermined feature.
2. Separate generation, clarification, evaluation and decision-making.
3. Use more than one ideation method because each exposes different possibilities.
4. Include silent and asynchronous participation to reduce status and production effects.
5. Make constraints visible, but do not allow premature feasibility concerns to eliminate all unusual ideas.
6. Convert ideas into concept cards with explicit assumptions.
7. Score independently before group discussion when hierarchy is strong.
8. Select experiments according to uncertainty, potential impact and learnability.
9. Record why a decision was made and what evidence could overturn it.
10. Treat safety, privacy, accessibility, inclusion and environmental impact as design criteria.
11. Use AI to expand and interrogate thinking, never to replace user evidence or accountable judgement.
12. Revisit rejected concepts when new evidence, technology or context changes the design space.

Challenges and Limitations

Ideation methods can create an illusion of progress. A busy workshop may produce many ideas without improving understanding of the problem. Participants may also overrepresent organisational perspectives, especially when users are absent. Evaluation matrices can create false precision, and voting can reward popularity rather than value. Co-creation can be extractive if participants’ labour is unpaid or their contributions are misrepresented. Analogies can import inappropriate assumptions, while AI can amplify bias at scale.

Accordingly, ideation should be embedded in an iterative learning system. Concepts need prototypes, user research, operational analysis and responsible review. The purpose is not to discover certainty in a meeting; it is to create better hypotheses and make uncertainty visible enough to investigate.

Chapter Summary

Ideation translates researched opportunities into alternative product possibilities. Effective practice alternates deliberate divergence with evidence-based convergence. Brainstorming creates shared momentum; brainwriting reduces status and production effects; SCAMPER transforms existing solutions; analogies transfer useful structures; co-creation brings stakeholders into design; and morphological analysis systematically combines alternatives.

Ideas become concepts when they specify a target user, context, value proposition, mechanism, assumptions, dependencies and a learning experiment. Evaluation should use transparent criteria while recognising that scores are judgements, not facts. Fixation, groupthink, hierarchy and HiPPO decision-making can be reduced through reframing, independent input, dissent, evidence records and clear decision governance. Product managers should use technology and AI carefully, maintaining human accountability and protecting privacy, inclusion, accessibility and safety. The most valuable concept is often not the one that appears best in a workshop, but the one that offers meaningful value and can be responsibly tested and learned from.

Key Terms

Ideation: The deliberate generation and development of possible responses to a problem.

Concept: A structured, testable proposition describing a possible product or service.

Divergence: Expanding the range of possibilities before selection.

Convergence: Narrowing, synthesising and prioritising alternatives.

Brainstorming: Facilitated spoken generation of ideas under deferred judgement.

Brainwriting: Written or digital generation of ideas, often conducted silently.

SCAMPER: A set of transformation prompts: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse or Rearrange.

Analogy: Transfer of a relationship or principle from another domain.

Co-creation: Collaborative development involving users or other stakeholders as active contributors.

Morphological analysis: Decomposition of a challenge into dimensions and systematic combination of alternatives.

Concept card: A concise record of a concept, its value proposition, assumptions and experiment.

Assumption: A proposition that must be true for a concept to succeed.

Fixation: Attachment to an existing solution, representation or assumption.

Groupthink: Suppression of critical analysis caused by pressure for agreement.

HiPPO: Reliance on the highest-paid person’s opinion instead of balanced evidence.

Psychological safety: A shared belief that people can contribute, question and dissent without undue interpersonal risk.

Decision matrix: A structured comparison of alternatives against explicit criteria.

Concierge pilot: A manually delivered service used to test value before automation.

Responsible innovation: Development that considers social, ethical, legal, environmental and long-term consequences.

Review Questions

Short Answer Questions

1. Distinguish an idea from a concept in product management.
2. Why should divergence and convergence normally be separated?
3. State two advantages of brainwriting over unstructured brainstorming.
4. What is the purpose of morphological analysis?
5. Give two ways a product manager can reduce HiPPO decision-making.

Long Answer Questions

1. Explain how a product manager should prepare and facilitate a multidisciplinary ideation session.
2. Compare brainstorming, SCAMPER, analogy and co-creation, including an appropriate use case and limitation for each.
3. Describe how raw ideas can be transformed into testable product concepts.
4. Discuss fixation and groupthink as threats to product innovation and evaluate methods for reducing them.
5. Explain why concept evaluation should combine strategic judgement, evidence, experimentation and responsible-innovation criteria.

Analytical / Application Questions

1. A team proposes adding a dashboard because users “need more visibility.” Design a reframing process and select two ideation methods that could uncover alternatives.
2. Construct a small morphological table for a service that helps remote employees maintain social connection. Explain how you would select combinations for testing.
3. An executive insists that a mass email campaign is the best response to low product adoption. Show how you would investigate the claim without allowing hierarchy to determine the decision.

Multiple Choice Questions with Answers

Question 1

Which activity is primarily associated with divergent thinking?

A. Selecting one concept against weighted criteria

B. Generating varied alternatives without premature judgement

C. Screening concepts for legal compliance

D. Estimating the cost of a chosen prototype

Correct Answer: B. Generating varied alternatives without premature judgement

Question 2

What is the main advantage of brainwriting in a hierarchical team?

A. It guarantees that every idea is feasible

B. It eliminates the need for facilitation

C. It gives participants an equal initial opportunity to contribute

D. It produces only radical innovations

Correct Answer: C. It gives participants an equal initial opportunity to contribute

Question 3

Which SCAMPER prompt asks what can be removed from a product or process?

A. Adapt

B. Combine

C. Eliminate

D. Reverse

Correct Answer: C. Eliminate

Question 4

What does morphological analysis systematically do?

A. Ranks employees by creative performance

B. Combines alternatives across defined design dimensions

C. Tests a prototype with representative users

D. Calculates product profitability

Correct Answer: B. Combines alternatives across defined design dimensions

Question 5

Which item belongs on a well-formed concept card?

A. Only the preferred interface colour

B. The target user, value proposition and key assumptions

C. A final guarantee of market success

D. A list of unrelated competitor slogans

Correct Answer: B. The target user, value proposition and key assumptions

Question 6

A senior executive states a preferred idea first, and the team quickly agrees despite limited evidence. Which risk is most evident?

A. HiPPO decision-making

B. Morphological analysis

C. Co-creation

D. Production prototyping

Correct Answer: A. HiPPO decision-making

Question 7

Why can a concierge pilot be useful during concept development?

A. It proves that automation is unnecessary in every context

B. It tests underlying value before substantial automation investment

C. It replaces all user research

D. It guarantees scalability

Correct Answer: B. It tests underlying value before substantial automation investment

Question 8

Which practice best reduces groupthink?

A. Requiring unanimous agreement before discussion

B. Allowing the most senior participant to score first

C. Collecting independent views and conducting an explicit dissent round

D. Removing all constraints from the challenge

Correct Answer: C. Collecting independent views and conducting an explicit dissent round

Question 9

How should an AI-generated product idea normally be treated?

A. As validated evidence of user demand

B. As a useful prompt requiring human verification and accountability

C. As automatically unbiased because it is machine-generated

D. As a final product specification

Correct Answer: B. As a useful prompt requiring human verification and accountability

Question 10

Which statement best describes responsible concept evaluation?

A. Only revenue potential should determine selection

B. A high workshop score establishes product-market fit

C. User value should be considered alongside feasibility, viability and potential harms

D. Ethical review should occur only after launch

Correct Answer: C. User value should be considered alongside feasibility, viability and potential harms