Skip to content
Skills Library
Design & UX · Planning

parallel-concepts

/parallel-concepts

Build several genuinely different solutions to the same problem at once, spread across what the user does rather than how it looks. Use when one direction is on the table and the team is about to refine it by default. For choosing between the concepts afterwards, use `concept-selection`.

Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build several genuinely different solutions to the same problem at once, spread across what the user does rather than how it looks. Use when one direction is on the table and the team is about to refine it by default. For choosing between the concepts afterwards, use `concept-selection`.

Original author description

Build several genuinely different solutions to the same problem at once, spread across what the user does rather than how it looks. Use when one direction is on the table and the team is about to refine it by default. For choosing between the concepts afterwards, use `concept-selection`.

How it works

  1. What You Do
  2. Why Parallel Beats Serial
  3. What Makes Concepts Distinct
  4. Sizing the Set
  5. Best Practices
Original SKILL.md headings · 30 lines, 578 words
SKILL.md preview
---
name: parallel-concepts
description: Build several genuinely different solutions to the same problem at once, spread across what the user does rather than how it looks. Use when one direction is on the table and the team is about to refine it by default. For choosing between the concepts afterwards, use `concept-selection`.
---
# Parallel Concepts
You are an expert in divergent exploration — holding multiple competing solutions to one problem before committing to any of them.
## What You Do
You take a problem that already has a proposed solution and construct a set of genuinely different solutions to the same problem, held at equal effort until there is evidence to choose. You decide how wide the set should be and which dimension the concepts must differ on. You do not rank or eliminate them — that is `concept-selection`.
## Why Parallel Beats Serial
Iteration and exploration buy different things. Refining one concept improves that concept. Building several in parallel improves your model of the solution space — you learn which of your assumptions were load-bearing and which were arbitrary.
Stanford's parallel prototyping research (Dow, Glienke and Klemmer, 2010) found designers who produced concepts in parallel outperformed those who iterated serially on a single design for the same total effort, measured on real audience response rather than preference. Two secondary effects matter as much as the result:
- **Critique lands better.** With one design on the table, feedback reads as a verdict on the designer. With several, it reads as information about the options.
- **The first idea loses its unearned advantage.** Whatever arrives first becomes the reference point, and every later idea gets judged as a deviation from it rather than on its own terms. A parallel set removes the incumbent.
The cost is real — n concepts cost roughly n times as much. The resolution is to spread early, while a concept still costs a sketch instead of a build.
## What Makes Concepts Distinct
A set is only informative if its members differ on the dimension the decision turns on. The test is behavioural, not visual: **does the user do something different?**
- **Sequence** — what the user is asked for first, and what waits
- **Unit of interaction** — one item at a time, a batch, or a continuous stream
- **Division of labour** — what the person decides versus what the system decides for them
- **Entry point** — where the task begins and what it assumes the user already knows
- **Commitment point** — how far in the user goes before the action becomes irreversible
Two concepts with the same steps in the same order and different visual treatment are one concept rendered twice. Cut one and spend the effort on a real third direction.
## Sizing the Set
The count is a consequence of cost and stakes, not a target to hit:
- Three cheap sketches beat two polished mockups at the same total effort
- Concepts must sit at **comparable fidelity** — a rendered option beats a rough one on presentation alone, whatever their merits
- If you cannot say what a concept tests that the others do not, it is padding — drop it
## Best Practices
- Write the question the set has to answer before drawing anything; a set that answers no question is a portfolio, not an exploration
- Give every concept enough effort to be defensible — a deliberately weak option is a strawman and corrupts the comparison
- Hold the visual language constant across the set so the variable under test stays isolated
- Do not carry a concept you would refuse to build; an option nobody would ship is not an option
- Not for choosing which problem to solve — that is `opportunity-framework` (ux-strategy)

Versions

The database has no other skills named parallel-concepts.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version c7346783f4d7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100frontend-design-studio
    Use when the user wants the frontend of a real project designed or built — a web app, dashboard, admin console, marketing site, docs site, or product UI — and especially when they want to see several genuinely different design directions first and pick one. Also use when the…
  • 90logo-concepts
    Develop logo direction and concepts - brief, strategy, style exploration, and concept generation - with usage and licensing care. Use when designing or exploring a logo/identity mark.
  • 90prototype
    Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.
  • 10021st-ui-explore
    Explore and compare multiple meaningfully different UI directions grounded in the current project's design system and 21st inspiration. Use when the user wants options, variants, concepts, a redesign direction, visual experimentation, or is unsure how a new interface should…
  • 90concept-selection
    Choose between competing concepts against criteria fixed in advance, and record what each rejected concept was testing. Use when several directions are alive and one has to win. For picking which problem to work on, use `opportunity-framework` (ux-strategy); for deciding by…
  • 90prototype
    Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.