Concept Synthesis

Purpose

Transform clusters of related raw ideas into coherent, self-standing concept summaries that can be meaningfully evaluated and compared. Concept synthesis is an integrative activity: it combines the strongest elements from multiple ideas within a cluster into a single concept that is richer than any individual idea.

When to Use

Use concept synthesis when:

• Affinity mapping has produced 15–25 clusters of raw ideas that need consolidation
• Evaluation or selection requires comparable, structured concept descriptions
• Multiple ideas within a cluster complement each other and could be integrated

Do NOT use when:

• Raw ideas are already at concept level (well-formed, comparable)—proceed directly to ranking
• The goal is to preserve all raw ideas without integration (e.g. for a creativity research archive)

Sample Size and Duration

Participants: 2–5 (facilitator-led, small group)

Duration: 2–4 hours for 15–25 clusters → 10–20 concepts

Expected output: 10–20 concept summaries + relationship map

Prerequisites

• Completed affinity map (15–25 named clusters with member ideas)
• A1.3 need statements and user typology (for traceability)
• Concept summary template (see below)
• 2–5 participants (ideation facilitator + 1–4 team members who participated in ideation)
• 2–4 hours (scales with cluster count)

Complete Procedure

Step 1: Review Clusters (15 minutes)

1. Walk through the affinity map; re-read member ideas in each cluster
2. Identify clusters that are: (a) large enough to warrant a standalone concept; (b) small but distinct enough to preserve; (c) complementary and worth merging; (d) redundant with another cluster
3. Determine target concept count: typically 10–20 from 15–25 clusters (some merge, some split, some map 1:1)

Step 2: Synthesise Each Concept (10–15 minutes per concept)

For each cluster (or cluster pair):

1. Identify the 3–5 strongest ideas within the cluster (by novelty, feasibility signal, or completeness)
2. Draft a concept summary integrating the strongest elements into a single coherent solution description
3. Use the standard concept summary format: itemize
4. Concept ID and name (e.g. A2.1-C007: “Proactive Health Alerts”)
5. Problem addressed (A1.3 need statement reference)
6. Solution summary (1 paragraph: what it does and how, at a functional level—not implementation detail)
7. Value proposition (why target users would prefer this over the status quo or current alternatives)
8. Target user segment (from A1.2 user typology)
9. Raw ideas combined (list of raw idea IDs that contributed)
10. Innovation type (incremental / adjacent / breakthrough) itemize
11. Avoid over-specifying: a concept summary describes what the solution does and why it is valuable, not how it is built. Technical specification belongs in A2.4.

Step 3: Verify Diversity (15 minutes)

1. Review the full set of 10–20 concepts
2. Check archetype diversity: are technology-led, service-led, process-led, and business-model-led approaches all represented?
3. If not, examine whether diversity was lost during synthesis (raw ideas existed but were not carried forward) and recover missing archetypes
4. Check innovation type distribution (incremental/adjacent/breakthrough); flag if a category has zero concepts

Step 4: Map Relationships (15 minutes)

1. Identify competing concepts (address the same pain point via different mechanisms)
2. Identify complementary concepts (address different pain points and could potentially combine downstream)
3. Document in a simple concept relationship matrix

Quality Criteria

1. 10–20 synthesised concepts produced
2. All concepts use the standard summary format with all seven fields completed
3. Every concept traceable to raw idea IDs and A1.3 need statements
4. Archetype diversity verified (technology / service / process / business-model approaches represented)
5. Innovation type distribution documented (incremental / adjacent / breakthrough)
6. Concept relationship map (competing / complementary) completed

Theoretical Foundation

Seminal references:

• : Established metrics for evaluating ideation output: quantity, variety, novelty, and quality. Demonstrated that raw ideas alone are insufficient for evaluation —concepts must be synthesised to a consistent level of abstraction before meaningful comparison is possible.
• : Defined concept as “an approximate description of the technology, working principles, and form of the product,” distinguishing it from both raw ideas (too vague) and specifications (too detailed for early evaluation). The concept summary format used here operationalises Ulrich and Eppinger's definition.

Contemporary references:

• : Demonstrated storyboard-based concept synthesis in design sprints: the team combines the best sketch elements into a single storyboard that becomes the prototype blueprint. This rapid visual synthesis complements the structured written synthesis described below.

Challenges and Solutions

Challenge 1: Loss of Novelty During Synthesis

• Symptoms: Synthesised concepts are “averaged” versions that lose the radical edge of the best raw ideas
• Solution: Preserve at least one high-novelty raw idea as a standalone concept (even if it lacks the coherence of a synthesised concept). Novelty lost in synthesis can be recovered in A2.2 design exploration.

Challenge 2: Too Many Concepts

• Symptoms: 25+ concepts (too many for meaningful A2.5 evaluation)
• Solution: Merge concepts that differ only in secondary features. The target of 10–20 ensures diversity without overwhelming the evaluation process.

Challenge 3: Uneven Abstraction Levels

• Symptoms: Some concepts are one-sentence sketches, others are detailed feature lists
• Solution: Enforce the standard template strictly. Every concept must have all seven fields completed at comparable depth. This is essential for fair comparison in A2.5.

Relationship to Other Methods

Concept Synthesis receives input from:

• Affinity Mapping (the referenced method): Named clusters with member ideas

Concept Synthesis provides output to:

• A2.1 Step~5: Light ranking using A2.5 criteria
• A2.5 Decision Point~1: Concept portfolio for evaluation and selection
• A2.2 Ideas Refined: Selected concepts advance to design exploration

Tools and Templates

• Concept summary template (7-field format described above)
• Concept relationship matrix template
• Completed affinity map (input from A2.1 Step~3)

• J. J. Shah, S. M. Smith & N. Vargas-Hernandez (2003). Metrics for Measuring Ideation Effectiveness. Design Studies. 24(2). pp. 111–134.
• J. Knapp, J. Zeratsky & B. Kowitz (2016). Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon & Schuster.
• K. T. Ulrich & S. D. Eppinger (2020). Product Design and Development. 7 ed. McGraw-Hill Education.