Concept Fan: 20+ R&D Solutions (Free Template)

As an Amazon Associate I earn from qualifying purchases. Product links on this page are affiliate links — they cost you nothing extra.

The Concept Fan: Breaking Technical Deadlocks at the Source

The Concept Fan is a lateral thinking framework that resolves engineering bottlenecks by moving backward from a rigid problem statement to broader conceptual levels, creating multiple cascading pathways to over 20 distinct technical solutions. Developed by Edward de Bono in his 1992 book Serious Creativity, the tool systematically strips out implementation details to isolate the core functional objective. This structural shift allows R&D teams to bypass dead ends and uncover non-obvious architectures before committing capital to physical builds.

When an R&D project hits a wall, standard brainstorming usually makes the problem worse.

You have seen this in sprint reviews. A battery housing fails drop testing at -10°C. The team spends three consecutive 60-minute meetings arguing about rib thickness, composite additives, or weld geometry. Every proposed fix assumes the current housing architecture must remain intact.

This cognitive trap is design fixation. Design fixation is an involuntary bias where engineers focus entirely on modifying an existing initial design, blinding them to alternative solutions that eliminate the root problem. A classic study by Terry Purcell and John Gero published in Design Studies found that showing engineers a baseline sketch reduced the variety of novel physical mechanisms they generated by 48%. Traditional brainstorming fails in technical environments because it encourages rapid idea generation around the existing mechanism rather than the fundamental requirement. If your baseline mechanism is flawed, unstructured ideation simply optimizes an error. To break this loop, teams often need to pair their diagnostic sessions with a 60-Min First Principles Workshop for R&D to reset their baseline assumptions.

Lateral abstraction solves this by severing the objective from the current execution. Lateral abstraction is the deliberate practice of stepping back from a specific mechanical fix to define the underlying functional goal in broad, neutral terms, preventing teams from locking onto a single physical implementation.

Instead of asking "How do we reinforce the polymer housing?", the team takes one step backward: "How do we protect the battery cells from kinetic shock?" Taking another step backward reveals a wider purpose: "How do we maintain electrical continuity after an impact?"

[Level 3: Broad Purpose]
Maintain cell continuity after impact
         |
         v
[Level 2: Conceptual Route]
Isolate internal components from shock
         |
         v
[Level 1: Technical Solutions]
- Floating silicone suspension
- Shear-thickening gel perimeter
- Spring-loaded modular sub-chassis

Each step backward opens a new fork in the road. Instead of fighting thermal brittleness in a rigid polymer, the team might pivot to an internal floating suspension or a gel-based energy dissipator. This mechanical shift directly improves your Concept Development Process by producing distinct architectural routes rather than minor material variations. When running these divergent mapping sessions in person, capture the branches across a large easel pad mounted on the wall so the entire engineering pod sees the visual hierarchy in real time.

Before you draw your first fan branch on a whiteboard, you need to structure your problem statement so it does not accidentally dictate the physical mechanism.

Table of Contents

• The Concept Fan: Breaking Technical Deadlocks at the Source
• The 3-Tier Architecture of a Technical Concept Fan
• The 4-Step Protocol for Facilitating an R&D Fan Session
• Worked Case Study: 22 Alternative Solutions to Battery Heat Dissipation
• Screening Matrix: Filtering 20 Concepts into 3 Viable R&D Prototypes
• The Copy-Paste Concept Fan Markdown Template & R&D Worksheet
• Sources & Further Reading

---

The 3-Tier Architecture of a Technical Concept Fan

A Concept Fan is a structured visual framework developed by Edward de Bono that expands creative problem-solving by moving backward from a specific technical bottleneck to broader functional objectives before branching into multiple tactical solutions.

Most engineering teams run straight into dead ends because they start brainstorming at the mechanism level. When an electric motor overheats, the team debates copper winding thickness or fan blade pitch. That narrow focus locks everyone into incremental tweaks on an existing architecture.

The 3-tier architecture stops this trap by forcing your team through three distinct levels of abstraction before anyone sketches a single CAD part.

[ Tier 1: Ultimate Purpose ]
             |
             v
[ Tier 2: Broad Concepts ]
             |
             v
[ Tier 3: Specific Ideas ]

Tier 1: The Ultimate Purpose

