$npx -y skills add human-avatar/skills-for-humanity --skill s4h-creativity-concept-fanApply Edward de Bono's Concept Fan to expand the solution space before committing to an approach. Use when the user has a goal or problem and wants to see the full range of ways to achieve it, feels locked into one solution, is evaluating options and wants to make sure they haven
| 1 | You are facilitating a Concept Fan session using Edward de Bono's technique. The Concept Fan is a tool for expanding solution space — it prevents premature commitment to one approach by making the full landscape of alternatives visible first. |
| 2 | |
| 3 | ## Why the concept fan matters |
| 4 | |
| 5 | Most thinking about solutions is too narrow. We take a goal, think of one or two approaches, evaluate them, and pick the best. This feels thorough but it's actually a small sample of the possible solution space. |
| 6 | |
| 7 | The Concept Fan works by moving up and down a ladder of abstraction. At the top is the broadest possible framing of what you're trying to achieve — the pure purpose. At the bottom are specific implementations. Between them are concepts — general approaches that can each spawn multiple implementations. |
| 8 | |
| 9 | By mapping this landscape before committing, you avoid the trap of evaluating implementations when you should still be choosing concepts. |
| 10 | |
| 11 | ## The structure |
| 12 | |
| 13 | Think of a fan with a handle and radiating spokes: |
| 14 | |
| 15 | - **The handle** is the goal — what you're ultimately trying to achieve, stated at its broadest useful level |
| 16 | - **First ring of spokes** are broad concepts — different general approaches to achieving the goal |
| 17 | - **Second ring of spokes** are sub-concepts — more specific approaches within each broad concept |
| 18 | - **Outer ring** are specific implementations — concrete things you could actually do |
| 19 | |
| 20 | The fan expands outward from abstract to specific. At each level, the question is: "What are all the different ways to achieve this?" |
| 21 | |
| 22 | ## Your process |
| 23 | |
| 24 | **Step 1: Establish the goal** |
| 25 | State the user's goal at two levels: |
| 26 | - Immediate goal: what they said they want |
| 27 | - Purpose level: why they want it — the underlying need it serves |
| 28 | |
| 29 | The purpose level is important because it sometimes reveals entirely different solution families that address the real need without solving the stated problem. |
| 30 | |
| 31 | **Framing check:** Confirm the specific challenge before continuing. State what you've identified — the actual goal being pursued and the purpose level behind it — in one sentence, then use `AskUserQuestion`: |
| 32 | - **Question:** "I'm reading this as: [your one-sentence framing of the goal and its underlying purpose]. Is that right?" |
| 33 | - **Header:** "Framing" |
| 34 | - **Options:** |
| 35 | - **Yes — proceed** — framing is correct |
| 36 | - **Adjust** — one element is off; user will correct it before you continue |
| 37 | - **Reframe** — different situation than read; incorporate the correction before proceeding |
| 38 | |
| 39 | **Step 2: Generate broad concepts (first ring)** |
| 40 | At the concept level, ask: "What are all the fundamentally different approaches to achieving this goal?" These should be distinct families of solutions, not variations on the same approach. |
| 41 | |
| 42 | Aim for 4–7 broad concepts. They should feel genuinely different from each other — different mechanisms, different assumptions, different resources they draw on. |
| 43 | |
| 44 | **Step 3: Expand each concept (second ring)** |
| 45 | **Before narrowing:** Show the complete set of broad concepts generated in Step 2 to the user first. Use `AskUserQuestion`: |
| 46 | - **Question:** "I've identified [N] broad concepts. Before I select the most promising to expand, are there any you'd flag as especially important, or any I've missed?" |
| 47 | - **Header:** "Prioritise" |
| 48 | - **Options:** |
| 49 | - **Proceed with your selection** — the set looks right |
| 50 | - **Flag one** — user will name a specific concept to prioritise for expansion |
| 51 | - **Add a missing one** — user will describe a concept family not yet on the list |
| 52 | |
| 53 | For 2–3 of the most promising broad concepts, generate 3–4 sub-concepts — more specific versions that show the range within that approach family. |
| 54 | |
| 55 | **Step 4: Generate specific implementations (outer ring)** |
| 56 | For the most interesting sub-concepts, suggest 2–3 concrete implementations — actual things that could be done. |
| 57 | |
| 58 | **Step 5: Highlight the overlooked** |
| 59 | After mapping the fan, identify: which concepts or sub-concepts did the user probably not consider before this exercise? These are the fan's main value — the alternatives that only become visible when you systematically expand the space. |
| 60 | |
| 61 | ## Human Check-in |
| 62 | |
| 63 | Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask: |
| 64 | |
| 65 | - **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?" |
| 66 | - **Header:** "Scope" |
| 67 | - **Options:** |
| 68 | - **Full analysis** — Complete all steps, reasoning shown throughout |
| 69 | - **Key findings only** — Bottom-line output, skip step-by-step detail |
| 70 | - **Concept level only** — Mid |