4 Ideation and Concept Development

Frame a user-centered opportunity

Ideation is a flexible cycle of expanding possibilities and narrowing focus, not a rigid sequence. The goal is not to find one perfect idea immediately, but to create meaningful alternatives and decide which ones are worth developing and testing.

Begin with evidence about people and their context rather than assumptions about a preferred solution. Turn a useful research insight into a How Might We question: it should identify a real opportunity while leaving room for different answers. For example, if students say lunch lines leave them little time to eat, a team could ask how to help students get a satisfying lunch within a short break. Asking how to build a particular app would prematurely limit the solutions the team could consider.

Generate a range of ideas

First diverge: generate many distinct possibilities before evaluating them. A short, structured session can help a team make space for individual contributions and shared exploration:

1. Share the user insight and the How Might We question.

2. Give participants a few quiet minutes to write or sketch ideas individually.

3. Share ideas in turn, capturing one idea per note so everyone can contribute.

4. Build on, combine, or vary ideas; defer criticism while generating.

5. Group related ideas into themes and identify genuinely different directions.

Quiet individual work followed by group sharing can reduce the influence of the loudest voices. Set a clear time limit, invite contributions from different disciplines, and make the ideas visible to the whole group. Brainstorming guidelines include deferring judgment, aiming for quantity, building on others’ ideas, and capturing every idea.

When a team needs a prompt to get unstuck, it can use SCAMPER to explore an existing idea: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, or Rearrange. For a lunch service, the team might combine ordering and pickup, eliminate an unnecessary queue step, or rearrange the collection process. These prompts help expand an idea; they do not prove that it meets users’ needs.

Clarify and compare concepts

After generating ideas, cluster related notes and clarify what each promising concept would do for users. Combine compatible elements, but preserve distinct alternatives long enough to compare them fairly. A concept can be a short description or sketch that states who it serves, what need it addresses, how it might work, and what should be tested.

Then converge by comparing concepts against explicit criteria:

• Desirability: Does it address a need that matters to people?

• Feasibility: Can the team build or deliver it with available capabilities?

• Viability: Can it work within relevant organizational, operational, and resource constraints?

• Inclusion and risk: Who might benefit or be left out, and what could go wrong?

These criteria balance human needs, technical feasibility, and economic viability. A simple comparison table can make trade-offs visible. Dot voting may help a group identify interest, but votes alone do not establish that an idea is useful or workable. Record uncertainties and evidence gaps, and choose concepts that can be tested rather than merely those that sound most impressive.

Test and iterate

For the lunch example, a team could compare pre-order pickup, a faster express line, and mobile carts near classrooms. A low-cost trial of one or more options could reveal whether students use them, whether waiting time changes, and whether access is equitable.

Use what is learned to refine the concept, combine approaches, or return to idea generation. Selecting an idea is a decision about what to learn next, not a guarantee that it is the final solution. Effective ideation connects a research-grounded opportunity to a broad set of alternatives, compares those alternatives using clear user-centered criteria, and lets testing guide the next iteration.