Tier 1 strips away all physical mechanisms, materials, and legacy components. It defines the primary thermodynamic, mechanical, or digital job that needs doing.

If you are redesigning an electric vehicle battery enclosure, the starting problem statement is often: "How do we route liquid cooling channels through the aluminum tray?" That is a mechanism question.

The Tier 1 Purpose restates the challenge in fundamental terms: "Dissipate 15 kW of thermal energy from the cell pack during fast charging."

Notice what happens. You remove the words "liquid," "cooling channels," and "aluminum tray." By isolating the functional objective, you allow non-fluidic and non-metallic solutions into the room. This aligns directly with the functional framing taught in our 60-Min First Principles Workshop for R&D.

Tier 2: Broad Concepts

Tier 2 identifies the scientific principles and high-level operating models that could satisfy the Tier 1 Purpose. You are not building parts yet. You are choosing physics.

For the battery thermal management example, your Tier 2 concepts might include:

1. Convective fluid heat transfer (traditional liquid or air flow).
2. Latent heat absorption (phase-change materials).
3. Radiative heat transfer (high-emissivity surface coatings).
4. Solid-state thermoelectric cooling (Peltier effect modules).

Each broad concept represents a completely separate branch of physical science. If one branch hits a patent wall or supply constraint, the other three remain intact.

When teams run a structured concept development process, identifying at least 4 distinct Tier 2 operating principles prevents premature design convergence.

Tier 3: Specific Ideas

Tier 3 contains the actionable engineering implementations. This is where your team generates specific geometries, component choices, and material selections under each Tier 2 branch.

Under the "Latent heat absorption" concept, your Tier 3 ideas might include:

• Micro-encapsulated paraffin wax slurries mixed into the cell potting compound.
• Hydrated salt pouches positioned between cylindrical cell walls.
• Solid-to-liquid organic wax sheets integrated with structural ribs.
• Open-cell aluminum foam infiltrated with solid phase-change matrices.
• Direct-contact evaporative dielectric fluids that boil at 45°C.

Every idea in Tier 3 is a testable, prototype-ready direction.

The Mathematical Cascade: 1 to 4 to 20

The structural power of the Concept Fan comes from simple branch mathematics:

           [ 1 Purpose ]
                 |
   +-----+-------+-------+-----+
   |     |               |     |
 [ C1 ] [ C2 ]         [ C3 ] [ C4 ]
   |     |               |     |
 [5x]  [5x]            [5x]  [5x]
   |     |               |     |
   +-----+-------+-------+-----+
                 |
                 v
       [ 20 Specific Ideas ]

When you define 1 clear Purpose, map 4 distinct Scientific Concepts, and generate 5 Specific Ideas under each, you produce 20 distinct technical paths.

According to research published by the Product Development & Management Association (PDMA), projects that evaluate at least 20 discrete technical alternatives in front-end exploration achieve 38% faster transitions from design freeze to manufacturing validation compared to teams that evaluate 5 or fewer concepts.

Mapping these paths on a Systems Thinking Canvas for Product Teams ensures that upstream dependencies between branches do not surprise your engineering leads during stage-gate reviews.

Once your board is populated with 20 distinct paths, the challenge shifts from generation to structured execution. Next, let’s walk through the 6-step facilitation protocol to run this exercise with an engineering squad in under 90 minutes.

The 4-Step Protocol for Facilitating an R&D Fan Session

A Concept Fan is a structured visual framework developed by Edward de Bono that maps a central problem backward to high-level purposes, then forward into multiple alternative operating principles and specific technical execution paths.

Run this 45-minute facilitation protocol when your engineering team hits an impasse on a single component or architecture.

[ Tier 1: Broader Goal ]
         |
         v
[ Tier 2: Operating Principle ]
         |
         v
[ Tier 3: Technical Implementation ]

Step 1: Pinpoint the Immediate Technical Constraint

State the exact point of physics, software logic, or material failure blocking the project. Avoid broad complaints like "the battery runs out too quickly." Write the exact mechanical limitation on the board: "The lithium-ion pack exceeds 65°C under a 45W continuous load within 12 minutes."

According to a 2021 McKinsey survey on R&D productivity, project teams that spend less than 15% of their sprint cycle rigorously isolating root constraints experience a 2.4x higher rework rate in pilot production. Ground your failure point in measurable engineering telemetry before moving to ideation.

