--- title: "Brainstorming Methods - Detailed Guide" description: "A comprehensive reference for understanding and applying brainstorming methods. Use this when you want to understand a method before applying it, or when exploring which approach fits your situation." type: skill canonical_url: https://claudary.paisolsolutions.com/skills/methods-detailed source: "Claudary" difficulty: intermediate author: "Claude Code Knowledge Pack" date: 2026-07-10T11:31:00.459Z license: CC-BY-4.0 attribution: "Brainstorming Methods - Detailed Guide — Claudary (https://claudary.paisolsolutions.com/skills/methods-detailed)" --- # Brainstorming Methods - Detailed Guide A comprehensive reference for understanding and applying brainstorming methods. Use this when you want to understand a method before applying it, or when exploring which approach fits your situation. ## Overview # Brainstorming Methods - Detailed Guide A comprehensive reference for understanding and applying brainstorming methods. Use this when you want to understand a method before applying it, or when exploring which approach fits your situation. --- ## Divergent Methods These methods help generate new ideas, break out of mental ruts, and expand the possibility space. ### SCAMPER **What it is:** A systematic checklist of prompts that force you to look at an existing concept from seven different angles. **The prompts:** - **S**ubstitute — What components, materials, or people could you swap out? - **C**ombine — What could you merge with something else? - **A**dapt — What could you borrow from another domain or context? - **M**odify — What could you magnify, minimize, or alter? - **P**ut to other uses — What else could this be used for? - **E**liminate — What could you remove entirely? - **R**everse/Rearrange — What if you flipped the order or orientation? **When to use:** You have an existing idea, product, or concept and want to systematically explore variations. **How to apply:** 1. Clearly state the current concept 2. Work through each letter, spending 2-3 minutes generating options 3. Don't judge during generation—capture everything 4. Review and identify the most promising variations **Example:** Brainstorming improvements to a newsletter - Substitute: What if it was audio instead of text? What if readers wrote it? - Combine: Newsletter + community forum? Newsletter + course? - Adapt: How do podcasters build audience? How do academic journals work? - Modify: What if it was daily instead of weekly? 10x longer? 10x shorter? - Put to other uses: Could the research become a book? A consulting framework? - Eliminate: What if there were no links? No images? No consistent schedule? - Reverse: What if readers pitched topics to you? What if you wrote about what NOT to do? --- ### Random Stimulus **What it is:** Introducing an unrelated word, image, or concept and forcing yourself to find connections to your problem. **When to use:** You're stuck in a mental rut, all ideas feel similar, or you need genuinely novel thinking. **How to apply:** 1. State your problem clearly 2. Generate a random stimulus (random word generator, open a book to random page, use a random image) 3. List attributes, associations, and characteristics of that stimulus 4. Force connections: "How might [attribute] apply to my problem?" 5. Develop any promising connections into actual ideas **Example:** Problem: "How to make MVPKit stand out" - Random word: "Lighthouse" - Associations: guidance, warning, coastal, beam of light, solitary, automated, historic - Forced connections: - "Guidance" → What if MVPKit included decision frameworks, not just code? - "Warning" → What if it flagged common MVP mistakes as you build? - "Beam of light" → What if it highlighted the ONE thing to focus on next? - "Automated" → What if the kit self-configured based on your answers? --- ### Forced Analogies **What it is:** Deliberately applying thinking from a different domain, industry, or persona to your problem. **When to use:** You want fresh perspectives or suspect your industry has blind spots. **How to apply:** 1. State your problem 2. Choose an unrelated domain (another industry, a historical period, a fictional universe, a specific person) 3. Ask: "How would they approach this?" or "How does this work in that domain?" 4. Extract principles and apply them to your context **Common analogy sources:** - Industries: How would a restaurant/hospital/airline handle this? - People: How would Bezos/your grandmother/a 5-year-old see this? - Nature: How do ecosystems/ant colonies/immune systems solve this? - History: How did pre-digital/medieval/ancient societies handle similar challenges? **Example:** Problem: "How to build community around a technical product" - Analogy: "How do churches build community?" - Observations: Shared rituals, regular gatherings, mentorship structures, shared mission, service opportunities, small groups within larger body - Applied: Weekly office hours (ritual), mentorship pairing for new users, clear mission statement, contribution pathways, cohort-based onboarding --- ### Worst Possible Idea **What it is:** Deliberately generating terrible, absurd, or counterproductive ideas, then examining what makes them bad and inverting. **When to use:** The group is self-censoring, ideas feel too "safe," or you need to loosen up. **How to apply:** 1. State the challenge 2. Ask: "What's the worst possible way to handle this?" 3. Generate genuinely bad ideas (not just mediocre—actively terrible) 4. For each bad idea, identify WHY it's bad 5. Invert: What's the opposite? What principle does this reveal? **Example:** Challenge: "Improve customer onboarding" - Worst ideas: - Require 47-step registration - Send 20 emails on day one - Hide all documentation - Make them figure out pricing after they've built something - Inversions: - Minimize required steps—what's the absolute minimum? - One well-timed email is better than many - Documentation should be discoverable in context - Pricing clarity before commitment builds trust --- ## Convergent Methods These methods help organize, prioritize, and narrow down options. ### Affinity Grouping **What it is:** Organizing ideas into clusters based on natural relationships, then naming those clusters. **When to use:** You have many ideas and need to see patterns and themes. **How to apply:** 1. List all ideas (on cards, sticky notes, or a list) 2. Look for ideas that "belong together"—don't force categories yet 3. Group similar ideas together 4. Name each cluster with a descriptive label 5. Look for clusters that are dense (lots of energy there) vs. sparse 6. Identify gaps: What categories are missing? **Tip:** Let groups emerge naturally rather than pre-defining categories. The naming often reveals insight. --- ### Weighted Scoring **What it is:** Evaluating options against explicit criteria with assigned weights. **When to use:** Complex decisions where multiple factors matter and you need to make tradeoffs explicit. **How to apply:** 1. Define criteria (3-7 factors that matter) 2. Assign weights to each criterion (must sum to 100%) 3. Score each option on each criterion (e.g., 1-5 scale) 4. Calculate weighted scores 5. Use scores as input, not final answer—discuss surprises **Example criteria for evaluating product ideas:** - Market size (20%) - Technical feasibility (15%) - Competitive differentiation (20%) - Alignment with skills/interests (15%) - Revenue potential (15%) - Time to MVP (15%) **Warning:** The value is in the conversation about weights and scores, not the final number. If the "winner" feels wrong, examine why. --- ### 2x2 Matrix **What it is:** Plotting options on two dimensions to reveal clusters and tradeoffs. **When to use:** You need to compare options and want to make tradeoffs visual. **How to apply:** 1. Choose two important dimensions (often tension exists between them) 2. Draw the matrix with dimensions as axes 3. Plot each option in the appropriate quadrant 4. Discuss what each quadrant represents 5. Look for options in the desirable quadrant; discuss whether others can be moved **Classic dimensions:** - Impact vs. Effort - Urgent vs. Important - Feasibility vs. Desirability - Risk vs. Reward - Short-term vs. Long-term value --- ## Problem-Framing Methods These methods help ensure you're solving the right problem. ### First Principles Thinking **What it is:** Breaking down a problem to its fundamental truths and rebuilding from there, rather than reasoning by analogy or convention. **When to use:** Conventional approaches aren't working, or you suspect you're trapped by inherited assumptions. **How to apply:** 1. State the problem or goal 2. Ask: "What do we know to be absolutely true here?" (not assumed, not conventional—proven) 3. List only foundational facts 4. Rebuild: "Given only these truths, what options exist?" 5. Compare to conventional thinking—where do they diverge? **Example:** "How should I price my course?" - Conventional: "Look at competitor pricing and position accordingly" - First principles: - What do I know? The course costs me X hours to create. Students get Y outcome. Market has Z alternatives. - What's actually true about pricing? Price = perceived value. Value = outcome achieved + experience + certainty. - Rebuild: What would I charge if competitors didn't exist? What outcome am I actually selling? --- ### 5 Whys **What it is:** Repeatedly asking "why" to drill past symptoms to root causes. **When to use:** You're treating symptoms rather than causes, or the real problem isn't clear. **How to apply:** 1. State the problem 2. Ask "Why does this happen?" or "Why is this a problem?" 3. Take the answer and ask "Why?" again 4. Repeat until you reach a root cause (usually 3-7 iterations) 5. Verify: Would solving this root cause address the original symptom? **Example:** - Problem: "I'm not making progress on my book" - Why? "I never have time to write" - Why? "Other tasks keep taking priority" - Why? "Writing feels less urgent than client work" - Why? "Client work has deadlines and the book doesn't" - Why? "I haven't committed to a deadline or accountability structure" - Root cause: Missing commitment structure, not missing time --- ### Inversion **What it is:** Instead of asking how to succeed, asking how to guarantee failure—then avoiding those things. **When to use:** You're stuck on the positive framing, you want to identify risks, or you need to challenge assumptions. **How to apply:** 1. State your goal 2. Ask: "How could I guarantee failure at this?" 3. Generate ways to fail (be specific and comprehensive) 4. Invert each one: What's the opposite? 5. Check: Are you currently doing any of the failure-guarantee actions? **Example:** Goal: "Launch a successful newsletter" - Guaranteed failures: - Write about whatever I feel like with no focus - Publish inconsistently - Never promote it - Ignore reader feedback - Make it indistinguishable from existing newsletters - Inversions: - Clear, specific focus - Consistent schedule - Active promotion strategy - Reader feedback loops - Distinctive angle/voice --- ### Jobs-to-be-Done **What it is:** Understanding what "job" the customer is "hiring" your product to do—focusing on the outcome they want rather than the product itself. **When to use:** Product or service ideation, understanding customer motivation, competitive analysis. **How to apply:** 1. Ask: "What is the customer trying to accomplish?" (the job) 2. Ask: "What's the situation or trigger that creates this need?" 3. Ask: "What does success look like for them?" 4. Ask: "What are they currently hiring to do this job?" (competitors, workarounds, doing nothing) 5. Ask: "What's frustrating about current solutions?" **JTBD statement format:** "When [situation], I want to [motivation], so I can [outcome]." **Example:** Analyzing MVPKit - Job: "When I have a validated idea and limited time, I want to ship a working product fast, so I can start getting real user feedback before I burn through my runway." - Current hires: Building from scratch, other boilerplates, no-code tools, hiring contractors - Frustrations: Boilerplates are bloated, no-code limits customization, scratch takes too long --- ## Perspective Shift Methods These methods help you see the problem from different angles. ### Six Thinking Hats **What it is:** A structured way to examine a topic from six distinct perspectives, one at a time. **The hats:** - **White Hat** — Facts and information. What do we know? What don't we know? - **Red Hat** — Feelings and intuition. What's your gut reaction? (No justification required) - **Black Hat** — Caution and risks. What could go wrong? What are the weaknesses? - **Yellow Hat** — Benefits and value. What's good about this? Why might it work? - **Green Hat** — Creativity and alternatives. What else is possible? New ideas? - **Blue Hat** — Process and meta. What hat should we wear next? Are we done? **When to use:** Group discussions that go in circles, decisions where emotions and logic are tangled, need for structured comprehensive analysis. **How to apply:** 1. Define the topic 2. Everyone wears the same hat at the same time 3. Spend 3-5 minutes per hat 4. Blue hat manages the process 5. Capture output from each hat separately --- ### Steelman **What it is:** Building the strongest possible case for a position you disagree with or are skeptical of. **When to use:** Before dismissing an option, testing your own ideas, understanding opposition, avoiding echo chambers. **How to apply:** 1. State the position you're skeptical of 2. Ask: "What would make a reasonable person believe this?" 3. Build the strongest case: best evidence, best arguments, best framing 4. Present it as if you believed it 5. Only after steelmanning, respond with your actual view **Why it matters:** If you can't articulate why smart people disagree with you, you don't understand your own position well enough. --- ### Pre-mortem **What it is:** Imagining the project has failed and working backward to identify what went wrong. **When to use:** Before committing to a plan, when confidence is high (that's when blind spots are biggest), for risk identification. **How to apply:** 1. State the project/decision 2. Imagine: "It's [6 months/1 year] from now. This failed. Why?" 3. Each person writes down reasons for failure independently 4. Share and compile the list 5. Prioritize: Which failure modes are most likely and most severe? 6. Address: What can we do now to prevent these? **Key insight:** It's psychologically easier to explain a failure that "happened" than to imagine one that might happen. --- ### Assumption Surfacing **What it is:** Explicitly identifying the assumptions underlying a plan or belief. **When to use:** Before major commitments, when something feels risky but unclear why, for foundational clarity. **How to apply:** 1. State the plan or belief 2. Ask: "For this to work, what must be true?" 3. List all assumptions (market, technical, resource, behavioral, timing) 4. For each: "How confident are we? What would change our mind?" 5. Identify the riskiest assumptions 6. Ask: "How can we test these before committing?" **Types of assumptions to check:** - Market: Do people want this? Will they pay? - Technical: Can we build it? In this timeline? - Resource: Do we have the time/money/skills? - Behavioral: Will users actually do what we expect? - Competitive: Will the landscape stay favorable? - Timing: Is now the right moment? --- ## Theological/Philosophical Methods These methods bring depth to foundational questions about purpose, assumptions, and stewardship. ### Presuppos --- Source: [Claudary](https://claudary.paisolsolutions.com/skills/methods-detailed) · https://claudary.paisolsolutions.com