What ideation is and why structure matters
Ideation is the stage in the design process involving the fast-paced generation of many ideas, where the priority is diversity of output rather than quality of any single idea. Traditional brainstorming — gathering people in a room to throw out ideas — has been consistently shown to produce fewer and lower-quality ideas than structured methods. The reasons are well-documented: production blocking (only one person can speak at a time), evaluation apprehension (people self-censor), social loafing (some coast while others carry), and anchoring (early ideas constrain later thinking).
Research bears this out. In an NN/g survey of UX professionals, only 18% rated their ideation process as effective. But among those who described their process as "very effective," 87% reported conducting some form of ideation before prototyping — not after. Effective ideation happens earlier in the design process, when the solution space is still open.
Diverge, then converge
Every creative method operates in one of two modes. Divergent methods expand options — generating as many ideas as possible without judgment. Convergent methods narrow options — evaluating, clustering, and selecting the best ideas. The critical rule: never diverge and converge simultaneously. When generating, defer all judgment. When evaluating, stop generating. Mixing the two modes kills both creativity and critical thinking.
Why structure improves creativity
Research on task instructions and creative performance shows that structure and constraint can improve creative thinking rather than limit it. Constraints help narrow focus, reframe the problem, and push participants past obvious solutions. A blank canvas is the enemy of creative output — a well-chosen constraint is its catalyst.
The desirability–viability–feasibility lens
During ideation, the focus is on user desirability — does it support user goals, needs, motivations, and behaviors? After ideation, selected ideas must also pass through business viability (is it profitable, fundable, aligned with goals?) and technical feasibility (can it be built, will it work, is it maintainable?). Keep all three lenses visible, but during divergent ideation, lead with desirability.
Setting up an ideation session NN/g
Timing and pacing
Keep ideation sessions under 3 hours. Take breaks as needed — creativity degrades with fatigue. The "Shower Principle" (inspiration arriving while the brain is distracted from the problem) is real: sleeping on a problem between sessions often produces better results than grinding through in one marathon. Dedicate 5–20% of total ideation time to warm-up activities before tackling the real problem.
Overcoming ideation stigma
If there's organizational resistance to "ideation" as a concept: involve decision-makers directly (builds buy-in through participation), call it something else ("design workshop" or "solution sprint"), plan time for ideation from the project start rather than squeezing it in, and pick formats that fit your team's culture.
Group composition
Ideation works at three scales: alone (deep focus, no social friction), in pairs (quick feedback loops), and in groups (diverse perspectives). The more people in a session, the harder it is to manage — keep ideation groups under 10 people. When deciding who to invite, consider roles (diverse disciplines mean diverse ideas), timing (earlier in the process allows for more multidisciplinary participation), personalities (consider conflict dynamics), and goals (do you need an implementable idea quickly, or do you want to explore all options?).
Have a dedicated facilitator who ideally does not contribute ideas. The facilitator sets the scope, establishes and enforces rules, keeps the group focused and within time limits, monitors group emotions and communication, and manages the parking lot — a dedicated space for documenting unrelated questions and ideas that arise during the session.
Defining the ideation goal
Clearly state the goal and keep it visible throughout the session. Any idea that doesn't relate goes into the parking lot. The goal sets the scope: a wider goal ("attract more new users") produces more variety and "blue sky" thinking; a narrower goal ("encourage current users to share content on other platforms") produces more practical, implementable ideas. Timing in the design process also influences scope — earlier stages allow broader goals, later stages demand narrower ones.
Before starting, get everyone on the same page by answering: Why are we here? What will we be doing? What background information do we need? What's our goal? How will we know if we're successful? What are we going to do with these ideas? What happens next?
The five rules of ideation
Five Rules of Ideation Framework
Use when: kicking off any ideation session — state these rules explicitly.
1. Focus on the user. Every idea should address user goals, needs, and behaviors. 2. Quantity over quality. The goal is volume and diversity — most ideas will be discarded, and that's the point. 3. No such thing as a bad idea (for now). Defer all judgment during divergent phases. A positive mood improves creative intuition. Adopt the improv mindset: "Yes, and…" 4. Stay focused. No multitasking, take breaks, consider banning devices, send unrelated ideas to the parking lot. 5. Document everything. Sketch, write, photograph. If it's not captured, it didn't happen.
Remote and hybrid ideation
Synchronous remote ideation (everyone contributes together at the same time) offers fast idea exchange and focused attention, but is tough to schedule and can feel awkward. Asynchronous ideation (everyone contributes over days or weeks) is more convenient and gives ideas time to incubate, but requires self-motivation and loses the energy of real-time exchange. Choose synchronous when you need a solution quickly; choose asynchronous when people need time to consider.
For remote sessions: assign a remote facilitator, use a warm-up activity to avoid silent lurkers, plan for technical mishaps, and ensure equal communication — if some teammates are remote, all should work digitally, even those who are co-located. Use breakout rooms for large groups. Tools range from collaborative canvases (Miro, FigJam, MURAL) to simple shared documents.
Warm-up techniques NN/g
Warm-ups set the creative tone, build psychological safety, and establish the "play" mindset before tackling the real problem. Use non-threatening, unrelated, fun challenges. Dedicate 5–20% of ideation time to warming up.
Telephone Warm-up
Use when: encouraging playfulness and practicing idea-building. 10–15 min, 3–8 people.
Each team member starts drawing or writing a solution on a sheet of paper. After two minutes, everyone passes their paper to the right and works on their neighbor's idea. Keep rotating until papers return to their original owners. The result is a chain of collaborative evolution — ideas morph in unexpected directions. Alternative: have people stand and move to the next chair rather than moving papers.
Opposite Day Warm-up / Technique
Use when: the team needs to see the problem differently. 15–30 min, 1+ people. Works solo and remote.
Flip the design goal: imagine you're trying to achieve the opposite outcome. If the goal is "make checkout easier," the opposite goal is "make checkout as difficult as possible." Generate "evil" ideas, then flip them into good ones. "Force users to pay only in cryptocurrency" flips to "offer a wide variety of payment methods." This works because it's psychologically safe (you can't fail at being bad), breaks anchoring, and the inversions often reveal genuinely novel solutions.
Mission Impossible Warm-up
Use when: turning constraints into opportunities. 5–10 min, 1+ people. Works solo and remote.
Take an existing product or idea, add an aspect that makes it seemingly impossible (a car with no wheels, a house built in a single day), and generate ideas to accomplish the impossible version. The technique identifies core obstacles and forces creative workarounds — a house built in one day leads to 3D-printed modular components, prefabricated assembly, and just-in-time logistics.
Toddler (Five Whys for Ideation) Warm-up / Technique
Use when: you need to focus on the core need, not the current implementation. 5–15 min, 1+ people.
Ask "why?" repeatedly until you hit the root cause or underlying need. Why does a car need keys? To prevent unauthorized access. That reframing opens alternative solutions: biometric access, PIN codes, geofencing, phone proximity. The technique separates the need from the current solution, creating space for fundamentally different approaches.
Paper Airplane Warm-up
Use when: establishing collaborative energy for in-person sessions. 5–10 min, 2–10 people in pairs.
Pairs work together to build a paper airplane using only their non-dominant hands. Competition: whose airplane flies farthest? The constraint forces collaboration, the physical craft establishes a "play" feeling, and the competition creates energy. Light, fast, effective for breaking ice.
Finding inspiration for ideation NN/g
Drucker's Eight Sources of Innovation Framework
Use when: scanning for ideation starting points before a session.
Peter Drucker identified eight sources of innovative opportunity, each mappable to UX research methods: 1. An unexpected success or failure (analytics, usability testing, expert evaluation, field studies). 2. A discrepancy between reality and belief (surveys, interviews, focus groups, field studies). 3. A weak link in a process (journey mapping, service blueprints). 4. Changes in industry or market (competitive analysis, competitive usability testing). 5. Demographics (user research, personas). 6. Changes in societal assumptions or beliefs (trend analysis, cultural research). 7. Scientific or technological advances (conferences, blogs, networking). 8. A relevant solution from an unrelated field (analogous inspiration).
Remember the Future Technique
Use when: understanding users' definition of success before generating solutions. From Hohmann's Innovation Games.
Ask participants to imagine a future point (a month, quarter, or year ahead) where they've been using your product continuously. Have them write down precisely how the product has made them successful, happy, or more effective. The responses reveal desired outcomes that become ideation prompts — participants articulate goals they might not express through direct questioning.
Keep research artifacts — personas, journey maps, empathy maps, usability findings, analytics dashboards — visible during ideation sessions. Simultaneous visibility of project materials helps identify patterns and encourages creative synthesis that doesn't happen when resources are hidden away.
Reframing the problem NN/g
When ideas feel stale or narrow, the problem itself may need reframing. These techniques change the lens through which the team sees the challenge, opening new solution directions.
Abstraction Core Method
Use when: you need cross-domain inspiration beyond incremental improvements. 15–45 min, 1+ people.
Rewrite your design problem in more general, abstract terms, then consider what other domains grapple with a similar abstracted problem. NASA needed to send large flat solar arrays to space in narrow rockets. Abstracted: "contain wide, flat material in a confined space of a different shape." Inspiration source: origami. The solution: origami-inspired folding solar panels. For UX: "our search results page is overwhelming" abstracts to "presenting many options without cognitive overload" — inspiration from restaurant menus, museum wayfinding, or airline booking flows.
Laddering Technique
Use when: the problem is either too vague or too specific. 15–30 min, 1+ people.
Move up and down levels of granularity. To abstract upward, ask: "Why? What is this problem an example of?" To get concrete, ask: "How? What would be an example of this problem?" If the problem is "users can't find the settings page," laddering up reveals "users can't configure the product to their needs." Laddering down from "improve the user experience" might surface "reduce the number of steps to complete a purchase."
Modeling Technique
Use when: the team needs shared understanding of a complex system. 15–30 min, 1+ people.
Create visual representations of the system, situation, workflow, feelings, or motivations — using affinity diagrams, flow charts, mind maps, rich pictures, storyboards, or research-informed maps like empathy maps, journey maps, and service blueprints. The act of visualizing cements understanding and reveals structure, gaps, and opportunities that aren't visible in verbal discussion. Optionally use the visual to align understanding with stakeholders.
Bodystorming Technique
Use when: identifying unconsidered aspects of an experience. 30–60 min, 2–10 people. In-person only.
Physically act out an idea, experience, or process. Assign roles — not just human roles like "user" or "customer," but also digital objects (the product, the internet) or physical objects (a phone, a kiosk). Bodystorming reveals spatial, temporal, and emotional dimensions that sketching and discussion miss. It works for acting out the current situation, exploring a potential idea, or testing a candidate concept with improvised props.
Deprivation & Simulation Studies Technique
Use when: building empathy for users whose experiences differ from the team's. 30+ min, 1–4 people.
Put yourself or your team in circumstances similar to your users'. Use aging simulation suits, vision distortion glasses, screen readers, or limited-bandwidth connections. OXO's entire kitchen tool line originated from designing for a user with arthritis — the ergonomic grips benefited everyone. The technique generates ideas grounded in lived experience rather than assumptions.
Ask an Outsider Technique
Use when: the team needs a fresh perspective and is stuck in domain expertise. 10–20 min, 2–4 people.
Summarize the problem for someone unfamiliar with it and optionally collect their ideas (which may or may not be directly useful). The real value is twofold: explaining the problem to an outsider forces you to reaffirm your own understanding, and naive questions often expose assumptions the team has stopped noticing. Alternative: explain the problem to a child — the simplification required is itself a reframing exercise.
Jumping-off points NN/g
These techniques provide external stimuli — cards, trends, personas, constraints — that give ideation a starting point when the blank canvas is paralyzing.
Design Idea Cards Technique
Use when: you need tangible, shuffleable prompts to trigger new directions. 10–30 min, 1+ people.
Use a deck of pre-made cards with design principles, attributes, concepts, or methodologies. Randomly select a card, read it, and try to apply it to your design problem. If nothing comes to mind, draw another. Available decks include IDEO Method Cards, NN/g Design Principle Cards (26 cards covering principles like Progressive Disclosure, Fitts's Law, Aesthetic-Usability Effect, Signal-to-Noise Ratio, Error Forgiveness, and Constraint), 77 Cards for physical products, and Designercise. Teams can also create custom decks with their own design principles or domain-specific prompts.
Trend Projection Technique
Use when: you want to create an extreme, future-facing version of your product. 30–60 min, 1+ people.
Start with a current design or technology trend (AI, augmented reality, voice interfaces, spatial computing). Apply the trend to your product in an extreme, unlimited-budget way. Then scale back to identify what you can use practically. The extreme version removes self-censoring ("that's too ambitious") and often reveals intermediate steps that are achievable. Think beyond the project in front of you.
Systematic Prediction Technique
Use when: shrinking an ideal vision into a practical roadmap. 15–30 min, 1+ people.
Start with an impractical, ideal design. Estimate how long it might take to create (2 years? 5 years?). Then scale back incrementally: if the ideal takes 5 years, what could be done in 2 years? In 1 year? In 6 months? Each step produces a progressively more implementable version of the vision, creating a natural roadmap from aspiration to action.
Design to the Persona Technique
Use when: simplifying the problem by narrowing focus to one user group at a time. 10–30 min, 1+ people.
For each user persona, design a different ideal solution — temporarily ignoring the needs of other users. Then compare persona-specific solutions: which ideas are common across personas? Which are in conflict? The technique prevents the "design for everyone" trap that produces bland, undifferentiated solutions. Combining with Parallel Design (each team member takes a different persona) multiplies the effect.
Edge Cases Technique
Use when: considering extreme users or unusual situations. 10–45 min, 1+ people.
Identify at least one extreme user or situation (a hypochondriac using a telehealth app, someone who distrusts doctors, a user with a poor internet connection). List the challenges those users would face, then generate solutions. Often, solutions designed for extreme users benefit everyone — curb cuts designed for wheelchair users help parents with strollers, delivery drivers with carts, and travelers with luggage.
Brainstorming and rapid ideation methods
Brainwriting (6-3-5) Core Method
Use when: you want many ideas from a group without verbal brainstorming downsides.
Six people each write 3 ideas in 5 minutes, then pass their sheet to the next person, who builds on those ideas with 3 more. After 6 rounds, you have 108 ideas in 30 minutes. Brainwriting eliminates production blocking (everyone writes simultaneously), reduces evaluation apprehension (ideas are semi-anonymous), and prevents anchoring (everyone starts independently). Works asynchronously — distribute sheets digitally with time windows.
SCAMPER Core Method
Use when: iterating on an existing design, feature, or product.
Seven structured provocations that force you to examine an existing solution from multiple angles. Substitute: What component could be replaced? Combine: What could be merged? Adapt: What could be borrowed from another context? Modify: What could be magnified, minimized, or altered? Put to other use: Could this serve a different purpose? Eliminate: What could be removed entirely? Reverse/Rearrange: What if the sequence changed?
Crazy Eights / 6-Up-1-Up Core Method
Use when: you need quick visual explorations of UI solutions. 30–90 min, groups of 2–6.
Fold a sheet into 8 panels (Crazy Eights) or 6 panels (6-Up-1-Up). Set a timer: 8 minutes for Crazy Eights, 6 for 6-Up-1-Up — one idea per panel. The time pressure forces rough, concept-level thinking. Each person then presents 3 of their best (or 1 in 6-Up-1-Up). Everyone gets 2 sticky dots to vote. Discuss, then do another round of rapid sketching incorporating feedback. Five participants generate 40 distinct approaches in under 10 minutes.
Worst Possible Idea Technique
Use when: the team is stuck in conventional thinking or afraid to suggest impractical ideas.
Generate the worst possible solutions to the design problem — the most expensive, confusing, hostile-to-users ideas imaginable. This is psychologically safe (you can't fail at being bad), breaks anchoring on "reasonable" solutions, and many terrible ideas contain the seed of a good one when inverted. "Force a 50-field form" inverted becomes "collect information progressively over time."
Analogous Inspiration Technique
Use when: you need breakthrough ideas beyond incremental improvements.
Look at how completely different domains solve similar underlying problems. Designing a queuing system? Study how theme parks manage wait times. Designing onboarding? Study how video games teach complex mechanics. Designing a dashboard? Study aircraft cockpits. The analogy doesn't need to be perfect — the value is in the cognitive shift from seeing your problem through a different lens.
Constraint-Based Design Technique
Use when: unlimited freedom is producing bland, unfocused solutions.
Add artificial constraints to force novel solutions. "What if we had no images?" — forces focus on typography and copy. "What if the entire flow fit on one screen?" — forces ruthless prioritization. "What if the user only had 10 seconds?" — strips away everything non-essential. "What if this had to be accessible to a screen reader?" — reveals structure and hierarchy issues. Constraints aren't limitations — they're creative catalysts.
Ideation frameworks NN/g
These are structured multi-step processes that orchestrate individual techniques into a complete ideation session.
Design Charrettes Framework
Use when: accelerating idea evolution through iterative critique cycles. 1–3 hours, groups of 2–6.
Each individual generates ideas on their own. In a group, each person presents some of their ideas. The group asks questions, makes suggestions, and critiques. Individuals refine their ideas. Repeat steps 2–3, usually 2–3 times. The tight loop between solo ideation and group critique produces rapid idea evolution — each cycle sharpens and combines the best elements.
Parallel Design Core Method
Use when: you want the benefits of group ideation without the pitfalls. 1–2 hours, 2+ people.
Each individual or pair works on designing a solution to the problem separately for 10–30 minutes. Then the group regroups to discuss ideas, compare approaches, and synthesize. Finally, generate new ideas as a group, building on the best elements. Parallel Design avoids groupthink and anchoring (everyone starts independently) while preserving the benefits of multiple viewpoints. Combining with Design to the Persona (each person takes a different persona) is particularly effective.
Design Studio Core Method
Use when: you want collaborative ideation with critique built in.
Round 1: everyone sketches individually (5 minutes). Round 2: each person presents sketches to the group (2 minutes each) with structured critique ("I like… I wish… What if…"). Round 3: everyone sketches again, incorporating feedback. Optional Round 4: pairs merge best ideas into combined sketches. The critique rounds prevent the brainstorming problem of generating ideas that never get evaluated. The iterative sketching builds on collective intelligence.
Lightning Design Jam (LDJ) Framework
Use when: the team needs to focus on one problem and avoid competitive dynamics. 30–90 min, groups of 2–6.
A tightly timed sequence: (1) silently write challenges from the week (7 min), (2) present problems to group (4 min each), (3) vote on highest-priority challenge with 2 dots (6 min), (4) reframe as "How might we…" (6 min), (5) silently generate solutions (7 min), (6) vote on solutions with 6 dots (10 min), (7) prioritize by dot count (30 sec), (8) decide on impact vs. effort (10 min), (9) generate actionable tasks (5 min). The silence and voting structure eliminate dominant-voice problems.
Google Design Sprint (Ideation Phase) Framework
Use when: you need a complete ideation-to-validation cycle in one week. Groups of 2–6.
The five-day sprint: Understand (define and explain the problem), Sketch (ideate), Decide (discuss, vote, select what to prototype), Prototype (build), Validate (test with users). The sprint compresses the entire diverge-converge-test cycle into a single focused week. Ideation techniques from this topic slot into the Sketch day.
Managing group dynamics NN/g
Two-thirds of UX professionals believe group ideation produces better ideas than solo work. But group ideation introduces specific problems that must be actively managed.
Six group ideation problems
Groupthink: everyone starts to conform, producing homogeneous ideas. Law of Primacy in Persuasion: the group fixates on the first idea presented. Shyness or free riding: some members stay quiet and don't contribute. Blocking: outgoing members talk over others, disrupting information flow. Hierarchy intimidation: everyone agrees with the highest-ranking member. Distractions: multitasking or deadline stress erodes focus and creativity.
- Be aware of the six problems — naming them makes them manageable
- Avoid choosing the first idea; keep evaluation for later
- Clearly establish session rules before starting
- Pull problem teammates aside discreetly to address behavior
- Consider not inviting superiors (or have them contribute silently)
- Take breaks as needed — creativity degrades with fatigue
- Consider banning laptops and smartphones during divergent phases
- Use structured techniques (silent writing before sharing prevents anchoring)
- Use warm-ups to set the creative, psychologically safe tone
- Have a dedicated facilitator who monitors dynamics
Be a better participant: come prepared, consider doing a solo ideation session before group work, and don't be afraid to ask questions about the process and goals.
Post-ideation: convergence and selection NN/g
After divergent ideation, the shift to convergent thinking requires bringing back considerations of business viability and technical feasibility alongside user desirability.
Idea Selection Process (Five Steps) Core Method
Use when: transitioning from a pile of ideas to a shortlist for prototyping.
1. Consolidate similar ideas into clusters. 2. Eliminate ideas that aren't feasible and can't be scaled down, modified, or recycled. 3. Group critique the remaining ideas against the original goals — how well does each support the success criteria? 4. Vote if needed to decide between remaining options (dot voting, forced ranking, or impact/effort matrix). 5. Assign tasks and plan implementation — who takes what forward, by when.
Forced Ranking Technique
Use when: multiple ideas survive initial filtering and the team needs to prioritize.
Each team member individually ranks candidate ideas by greatest potential impact on the stated goal (1–5, where 5 is highest impact). Add scores across all team members. Highest total wins. The individual ranking step prevents the loudest voice from dominating, and the summation balances diverse perspectives.
Three types of feedback on ideas
Reaction-based ("I love it," "I'm not feeling it") — emotional gut reactions, not useful for decision-making. Direction-based ("Make it more like X," "That should be a button") — starts with a suggestion but lacks reasoning. Critique — identifies a specific aspect and explains whether it meets the objective and why. Only critique is consistently helpful. During convergence, insist on critique-format feedback.
After selection: be transparent about how decisions were made. Communicate with teammates who submitted ideas but weren't on the selection team. Treat ideas from group sessions as collective products — don't assign credit to individuals ("Great idea, Mike!"), credit the group ("Thanks to the whole team").
Conduct a retrospective on the ideation process itself: What worked? What didn't? How can the approach be modified? What problem did we encounter that a different technique could solve?
Choosing the right technique NN/g
Good for warm-ups: Telephone, Paper Airplane, Opposite Day, Mission Impossible, Toddler, Abstraction, Laddering, Modeling, Bodystorming
Good for solo ideation: Opposite Day, Mission Impossible, Toddler, Abstraction, Laddering, Modeling, Design Idea Cards, Trend Projection, Design to the Persona, Edge Cases
Good for remote: Opposite Day, Mission Impossible, Toddler, Abstraction, Laddering, Modeling, Ask an Outsider, Trend Projection, Design to the Persona, Edge Cases, Systematic Prediction, Design Charrettes, Crazy Eights
Good for when you're stuck: Opposite Day, Toddler, Abstraction, Ask an Outsider, Design Idea Cards
Real-world examples
Case study
IDEO: Deep Dive methodology
IDEO's "Deep Dive" process — documented in an ABC Nightline segment redesigning a shopping cart — demonstrates structured creativity at scale. The team conducted rapid field research, followed by structured brainstorming with strict rules (defer judgment, encourage wild ideas, build on others', stay focused, one conversation at a time, be visual, go for quantity). They voted, prototyped top concepts in hours, and tested with users the same day.
Why it works: The combination of real-world observation, structured ideation rules, rapid prototyping, and same-day testing creates a feedback loop that generates and validates ideas faster than any single method alone.
Case study
Constraint-driven innovation at Twitter
Twitter's original 140-character limit — imposed by SMS technical constraints — became the product's defining creative feature. The constraint forced concision, spawned new communication patterns (threads, hashtags, @mentions), and differentiated Twitter from every other platform. When the limit was relaxed to 280 characters, average tweet length barely changed — users had internalized the creative value of brevity.
Why it matters: Constraints aren't always obstacles — they can be the foundation of novel, distinctive experiences that wouldn't emerge from unconstrained design.
Case study
Abstraction in practice: NASA solar arrays
NASA needed to send large flat solar arrays to space, but rockets must be narrow. Abstracting the problem — "contain wide, flat material in a confined space of a different shape" — led engineers to the domain of origami. The result: origami-inspired folding solar panels that pack compactly and deploy in orbit. The cross-domain insight came not from aerospace expertise but from reframing the physical constraint at a higher level of abstraction.
Why it matters: The Abstraction technique's power lies in detaching the problem from its domain, making it legible to solutions from entirely unrelated fields.
Case study
OXO Good Grips: deprivation-driven design
OXO's founder watched his wife struggle with a vegetable peeler due to arthritis. Rather than designing "an arthritis product," the team used deprivation simulation — experiencing kitchen tasks with impaired grip — to redesign handles from first principles. The resulting Good Grips line became a mainstream bestseller, because ergonomic grips that solve for arthritis also feel better to everyone.
Why it matters: Designing for extreme users (via Deprivation Studies and Edge Cases) often produces solutions with universal appeal — the curb-cut effect applied to product design.
Case study
Persona + Parallel Design: artisan.ly marketplace
A design team used Parallel Design combined with Design to the Persona for an Etsy-like handmade goods marketplace. One group designed a personalized dashboard for Maria (buyer persona: bakery owner wanting decorative items, overwhelmed by choice), another for Caleb (seller persona: student leatherworker managing orders). When the groups reconvened, comparing the persona-specific solutions revealed shared needs (order status visibility) and conflicts (buyers want browsing; sellers want order management) that informed a modular dashboard architecture.
Why it matters: Combining Parallel Design with personas prevents "design for everyone" blandness and surfaces genuine user-to-user tensions that a single-persona approach would miss.
Common pitfalls
Brainstorming without structure
An unstructured session dominated by the loudest voices produces fewer, less diverse ideas than any structured method. If you're bringing people together for ideation, use a method — any method is better than "let's just throw out ideas."
Generating ideas without a defined problem
"Let's brainstorm ideas for the new feature" is too vague. "How might we reduce first-time user drop-off during onboarding?" gives the team something to push against. The quality of ideation output is directly proportional to the quality of the problem statement.
Falling in love with ideas too early
The point of creative methods is to generate many options. If the team commits to the first good idea, the rest of the session is wasted. Defer commitment until you've explored widely. Dot-voting and structured evaluation after ideation prevent premature attachment.
Skipping ideation entirely
Jumping straight from problem definition to prototyping narrows the solution space to whatever first comes to mind. Even 30 minutes of structured ideation before prototyping dramatically increases the diversity and quality of explored solutions. The 87% correlation between pre-prototyping ideation and effectiveness is not coincidental.
Ignoring group dynamics problems
Groupthink, hierarchy intimidation, and blocking don't fix themselves. A facilitator who doesn't actively manage dynamics will get the same mediocre results as unstructured brainstorming — just with more steps. Name the problems, use silent-first techniques, and address dominant participants discreetly.
Never moving past divergence
Some teams generate ideas endlessly but never converge. Without a structured convergence process (consolidate, eliminate, critique, vote, assign), ideation output rots in a Miro board. The post-ideation steps — selection, critique, task assignment, and retrospective — are as important as the idea generation itself.