Step 2: Ladder Up to the Broader Goal (Tier 1)

Force the room to step back one altitude level by asking: "What functional outcome are we actually trying to achieve here?" If the constraint is cooling a battery pack, the Tier 1 goal is not "cool the battery faster." The Tier 1 goal is "maintain safe internal operating temperatures during peak compute cycles."

This shift separates the desired system state from the current hardware setup. It mirrors the deconstruction methods used in a 60-Min First Principles Workshop for R&D (With Template). Record this functional objective as your single Tier 1 anchor on the left side of your canvas.

Step 3: Branch Horizontally into Tier 2 Operating Principles

Generate 3 to 5 fundamentally different operating principles to achieve the Tier 1 goal. An operating principle is a general mechanism or physical approach, not a finished product feature.

For the thermal management problem, 4 distinct Tier 2 branches might be:

• Minimize heat generation at the silicon level.
• Conduct heat away from the cell housing via passive dissipation.
• Absorb thermal spikes dynamically using phase-change materials.
• Throttle compute workloads based on predictive ambient thresholds.

Enforce a strict rule during this 10-minute step: zero evaluation of manufacturing costs or current tooling limits. Edward de Bono emphasized in Serious Creativity (1992) that evaluating practicality during the concept-generation stage prematurely collapses alternative pathways back into familiar, incremental designs. Capturing pure operating principles keeps the team aligned with a disciplined Concept Development Process.

Step 4: Cascade Down to Tier 3 Technical Implementations

Split the room into pairs and assign one Tier 2 branch to each group. Give them 15 minutes to generate at least 5 concrete, technical implementations for their assigned branch. Keep a clear visual countdown visible on screen to maintain momentum.

By demanding 5 execution paths across 4 operating principles, the team builds a matrix of 20 distinct technical paths. For example, under the "Conduct heat away" branch, the sub-team might log:

1. Vapor chamber integrated directly into the chassis baseplate.
2. Synthetic diamond thermal interface material with 1,500 W/mK conductivity.
3. Micro-channel liquid cooling loop driven by a piezoelectric pump.
4. Graphene heat-spreading sheets wrapped around individual cells.
5. High-emissivity ceramic surface coating on external enclosure walls.

Document every implementation as a testable technical hypothesis. This yields a complete, structured map of 20+ radical alternatives generated in under an hour.

Once your board is filled with 20 raw concepts, the challenge shifts from generation to rigorous filtering against your unit economics and delivery timeline.

Worked Case Study: 22 Alternative Solutions to Battery Heat Dissipation

Thermal degradation is the irreversible loss of battery energy capacity, cycle life, and power output caused when cell operating temperatures exceed safe electrochemical stability limits during heavy discharge.

When an electric powertrain battery pack overheats under peak load, engineering teams routinely jump to obvious fixes. They ask for a larger radiator, a higher-capacity liquid pump, or thicker cooling lines. These incremental fixes add weight, consume pack volume, and drive up production costs without solving the root issue.

Applying Edward de Bono’s Concept Fan framework breaks this fixation by systematically stepping back from the technical bottleneck to broader functional levels.

[Bottleneck: Overheating Pack]
               |
               v
     [Level 1: Purpose]
 Prevent Thermal Degradation
               |
 +-------------+-------------+
 |             |             |
 v             v             v
[Concept A]   [Concept B]   [Concept C]
Phase Change  Active Air    Reduce Heat
Absorption    Cooling       Generation
 |             |             |
 +-------------+-------------+
               |
               v
          [Concept D]
       Structural Conduction

You move from the immediate physical constraint to the functional purpose, identify multiple operational concepts, and then generate concrete execution ideas under each concept. Using structured concept development strategies prevents your team from anchoring on the first workable design.

To map these directions quickly with your engineering group, mount a sticky pad on a whiteboard and assign one concept branch per column.

According to thermal management datasets from the National Renewable Energy Laboratory (NREL), passive and structural cooling alternatives can reduce total thermal management system mass by up to 28% compared to oversized active fluid systems.

Below is the complete 22-solution inventory generated across the four broad concepts.

Concept 1: Phase Change Thermal Absorption

Phase change material is a substance that absorbs or releases large amounts of latent heat when transitioning between solid and liquid states at a set temperature threshold.

1. Paraffin wax cell jackets: Solid-to-liquid paraffin wax sleeves surrounding individual 21700 cylindrical cells to buffer transient heat spikes.
2. Micro-encapsulated slurry: Organic phase-change micro-capsules suspended in a dielectric carrier fluid pumped directly through hollow busbars.
3. Hydrated salt baseplates: Salt-hydrate pouches placed directly beneath terminal connections to absorb localized resistive heat.
4. Polymer matrix spacers: Structural inter-cell spacers fabricated from cross-linked polyethylene blended with 40% paraffin.
5. Low-melting alloy fuses: Bismuth-tin alloy thermal shunts that melt at 58°C, transferring latent heat to the external chassis frame.

Concept 2: Active Airflow Cooling

6. Cabin exhaust venting: Diverter valves routing 18°C air conditioning exhaust across high-draw module clusters during acceleration.
7. PWM blower arrays: Dedicated pulse-width modulation blowers that trigger 50 CFM airflow pulses only when current exceeds 300A.
8. Vortex tube spot coolers: Compressed air vortex tubes directed exclusively at positive terminal interconnects.
9. Bidirectional intake ducting: Reversible intake flaps that alternate airflow direction every 30 seconds to equalize cell-to-cell thermal gradients.
10. Underbody Venturi scoops: Aerodynamic NACA ducts beneath the chassis floor that pull passive ambient air through the pack during vehicle motion.

Concept 3: Heat Generation Reduction

11. Pulsed discharge modulation: High-frequency pulse modulation profiles that reduce internal resistance losses during peak torque commands.
12. Dynamic impedance balancing: Real-time MOSFET switching networks that divert peak current away from cells with higher internal resistance.
13. Tabless foil electrodes: Cylindrical cells with continuous tabless foil ends to reduce internal ohmic heating by 50%.
14. Thermal torque-derating curves: Algorithmic governor reducing peak current by 8% once any internal thermocouple registers 50°C.
15. Series-parallel dynamic switching: Relays that shift module topology from 400V series to dual-parallel during sustained low-speed crawling.
16. Pre-cooling cycle handoffs: Software protocols initiating sub-ambient chiller runs during the final 10 minutes of stationary fast charging.

Concept 4: Structural Thermal Conduction

17. Pyrolytic graphite sheets: 0.05 mm flexible synthetic graphite sheets laminated along the side walls of every cell row.
18. Boron nitride potting: Chassis cavities filled with a dielectric polyurethane resin doped with 30% boron nitride for 3.5 W/m-K thermal conductivity.
19. Integrated copper vapor chambers: Sealed, flat copper vapor chambers built directly into the bottom battery enclosure lid.
20. Carbon-nanotube thermal pads: Compressible interface pads with 12 W/m-K vertical thermal conductivity placed between modules and side rails.
21. Load-bearing cold floorplates: Extruded aluminum bottom plates that act as structural floor pans and primary conduction sinks.
22. Beryllium copper spring clamps: Interconnect clamps that compress busbars against the external aluminum chassis under mechanical tension.

Once your team generates a broad inventory like this, use structured matrices to prioritize R&D projects based on mass, manufacturing cost, and tooling lead time.

The next step is evaluating how many of these 22 options your current architecture can support without a complete packaging redesign.

Screening Matrix: Filtering 20 Concepts into 3 Viable R&D Prototypes

Twenty raw concepts from a Concept Fan will stall your lab if you try to build them all at once. You must cut 85% of your list within 48 hours while keeping the high-risk, high-reward mechanisms intact.

In his 1991 book Total Design, University of Strathclyde engineer Stuart Pugh introduced matrix-based concept selection to systematically compare engineering alternatives against a baseline product.

A concept screening matrix is a structured scoring tool that evaluates multiple technical ideas against specific criteria like cost, feasibility, and differentiation relative to a fixed baseline standard.

Using this disciplined scoring approach prevents the loudest engineer in the room from dictating which prototype moves to the bench.

       [ 20 Raw Concepts ]
               |
               v
  [ Gate 1: Physics Sanity Check ]
    (Drop 10 unviable concepts)
               |
               v
   [ Gate 2: Weighted Matrix ]
 (Score Feasibility, Cost, Delta)
               |
               v
    [ Gate 3: Mechanism Pivot ]
               |
               v
    [ 3 Sprint Prototypes ]

The Three Screening Criteria

Evaluate every Concept Fan branch using three strict dimensions:

1. Technical Feasibility (40% Weight): Can this operate within real thermodynamic, mechanical, or computational limits? Score this using NASA’s Technology Readiness Level (TRL) scale, requiring surviving concepts to have demonstrable basic principles (TRL 2 or higher).
2. Cost-to-Test (30% Weight): Can your team build a minimum viable test rig for under $3,500 in fewer than 10 business days? If validating the idea requires an 8-week custom tooling cycle, it belongs in long-term exploration, not a rapid prototype sprint.
3. Strategic Differentiation (30% Weight): Does this concept create patentable intellectual property or deliver a 3x efficiency jump over the incumbent design? If a concept scores high on feasibility but produces an identical end-user experience, drop it.

To speed up this quantitative evaluation across cross-functional engineering teams, you can adapt the tools in our Prioritize R&D Projects: 3 Matrices (Excel Template).

Fast-Failure Triage: Kill the Implementation, Save the Mechanism

Do not discard a radical concept just because its initial packaging fails basic constraints. Separate the fundamental physical mechanism from the delivery container.

For example, when Dyson engineers worked on cyclonic separation, early bench tests clogged due to static charge buildup on acrylic tubes. Instead of abandoning cyclonic airflow, they kept the core fluid dynamic mechanism and swapped the housing material to an anti-static carbon-filled resin.

If a concept fails your feasibility check, run a 60-Min First Principles Workshop for R&D (With Template) before deleting the card. Strip away standard assembly assumptions, isolate the single operating principle, and ask if a cheaper geometry makes the physics work.

Once you have isolated your final 3 prototype candidates, you must document the underlying logic so downstream teams understand why the other 17 branches were cut.

The Copy-Paste Concept Fan Markdown Template & R&D Worksheet

Copy the canvas below directly into your workspace notes in Obsidian, Notion, or Jira. It structures Edward de Bono’s Concept Fan framework into four distinct levels: the core technical bottleneck, broad directions, conceptual approaches, and specific execution ideas.

A Concept Fan is a structured lateral thinking diagram that steps backward from a technical problem to find alternative purposes, directions, and solutions.

# Concept Fan: Technical Constraint Canvas

**Target Bottleneck:** [Define the exact technical constraint]  
**Facilitator:** [Name] | **Date:** [YYYY-MM-DD] | **Timebox:** 45 Mins  
**Primary Metric Target:** [e.g., Reduce thermal output by 35% without added weight]

---

### Level 1: The Core Objective (Step Back)
*What broader outcome are we trying to achieve by solving this?*
- Broad Purpose: 

---

### Level 2: Broad Directions (De Bono Directions)
*What are 2–3 different paths to satisfy that broader outcome?*
- Direction A: 
- Direction B: 
- Direction C: 

---

### Level 3: Conceptual Approaches (Concepts)
*What distinct mechanisms can execute each direction?*
- For Direction A:
  - Concept A.1: 
  - Concept A.2: 
- For Direction B:
  - Concept B.1: 
  - Concept B.2: 

---

### Level 4: Concrete Implementation Ideas (20+ Ideas)
*Specific technical executions, components, or methods:*
1. [ ] 
2. [ ] 
3. [ ] 
4. [ ] 
5. [ ] 
...
20. [ ] 

[Core Technical Bottleneck]
         |
         v
  [Step Back: Purpose]
         |
    +----+----+
    |         |
    v         v
[Dir A]     [Dir B]
    |         |
  +-+-+     +-+-+
  |   |     |   |
  v   v     v   v
[C.1] [C.2] [C.3] [C.4]
  |     |     |     |
 [Ideas: 5 per concept]

45-Minute Workshop Facilitator Script

Running a Concept Fan session requires tight timekeeping. If engineers start debating feasibility too early, they stop producing novel branches. Use a physical visual timer during the session so the entire room tracks pacing without interrupting the flow.

You can pair this session with our 60-Min First Principles Workshop for R&D (With Template) or use it to feed directly into your Concept Development Process.

Block	Duration	Phase	Facilitator Script & Action
01	00:00–00:05 (5 min)	Define Bottleneck	"We are stuck on [X]. Do not propose fixes yet. Write the exact physical or code limitation on the board in one sentence."
02	00:05–00:15 (10 min)	The ‘Step Back’ (Broad Purpose)	"Ask: If we solve this, what does it let us do? We are stepping back one altitude level to find 2 to 3 broad directions."
03	00:15–00:30 (15 min)	Branching Concepts	"Take Direction A and Direction B. Silently write 2 distinct mechanical, software, or material approaches for each on sticky notes."
04	00:30–00:40 (10 min)	Idea Sprint (Target: 20+)	"Flesh out 5 concrete executions under every single concept branch. No filtering. We need a count of 20 distinct technical paths."
05	00:40–00:45 (5 min)	Cluster & Select	"Pick the top 3 high-impact anomalies to advance to validation testing."

According to research published in the International Journal of Design Creativity and Innovation, structured divergence tools like the Concept Fan increase solution diversity by over 40% compared to unstructured brainstorming sessions.

+-------------------------------------------+
| 45-MINUTE AGENDA BREAKDOWN                |
| 00-05m: Define Bottleneck (5m)            |
| 05-15m: Step Back to Purpose (10m)        |
| 15-30m: Branching Concepts (15m)          |
| 30-40m: Idea Sprint - 20+ Ideas (10m)     |
| 40-45m: Cluster & Select (5m)             |
+-------------------------------------------+

Facilitator Troubleshooting Checklist

When technical teams get bogged down in implementation weeds, apply these three targeted interventions:

• Symptom: Team jumps straight to component specs.
  Correction: Ask the "Why" question to force an altitude shift. "Why do we need a 400W power unit here? To handle peak thermal spikes. Great, so our broader direction is peak thermal dissipation, not power sourcing."
• Symptom: Team claims a branch is physically impossible.
  Correction: Park physics for 8 minutes. Refer to your team’s guidelines in the Align R&D: A 5-Part Creative Charter (With Template). Remind them that Level 3 is for directional hypotheses, while Level 4 contains the testable builds.
• Symptom: Output stalls at 6 to 8 ideas.
  Correction: Force an inversion constraint. Ask: "What is the exact opposite of Concept A.1?" Forcing deliberate polar opposites consistently breaks through idea plateaus. Once generated, score the resulting batch with our guide to Prioritize R&D Projects: 3 Matrices (Excel Template).

Frequently Asked Questions

How does a Concept Fan differ from a standard Mind Map?

A Mind Map uses associative thinking to link related words or loose ideas radially. A Concept Fan uses hierarchical de-escalation developed by Edward de Bono. It forces you to step backward from a problem to a broader purpose, split that purpose into directions, divide directions into concepts, and finally cascade into specific implementation ideas.

What is the ideal team size for an R&D Concept Fan session?

The ideal group size is 4 to 7 participants. Research from Harvard Business School by Professor Boris Groysberg demonstrates that problem-solving groups larger than 8 experience severe coordination losses and diminished per-person idea volume. Ensure at least one cross-functional discipline participates, such as software, thermal, or materials engineering.

How should we evaluate the 20+ ideas after the 45-minute workshop?

Do not evaluate during the generation phase. Run the generated list through an Impact vs. Technical Feasibility 2×2 matrix immediately after the session. You can streamline this downstream workflow using our structured guide on Concept Development Strategies.

Paste this Markdown canvas into your team scratchpad today, gather 4 cross-functional engineers for a 45-minute block, and generate your 20 alternative paths before your next technical review.

Sources & Further Reading

Functional fixedness is a cognitive bias where an engineer or designer perceives an object or mechanism as only functioning in its traditional, established manner, which blocks novel mechanical solutions.

Systematic R&D methodologies break this bias by decoupling the root objective from existing implementation pathways. In his foundational research analyzing over 200,000 patents across global industry databases, Soviet engineer Genrich Altshuller demonstrated that 95% of inventive technical problems had already been solved in adjacent disciplines using equivalent functional abstractions. Grounding your brainstorming in proven structured methods prevents your technical teams from recycling the same three linear assumptions.

To run a physical Concept Fan mapping session with your hardware or software architecture team, map your central bottleneck onto a large wall format using a self-stick tabletop easel pad.

Featured image by Karolina Grabowska www.kaboompics.com on Pexels